https://bugs.kde.org/show_bug.cgi?id=478806
Bug ID: 478806
Summary: Plasmashell Coredump After Kscreenlock_greet[er] Fails
To Display And Screen Remains Black
Classification: Plasma
Product: plasmashell
Version: 5.27.10
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: nroycea+...@gmail.com
Target Milestone: 1.0
SUMMARY
When the screen *BEGINS* the transition to lockscreen (idle), and I move my
mouse to stop the transition, the screen remained black with only the mouse
cursor showing/moving.
Switching ttys, I tried to restart the plasmashell service (not sure that could
be done from another tty), and it crashed.
I used "loginctl" to lock all sessions and unlock that GUI one, where I could
switch back to it, only to find plasmashell was still dead.
With "konsole" still up, I again tried to restart plasmashell, but the same
coredump was happening.
I manually started plasmashell, circumventing the service, and it came back.
Even with it being back, I STILL could not restart the plasmashell service
without it coredumping.
I'm currently still live on this system (no reboot yet) in case other testing
would like to be done while in this state.
STEPS TO REPRODUCE
1. Wait for screen lock to *start*, and move mouse to avoid it the moment the
screen goes black (starting to lock).
2. Notice screen remains black and no unlocker is presented. Only the mouse
cursor is displayed.
3. Switch tty and try to restart plasmashell service. //Fails
4. $ loginctl lock-sessions; loginctl list-sessions; loginctl unlock-session
<#>
5. Switch back to GUI and notice plasmashell is still dead.
6. Try to restart plasmashell service in konsole and notice it coredumps again.
7. $ plasmashell --replace & //"--replace" not needed if "$ ps" doesn't show it
running.
8. Notice plasmashell is now running after having started it manually from
konsole.
OBSERVED RESULT
Crash
EXPECTED RESULT
Don't crash
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
Dump:
*****
Message: Process 698869 (plasmashell) of user 1000 dumped core.
Stack trace of thread 698869:
#0 0x00007f3817b6283c n/a (libc.so.6 + 0x8e83c)
#1 0x00007f3817b12668 raise (libc.so.6 + 0x3e668)
#2 0x00007f3817afa4b8 abort (libc.so.6 + 0x264b8)
#3 0x00007f3817fd10c2 _ZNK14QMessageLogger5fatalEPKcz
(libQt5Core.so.5 + 0xa00c2)
#4 0x00007f38185a8402
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 +
0x13f402)
#5 0x00007f38185a8a99
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 +
0x13fa99)
#6 0x00007f38181ccc05 _ZN23QCoreApplicationPrivate4initEv
(libQt5Core.so.5 + 0x29bc05)
#7 0x00007f38185a8b46 _ZN22QGuiApplicationPrivate4initEv
(libQt5Gui.so.5 + 0x13fb46)
#8 0x00007f3818e4bb9e _ZN19QApplicationPrivate4initEv
(libQt5Widgets.so.5 + 0x175b9e)
#9 0x0000556f3e29f3c6 n/a (plasmashell + 0x213c6)
#10 0x00007f3817afbcd0 n/a (libc.so.6 + 0x27cd0)
#11 0x00007f3817afbd8a __libc_start_main (libc.so.6 + 0x27d8a)
#12 0x0000556f3e2a2515 n/a (plasmashell + 0x24515)
Stack trace of thread 698870:
#0 0x00007f3817bd6f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f3816c872b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f3816c27162 g_main_context_iteration
(libglib-2.0.so.0 + 0x58162)
#3 0x00007f381821bf7c
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x2eaf7c)
#4 0x00007f38181cbe74
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x29ae74)
#5 0x00007f38180284f6 _ZN7QThread4execEv (libQt5Core.so.5 +
0xf74f6)
#6 0x00007f3818b07a9a n/a (libQt5DBus.so.5 + 0x18a9a)
#7 0x00007f381802471a n/a (libQt5Core.so.5 + 0xf371a)
#8 0x00007f3817b609eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007f3817be47cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64
*****
--
You are receiving this mail because:
You are watching all bug changes.
