Bug 520259 - Attempting to add a new application on the Keyboard >> Shortcuts screen triggers a kwin crash
Summary: Attempting to add a new application on the Keyboard >> Shortcuts screen trigg...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.6.90
Platform: KDE Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-05-16 16:45 UTC by pg_tips
Modified: 2026-05-22 19:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.8.0
Sentry Crash Report:


Attachments
Journal entry with stack trace (20.18 KB, text/plain)
2026-05-16 16:45 UTC, pg_tips
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pg_tips 2026-05-16 16:45:54 UTC
Created attachment 192363 [details]
Journal entry with stack trace

Attempting to add a new application on the Keyboard >> Shortcuts screen triggers a kwin crash

DESCRIPTION
Attempting to add a new application on the Keyboard >> Shortcuts screen triggers a kwin crash

STEPS TO REPRODUCE
1. In System Settings, go to the Keyboard >> Shortcuts screen
2. Click the "Add New" button at the top right
3. Choose any application to add

OBSERVED RESULT
The screen briefly goes black, then reappears with a Kwin crash report. The application is not succesfully added to the keyboard shortcuts - instead at the top of the Shortcuts screen there's an error banner reading "Error while communicating with the global shortcuts service".

EXPECTED RESULT
The selected application should be added and made available to add shortcuts to, without any crash.

SOFTWARE/OS VERSIONS
Operating System: KDE Linux 2026-05-16 image
KDE Plasma Version: 6.6.90
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.0

ADDITIONAL INFORMATION
Nvidia GPU (RTX 3060 Ti) using open-kernel driver 595.71.05.
I haven't seen any kwin crashes on this system other than when performing this specific sequence of events.

Attempting to download debug symbols in the crash report window failed, so there's a lot of ??? in the stack trace, but I'm attaching what I could recover from the journal.
Comment 1 TraceyC 2026-05-18 15:24:54 UTC
Thank you for the bug report. I'm not able to reproduce this on git-master. Unfortunately the backtrace is incomplete, as you mentioned. We do need the missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

#6  0x00007f9de3fc84c2 n/a (libKGlobalAccelD.so.0 + 0x264c2)
#10 0x00007f9de2be1f89 n/a (libQt6DBus.so.6 + 0x44f89)
#22 0x0000557828148763 n/a (/bin/kwin_wayland + 0x3f763)


Could you please install debug packages and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Comment 2 matthew.prakhov@gmail.com 2026-05-20 17:02:45 UTC
As a temporary workaround I just manually write all the apps and the shortcuts inside of ~/.config/kglobalshortcutsrc
Comment 3 pg_tips 2026-05-22 18:17:31 UTC
This is fixed in Plasma 6.8 dev version, which has now reached KDE Linux. I assume as far as 6.7 is concerned, it's a matter of backporting the right fix.

@TraceyC unfortunately I'm still struggling to get a proper stack trace. Is this still useful? (e.g. to pinpoint which code change needs to be backported) If so then I'll persevere :)
Comment 4 TraceyC 2026-05-22 19:24:42 UTC
(In reply to pg_tips from comment #3)
> This is fixed in Plasma 6.8 dev version, which has now reached KDE Linux. I
> assume as far as 6.7 is concerned, it's a matter of backporting the right
> fix.
> 
> @TraceyC unfortunately I'm still struggling to get a proper stack trace. Is
> this still useful? (e.g. to pinpoint which code change needs to be
> backported) If so then I'll persevere :)

No need to struggle! If the bug has been fixed, that's the important thing. I'll close this out, since you've verified the fix.