SUMMARY *** It does not happen every time, but more than half of the time for me. Note that I might confuse some button or tab namings because I am translating them from German. *** STEPS TO REPRODUCE 1. Open Spectacle (in the terminal to get output there) 2. Choose the Recording tab and click the "Window"-button 3. Choose the "Spectacle"-window to record by clicking it 4. Click finish recording OBSERVED RESULT 1. I get the following output in the terminal: kpipewire_record_logging: VAAPI: Failed to initialize display kpipewire_record_logging: DRM device not found kpipewire_record_logging: VAAPI: Failed to initialize display kpipewire_record_logging: DRM device not found 3. I get the output above again and the second counter hangs at 0 4. Nothing happens, Spectacle is entirely frozen EXPECTED RESULT 1. No error 3. No error, the second counter starts counting and Spectacle starts recording itself 4. The recording gets finished and saved and Spectacle is overall responsive SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 615 Manufacturer: Microsoft Corporation Product Name: Surface Go 2 System Version: 1
Spectacle was able to record its own window 4 out of 4 attempts when freshly launched. After successfully recording itself, it was then 4 for 4 freezing up when trying again to record itself again. So I tried with recording some other apps and got the same results- always successful recording the first time, froze up trying to record a second window. I'm not getting the terminal errors that you are.
Thank you for the bug report, and I'm sorry we weren't able to look into it yet. A lot has changed since it was reported; can I ask you to see if this is still an issue with Plasma 6.5 or later? Thanks a lot!
I just tried to reproduce it again, but everything seems to work fine. So I guess some changes fixed it and we can close this report. Thanks for reminding me :)