I’ve been attempting to capture a screenshot of krita-5.2.6-2.fc41’s loading window, but when I can catch it, see the undermentioned instead:
Is anyone able to reproduce this, and explain to me what the first one means?
krita-5.2.6-2.fc41.x86_64
Name : spectacle Epoch : 1 Version : 6.3.2.1 Release : 1.fc41 Architecture : x86_64 Installed size : 6.1 MiB Source : spectacle-6.3.2.1-1.fc41.src.rpm From repository : @stored_transaction
@skyfishgoo, the Krita image differs for me, but yes – thank you.
Though, I utilised merely Meta + Print Screen, instead:
I wonder whether that matters.
This also appears if I attempt to use the GUI’s “Active window” mode on plasmashell’s desktop:/:
An error occurred while taking a screenshot.
KWin screenshot request failed:
Invalid window requested
Potentially relevant information:
- Method:
CaptureActiveWindow- Method specific arguments:
QMap(("include-decoration", QVariant(bool, true))("include-shadow", QVariant(bool, false))("native-resolution", QVariant(bool, true)))
…but doesn’t reproduce if I use the key bind for it!
It’s just a bug in Spectacle, I suppose.
Reported at bugs.kde.org/show_bug.cgi?id=501593.
@UncleSpellbinder, what do you have that mapped to? From your screenshot, you appear to be using the default mapping [1] – “Full Screen” – which indeed acts correctly. This solely affects “Active Window” mode. [2]
If you’re to attempt to reproduce, I implore you to evaluate whether you’re able to capture plasmashell’s desktop:/ via the initial GUI’s “Active Window” button:
…because this method is easier.
Ahhhh. I see. Well, as far as loading screens, they really aren’t “windows”. So technically, there’s nothing to capture. It gives the same error message if trying to capture GIMP’s loading screen, Krita loading screen, and Audacity loading screen when using “Active Window” mode.
@UncleSpellbinder, thanks for that! There must be something special about them, although they’re definitely windows:
Perhaps they’re analogous to context menus, which are also technically windows (to KWin) but can’t be focussed, unlike these loading windows, which can.
If I could get one to hang, perhaps its window properties would reveal something noteworthy. I’m not fast enough to send a STOP via System Monitor.
@UncleSpellbinder, you don’t see the window decorations because you’re running them without noborderrule=2 in your .kwinrules, and/or they’re not running under XWayland. …However, they are, so it’s the former. [1]
What you’re seeing are just CSDs.
