Desktop Non-Functional After Killing Plasma-Workspace and Restarting

Issues & Assistance Unsupported Software (AUR & Other)
1

Greetings,

So, I was messing around with customizing my panels and noticed that the bar graph no longer loads for total cpu usage in the panel properly so I tried various other chart styles. Upon loading the process table chart style, the config menu froze and I was prompted to end or wait for the plasma-workspace process. I didn’t see the harm in doing so until when I later rebooted and now things don’t work properly. I can still open apps, but the desktop doesn’t otherwise function. From what I have read it seems that plasma-workspace will not automatically restart if killed for some reason. I have tried restarting it myself to no avail. Any help would be appreciated. I would rather not have to recustomize everything again. (NOTE: this issue persists even when using snapper to reload an earlier snapshot).
garuda-inxi:

System:
  Kernel: 6.9.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/.snapshots/1570/snapshot/boot/vmlinuz-linux-zen
    root=UUID=acc91bbd-51b8-4669-9368-f85ecd75b0a1 rd.udev.log_priority=3
    vt.global_cursor_default=0
    resume=UUID=5bb1f004-d544-4ddf-bfac-8a1cf21296d8 loglevel=3
    nvidia-drm.modeset=1 ibt=off
    rootflags=defaults,noatime,compress=zstd,subvol=@/.snapshots/1570/snapshot
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.2.0
    wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: ThinkPad W541 v: 1.0
    serial: <superuser required> Chassis: type: 9 serial: <superuser required>
  Mobo: LENOVO model: ThinkPad W541 v: 1.0 serial: <superuser required>
    BIOS: coreboot v: 4.20-410-g3e523b495c date: 06/17/2023
CPU:
  Info: model: Intel Core i7-4710MQ bits: 64 type: MT MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 3446 high: 3500 min/max: 800/3500 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 3385 2: 3331 3: 3500
    4: 3500 5: 3393 6: 3500 7: 3462 8: 3500 bogomips: 39909
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo
    driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports:
    active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0416 class-ID: 0300
  Device-2: NVIDIA GK107GLM [Quadro K1100M] vendor: Lenovo driver: nvidia
    v: 470.239.06 alternate: nouveau,nvidia_drm non-free: series: 470.xx+
    status: legacy-active (EOL~2024-09-xx) arch: Kepler code: GKxxx
    process: TSMC 28nm built: 2012-2018 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none empty: DP-3
    bus-ID: 01:00.0 chip-ID: 10de:0ff6 class-ID: 0300
  Device-3: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-12:4 chip-ID: 5986:026a
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: crocus
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: AU Optronics 0x34ed built: 2012 res: 1920x1080
    hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: crocus device: 3 drv: swrast gbm: drv: crocus
    surfaceless: drv: crocus x11: drv: crocus inactive: wayland,device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.0-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4600 (HSW
    GT2) device-ID: 8086:0416 memory: 1.46 GiB unified: yes
  API: Vulkan v: 1.3.279 layers: 4 device: 0 type: integrated-gpu name: Intel
    HD Graphics 4600 (HSW GT2) driver: mesa intel v: 24.1.0-arch1.1
    device-ID: 8086:0416 surfaces: xcb,xlib device: 1 type: discrete-gpu
    name: Quadro K1100M driver: nvidia v: 470.239.06 device-ID: 10de:0ff6
    surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe (LLVM 17.0.6 256
    bits) driver: mesa llvmpipe v: 24.1.0-arch1.1 (LLVM 17.0.6)
    device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-3: NVIDIA GK107 HDMI Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:0e1b class-ID: 0403
  API: ALSA v: k6.9.2-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.7 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: Intel Ethernet I217-LM driver: N/A modules: e1000e port: 1040
    bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:08b2 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-11:3 chip-ID: 8087:07dc
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 931.51 GiB used: 31.16 GiB (3.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 3B6Q scheme: MBR
Partition:
  ID-1: /home raw-size: 914.37 GiB size: 914.37 GiB (100.00%)
    used: 31.16 GiB (3.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-2: /var/log raw-size: 914.37 GiB size: 914.37 GiB (100.00%)
    used: 31.16 GiB (3.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
  ID-3: /var/tmp raw-size: 914.37 GiB size: 914.37 GiB (100.00%)
    used: 31.16 GiB (3.4%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.58 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.14 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
  System Temperatures: cpu: 64.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.58 GiB used: 4.12 GiB (26.4%)
  Processes: 273 Power: uptime: 6m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 0 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 6.18 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd
    v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1951 libs: 442 tools: octopi,paru pm: flatpak
    pkgs: 0 Compilers: clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi
    default: Bash v: 5.2.26 running-in: ghostty inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2023-12-07
  Last full system update: 2024-05-31
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       <superuser required>
  Failed units:            systemd-remount-fs.service
2

Found a solution:

Delete the offending panel widget directly from ~/.config/plasma-org.kde.plasma.desktop-appletsrc. Make sure to remove all relevant sections with the same applet id. I think something is really broken with some of the widgets currently, though I can only be certain of the bar graph and process chart options for the individual core usage widget.

2 Likes
3

Ran in to this non usable desktop a couple of weeks back because of a widget I wanted to test. I just rolled back the system during boot.

4

I had tried to do the same, but the reboot process would hard freeze and the rollback wouldn’t take (at least, it doesn’t roll back userspace widgets)

5

You either didn’t go back to before you added the widget (hence why I truly hate snaphots taken after updates are done), or your snapshots are broken.

6

Restoring a snapshot of the root subvolume should not touch anything in the home subvolume. Configurations in ~/.config will be intact after rebooting from the snapshot restoration.

You can set up a separate Snapper config for the home subvolume to take snapshots of it as well, but it is not configured by default. In this case, I think the post marked as the solution is correct.

Test restoring a snapshot from Btrfs Assistant from a “normal” boot (not booting into a snapshot overlay from Grub).

For example, install an application, then restore the “pre-installation” snapshot from Btrfs Assistant immediately afterward and reboot to confirm the snapshots are working normally (after rebooting, the new application should be gone).

7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.