https://bugs.kde.org/show_bug.cgi?id=482378

            Bug ID: 482378
           Summary: recorder docker works perfectly except for no
                    auto-start (have box checked)
    Classification: Applications
           Product: krita
           Version: nightly build (please specify the git hash!)
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Dockers/Recorder
          Assignee: krita-bugs-n...@kde.org
          Reporter: pinkskyatni...@posteo.org
  Target Milestone: ---

SUMMARY
***
Hello, running Sunday's krita-5.3.0-prealpha-de10297103-x86_64.appimage and
it's awesome except for the issue of recorder not auto-starting, even though
have it set to auto-start. Have managed to forget to record every single time
for 2 days, lol, but was testing brushes etc so no work recordings lost. Was
previously running krita-5.2.0-prealpha-e41db7b620-x86_64.appimage and no
issues.
***


STEPS TO REPRODUCE
1. Open Krita.
2. Start new or open already active canvas.
3. Check recorder docker and see that it hasn't automatically started
recording. 

OBSERVED RESULT
Recorder docker not running/needs to be manually started. 

EXPECTED RESULT
Docker is set to auto-start, and usually does that perfectly.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: MX Linux 21 xfce, running Mate 1.24.1, kernel 5.10, x11, mesa
20.3.5
amd ryzen7, radeo rx5700xt, 32 ram

Qt Version: 5

ADDITIONAL INFORMATION
Wasn't sure if other autostart plugin (oughtasave) may be clashing with
recorder, but testing removing it didn't fix things. Not running many plugins
otherwise ... old reference docker, kanvasbuddy, Krita UI redesign, scratchpad,
shortcut composer, brushes fixer special. Also trying out reference tabs docker
+ have toolkit installed although may remove latter. 
Have added recorder button to Kanvasbuddy; not sure if that would affect the
recorder docker though, as otherwise record/export works great using the open
mp4 codec.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to