Bug 497204

Created attachment 176441 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

In my case bottom panel disappears and never shows up.
OpenSUSE Tumbleweed plasma 6.2.4, Framework 6.8.0, Qt Version 6.8.1

Drkonqi doesn't works so i gathered some logs from journal if it may help
Dec 08 18:45:15 localhost plasmashell[2488]: qml: Connection lost
Dec 08 18:45:18 localhost plasmashell[2488]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Dec 08 18:45:18 localhost plasmashell[2488]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 08 18:45:18 localhost plasmashell[2488]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 08 18:45:18 localhost plasmashell[2488]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 08 18:45:18 localhost plasmashell[2488]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 08 18:45:18 localhost plasmashell[2488]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:238:17: Unable to assign [undefined] to bool
Dec 08 18:45:18 localhost plasmashell[2488]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:370:21: Unable to assign [undefined] to bool
Dec 08 18:48:54 localhost plasmashell[2488]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 08 18:48:54 localhost plasmashell[2488]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 08 18:48:55 localhost plasmashell[2488]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

PS It is not only about panel, but whole session is broken

I have been having the same issue, but with Manjaro KDE.

Reported here:-
https://forum.manjaro.org/t/plasma-is-crashing-after-suspend-since-last-big-update/171347

Hopefully it can be tracked down as it looks like a very hard one to diagnose. There is nothing obvious in the journal that i can see. At least it's not too intermittent, it happens almost every suspend wake cycle (with a good while between the sleep and wake).
```
Operating System: Manjaro Linux 
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.12.1-4-MANJARO (64-bit)
Graphics Platform: X11
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Micro Computer (HK) Tech Limited
Product Name: Venus Series
```

```
❱inxi -b
System:
  Host: greg-venusseries Kernel: 6.12.1-4-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux
Machine:
  Type: Desktop System: Micro (HK) Tech product: Venus Series v: N/A
    serial: <superuser required>
  Mobo: Shenzhen Meigao Equipment model: AHWSA serial: <superuser required>
    UEFI: American Megatrends LLC. v: AHWSA.1.22 date: 03/12/2024
CPU:
  Info: 14-core (6-mt/8-st) 13th Gen Intel Core i9-13900H [MST AMCP]
    speed (MHz): avg: 756 min/max: 400/5200:5400:4100
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
    loaded: modesetting dri: iris gpu: i915 resolution: 3840x2160~60Hz
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1
    renderer: Mesa Intel Graphics (RPL-P)
Network:
  Device-1: Intel Ethernet I226-V driver: igc
  Device-2: Intel Ethernet I226-LM driver: igc
  Device-3: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
Drives:
  Local Storage: total: 1.84 TiB used: 171.85 GiB (9.1%)
Info:
  Memory: total: 32 GiB note: est. available: 31.07 GiB used: 7.89 GiB (25.4%)
  Processes: 424 Uptime: 2d 18h 56m Shell: fish inxi: 3.3.36
```

The same issue persists with X11 after updating KDE to version 6.2.4 on openSUSE Tumbleweed
At the moment of unlocking journalctl says:

Dec 02 23:21:51 zeus kded6[8262]: org.kde.pulseaudio: No object for name "alsa_output.usb-Generic_USB_Audio-00.HiFi_7_1__Headphones__sink.monitor"
Dec 02 23:21:51 zeus kdeconnectd[8465]: 2024-12-02T23:21:51 org.kde.pulseaudio: No object for name "alsa_output.usb-Generic_USB_Audio-00.HiFi_7_1__Headphones__sink.monitor"
Dec 02 23:21:51 zeus plasmashell[20569]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 23:21:51 zeus plasmashell[20569]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 23:21:51 zeus plasmashell[20569]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 23:21:51 zeus plasmashell[20569]: kde.plasmashell: requesting unexisting screen available rect -1

Nothing more useful is found in the logs.

It doesn't happen consistently. Sometimes it might not occur for several lock and sleep cycles, and other times it happens two or three times in a row, just when locking the screen. I couldn't establish any logical pattern. Moreover, the Plasma shell crashes completely - it can only be restarted through systemctl --user restart plasma-plasmashell, and already open windows change their size, requiring manual readjustment.

Actually i have seen the same log errors as reported by others so i guess they may well point to the problem 

My journalctl at wake when plasma has crashed:-

Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: XRandROutput 66 update 
                                                                            m_connected: 0 
                                                                            m_crtc XRandRCrtc(0x5be7d4e726c0) 
                                                                            CRTC: 62 
                                                                            MODE: 72 
                                                                            Connection: 1
Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: Output 66 : connected = false , enabled = true
Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: XRandROutput 66 update 
                                                                            m_connected: 1 
                                                                            m_crtc XRandRCrtc(0x5be7d4e726c0) 
                                                                            CRTC: 62 
                                                                            MODE: 72 
                                                                            Connection: 1
Dec 10 15:36:01 greg-venusseries kscreen_backend_launcher[299292]: kscreen.xrandr: Output 66 : connected = false , enabled = true
Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 10 15:36:01 greg-venusseries plasmashell[576338]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 10 15:36:01 greg-venusseries joplin-desktop[299538]: [299538:1210/153601.476790:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Dec 10 15:36:01 greg-venusseries kdeconnectd[299431]: 2024-12-10T15:36:01 org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 10 15:36:01 greg-venusseries kded6[299207]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"

Searchable backtrace from the attachment

Thread 1 (Thread 0x7f316780f6c0 (LWP 3383415)):
[KCrash Handler]
#5  0x00007f319dd29b7b in qDeleteAll<QList<QSGCurveAbstractNode*>::const_iterator> (begin=..., end=...) at /usr/include/qt6/QtCore/qalgorithms.h:27
#6  qDeleteAll<QList<QSGCurveAbstractNode*> > (c=...) at /usr/include/qt6/QtCore/qalgorithms.h:35
#7  QQuickShapeCurveRenderer::updateNode (this=0x55a3cd103490) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quickshapes/qquickshapecurverenderer.cpp:420
#8  0x00007f319dd16a7a in QQuickShape::updatePaintNode (this=0x55a3cd23c4a0, node=<optimized out>) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quickshapes/qquickshape.cpp:1184
#9  0x00007f32150b3334 in QQuickWindowPrivate::updateDirtyNode (this=this@entry=0x55a3cf6d4740, item=item@entry=0x55a3cd23c4a0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/items/qquickwindow.cpp:2255
#10 0x00007f32150b3b1c in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55a3cf6d4740) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/items/qquickwindow.cpp:1997
#11 0x00007f32150b7c54 in QQuickWindowPrivate::syncSceneGraph (this=0x55a3cf6d4740) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/items/qquickwindow.cpp:573
#12 0x00007f32152cdcc8 in QSGRenderThread::sync (this=this@entry=0x55a3ca8d84a0, inExpose=inExpose@entry=true) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:552
#13 0x00007f32152cf1a6 in QSGRenderThread::syncAndRender (this=this@entry=0x55a3ca8d84a0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:715
#14 0x00007f32152d0263 in QSGRenderThread::run (this=0x55a3ca8d84a0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:974
#15 0x00007f321375473c in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:326
#16 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=<optimized out>) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:262
#17 QThreadPrivate::start (arg=0x55a3ca8d84a0) at /usr/src/debug/qt6-qtbase-6.7.2-6.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:285
#18 0x00007f3212ea66d7 in start_thread (arg=<optimized out>) at pthread_create.c:447
#19 0x00007f3212f2a60c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

I'm not able to reproduce this on Plasma 6.2.4 or git-master

inxi -b                                                                                                                                                                                                                                                                                                                       Tue 10 Dec 2024 09:55:54 PM MSK
System:
  Host: zeus Kernel: 6.11.8-1-default arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.4 Distro: openSUSE Tumbleweed 20241206
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG B650 TOMAHAWK WIFI (MS-7D75)
    v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.E0
    date: 02/20/2024
CPU:
  Info: 8-core AMD Ryzen 7 7700 [MT MCP] speed (MHz): avg: 4005
    min/max: 400/5389
Graphics:
  Device-1: NVIDIA AD104 [GeForce RTX 4070 SUPER] driver: nvidia v: 550.135
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael driver: amdgpu
    v: kernel
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 2560x1440
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 550.135
    renderer: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
Drives:
  Local Storage: total: 931.51 GiB used: 729.9 GiB (78.4%)
Info:
  Memory: total: 32 GiB note: est. available: 30.54 GiB used: 13.3 GiB (43.5%)
  Processes: 689 Uptime: 10h 44m Shell: fish inxi: 3.3.36

Another one: https://www.reddit.com/r/kde/comments/1hb77ec/how_to_diagnose_this_plasma_shell_crash/

Why changed title to [Wayland] ?, many people including me are using X11 not Wayland.

Just happened again, not long after a reboot to use a new kernel.  I can attach the entire new core dump if that would be helpful - these are the lines in the logs between login and activation of DrKonqi:

Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:20 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:20 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: org.kde.powerdevil: [DDCutilDisplay]: ddca_get_non_table_vcp_value -5
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.50 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.50 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.50 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.50 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: org.kde.powerdevil: [DDCutilDisplay]: ddca_set_non_table_vcp_value -3007
Dec 11 10:18:21 demonslayer org_kde_powerdevil[4204]: org.kde.powerdevil: [DDCutilDisplay]: "DELL 1708FP" retrying to set DDC/CI brightness in 1000 milliseconds - attempt no. 1
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:21 demonslayer plasmashell[4135]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
Dec 11 10:18:21 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-3: fd=34], Keeping adjusted sleep multiplier 2.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-4: fd=34], Replacing adjusted sleep multiplier 0.05 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: org.kde.powerdevil: [DDCutilDisplay]: ddca_get_non_table_vcp_value -5
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.70 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.70 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.70 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:22 demonslayer org_kde_powerdevil[4204]: dh=Display_Handle[i2c-2: fd=34], Replacing adjusted sleep multiplier 0.70 with 1.00 for SE_POST_WRITE or SE_POST_SAVE_SETTINGS
Dec 11 10:18:22 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_14.2.analog-stereo.monitor"
Dec 11 10:18:23 demonslayer kded6[4070]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_01_00.1.pro-output-3.monitor"
Dec 11 10:18:23 demonslayer plasmashell[4135]: file:///home/daveo/.local/share/plasma/plasmoids/org.kde.userbase.plasma.luna3/contents/ui/LunaIcon.qml:213: TypeError: Value is undefined and could not be converted to an object
Dec 11 10:18:23 demonslayer plasmashell[4135]: file:///home/daveo/.local/share/plasma/plasmoids/org.kde.userbase.plasma.luna3/contents/ui/LunaIcon.qml:166: TypeError: Value is undefined and could not be converted to an object
Dec 11 10:18:23 demonslayer plasmashell[4135]: KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
Dec 11 10:18:23 demonslayer audit[4135]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=4135 comm="QSGRenderThread" exe="/usr/bin/plasmashell" sig=11 res=1

Also can confirm that the crash doesn't happen at every screen wake, and it apparently doesn't even need to have been sleeping all that long for it to occur - monitors had been off for less than 20 minutes before this last crash.

Could possible be related to Bug 493572.

Can also confirm that the crash happens in both Wayland and X11 versions of Plasma.

(In reply to Dmitry from comment #11)
> Another one:
> https://www.reddit.com/r/kde/comments/1hb77ec/
> how_to_diagnose_this_plasma_shell_crash/

I'm the user in the reddit thread.

I think I know about more about when it does and doesn't crash for me.

I'm using a laptop that I keep closed with an external monitor. If the screen locker activates after a timeout,there's a very high chance it'll have crashed when I unlock. I noticied, if I open the laptopand have the second display, it does not crash on unlock.

I'm not sure what are useful logs to get, but it's a fairly consistent crash for me

This is the output of `plasmashell --replace` after I unlock with no shell present
```org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Expected '>', but got '[a-zA-Z]'." line 1 col 267
org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Expected '>', but got '[a-zA-Z]'." line 1 col 256
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kf.kunitconversion: currency conversion table data obtained via network
org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Expected '>', but got '[a-zA-Z]'." line 1 col 233
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kde.plasmashell: requesting unexisting screen available rect -1
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
kf.plasma.quick: Exposed with no visual parent. Window positioning broken.
org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Expected '>' or '/', but got '<'." line 1 col 313
org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Expected '>', but got '[a-zA-Z]'." line 1 col 262
org.kde.plasma.notificationmanager: Notification to send to backend contains invalid XML:  "Unexpected '''." line 1 col 47
^C
```

I changed my "Screen Locking" timeout to 1 minute to observer what happens.

The screen locks after 1 minute, then a short time later, the monitor turns off, but back on almost instantly. NB, it seems with this bug/some other issue, it seems my monitor is never turned off.

Journal logs for this time here https://pastebin.com/pp4VHFm4

Marking confirmed since this is affecting multiple peope

Has there been any movement on this yet? I got so peeved off with it I reinstalled the OS but it still does it. So I built a script to automate watching the panel (taskbar), if it is not visible then it restarts plasma. It's a terrible resolution.

(In reply to jackdinn from comment #23)
> Has there been any movement on this yet? I got so peeved off with it I
> reinstalled the OS but it still does it. So I built a script to automate
> watching the panel (taskbar), if it is not visible then it restarts plasma.
> It's a terrible resolution.

The behavior hasn't changed at all - the issue is still occurring regularly, including on version 6.2.5

Actually, there seem to be some changes. I feel like the complete disappearance of the environment happens less frequently now. However, after unlocking the screen, windows often resize as if the environment had crashed. The bottom part of all maximized windows ends up hidden behind the taskbar panel. This behavior might have existed as well, and I'm not sure if any work was done on this issue in 6.2.5, but I've only started noticing it after updating.

I can comfirm this, too.

Plasma 6.2.4
OS: Gentoo
Kernel: 6.6.62
Graphics: X11, single monitor

When the screen (not the system, which stays on all the time) comes back from idle sleep/screenlock, the panel and the background are gone, I can restore it from a console with plasmashell --replace.

In my case plasmashell crashes without any error messages in the logs, but if I had started it in a shell, there is at least one line I have in common with the other crash reports here:

kde.plasmashell: requesting unexisting screen available rect -1

I can confirm, too (same description as Mathias comment above) 

Plasma 6.2.4 and 6.2.5
OS: Arch
Kernel: 6.12.17
Graphics: X11, single monitor
Hardware: Intel N100 + Intel Graphic + Memory 32 GB RAM

Always when switching the screen off and on again. No crash, but panel inactive afterwards:
kde.plasmashell: requesting unexisting screen available rect -1

Updated to 6.13.0-1-MANJARO as someone had posted that it seemed to be fixed after this kernel update but unfortunately its not :(

```
Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1
Feb 09 17:47:12 greg-venusseries plasmashell[857402]: kde.plasmashell: requesting unexisting screen available rect -1

```

Of course, the DE bug can't be fixed in the kernel. The issue remains exactly as it was.

"Interestingly" this has stopped being an issue for me, but I swapped from using HDMI output directly to a USB-C dock (Dell WD19).

(In reply to Mathias from comment #26)
> I can comfirm this, too.
> 
> Plasma 6.2.4
> OS: Gentoo
> Kernel: 6.6.62
> Graphics: X11, single monitor
> 
> When the screen (not the system, which stays on all the time) comes back
> from idle sleep/screenlock, the panel and the background are gone, I can
> restore it from a console with plasmashell --replace.
> 
> In my case plasmashell crashes without any error messages in the logs, but
> if I had started it in a shell, there is at least one line I have in common
> with the other crash reports here:
> 
> kde.plasmashell: requesting unexisting screen available rect -1

Seeing the same thing on Plasma 6.3.0, Arch Linux with Wayland, kernel 6.12.10.

My laptop is connected to an external monitor with HDMI, and the laptop's lid is closed. When the monitor is turned off as a result of power management settings, and the laptop stays on, and I press a key so that the monitor wakes up, plasmashell doesn't show anymore. If I run it with `plasmashell --replace`, it prints 4 x `kde.plasmashell: requesting unexisting screen available rect -1` on monitor wakeup.

To get plasmashell to display again, I can either restart plasmashell or briefly lift the laptop lid.

*** Bug 499266 has been marked as a duplicate of this bug. ***

Seems to be fixed as of a full system update on endeavourOS as of this past week 

System:
  Host: endeavour Kernel: 6.13.3-arch1-1 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.3.1 Distro: EndeavourOS
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z690-P WIFI v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 2212
    date: 12/13/2022
CPU:
  Info: 10-core (6-mt/4-st) 12th Gen Intel Core i5-12600K [MST AMCP]
    speed (MHz): avg: 800 min/max: 800/5000:3800
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] driver: nvidia
    v: 570.86.16
  Device-2: Logitech Logi Webcam C920e driver: snd-usb-audio,uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.5 driver: X:
    loaded: nvidia unloaded: modesetting gpu: nvidia,nvidia-nvswitch resolution:
    1: N/A 2: N/A 3: N/A
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.86.16 renderer: NVIDIA GeForce
    RTX 3060 Ti/PCIe/SSE2
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi
  Device-2: Realtek RTL8125 2.5GbE driver: r8169
Drives:
  Local Storage: total: 13.91 TiB used: 5.18 TiB (37.3%)
Info:
  Memory: total: 32 GiB note: est. available: 31.09 GiB used: 5 GiB (16.1%)
  Processes: 515 Uptime: 3d 3h 3m Shell: Bash inxi: 3.3.37

(In reply to netrunner1197 from comment #33)
> Seems to be fixed as of a full system update on endeavourOS as of this past
> week 

That's great news. Is anyone else still experiencing this bug on Plasma 6.3.1?

(In reply to TraceyC from comment #34)
> (In reply to netrunner1197 from comment #33)
> > Seems to be fixed as of a full system update on endeavourOS as of this past
> > week 
> 
> That's great news. Is anyone else still experiencing this bug on Plasma
> 6.3.1?

Cant say , that version of plasma is not going to be pushed until maybe next month for me.

Upgraded to 6.3.1 earlier today, been running without issues so far. Will comment again after testing some more.

Was there a specific change addressing this bug? I didn't see anything mentioned.

$ systemctl --user status plasma-plasmashell.service | grep active
     Active: active (running) since Mon 2025-02-24 08:56:27 CET; 11h ago

(In reply to TraceyC from comment #34)
> (In reply to netrunner1197 from comment #33)
> > Seems to be fixed as of a full system update on endeavourOS as of this past
> > week 
> 
> That's great news. Is anyone else still experiencing this bug on Plasma
> 6.3.1?

Unfortunately I still experience the bug, as I described it in an earlier comment, on Plasma 6.3.1 (Arch Linux).

Hasn't been fixed in Plasma 6.3.1. The behavior remains unchanged.

I'm sorry to hear this is still happening in 6.3.1. Thanks for confirming.

I see a big improvement on Fedora 40 runnnig 6.13.4: upon wake, the panels briefly disappear (and the windows above them resize to fit the available space), then come right back (and the windows resize back to how they were before).  There is no crash notification and the system seems stable.  Hooray and thank you!

Its still got the same fault on plasmashell 6.3.2. No change noticeable. Still crashes plasma on resume.

(Manjaro KDE)

(In reply to Haakon Nilsen from comment #37)
> (In reply to TraceyC from comment #34)
> > (In reply to netrunner1197 from comment #33)
> > > Seems to be fixed as of a full system update on endeavourOS as of this past
> > > week 
> > 
> > That's great news. Is anyone else still experiencing this bug on Plasma
> > 6.3.1?
> 
> Unfortunately I still experience the bug, as I described it in an earlier
> comment, on Plasma 6.3.1 (Arch Linux).

Strange. For me, the issue seems to fixed when my monitors return from sleep, but switching back to my endeavour machine from another input still causes the crash

(In reply to netrunner1197 from comment #42)
> Strange. For me, the issue seems to fixed when my monitors return from
> sleep, but switching back to my endeavour machine from another input still
> causes the crash

I also see a duality which might be related to what you're seeing: I don't see the problem when my laptop wakes up and also causes my monitor to wake up, but if my monitor goes to sleep as a result of power management settings and the laptop stays on, I consistently see the problem when the monitor wakes up.

For now I've just disabled monitor sleep in settings.

I've developed a workaround. Haven't tested it extensively so I'm not 100% sure it's solid but I think it's going to work:


```js
// watcher.js
workspace.windowRemoved.connect(function(client) {
  if (client.resourceClass === "plasmashell" && client.dock) {
    print("plasmashell dock disappeared, restarting")
    callDBus(
      "org.freedesktop.systemd1",
      "/org/freedesktop/systemd1",
      "org.freedesktop.systemd1.Manager",
      "RestartUnit",
      "plasma-plasmashell.service",
      "replace",
      reply => {
          print(JSON.stringify(reply))
        }
    );
  }
})
```

```fish
#!/usr/bin/env fish
# watcher.fish

set id (qdbus \
  --session \
  org.kde.KWin \
  /Scripting \
  org.kde.kwin.Scripting.loadScript \
  (pwd)/watcher.js)

qdbus --session org.kde.KWin /Scripting/Script$id org.kde.kwin.Script.run

function cleanup
  echo stopping script
  qdbus --session org.kde.KWin /Scripting/Script$id org.kde.kwin.Script.stop
end

trap cleanup EXIT SIGINT

journalctl CODE_FILE="file://"(string escape --style=url (realpath (pwd)/watcher.js)) -f -S "10 seconds ago"
```

Keep the script running and it should automatically detect when the plasmashell dock dies, and then it will restart it through systemd.

When I confirm this is bullet proof, I'll turn it into a systemd service, should be easy.

i just made a rough and ready hackup bash script to watch the panel. Its been working for me since this whole thing started (some time around X-mas).

```
❱cat /home/greg/bash/monitor_plasma_panel.sh
#!/bin/bash
sleep 15
# Log file path
LOG_FILE="/home/greg/bash/monitor_plasma_panel.log"

# Command to restart Plasma
RESTART_COMMAND="plasmashell --replace &"

# Panel window properties
PANEL_NAME="plasmashell"
PANEL_HEIGHT=48

# Function to log messages
log_message() {
    echo "$(date '+%Y-%m-%d %H:%M:%S') - $1" >> "$LOG_FILE"
}

# Function to check the panel status
check_panel_status() {
    local panel_info
    panel_info=$(xwininfo -name "$PANEL_NAME" 2>/dev/null)

    if [[ -z "$panel_info" ]]; then
        log_message "Panel not found."
        return 1
    fi

    # Extract the height of the panel
    local current_height
    current_height=$(echo "$panel_info" | awk '/Height:/ {print $2}')

    if [[ -z "$current_height" ]]; then
        log_message "Unable to determine panel height."
        return 1
    fi

    if [[ "$current_height" -lt 3 ]]; then
        log_message "Panel height less than 3: $current_height (expected $PANEL_HEIGHT)."
        return 2
    fi

    # log_message "Panel is running normally with height $current_height."
    return 0
}

# Monitoring loop
while true; do
    check_panel_status
    status=$?

    if [[ $status -ne 0 ]]; then
        log_message "Panel issue detected. Restarting Plasma..."
        eval "$RESTART_COMMAND"
        sleep 5  # Wait for Plasma to restart
    fi

    # Adjust the monitoring interval as needed (in seconds)
    sleep 10
done
```


However, i have disabled it atm because i got a system update today including plasmashell 6.3.4, so we shall see how 6.3.4 goes but im not holding my breath.

I updated to KDE 6.3.4 a couple of days ago, and this bug appeared that same day sometime after I had already rebooted

yes, iv just updated to plasmashell 6.3.4 but the bug is still there unfortunately.

I upgraded to plasma 6.4.5 today. The bug is still there.

(In reply to Gabriel from comment #50)
> Arch Linux, 6.16.8-zen1-1-zen, KDE Plasma 6.4.5, KDE Frameworks 6.18.0, Qt
> 6.9.2, Mesa 25.2.3 (RDNA3 GPU), Wayland
> 
From what you describe, plasmashell might not actually be crashing. If so, you're experiencing a different bug. To determine this, we need a backtrace of it. Can you please attach a backtrace of the crash (if there was one) using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

If there is no coredump, plasmashell didn't crash and you have a different bug.

The bug hasn't occurred for me since some update a couple of months ago. Current Plasma is 6.4.5

For folks coming across this, if you think you have this crash, we need a complete backtrace to see if that's the case. If the backtrace is the same or very similar to the one in comment #8 then you have the same crash.
https://bugs.kde.org/show_bug.cgi?id=497204#c8

If you don't have a crash, you have a different bug.

(In reply to TraceyC from comment #55)
> (In reply to Yuriy Vidineev from comment #54)
> > I have the same symptom: Plasma crashes after each wake-up. I have an
> > external screen connected. 
> 
> Based on the backtrace, you have a different crash. There can be different
> code involved in crashes that have the same symptoms.
> Your crash is bug 487660, which has a fix that will ship with 6.5.0.

Hi Tracey. Ooops, sorry. Thanks for the correction, and have a great day!