Created attachment 167269 [details] journal entries from plasma panel crash in X11 SUMMARY If I connect a secondary monitor and have it arranged to the left of the primary screen, icons on the left side of the plasma panel become unresponsive to mouse clicks. Icons on the right side of the panel seem to work fine, and pressing the Meta key brings up the application launcher just fine. I have been able to reproduce this both in VirtualBox and on real hardware. This bug only happens if I am already logged into a Wayland session before connecting the second screen. If the second screen is connected prior to logging in, then the plasma panel functions just fine. Here is a video demonstrating the issue in VirtualBox: https://youtu.be/jGWVN3tkZr4 If I connect the secondary screen while logged into an X11 session, plasma appears to crash (black screen, panel and desktop widgets eventually reload), but once everything is back up, the panel responds as normal to mouse clicks. I have attached the system journal entries pertaining to this event, though I don't know how useful they are. No crash reporter was offered. STEPS TO REPRODUCE 1. In a Wayland session, connect a secondary screen and configure it to appear to the left of the primary screen. 2. Disconnect the screen and restart the computer. 3. Log into a Plasma Wayland session. 4. Connect the secondary screen. OBSERVED RESULT Icons on the left side of the panel are unresponsive to mouse clicks or hover actions until the secondary monitor is disconnected. EXPECTED RESULT The icons should respond as normal. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2
What GPU hardware are you using?
(In reply to Nate Graham from comment #1) > What GPU hardware are you using? It is an old AMD APU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver)
Sounds a bit like Bug 483188. Does it start working if you restart plasmashell or maximize and de-maximize a window?
(In reply to Nate Graham from comment #3) > Sounds a bit like Bug 483188. Does it start working if you restart > plasmashell or maximize and de-maximize a window? Neither of these steps work. The command to restart plasmashell (systemctl --user restart plasma-plasmashell) does nothing. The panel just sits there, frozen until I unplug the secondary monitor. Also, while I mentioned that my affected laptop has an AMD GPU, I can reproduce this bug in VirtualBox on a different system with an NVIDIA graphics card (though obviously the NVIDIA driver is not running inside the virtual machine). See the video linked in my original report.
Just now after testing your last steps, I unplugged the secondary monitor, and only some parts of the panel became responsive again to clicks. The panel itself isn't dead, though... I can still hit the Meta key to bring up the menu. It's just dead to mouse clicks throughout some areas of the panel. Again, this bug only happens when the secondary monitor is configured *to the left* of primary.
I'm having exactly the same issue ever since the first KDE 6 beta. I'm using a AMD 6900 XT and the panel also only becomes unresponsive when the secondary monitor is on the left of the primary. It also behaves really strangely. If I turn the monitor on, the left side of the panel and the panel itself become unresponsive. If I turn the monitor off again, the right side of the panel and the panel itself become unresponsive. The only way to properly revive the panel is by putting the monitor somewhere else in the display settings and back again, at which point everything works normally.
I'm not able to reproduce this with my laptop and an external HP screen arranged to the left of the primary screen. I do have an Intel GPU though. Affected people, are you able to reproduce the issue in a new clean user account, by doing *exactly* the following: 1. Plug in screen 2. Ignore screen chooser OSD 3. Right-click on desktop > Configure Displays… 4. Move newly-connected screen to the left of the primary screen and click apply If not, please try by replacing steps 2-5 with "click on 'extend to left' in the screen chooser OSD" Either way, we need to know if it reproduces at all in a new clean user account. Thanks all!
(In reply to Nate Graham from comment #7) > Either way, we need to know if it reproduces at all in a new clean user > account. Thanks all! When I try these steps in a new user account with no changes to the UI from default, the following happens: 1. Plug in the monitor and configure to the left of primary screen: the panel works fine. 2. Unplug the monitor: the right side of the panel becomes unresponsive. 3. Reboot & log in again. Panel will again be responsive. 4. Plug in the monitor (which will remember its configuration to the left of primary): panel is unresponsive. 5. Unplug the monitor: all but the leftmost bit of the panel remains unresponsive. I haven't tried this yet with VirtualBox, but here is the system info from the laptop on which I reproduced the above: OS: KDE Neon 6.0 User Edition (Plasma Desktop 6.0.3, KDE Frameworks 6.0.0, Qt 6.7.0) Linux Kernel: 6.5.0-27-lowlatency (64-bit) PC: HP Pavilion m6-1035dx laptop CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable Screen #1 (LVDS-1, screen 0): - Resolution: 1366 x 768 @ 60 Hz Screen #2 (HDMI-A-1, screen 1): - Monitor: Dell P170Sb 17" LCD Monitor - Resolution: 1280 x 1024 @ 75 Hz
I took a video reproducing steps 4 and 5 above on my laptop (after the reboot): https://youtu.be/Ew2JgrpOG7I
It seems like this issue was fixed at some point. I'm running Fedora 40 and things work fine here now with the latest update. Also works fine on KDE neon unstable.
Glad to hear it. S. Christian Collins, is that your experience too?
(In reply to Nate Graham from comment #11) > Glad to hear it. S. Christian Collins, is that your experience too? Yes, this does appear to be fixed now! Hooray!
Great news!