Bug 2223269 - KDE panel regularly freezes when switching monitors after upgrading to Fedora 37, need to kill plasmashell
Summary: KDE panel regularly freezes when switching monitors after upgrading to Fedora...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 37
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-17 07:39 UTC by Basic Six
Modified: 2024-01-15 12:19 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-01-15 12:19:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Basic Six 2023-07-17 07:39:16 UTC
In Fedora 37, KDE now regularly freezes whenever the display configuration is implicitly changed, for example by connecting an external monitor or closing the laptop lid (thereby turning off the second screen). And every couple of days, it even freezes without any display change.

I've used KDE on Fedora for years with multiple monitors, for example on a docking station, often removing the laptop from the docking station disconnecting the additional monitors and back. Although there were bugs, it worked fine most of the time but now, it appears to have become terribly buggy and unreliable on Fedora 37.

Symptoms:
The taskbar freezes, so the clock is stuck and when switching workspaces, the taskbar still shows the windows from the previous workspace. However, everything else seems to work normally, it is possible to use the system as long as you remember which windows you have open and on which workspace (or use Alt+Tab to see a list, that works too). If you're connected to the wrong network or want to change the volume, you're out of luck because those settings are controlled from the KDE taskbar which is frozen.

Workaround:
Either open a terminal from within KDE or hit Ctrl+Alt+F3 to switch to a text tty, log in and enter:
export DISPLAY=:0
Run this command to terminate and restart the frozen KDE panel:
pkill plasmashell ; plasmashell --replace &
(If you've switched to a test tty, hit Ctrl+Alt+F2 or similar to go back to your graphical desktop.)

Symptom:
Another aspect is that, when turning off a monitor, the lock screen is broken. You'd go away for a couple of minutes or lock manually, come back to your laptop and instead of the lock screen with the password prompt and everything, you get a blue screen (not a Windows bluescreen), as if the second monitor that you've disconnected was still there and is now showing the password prompt as if KDE didn't notice that that monitor is gone. (In a multi-monitor setup, KDE will show the password prompt on one screen only and it appears to be the one which happens to have the mouse cursor on it.)

Workaround:
To get back into your KDE session when the lock screen does not show a password prompt after changing monitors, you need to terminate the lock screen manually from a text tty:
1. Switch to a text tty: Ctrl+Alt+F3, log in and run this command once:
export DISPLAY=:0
2. Enter this command to terminate the frozen lock screen:
pkill -9 kscreenlocker
3. Switch back to your graphical desktop: Ctrl+Alt+F2



Reproducible: Always

Steps to Reproduce:
1. Open bug report for Fedora.
2. Wait.
3. Bug report is closed automatically with "CLOSED EOL".
Actual Results:  
It seems like KDE does not notice when a monitor is turned off.

Expected Results:  
You'd think a desktop environment suite as mature and old as KDE would be able to handle multiple monitors even when one of them is turned off without restarting the computer.

I consider using KDE on a multi-monitor workstation a major feature, so I'm setting the severity accordingly.

I've not yet seen relevant log messages when this happens. But I've noticed that the following new log message is filling the system log:

deepin-system-monitor-plugin-popup[3481101]: QDBusArgument: read from a write-only object

It seems to run some kind of infinite loop:
# grep -c 'deepin-system-monitor-plugin-popup' /var/log/messages
171103

I don't know what this is. It's obviously broken, so I want to get rid of it. Don't know if that's related to KDE freezing almost daily now.

Comment 1 Aoife Moloney 2023-11-23 01:47:50 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2024-01-15 12:19:08 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.