Bug 468991

Summary: Crash in ShellCorona::handleScreenOrderChanged() on login in multi-GPU multi-xscreen environment
Product: [Plasma] plasmashell Reporter: Håkon Innerdal <haakon>
Component: ContainmentAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: akselmo, aleixpol, kde, nate, notmart
Priority: NOR Keywords: drkonqi, multiscreen
Version First Reported In: 5.27.4   
Target Milestone: 1.0   
Platform: Compiled Sources   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=454621
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: working xorg conf
xorg.conf that causes crash

Description Håkon Innerdal 2023-04-26 08:59:45 UTC 
Application: plasmashell (5.27.4)
 (Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.105.0
Operating System: Linux 6.2.12-gentoo-dist x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Crash on login every time, 

May be related; added plasmoid "ChatGPT" recently to panel. panel disappeared, chrashes begun after that.

May be related; I'm using 6 monitors over 2 GPU, multiple screens, xorg.conf (Old setup that I have used in KDE, that has other issues,  XScreen 1 never get keyboard focus, nor window decorations, but I use it to direct a browser + terminal for logging output to DISPLAY=:0.1 );

-----------------------------------

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 525.89.02


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 1920 0
    Screen      1  "Screen1" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from data in "/etc/conf.d/gpm"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "BenQ G2410HD"
    HorizSync       24.0 - 83.0
    VertRefresh     50.0 - 76.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "DELL G2410"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce RTX 2060"
    BusID          "PCI:8:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVIDIA GeForce RTX 2060"
    BusID          "PCI:9:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-3"
    Option         "metamodes" "DP-1: nvidia-auto-select +0+0, DVI-D-0: nvidia-auto-select +0+1080, HDMI-1: nvidia-auto-select +1920+0, HDMI-0: nvidia-auto-select +1920+1080; DVI-D-0: nvidia-auto-select +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1680x1050 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1600x900 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1280x1024 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1280x1024_60 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1280x960 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1280x720 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1152x720 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1024x768 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1024x768_60 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 800x600 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 800x600_60 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 640x480 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 640x480_60 +0+0, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1440x900, viewportout=1728x1080+96+0}, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1366x768, viewportout=1920x1079+0+0}, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1280x800, viewportout=1728x1080+96+0}, HDMI-1: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "DVI-D-0: nvidia-auto-select +0+0, HDMI-0: nvidia-auto-select +0+1080; DVI-D-0: 1280x1024 +0+0, HDMI-0: nvidia-auto-select +0+1024; DVI-D-0: 1280x1024_60 +0+0, HDMI-0: nvidia-auto-select +0+1024; DVI-D-0: 1152x864 +0+0, HDMI-0: nvidia-auto-select +0+864; DVI-D-0: 1024x768 +0+0, HDMI-0: nvidia-auto-select +0+768; DVI-D-0: 1024x768_60 +0+0, HDMI-0: nvidia-auto-select +0+768; DVI-D-0: 800x600 +0+0, HDMI-0: nvidia-auto-select +0+600; DVI-D-0: 800x600_60 +0+0, HDMI-0: nvidia-auto-select +0+600; DVI-D-0: 640x480 +0+0, HDMI-0: nvidia-auto-select +0+480; DVI-D-0: 640x480_60 +0+0, HDMI-0: nvidia-auto-select +0+480; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1680x1050, viewportout=1728x1080+96+0}, HDMI-0: nvidia-auto-select +0+1050; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1440x900, viewportout=1728x1080+96+0}, HDMI-0: nvidia-auto-select +0+900; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1366x768, viewportout=1920x1079+0+0}, HDMI-0: nvidia-auto-select +0+768; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1280x800, viewportout=1728x1080+96+0}, HDMI-0: nvidia-auto-select +0+800; DVI-D-0: nvidia-auto-select +0+0 {viewportin=1280x720}, HDMI-0: nvidia-auto-select +0+720"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
-----------------------------------

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#5  0x00007f6ee4eae8bf in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#6  0x00007f6ee4e5eb12 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#7  0x00007f6ee4e484b2 in __GI_abort () at abort.c:79
#8  0x00007f6ee5092a89 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#9  0x00007f6ee5091802 in qt_assert(char const*, char const*, int) () from /usr/lib64/libQt5Core.so.5
#10 0x000055ab0405817c in ShellCorona::handleScreenOrderChanged(QList<QScreen*>) [clone .cold] ()
#11 0x000055ab04099201 in QtPrivate::QSlotObject<void (ShellCorona::*)(QList<QScreen*>), QtPrivate::List<QList<QScreen*> const&>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#12 0x00007f6ee52eb534 in void doActivate<false>(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5
#13 0x000055ab040a9c37 in ScreenPool::handleOutputOrderChanged(QStringList const&) ()
#14 0x00007f6ee52eb534 in void doActivate<false>(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5
#15 0x000055ab0405a8c2 in OutputOrderWatcher::outputOrderChanged(QStringList const&) ()
#16 0x000055ab0407ff04 in OutputOrderWatcher::refresh() ()
#17 0x000055ab04080b10 in X11OutputOrderWatcher::refresh() ()
#18 0x00007f6ee52eb534 in void doActivate<false>(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5
#19 0x00007f6ee52f036a in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib64/libQt5Core.so.5
#20 0x00007f6ee52e2305 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#21 0x00007f6ee5f768de in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#22 0x00007f6ee52b3898 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#23 0x00007f6ee530b309 in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#24 0x00007f6ee530bbd1 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5
#25 0x00007f6ee3f7364c in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f6ee3f738f8 in g_main_context_iterate.constprop () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f6ee3f7398c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f6ee530bd46 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#29 0x00007f6ee52b1d3b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#30 0x00007f6ee52baa96 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#31 0x000055ab0405a0dd in main ()
[Inferior 1 (process 10304) detached]

Reported using DrKonqi
Comment 1 Håkon Innerdal 2023-04-26 09:30:29 UTC 
Additional information;
the crash happens on a new/ clean user config.
If I remove xorg.conf, or comment out Screen1 section, login is ok.
Comment 2 Håkon Innerdal 2023-04-26 09:33:25 UTC 
Created attachment 158439 [details]
working xorg conf

xorg.conf that works
Comment 3 Håkon Innerdal 2023-04-26 09:34:45 UTC 
Created attachment 158440 [details]
xorg.conf that causes crash

adding a Screen1 section, causes plasmashell to crash on login
Comment 4 Håkon Innerdal 2023-05-02 12:18:58 UTC 
Downgraded to the following packages in gentoo, and the crash did go away;
kde-plasma/plasma-workspace-wallpapers-5.27.2
kde-plasma/oxygen-sounds-5.27.2
kde-plasma/kdecoration-5.27.2
kde-plasma/layer-shell-qt-5.27.2
kde-plasma/libkscreen-5.27.2
kde-plasma/kwayland-integration-5.27.2
kde-plasma/xembed-sni-proxy-5.27.2
kde-plasma/kgamma-5.27.2
kde-plasma/polkit-kde-agent-5.27.2
kde-plasma/kpipewire-5.27.2
kde-plasma/kwrited-5.27.2
kde-plasma/kwallet-pam-5.27.2
kde-plasma/ksshaskpass-5.27.2
kde-plasma/kactivitymanagerd-5.27.2
kde-plasma/kmenuedit-5.27.2
kde-plasma/drkonqi-5.27.2
kde-plasma/libksysguard-5.27.2
kde-plasma/ksystemstats-5.27.2
kde-plasma/xdg-desktop-portal-kde-5.27.2
kde-plasma/plasma-vault-5.27.2
kde-plasma/plasma-pa-5.27.2
kde-plasma/plasma-systemmonitor-5.27.2
kde-plasma/milou-5.27.2
kde-plasma/plasma-welcome-5.27.2
kde-plasma/discover-5.27.2
kde-plasma/breeze-5.27.2
kde-plasma/plasma-integration-5.27.2
kde-plasma/breeze-gtk-5.27.2
kde-plasma/kscreenlocker-5.27.2
kde-plasma/kwin-5.27.2
kde-plasma/libkworkspace-5.27.2
kde-plasma/kde-cli-tools-5.27.2
kde-plasma/systemsettings-5.27.2
kde-plasma/oxygen-5.27.2
kde-plasma/kinfocenter-5.27.2
kde-plasma/kscreen-5.27.2
kde-plasma/khotkeys-5.27.2
kde-plasma/powerdevil-5.27.2
kde-plasma/sddm-kcm-5.27.2
kde-plasma/bluedevil-5.27.2
kde-plasma/kde-gtk-config-5.27.2
kde-plasma/plasma-nm-5.27.2
kde-plasma/plasma-disks-5.27.2
kde-plasma/plasma-workspace-5.27.2
kde-plasma/kdeplasma-addons-5.27.2
kde-plasma/plasma-desktop-5.27.2
kde-plasma/plasma-browser-integration-5.27.2
kde-plasma/plasma-meta-5.27.2
Comment 5 Akseli Lahtinen 2024-06-06 13:07:39 UTC 

*** This bug has been marked as a duplicate of bug 468873 ***