https://bugs.kde.org/show_bug.cgi?id=465877
Bug ID: 465877
Summary: After plasma 5.26=>5.27 update, most KDE apps often
crash when monitors enter powersaving mode.
Classification: Plasma
Product: plasmashell
Version: 5.27.0
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Multi-screen support
Assignee: plasma-b...@kde.org
Reporter: mec...@gmail.com
CC: aleix...@kde.org, notm...@gmail.com
Target Milestone: 1.0
Created attachment 156331
--> https://bugs.kde.org/attachment.cgi?id=156331&action=edit
journalctl log
I'm probably reporting this against the wrong component, but who knows, it
looks like a tricky one. Logs indicate that it could be related to the new
multiscreen support. Anyway - ever since upgrading from plasma 5.26 to 5.27.0
on a dual-monitor setup, I have started getting a really strange issue in about
1/3 of cases. It goes like this:
* First, you need to leave the machine idle long enough for the powersaver to
kick in and turn off the monitors
* Then, mouse/keyboard events enable the monitors correctly, but "enter
password" dialog doesn't appear, the lock screen behaves as if it were frozen.
You can still enter the password blindly and press enter, however
* When you do this, you are greeted by a long list of dr konqi reports about
crashed applications. In every single case, the backtrace looks like this:
[KCrash Handler]
#4 0x00007f90efef506d in () at /lib64/libQt5XcbQpa.so.5
#5 0x00007f90efef90ff in () at /lib64/libQt5XcbQpa.so.5
#6 0x00007f90efef8400 in () at /lib64/libQt5XcbQpa.so.5
#7 0x00007f90efed4524 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() at /lib64/libQt5XcbQpa.so.5
#8 0x00007f90efed54b6 in
QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib64/libQt5XcbQpa.so.5
#9 0x00007f90efefb143 in () at /lib64/libQt5XcbQpa.so.5
#10 0x00007f90f7f27a90 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#11 0x00007f90f7f27e48 in () at /lib64/libglib-2.0.so.0
#12 0x00007f90f7f27edc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#13 0x00007f90fbf33c16 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib64/libQt5Core.so.5
#14 0x00007f90fbedac5b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib64/libQt5Core.so.5
#15 0x00007f90fbee2dc6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#16 0x000055d2152ef701 in ()
#17 0x00007f90fb62caf0 in __libc_start_call_main () at /lib64/libc.so.6
#18 0x00007f90fb62cbb9 in __libc_start_main_impl () at /lib64/libc.so.6
#19 0x000055d2152f0065 in ()
[Inferior 1 (process 2930) detached]
Non-KDE apps like firefox survive. What further complicates matters is that
this doesn't seem to happen every time, only about 1/3.
There's a lot of seemingly relevant messages in the systemd journal, I'm
attaching these in a separate file.
OBSERVED RESULT
Many crashes, as described above.
EXPECTED RESULT
No crashes.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.0 (X11)
KDE Plasma Version:
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
