SUMMARY *** After upgrade from 5.111 -> 5.112 yesterday, starting plasma (startplasma-x11) fails. Ksplash shows start animation, but no worktig session starts up. startplasma-x11 does not log anything, but eats up each second more 200kB of memory, consumes 100% CPU, *** STEPS TO REPRODUCE 1. Arch Linux - AMD CPU - AMDGPU Radeon RX 470/480/570/570X/580/580X/590] (rev e1) 2. $HOME on NFS, .config, .local as subvolume from local btrfs 3. sddm, startplasma-x11, config was more than 1 year old, unchanged OBSERVED RESULT: startplasma-x11 leaks memory, 100% CPU usage, looks like a dead-end-loop $HOME/.xsession-errors are not used to log, no working session created EXPECTED RESULT working session SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux current version (2023-11-20) KDE Plasma Versions extracted from pacman.log, shows up the version change, which caused the problem. plasma-framework5 (5.111.0-1 -> 5.112.0-1) KDE Frameworks Version: plasma-framework5 (5.111.0-1 -> 5.112.0-1) Qt Version: upgraded qt5-base (5.15.11+kde+r138-1 -> 5.15.11+kde+r146-1) ADDITIONAL INFORMATION [2023-11-20T11:24:47+0100] [ALPM] upgraded kcoreaddons5 (5.111.0-1 -> 5.112.0-1) Sorry drkonqui or aditional logs are not written or availble.
How exactly do you execute startplasma-x11? Do you see anything in the system journal? Do you still encounter this problem if you start with a clean .config folder?
A clean .config works, but is not an option, due a huge amount of kwallet (gnupg) keys and forms data for chromium and saving/restoring them is nessesary. I tried out to remove anything not nessesary out of the way in .cache (deleted completely) .config (deleted partially, execpt license files of commercial licenses, kwallet files, chromium (arch version), gnupg (linked from $HOME/.gnupg -> .config/gnupg. startplasma-x11 was triggered by the sddm standard session startup. Unfortunately no logging in systemd journal or dmesg or .xsession-errors are done. Changing the Xsession start profile to "xterm" and starting "strace /usr/bin/startplasma-x11" in there gives no clue. I'll try to catch the strace out, Last line is IMHO "brk" line, repeating endless, and console top shows up no forks, but 100% cpu and expotentially raising memory usage, each second 200kiB RSS segement. User auth is done by ldap/nslcd/pam_ldap from central ldap server. This Filesystem setup was nessesary, due performance prooblems with kde/plasma users, if a nfs-server home was used: server:/home 734002176 198294528 532041728 28% /home /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.cache /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.config /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.fonts /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.local /dev/sdb3 1447541220 1324448464 84672400 94% /home/jojo/.thunderbird tmpfs 13184980 156 13184824 1% /run/user/10000 i.E. /home/jojo/.* is mounted as btrfs subvolume, to keep buggy IO-intensive tasks on the local machine. We are a small company, having 20 employee logging in each morning at 8am. The startup of plasma sessions was without "local mounted" helps a DDOS against the NFS Server. standby, I try to grep more logs
Created attachment 163353 [details] startplasma-ps-axef.log Process environment of crashing startplasma-x11
Created attachment 163354 [details] strace log of failing startplasma-x11 manually created stack trace (strace startplasma-x11 &>log)
Could you increase the log level of systemd journal to debug and report the output of journalctl -b ?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!