Bug 503428

Summary: Switch Display menu (Meta+P) does not appear / crashes
Product: [KDE Neon] neon Reporter: Robbe <robbe.profiles>
Component: Packages User EditionAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: john.kizer, jr, neon-bugs
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Robbe 2025-04-27 10:32:44 UTC
SUMMARY
The Meta+P shortcut is used by KDE for the "Switch Display" menu (according to the Shortcuts system settings).
The menu allows for disabling monitors, mirroring or extending.
After an update to the currently (27/04/25) most recent packages, it stopped appearing.

STEPS TO REPRODUCE
1. Update packages using `pkcon update`
2. Press `meta+P`

OBSERVED RESULT
"Switch Display" menu does not appear.

journalctl --user -xe:
```
Apr 27 12:05:25 <REDACTED> systemd[3393]: app-org.kde.kscreen@<CHANGES EACH CALL>.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 12:05:25 Bumblebee-Linux systemd[3393]: app-org.kde.kscreen@<CHANGES EACH CALL>.service: Failed with result 'exit-code'.
```

journal entry appears each time meta+P is pressed

EXPECTED RESULT
The Switch Display menu appears

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 6.3
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION
Was both tested on main system (which was originally KDE Neon based on Ubuntu 22.04 and upgraded using the tool) and on a "clean VM".
This VM was created using the then (1-2 months ago) most recent image and last updated around a month ago.
Using Meta + P in the VM resulted in the menu popping up (even without external displays), but after updating using `sudo pkcon update` the menu no longer appeared.

I have also attempted to rebind the shortcut, but this also does not work.

`kscreen-doctor -o` finds both monitors (on my main system)
Comment 1 John Kizer 2025-04-28 05:20:13 UTC
Hi - merging this in with the existing bug report for this issue. Thanks!

*** This bug has been marked as a duplicate of bug 502486 ***