plasmashell doesn't work after long sleep

I am on EndeavourOs and when my laptop sleeps for a long enough time (haven’t measured it) plasma shell doesn’t start after entering. I have to logout for it to work properly.
I use an old laptop with [
{
“type”: “Title”,
“result”: {
“userId”: 1000,
“userName”: “paualberti”,
“fullUserName”: “paualberti”,
“hostName”: “paualberti-81mx”,
“homeDir”: “/home/paualberti/”,
“exePath”: “/usr/bin/fastfetch”,
“userShell”: “/usr/bin/fish”,
“pid”: 58313,
“cwd”: “/home/paualberti/”
}
},
{
“type”: “Separator”,
“error”: “Unsupported for JSON format”
},
{
“type”: “OS”,
“result”: {
“buildID”: “rolling”,
“codename”: “rolling”,
“id”: “endeavouros”,
“idLike”: “arch”,
“name”: “EndeavourOS”,
“prettyName”: “EndeavourOS”,
“variant”: “”,
“variantID”: “”,
“version”: “rolling”,
“versionID”: “”
}
},
{
“type”: “Host”,
“result”: {
“family”: “IdeaPad S145-15IGM”,
“name”: “81MX”,
“version”: “Lenovo IdeaPad S145-15IGM”,
“sku”: “LENOVO_MT_81MX_BU_idea_FM_IdeaPad S145-15IGM”,
“vendor”: “LENOVO”,
“serial”: “”,
“uuid”: “”
}
},
{
“type”: “Kernel”,
“result”: {
“architecture”: “x86_64”,
“name”: “Linux”,
“release”: “6.19.11-arch1-1”,
“version”: “#1 SMP PREEMPT_DYNAMIC Thu, 02 Apr 2026 23:33:01 +0000”,
“pageSize”: 4096
}
},
{
“type”: “Uptime”,
“result”: {
“uptime”: 163500700,
“bootTime”: “2026-04-11T14:01:59.828+0200”
}
},
{
“type”: “Packages”,
“result”: {
“all”: 1297,
“amSystem”: 0,
“amUser”: 0,
“apk”: 0,
“brew”: 0,
“brewCask”: 0,
“choco”: 0,
“dpkg”: 0,
“emerge”: 0,
“eopkg”: 0,
“flatpakSystem”: 0,
“flatpakUser”: 0,
“guixSystem”: 0,
“guixUser”: 0,
“guixHome”: 0,
“hpkgSystem”: 0,
“hpkgUser”: 0,
“kiss”: 0,
“linglong”: 0,
“macports”: 0,
“mport”: 0,
“moss”: 0,
“nixDefault”: 0,
“nixSystem”: 0,
“nixUser”: 0,
“opkg”: 0,
“pacman”: 1297,
“pacstall”: 0,
“paludis”: 0,
“pisi”: 0,
“pkg”: 0,
“pkgtool”: 0,
“pkgsrc”: 0,
“rpm”: 0,
“scoopUser”: 0,
“scoopGlobal”: 0,
“snap”: 0,
“soar”: 0,
“sorcery”: 0,
“winget”: 0,
“xbps”: 0,
“pacmanBranch”: “”
}
},
{
“type”: “Shell”,
“result”: {
“exe”: “/usr/bin/fish”,
“exeName”: “fish”,
“exePath”: “/usr/bin/fish”,
“pid”: 58059,
“ppid”: 58057,
“processName”: “fish”,
“prettyName”: “fish”,
“version”: “4.6.0”,
“tty”: 1
}
},
{
“type”: “Display”,
“result”: [
{
“id”: 3543560144569582664,
“name”: “EK241Y H”,
“primary”: true,
“output”: {
“width”: 1920,
“height”: 1080,
“refreshRate”: 74.973,
“drrStatus”: null,
“dpi”: 96
},
“scaled”: {
“width”: 1920,
“height”: 1080
},
“preferred”: {
“width”: 1920,
“height”: 1080,
“refreshRate”: 60.0
},
“physical”: {
“width”: 527,
“height”: 296
},
“rotation”: 0,
“bitDepth”: 0,
“hdrStatus”: “Unsupported”,
“type”: “External”,
“manufactureDate”: {
“year”: 2023,
“week”: 52
},
“serial”: 891331531,
“platformApi”: “wayland-kde”
}
]
},
{
“type”: “DE”,
“result”: {
“processName”: “plasmashell”,
“prettyName”: “KDE Plasma”,
“version”: “6.6.4”
}
},
{
“type”: “WM”,
“result”: {
“processName”: “kwin_wayland_wrapper”,
“prettyName”: “KWin”,
“protocolName”: “Wayland”,
“pluginName”: “”,
“version”: “”
}
},
{
“type”: “WMTheme”,
“result”: “Breeze”
},
{
“type”: “Theme”,
“result”: {
“theme1”: “Breeze (Dark) [Qt]”,
“theme2”: “Breeze-Dark [GTK2], Breeze [GTK3]”
}
},
{
“type”: “Icons”,
“result”: {
“icons1”: “breeze-dark [Qt]”,
“icons2”: “breeze-dark [GTK2/3/4]”
}
},
{
“type”: “Font”,
“result”: {
“display”: “Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]”,
“fonts”: [
“Noto Sans (10pt)”,
“Noto Sans (10pt)”,
“Noto Sans (10pt)”,
“Noto Sans (10pt)”
]
}
},
{
“type”: “Cursor”,
“result”: {
“theme”: “breeze_cursors”,
“size”: “24”
}
},
{
“type”: “Terminal”,
“result”: {
“processName”: “foot”,
“exe”: “/usr/bin/foot”,
“exeName”: “foot”,
“exePath”: “/usr/bin/foot”,
“pid”: 58057,
“ppid”: 21090,
“prettyName”: “foot”,
“version”: “1.26.1”,
“tty”: “”
}
},
{
“type”: “TerminalFont”,
“result”: {
“font”: {
“name”: “iosevka nerd font”,
“size”: “15”,
“styles”: ,
“pretty”: “iosevka nerd font (15pt)”
},
“fallback”: {
“name”: “”,
“size”: “”,
“styles”: ,
“pretty”: “”
}
}
},
{
“type”: “CPU”,
“result”: {
“cpu”: “Intel(R) Celeron(R) N4000”,
“vendor”: “GenuineIntel”,
“packages”: 1,
“cores”: {
“physical”: 2,
“logical”: 2,
“online”: 2
},
“frequency”: {
“base”: 2552,
“max”: 2600
},
“coreTypes”: ,
“temperature”: null,
“march”: “x86_64-v2”,
“numaNodes”: 1
}
},
{
“type”: “GPU”,
“result”: [
{
“index”: null,
“coreCount”: null,
“coreUsage”: null,
“memory”: {
“dedicated”: {
“total”: null,
“used”: null
},
“shared”: {
“total”: null,
“used”: null
},
“type”: null
},
“driver”: “i915”,
“name”: “UHD Graphics 600”,
“temperature”: null,
“type”: “Integrated”,
“vendor”: “Intel”,
“platformApi”: “DRM (card1)”,
“frequency”: 650,
“deviceId”: 16
}
]
},
{
“type”: “Memory”,
“result”: {
“total”: 3913801728,
“used”: 2609164288
}
},
{
“type”: “Swap”,
“result”:
},
{
“type”: “Disk”,
“result”: [
{
“bytes”: {
“available”: 167817916416,
“free”: 180637663232,
“total”: 250903908352,
“used”: 70266245120
},
“files”: {
“total”: 15630336,
“used”: 508970
},
“filesystem”: “ext4”,
“mountpoint”: “/”,
“mountFrom”: “/dev/nvme0n1p1”,
“name”: “endeavouros”,
“volumeType”: [
“Regular”
],
“createTime”: “2026-04-08T13:52:55.000+0200”
}
]
},
{
“type”: “LocalIp”,
“result”: [
{
“name”: “wlan0”,
“defaultRoute”: {
“ipv4”: true
},
“ipv4”: “192.168.0.22/24”
}
]
},
{
“type”: “Battery”,
“result”: [
{
“capacity”: 95.0,
“manufacturer”: “SMP”,
“manufactureDate”: “”,
“modelName”: “L16M2PB1”,
“status”: “AC Connected”,
“technology”: “Li-poly”,
“serial”: " 9344",
“temperature”: null,
“cycleCount”: 0,
“timeRemaining”: null
}
]
},
{
“type”: “PowerAdapter”,
“result”:
},
{
“type”: “Locale”,
“result”: “en_GB.UTF-8”
},
{
“type”: “Break”,
“error”: “Unsupported for JSON format”
},
{
“type”: “Colors”,
“error”: “Unsupported for JSON format”
}
].

I am not sure if it is a reproducible error or not. Also, only a minor inconvenience since i don’t leave it sleeping all that often.

Look in the system and user journal for error from your GPU, kwin and plasma shell.
That may give a clue about what is wrong.

Apr 13 15:22:33 paualberti-81mx kernel: OOM killer disabled.
Apr 13 15:22:32 paualberti-81mx kwin_wayland[61927]: Libinput: event2 - Power Button: client bug: event processing lagging behind by 656ms, your system is too slow
Apr 13 15:22:33 paualberti-81mx kernel: Freezing user space processes completed (elapsed 0.004 seconds)
Apr 13 15:22:32 paualberti-81mx kwin_wayland[61927]: Libinput: event1 - Power Button: client bug: event processing lagging behind by 680ms, your system is too slow
Apr 13 15:22:32 paualberti-81mx kernel: Freezing user space processes
Apr 13 15:22:32 paualberti-81mx kwin_wayland[61927]: Libinput: event0 - Lid Switch: client bug: event processing lagging behind by 693ms, your system is too slow
Apr 13 15:22:32 paualberti-81mx kernel: Filesystems sync: 0.007 seconds

I was out for about an hour and this showed in journalctl right after. Maybe the problem is how bad my cpu is.

hi, welcome.

a beginners tip for posting command line text is to use the preformatted option in the tool bar </> button for better readability, and to provide your kinfo output like so.

Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.17.0-20-generic (64-bit)
Graphics Platform: offscreen
Processors: 28 × Intel® Core™ i7-14700K
Memory: 62.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6800

as for your issue, it could be that the system is going into hibernation and you do not have it set up to recover from hibernation.

it’s a rather complex interaction between the os and your firmware that requires some painstaking set up… if not done right, or completely, then it will fail to resume.

Thanks. I do not know since I don’t think i have touched any of it. My config is mostly default. I used to use dwm so I as still familiarising myself with plasma. I don’t care about the wallpaper but I would like for the taskbar to restore. Power management and screen locking are in default. Should i create an autostart script with pidof -qs plasmashell || plasmashell &? I am not sure how it works, i tried to export a few variables before but it never worked. Isn’t it supposed to be a shell script?

when it restores properly, you should get your desktop back just as you left it before it went to sleep… anything short of that is probably corrupted.

if waking it right ways works as intended but after a time it does not resume completely, that’s an indication that what was stored in ram (or vram) was lost when the power was shut down by the firmware (hibernation).

and since there is no image saved to disk, the resume cannot complete and you get a borked desktop… you can try restarting the plasma shell and it may clear up any artifacts, but it’s probably better to just reboot or re-log at that point.

you could look into your firmware to see if there is a power saving mode you can disable so that the ram remains powered until the battery dies.