Bug 478239

Summary: Plasma crashes in QWaylandClientExtensionPrivate::handleRegistryGlobal() crashes after sleep
Product: [Plasma] plasmashell Reporter: kde-bugs
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: akselmo, kde, kde, nate, notmart
Priority: NOR Keywords: drkonqi
Version: 5.27.9   
Target Milestone: 1.0   
Platform: Kubuntu   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=414834
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kde-bugs 2023-12-08 05:37:58 UTC 
Application: plasmashell (5.27.9)

Qt Version: 5.15.3
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-37-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04.3 LTS
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
After sleep plasma crashes, screen is dark and only cursor is visible. If I connect external monitor after it, plasma "reloads" and appears message tha suggests calling "loginctl unlock-session X" in tty.
Can be reproduced sometimes.
Note, that calling `loginctl unlock-session X` from tty helps even if message is not visible and only cursor is on screen

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x0000000000000000 in  ()
#5  0x00007efda0347a07 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#6  0x00007efda032cb99 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#7  0x00007efda0352a76 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#8  0x00007efda08aee2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
#9  0x00007efda08ab493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
#10 0x00007efda1368b20 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#11 0x00007efda13692c3 in  () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#12 0x00007efda13694bc in wl_display_dispatch_queue_pending () at /lib/x86_64-linux-gnu/libwayland-client.so.0
#13 0x00007efda032c103 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#14 0x00007efd9eef17c8 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007efd9eef4cb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007efd9eef54e3 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007efd9fb6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007efd9eeb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007efd9ef13cc5 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007efd9da7dd3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007efd9dad3258 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007efd9da7b3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007efd9ef130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007efd9eeb875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007efd9eec0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x000055bdcab43a6b in  ()
#27 0x00007efd9e429d90 in __libc_start_call_main (main=main@entry=0x55bdcab42b50, argc=argc@entry=1, argv=argv@entry=0x7ffc92735c18) at ../sysdeps/nptl/libc_start_call_main.h:58
#28 0x00007efd9e429e40 in __libc_start_main_impl (main=0x55bdcab42b50, argc=1, argv=0x7ffc92735c18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc92735c08) at ../csu/libc-start.c:392
#29 0x000055bdcab43b95 in  ()
[Inferior 1 (process 162497) detached]

The reporter indicates this bug may be a duplicate of or related to bug 439712, bug 439834.

Reported using DrKonqi
Comment 1 Nate Graham 2023-12-08 16:14:42 UTC 
Do you have an NVIDIA GPU?
Comment 2 kde-bugs 2023-12-09 07:48:16 UTC 
(In reply to Nate Graham from comment #1)
> Do you have an NVIDIA GPU?

Nope. AMD Ryzen 7 6800H with Radeon Graphics
Comment 3 Marco Martin 2023-12-11 14:42:33 UTC 
Hi, can you try to replicate the problem with debug symbols installed?
see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 4 David Redondo 2023-12-11 14:44:34 UTC 
It reminds me a bit of the crash that https://invent.kde.org/qt/qt/qtwayland/-/commit/4bce11a39578ed43d7efd61e2140704e84386cb9 fixed
Comment 5 Akseli Lahtinen 2024-06-06 13:44:18 UTC 
Setting this NEEDSINFO WAITINGFORINFO since we need backtrace with debug symbols. 

See comment https://bugs.kde.org/show_bug.cgi?id=478239#c3
Comment 6 Bug Janitor Service 2024-06-21 03:47:25 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2024-07-06 03:47:34 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!