Bug 478413

Summary:	Reconnecting a monitor causes the super key shortcut for application launcher to stop working
Product:	[Plasma] plasmashell	Reporter:	Nora <blackcatgames>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	REPORTED ---
Severity:	normal	CC:	nate, niccolo.venerandi
Priority:	NOR	Keywords:	multiscreen, qt6
Version:	master
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nora 2023-12-11 20:49:24 UTC

Disconnect a monitor, Reconnect and find the super key no longer works for the application launcher menu.
I'm not sure at what step it actually breaks if i could get a way to fix the broken super key quickly I could test it. 

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40 (Kionite rawhide) 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.7.0-0.rc4.20231208git5e3f5b81de80.38.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 5600 XT
Mesa: 23.3.0

ADDITIONAL INFORMATION
A little about my monitor setup in case it's related. I have two monitors the left one being the primary one and the right one being just an additional monitor. The right monitor actually holds the panel with the application launcher otherwise it's completely default. The monitor that I'm noticing the bug with is the primary one disconnecting I haven't tested the other one yet.

Comment 1 Nate Graham 2023-12-11 22:30:41 UTC

Cannot reproduce when the panel containing Kickoff is on either the screen that gets unplugged and re-plugged, or the one that doesn't. In both cases, the Super key opens Kickoff after replugging the screen. If it's relevant, my hardware is all Intel (CPU and GPU), no AMD.

Comment 2 Nora 2023-12-12 00:34:37 UTC

I've tried checking the journalctl while doing an unplug/replug to see if it produces anymore useful information. Also I'm not sure if this is a new thing or a different thing, but when the screen locked and I logged back in I no longer had a panel, I got a notification plasma shell has crashed and offered me to send a crash report (I did), the panel eventually appeared again but once again the super key was not working.

Also one more thing to note is when I disconnect the primary monitor I no longer have a panel on my connected monitor. I don't know if that's intended or not.

Dec 11 17:24:01 fedora plasmashell[2225]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78: TypeError: Type error
Dec 11 17:24:09 fedora plasmashell[2225]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78: TypeError: Type error
Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: start-pre operation timed out. Terminating.
Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: Control process exited, code=killed, status=15/TERM
Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: Failed with result 'timeout'.
Dec 11 17:24:09 fedora systemd[1909]: Failed to start drkonqi-coredump-pickup.service - Consume pending crashes using DrKonqi.
Dec 11 17:24:31 fedora plasmashell[2225]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 11 17:24:31 fedora plasmashell[2225]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 11 17:24:37 fedora plasmashell[2225]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:118:5: QML Connections: Detected function "onActivated" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.

Comment 3 Nate Graham 2023-12-12 19:41:22 UTC

The crash may be related, but it should be reported separately. Can you submit a new bug report for that, with a backtrace of the crash included?