Bug 410211 - plasmashell segmentation fault in ScreenPool::ScreenPool() when Plasma on X autologin froze on the splash screen in Fedora Rawhide
Summary: plasmashell segmentation fault in ScreenPool::ScreenPool() when Plasma on X a...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.16.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
: 447791 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-07-25 22:49 UTC by Matt Fagnani
Modified: 2024-02-23 00:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Fagnani 2019-07-25 22:49:50 UTC
Application: plasmashell (5.16.2)

Qt Version: 5.12.4
Frameworks Version: 5.59.0
Operating System: Linux 5.3.0-0.rc1.git1.1.fc31.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I booted into the Fedora Rawhide/31 KDE Plasma spin image Fedora-KDE-Live-x86_64-Rawhide-20190724.n.0.iso at
https://koji.fedoraproject.org/koji/buildinfo?buildID=1319740

I ran sudo dnf install x*amd* kwin*way* pla*way*
kwayland-integration-5.16.2-1.fc31.x86_64     
kwin-wayland-5.16.2-1.fc31.x86_64             
plasma-workspace-wayland-5.16.2-2.fc31.x86_64 
xorg-x11-drv-amdgpu-19.0.1-1.fc31.x86_64      
xorg-x11-server-Xwayland-1.20.5-5.fc31.x86_64 

I logged out of Plasma. I switched to VT2 when I ran sudo systemctl restart sddm.
Plasma on X logged in automatically but Plasma froze on the splash screen. I ran sudo systemctl stop sddm in VT2. I ran startplasmacompositor & from VT2. Plasma on Wayland started, but drkonqi showed this segmentation fault in plasmashell. I installed the plasma-workspaces and qt5-qtbase debugging rpms. I haven't seen this crash before when doing similar steps to start Plasma on Wayland.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4a48b7dd00 (LWP 3462))]

Thread 2 (Thread 0x7f4a359f6700 (LWP 3721)):
#0  0x00007f4a466fd79f in poll () from /lib64/libc.so.6
#1  0x00007f4a453102ee in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#2  0x00007f4a45310423 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f4a46c90bd3 in QEventDispatcherGlib::processEvents (this=0x7f4a300018e0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f4a46c3a9db in QEventLoop::exec (this=this@entry=0x7f4a359f5cf0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x00007f4a46a93625 in QThread::exec (this=this@entry=0x7f4a4752a060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x00007f4a474a6f4a in QDBusConnectionManager::run (this=0x7f4a4752a060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#7  0x00007f4a46a94776 in QThreadPrivate::start (arg=0x7f4a4752a060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361
#8  0x00007f4a45ef04e2 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f4a46708333 in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f4a48b7dd00 (LWP 3462)):
[KCrash Handler]
#5  ScreenPool::ScreenPool (this=0x55f81a24adb0, config=..., parent=<optimized out>) at /usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/shell/screenpool.cpp:48
#6  0x000055f8198ba860 in ShellCorona::ShellCorona (this=0x55f81a21ff50, parent=<optimized out>) at /usr/include/qt5/QtCore/qarraydata.h:257
#7  0x000055f8198c7b9f in ShellManager::loadHandlers (this=0x7f4a3000b050) at /usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/shell/shellmanager.cpp:93
#8  0x000055f81988f5a5 in ShellManager::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/x86_64-redhat-linux-gnu/shell/plasmashell_autogen/EWIEGA46WW/moc_shellmanager.cpp:104
#9  0x00007f4a46c66bda in QObject::event (this=0x7f4a3000b050, e=<optimized out>) at kernel/qobject.cpp:1260
#10 0x00007f4a47736af6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007f4a4773fe80 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007f4a46c3bad8 in QCoreApplication::notifyInternal2 (receiver=0x7f4a3000b050, event=0x55f81a1dd8f0) at kernel/qcoreapplication.cpp:1084
#13 0x00007f4a46c3ea7b in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55f81a100b90) at kernel/qcoreapplication.cpp:1821
#14 0x00007f4a46c90e27 in postEventSourceDispatch (s=0x55f81a1d2fc0) at kernel/qeventdispatcher_glib.cpp:276
#15 0x00007f4a4530ffed in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x00007f4a45310380 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#17 0x00007f4a45310423 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007f4a46c90bb5 in QEventDispatcherGlib::processEvents (this=0x55f81a1b1360, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#19 0x00007f4a46c3a9db in QEventLoop::exec (this=this@entry=0x7ffe296ad0d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#20 0x00007f4a46c42706 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#21 0x000055f81988e7e4 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.16.2-2.fc31.x86_64/shell/main.cpp:215
[Inferior 1 (process 3462) detached]

Reported using DrKonqi
Comment 1 David Edmundson 2019-07-25 22:55:40 UTC
> I ran startplasmacompositor & from VT2. 

Please use the login manager.

This crash is because you're running plasmashell in X, which is questionable.
Comment 2 Matt Fagnani 2019-07-26 00:57:09 UTC
David, I was going to log in to Plasma on Wayland from sddm as I usually do, but the Fedora live image is set to autologin to Plasma on X. I had stopped sddm, Plasma, and X before I ran startplasmacompositor. I restarted sddm so that the X amdgpu driver would be used instead of the X modesetting driver since the system has a Radeon R5 GPU.

I think that the plasmashell crash was more likely to have happened when the autologin to Plasma on X got stuck on the splash screen and I stopped sddm than when I ran startplasmacompositor. The trace of the segmentation fault doesn't appear to have any Wayland-specific functions. The Wayland session appear normally. I just didn't see drkonqi until the Wayland session started.. plasmashell and drkonqi aborted after I stopped sddm and before I ran startplasmacompositor the next time I tried to reproduce the crash. The Plasma on X autologin splash screen freeze has happened several times after restarting sddm with two Fedora rawhide live images. The circle stopped spinning after a few seconds, and the desktop didn't appear. I'm sorry about the mixup. Thanks.
Comment 3 Nate Graham 2022-01-12 16:04:45 UTC
*** Bug 447791 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2024-02-22 20:51:06 UTC
Fedora is no longer set up this way; Can we ask you to please check if this is still an issue with Plasma 6.0? Thanks a lot!
Comment 5 Matt Fagnani 2024-02-22 22:55:51 UTC
(In reply to Nate Graham from comment #4)
> Fedora is no longer set up this way; Can we ask you to please check if this
> is still an issue with Plasma 6.0? Thanks a lot!

I'm using Fedora 40 now which dropped official support for Plasma on X. I haven't seen this problem in years.
Comment 6 Nate Graham 2024-02-23 00:38:40 UTC
Ok, thanks. Let's close it. Thanks anyway!