I came from an old KDE installation, so it's not a fresh install.

Could you go to system settings - shortcuts - spectacle, and provide a screenshot of what shortcuts spectacle has assigned? (In particular check Default Shortcuts to see if it has print assigned)

If you run xev, and press the Print key, what do you see printed in the console?

Created attachment 167855 [details]
Shortcuts screenshot

It says Meta+Shift+Print. I'm 99% sure that I haven't set this shortcut.

I'm sorry that it's in Hungarian, but for some reason `LC_ALL=C.UTF-8 systemsettings` doesn't change the individual KCM pages to English (just the main window). I hope that the localisation doesn't change the order and you can match with your setup.

This is what xev reports back for pressing and releasing the print screen button:

KeyPress event, serial 41, synthetic NO, window 0x4400001,
    root 0x1e1, subw 0x0, time 60011851, (1094,485), root:(1097,521),
    state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x4400001,
    root 0x1e1, subw 0x0, time 60011971, (1094,485), root:(1097,521),
    state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

(In reply to Szőts Ákos from comment #3)
> Created attachment 167855 [details]
> Shortcuts screenshot
> 
> It says Meta+Shift+Print. I'm 99% sure that I haven't set this shortcut.
> 
> I'm sorry that it's in Hungarian, but for some reason `LC_ALL=C.UTF-8
> systemsettings` doesn't change the individual KCM pages to English (just the
> main window). I hope that the localisation doesn't change the order and you
> can match with your setup.
> 
> This is what xev reports back for pressing and releasing the print screen
> button:
> 
> KeyPress event, serial 41, synthetic NO, window 0x4400001,
>     root 0x1e1, subw 0x0, time 60011851, (1094,485), root:(1097,521),
>     state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
>     XLookupString gives 0 bytes: 
>     XmbLookupString gives 0 bytes: 
>     XFilterEvent returns: False
> 
> KeyRelease event, serial 41, synthetic NO, window 0x4400001,
>     root 0x1e1, subw 0x0, time 60011971, (1094,485), root:(1097,521),
>     state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES,
>     XLookupString gives 0 bytes: 
>     XFilterEvent returns: False

For "Spectacle", is "Print" selected as the default shortcut? Also, it would be great if you could upload the content of your  `~/.config/kglobalshortcutsrc`.

Just looking at the screenshot, it seems that `Print` is not assigned as a shortcut for anything. So spectacle doesn't launch when you press print. It should be the default shortcut for "Spectacle". Maybe you removed that at some point?

This is the relevant section for Spectacle from the file:

[services][org.kde.spectacle.desktop]
ActiveWindowScreenShot=none
FullScreenScreenShot=none
RectangularRegionScreenShot=none
_launch=Meta+Shift+Print

Apart from it, do you need the full config file?

I remember Print Screen disappeared (or never appeared) during the change of KSnapshot -> Spectacle change. If I recall correctly, during KSnapshot time it wasn't always bound to start that application and I think I never received this functionality.

I can, of course, bind it, but that won't help for the other long-time users who have the same problem and therefore I don't want alter the current debuggable configuration.

Do you have more than one monitor?

Does the window appear if you run 'spectacle -a' or 'spectacle -l' ?

No, I have only one monitor with multiple inputs. Spectacle starts for both kinds of invocation.

> I remember Print Screen disappeared (or never appeared) during the change of KSnapshot -> Spectacle change. If I recall correctly, during KSnapshot time it wasn't always bound to start that application and I think I never received this functionality.

Ahh that was several years ago and if that was indeed the issue we can't do anything about it now..

I have the exact same grievance. After updating to 

Operating System: openSUSE Tumbleweed 20240430
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-1-default (64-bit)

The shortcuts for Spectacle are de-activated. I have to go into settings and set all the shortcuts active again (I'm using the default assigned). The remnants of conflicting shortcuts I manually removed from the config file. It is not clear what triggers the reset of the shortcuts for spectacle as it was doing ok for a while.

Could this be an openSUSE issue?
I haven't experienced this bug with Fedora 38/39/40 nor before with Slackware 14/15/-current.

(In reply to Ricardo J. Barberis from comment #10)
> Could this be an openSUSE issue?
> I haven't experienced this bug with Fedora 38/39/40 nor before with
> Slackware 14/15/-current.

probably not, we don't have anything changing global shortcuts

*** Bug 487397 has been marked as a duplicate of this bug. ***

Can you check if this fixes the issue for you? https://discuss.kde.org/t/spectacles-global-shortcuts-reset-after-reboot/15882

This is the most annoying bug I have experienced with KDE Plasma in a while. I have Spectacle using the default shortcuts (which has a conflicting shortcut for recording a window btw) and the shortcuts get reset every time to nothing. I had 2 Spectacles listed, but that was not the issue. I reverted everything to default and that did not resolve anything either. It appears related to upgrade process, but I have not found which update breaks the shortcuts.

Try removing ~/.local/share/kglobalaccel - I think that fixed the issue for me.

Do you still hit this bug?

(In reply to Vlad Zahorodnii from comment #16)
> Do you still hit this bug?

I have not encountered this anymore. Seems to be fixed indirectly.

A possibly relevant merge request was started @ https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/99

Git commit d62b708c04a0518bf119ed50c0fcc8610361efe0 by Vlad Zahorodnii.
Committed on 05/05/2026 at 09:21.
Pushed by vladz into branch 'master'.

Avoid resetting global shortcut keys without explicit user input

KGlobalAccelD tries to do a noble and a reasonable (at quick glance)
thing such as manage contested global shortcut keys. But KGlobalAccelD
can even do that without user's knowledge. For example, with some
package managers, applications can be uninstalled and installed, there
is a lot of uncertainty.

This change makes KGlobalAccelD to be more conservative so it doesn't
try to reset user configuration without user's input. If the user wants
to re-assign a global shortcut, they will be asked that in system
settings. If a particular shortcut is contested, then KGlobalAccelD will
try to make the best of it and activate an action that was registered
with that shortcut first.

M  +32   -0    autotests/shortcutstest.cpp
M  +11   -16   src/globalshortcut.cpp

https://invent.kde.org/plasma/kglobalacceld/-/commit/d62b708c04a0518bf119ed50c0fcc8610361efe0