Bug 461594

Summary: Plasma shell crashes when trying to use Open GL rendering backend
Product: [Plasma] plasmashell Reporter: ivan.pepelko
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kde, nate
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.26.2   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description ivan.pepelko 2022-11-08 15:29:38 UTC 
Application: plasmashell (5.26.2)

Qt Version: 5.15.7
Frameworks Version: 5.99.0
Operating System: Linux 6.0.7-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.26.2 [KCrashBackend]

-- Information about the crash:
I have another issue, where on every boot, taskbar notification 'Software renerer in use' is shown.
When rendering backend is not set to OpenGL, there is no crash, but the notification persists on every boot.
Setting explicitly to OpenGL crashes plasma shell on login and then it restarts with software renderer.

The laptop is (should be) using discrete GPU.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007f8bdcd7eaf4 in QOpenGLContext::isValid() const () from /usr/lib/libQt5Gui.so.5
#5  0x00007f8bde3d5bc8 in ?? () from /usr/lib/libQt5Quick.so.5
#6  0x00007f8bde3db395 in ?? () from /usr/lib/libQt5Quick.so.5
#7  0x00007f8bdcd55c77 in QWindow::event(QEvent*) () from /usr/lib/libQt5Gui.so.5
#8  0x00007f8bdd578b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#9  0x00007f8bdc88cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#10 0x00007f8bdcd499f4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/libQt5Gui.so.5
#11 0x00007f8bdcd28985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#12 0x00007f8bd752f710 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#13 0x00007f8bdad1687b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x00007f8bdad6d279 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x00007f8bdad15132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#16 0x00007f8bdc8d7c4c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#17 0x00007f8bdc88573c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#18 0x00007f8bdc890269 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#19 0x000056488c11f10f in ?? ()
#20 0x00007f8bdc03c290 in ?? () from /usr/lib/libc.so.6
#21 0x00007f8bdc03c34a in __libc_start_main () from /usr/lib/libc.so.6
#22 0x000056488c11f4c5 in ?? ()
[Inferior 1 (process 1219) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2022-11-08 17:46:24 UTC 
No KDE code is implicated in what I can see from the backtrace, and the backtrace has no debug symbols for anything that would help. :(

If this crash is reproducible, could you please install debug symbols for Qt, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Also, what GPU and GPU drivers are you using?

Thanks!
Comment 2 Bug Janitor Service 2022-11-23 05:16:13 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 3 Bug Janitor Service 2022-12-08 05:15:44 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!