UID 1000/taskbar freeze and dualmonitor quirk

[StoneCold]

Hey folks,

I found a strange issue with my desktop recently.

• Sometime during the KDE 6 update-cycle, my issue is to do with User Manager. After a few hours of use at random intervals (usually when there is a lot of programs open and after I open a program) my taskbar will completely freeze and nothing I click on it will work. My programs still function and I can switch between open windows, but I cannot operate on the taskbar to open new programs etc. Opening programs through terminal still works. This issue is resolved after a restart. When rebooting, my log screen gets hung on “user manager UID 1000” for a minute or two before restarting. This does not occur when everything functions at restart. I might have turned a setting on somewhere.

On a side note, I plugged in a new monitor today (dual monitor) and the main screen has a weird yellow tint as if night light is still turned on. The secondary monitor does not get this. It’s only occurs on the one I click “Primary screen”. Any idea on this? Found this post on manjaro forums with a similar problem but no reply

I am unsure if this is a quirk of KDE, my computer or something else entirely. Not OS breaking issues (I hope) but they are quite annoying nevertheless. I haven’t really found any posts about this specific issue. Any advice is appreciated

Thanks.

System:
Kernel: 6.11.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=63089043-f873-4241-853d-0c85c3696a60 rw rootflags=subvol=@
pcie_acs_override=downstream,multifunction amd_iommu=on iommu=pt
loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A info: frameworks v: 6.7.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: B650 LiveMixer
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 2.10 date: 03/21/2024
CPU:
Info: model: AMD Ryzen 5 7500F bits: 64 type: MT MCP arch: Zen 4 gen: 4
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 6 MiB
desc: 6x1024 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 5040 min/max: 400/5074 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 5040 2: 5040 3: 5040
4: 5040 5: 5040 6: 5040 7: 5040 8: 5040 9: 5040 10: 5040 11: 5040 12: 5040
bogomips: 88632
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 22 [Radeon RX 6700/6700
XT/6750 XT / 6800M/6850M XT] vendor: ASRock driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,
DP-2, DP-3, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:73df class-ID: 0300
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 18.1.8 DRM 3.59 6.11.6-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.295 layers: 10 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.2.6-arch1.1
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.2.6-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h/19h HD Audio
vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0d:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: PreSonus Audio AudioBox USB 96 driver: snd-usb-audio type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:7 chip-ID: 194f:0303
class-ID: fe01 serial: <filter>
API: ALSA v: k6.11.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 08:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:2 chip-ID: 2b89:8761
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 5.91 TiB used: 2.94 TiB (49.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Crucial model: CT2000P3PSSD8
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P9CR40A temp: 31.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 30.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD2003FZEX-00Z4SA0 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: 1E.8
scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 1.54 TiB (84.4%)
fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.54 TiB (84.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.54 TiB (84.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.54 TiB (84.4%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.96 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 39.9 C mobo: 30.5 C gpu: amdgpu temp: 37.0 C
mem: 34.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB note: est. available: 30.96 GiB used: 5.5 GiB (17.8%)
Processes: 331 Power: uptime: 59m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.37 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1901 libs: 574 tools: pamac,paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-04-29
Last full system update: 2024-11-07 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

[FameWolf]

Try “systemctl --user restart plasma-plasmashell.service” from a terminal when it happens.

[StoneCold]

Thanks for the suggestion. Was waiting for it to happen again and it helped. Any idea why this is happening? Any permanent fixes?

[FameWolf]

I haven’t a clue but I’ve had to restart it several times…both when the panel at the bottom would stop auto hiding (I eventually removed it and installed crystal dock) or when like you the entire thing would freeze but I could restart the system via ctrl alt f4 or logging in via ssh (disabled by default so enabled/started the sshd service).

This is untested but you can try the following workaround:

Here’s a Bash script to monitor the KDE Plasma-plasmashell service and restart it if it becomes unresponsive:

#!/bin/bash

while true; do
  # Check if the service is running
  service plasma-plasmashell status > /dev/null 2>&1
  if [[ $? -eq 0 ]]; then
    echo "KDE Plasma Shell is already running."
  else
    # Restart the service
    systemctl restart plasma-plasmashell
  fi

  sleep 10
done

Monitoring KDE Plasma-plasmashell Service with Bash Script

This script monitors the plasma-plasmashell service and restarts it if it becomes unresponsive. It's designed to run continuously in the background, ensuring your Plasma desktop environment stays up and running smoothly.

Here's how it works:

1. Script: The code is stored in a file named plasma_monitor.sh.
2. Service Check: The script uses the service command to check if the service is currently active (status). It captures any output from this command and stores it for later use.
3. Restarting the Service: If the service isn't running, the script restarts it using systemctl restart plasma-plasmashell. This ensures your Plasma environment remains operational.
4. Background Execution: The loop continues indefinitely (while true; do ... done), ensuring that the script is always checking for the status of the service and restarting if necessary.

How to Use:

1. Save the code as plasma_monitor.sh.
2. Make it executable: chmod +x plasma_monitor.sh.
3. Run the script in the background: ./plasma_monitor.sh & (This runs the script and keeps it running even after you close your terminal)

Key Points:

* Continuous Monitoring: The script continuously checks for service status, ensuring a reliable experience.
* Automatic Restarting: If the Plasma-plasmashell service becomes unresponsive, it's automatically restarted to keep things working smoothly.

[StoneCold]

Thank you very much for this handy script. I was about to mark this solved as it has helped a lot but somehow it has gotten worse and not even the script/command work anymore to unfreeze the system.

It started happening more often and sometimes almost a few minutes into normal usage. I reckon an update caused the command not to work properly so I will try to rollback and investigate. Will keep you updated.

[FameWolf]

Try the lts kernel and see if the issue still happens (as often?). I’ve prevented my pc from going to sleep which has stopped some of the freezes that occured after coming out of sleep. Note that each time the desktop freezes if you kill the plasmashell it resets the “block” you put on sleep so you have to do so again. (when you click the battery icon it gives a “manually block” option for sleep.)