Plasma is crashing after suspend since last big update

jackdinn · 2 December 2024 10:20

For the last couple of days, the plasma panel (I assume all of plasma) is missing after suspend. It also sometimes crashes for no apparent reason. The panel is gone and so is the desktop but the menu still works so do windows and krunner.

I have not seen this behavior before the most recent plasma update on the 30th.

There does not seem to be anything much in the logs but maybe someone can spot something.

Plasma updates:-

[2024-11-30T12:25:29+0000] [ALPM] upgraded plasma-activities (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:29+0000] [ALPM] upgraded libplasma (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:39+0000] [ALPM] upgraded plasma-activities-stats (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:39+0000] [ALPM] upgraded plasma5support (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:39+0000] [ALPM] upgraded plasma-integration (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:39+0000] [ALPM] upgraded plasma-workspace (6.1.5-1.0 -> 6.2.4-1.1)
[2024-11-30T12:25:39+0000] [ALPM] upgraded kdeplasma-addons (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:44+0000] [ALPM] upgraded plasma6-themes-breath-migration (24.0.0-3 -> 24.0.0-4)
[2024-11-30T12:25:44+0000] [ALPM] upgraded plasma6-themes-breath (24.0.0-3 -> 24.0.0-4)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-browser-integration (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-desktop (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-nm (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-pa (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-systemmonitor (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-thunderbolt (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-vault (6.1.5-1 -> 6.2.4-1)
[2024-11-30T12:25:46+0000] [ALPM] upgraded plasma-workspace-wallpapers (6.1.5-1 -> 6.2.4-1)

❱inxi -b
System:
  Host: greg-venusseries Kernel: 6.11.10-2-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
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)

❱journalctl /usr/bin/plasmashell 
Dec 02 02:28:46 greg-venusseries plasmashell[61449]: qrc:/qt/qml/org/kde/ksysguard/faces/ExtendedLegend.qml:58: TypeError: Cannot read property 'sensors' of null
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: kde.plasmashell: requesting unexisting screen available rect -1
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:13 greg-venusseries plasmashell[61449]: org.kde.pulseaudio: No object for name "alsa_output.usb-Jieli_Technology_UACDemoV1.0_4153303135383906-01.analog-stereo.monitor"
Dec 02 09:59:14 greg-venusseries plasmashell[61449]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"

this shows the log from the last entry when i went to bed and then all logs for plasma after waking system this morning.

I have to keep using kquitapp5 plasmashell & kstart5 plasmashell & disown $argv to get the panel back

scotty65 · 2 December 2024 10:31

I’m afraid I can’t help with what is causing the issue (it’s just been a very long day for me and my concentration is waning). However, I can recommend an easier command for restarting the plasmashell:

systemctl restart --user plasma-plasmashell

I actually saved it in a script named reloadplasma6:

#!/bin/bash

# Both of these will work, but systemctl is
# preferable for a systemd installation

# kquitapp6 plasmashell; kstart plasmashell

systemctl restart --user plasma-plasmashell

exit 0

jackdinn · 2 December 2024 10:33

o ok thx, but i just have an (fish) abbreviation “rp” sooo …

But i shall put it in my notes about how to restart plasma.

Ben · 3 December 2024 02:13

This is very odd, if I might say so.

After using krunner (where the command is remembered) I had an occasional issue where the panel wasn’t completely drawn.

So you could do “plasma restart”

abbr pr 'systemctl --user restart plasma-plasmashell.service

You could also make a custom command for this (don’t need a terminal to run it)

kate ~/.local/bin/pr

paste:

#!/bin/bash

systemctl --user restart plasma-plasmashell.service

Then:

chmod +x ~/.local/bin/pr

So then you can do it from krunner.

Wayland or X11: have you tried both?
Check for clues in Journal?

journalctl -p3 -xb --no-hostname

Check new USER account login

(is this the installation/update, or is this messed up by USER data?)

jackdinn · 4 December 2024 09:05

well i was hoping that it would crash the plasma again this morning so i could give you the journalctl -p3 -xb --no-hostname logs but it didn’t do it this time.

It did do it once yesterday after noon, just for no reason while i was using it, but i was busy so i just reset plasma and went on with what i was doing.

I did have a direct email from a chap who said he is having the same issue on opensuse and he was thinking its to do with the monitor, He wanted to open a bug report but is finding it hard to gather any info/logs the same as me. But my monitor is nothing like his so i doubt it’s to do with the monitor.

Ben · 4 December 2024 10:56

This is certainly a great idea. However, I’m curious HOW you ‘reset’ plasma.

I’d go with moving .config to .configBUG and moving back ONLY folders/settings I was confident could have no effect. The rest will auto-generate… and if that clears the fault, it’s party time

jackdinn · 4 December 2024 11:12

Yea its all good sound logical debugging steps, and if i was not so busy i might even do so, but i am busy, so i had just hoped that someone might have already had an answer that i could quickly implement.

maybe when i get a spare couple of hours.

I said how i reset it
kquitapp5 plasmashell & kstart5 plasmashell & disown $argv;

Ben · 4 December 2024 11:29

Yes, you did - I get confused with the colloquial ‘reset’ meaning ‘delete that sh1t and start again’.

soundofthunder · 4 December 2024 12:09

If we’re speaking colloquially, in terms of one’s and two’s, shouldn’t that be “delete that sh2t and start again”?

Please excuse me, I had too much free time on my hands today. I’ll see myself out.

jackdinn · 4 December 2024 12:22

Ho ho , was that a strain to think of? ^^

soundofthunder · 4 December 2024 12:23

Yes, it took me all of 5 seconds.

jackdinn · 4 December 2024 12:24

woh, 5 sec,s ehh, i wish i was young again.

soundofthunder · 4 December 2024 12:37

As do I.
I’ve just been skimming through the thread for a little catch up.

There are two recent Known Issues and Solutions that could be related in some way. They are noted in the Stable Update 2024-10-10 announcement:

System freeze on suspend

A feature in systemd 256 freezing a user session when suspending may freeze the system.

[SOLVED] System freezes after sleep since update / Newbie Corner / Arch Linux Forums

Systemd 256 may break sleep

The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.
System freezes for 60 seconds and then wakes back up or hangs after waking up

Since systemd v256, systemd freezes user.slice before sleeping. This process can fail due to kernel bugs, particularly when KVM is in use.[13] [14]

Messages in the logs will contain Failed to freeze unit 'user.slice' before sleep. When such an issue occurs, trying to login (start another session) would fail with pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'.

To temporarily revert back to the old behavior, edit systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service with the following drop-in:
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
– Power management/Suspend and hibernate - ArchWiki

…and…

The workaround for this last one is to set your session to empty on login.

System Settings:

→ Session → Desktop Session → Session Restore
→ On login, launch apps that were open:

Start with an empty session

But keep in mind, this could be something else entirely as it’s likely these issues are now fixed with the most recent updates.

jackdinn · 4 December 2024 12:58

I checked journelctl for all of them errors bit don’t see any of them during the last 48 hours

Mine has always been set that way since i prefer to be in manual control of each startup app/service etc.

jackdinn · 4 December 2024 17:58

Ok i happened again, suspend at 13:57 & resume at 17:54.

journalctl -p3 -xb --no-hostname
Dec 04 13:57:13 bluetoothd[764]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 04 13:57:18 bluetoothd[764]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 04 13:57:23 bluetoothd[764]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 04 17:54:12 kernel: spd5118 13-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Dec 04 17:54:12 kernel: spd5118 13-0052: PM: failed to resume async: error -6
Dec 04 17:54:12 kernel: spd5118 13-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Dec 04 17:54:12 kernel: spd5118 13-0050: PM: failed to resume async: error -6
Dec 04 17:54:20 bluetoothd[764]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 04 17:54:26 bluetoothd[764]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

I dont use wayland because to much that i use does not work properly so i cant really test it more than just suspending it a waking it but iv tried that and it was fine for a couple of tries but then again it can be fine on x11.

jackdinn · 6 December 2024 10:14

I created a new user account yesterday, completely stock themes and widgets. Plasma crashed again this morning.

Dec 06 02:32:13 greg-venusseries bluetoothd[780]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to B0:38:E2:51:B1:F0: Connection reset by peer (104)
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0050: Failed to write b = 0: -6
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0050: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0050: PM: failed to resume async: error -6
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0052: Failed to write b = 0: -6
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0052: PM: dpm_run_callback(): spd5118_resume [spd5118] returns -6
Dec 06 10:05:12 greg-venusseries kernel: spd5118 13-0052: PM: failed to resume async: error -6
Dec 06 10:05:12 greg-venusseries bluetoothd[780]: profiles/audio/avdtp.c:l2cap_connect() connect to B0:38:E2:51:B1:F0: No route to host (113)
Dec 06 10:05:12 greg-venusseries bluetoothd[780]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for B0:38:E2:51:B1:F0: Input/output error
Dec 06 10:05:12 greg-venusseries bluetoothd[780]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 98:47:44:53:4E:E1: Host is down (112)
Dec 06 10:05:22 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:05:27 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:05:33 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:05:43 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:05:48 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:05:53 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:03 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:09 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:14 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:24 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:29 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:34 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:45 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:50 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:06:55 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:05 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:11 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:16 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:26 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:31 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:36 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:47 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:52 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:07:57 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:08:07 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:08:07 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress
Dec 06 10:08:08 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:08:08 greg-venusseries bluetoothd[780]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to B0:38:E2:51:B1:F0: Operation already in progress (114)
Dec 06 10:12:44 greg-venusseries (sd-worker)[74429]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74430]: Failed start worker process: No such file or directory
Dec 06 10:08:07 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Operation already in progress
Dec 06 10:08:08 greg-venusseries bluetoothd[780]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Dec 06 10:08:08 greg-venusseries bluetoothd[780]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to B0:38:E2:51:B1:F0: Operation already in progress (114)
Dec 06 10:12:44 greg-venusseries (sd-worker)[74429]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74430]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74431]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74432]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74433]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74434]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74435]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74436]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74437]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74438]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74439]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74440]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74441]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74442]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74443]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74444]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74445]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74446]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74447]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74448]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74449]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74450]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74451]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74452]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74453]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74454]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74455]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74456]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74457]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74458]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74459]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74460]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74461]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74462]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74463]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74464]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74465]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74466]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74467]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74468]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74469]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74470]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74471]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74472]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74473]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74474]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74475]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74476]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74477]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74478]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74479]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74480]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74481]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74482]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74483]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74484]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74485]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74486]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74487]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74488]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74489]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74490]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74491]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74492]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74493]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74494]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74495]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74496]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74497]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74498]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74499]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74500]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74501]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74502]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74503]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74504]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74505]: Failed start worker process: No such file or directory
Dec 06 10:12:44 greg-venusseries (sd-worker)[74506]: Failed start worker process: No such file or directory

Im going to have to write a script to automatically start the plasma panel. Problem is i cant figure a way to detect that its failed with bash.

Iv tried

pgrep plasmashell
qdbus | grep org.kde.plasmashell
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.showInteractiveConsole

none of which i can use to tell when the panel has crashed.

medmedin · 6 December 2024 12:31

To restart Plasma desktop without logging out simply run in terminal:
plasmashell --replace

Waking up from hibernation is currently broken for many people with kernel 6.12, and some with 6.11, so try lts 6.6.

jackdinn · 6 December 2024 13:09

Yea i know how to restart it, i was asking how to detect that its gone so i can script an automated restart.

This kinda thing:

#!/bin/bash

# Check if plasmashell is running
if ! pgrep plasmashell > /dev/null; then
  echo "Plasmashell not running. Restarting..."
  kquitapp5 plasmashell && plasmashell --replace &
else
  echo "Plasmashell is running."
fi

But i cant find any way to detect the failed panel?

Ok yea, have switched to 6.6, we shall see how we go.

Cheers

Ben · 6 December 2024 13:17

Memory error (spd5118) solved for Arch:
https://bbs.archlinux.org/viewtopic.php?id=300008

The error you’re receiving is hallmark of VRAM decay, [SOLVED] display error when waking from sleep/hibernation on nvidia / Newbie Corner / Arch Linux Forums
While that doens’t fit the 30s thing or explain the 6.11 condition, make sure to enable https://wiki.archlinux.org/title/NVIDIA … er_suspend

Affirmative! Configuring nvidia-module as described here did in fact resolve the issue. It is however not necessary to blacklist spd5118 kmod.

jackdinn · 6 December 2024 13:29

does it apply if i dont have a nvidia?

Plasma is crashing after suspend since last big update

Check for clues in Journal?

Check new USER account login