Garuda KDE doesn't shutdown or reboot properly

This is such an annoying bug because it’s not always consistent. It comes around once in a while. This bug has followed me from my previous laptop into my new laptop. It just freezes when I press shutdown and I have to manually press the power button to shutdown, the fans start ramping up too. Even when I try reboot directly from the terminal, it sometimes stop in the process of rebooting and freezes. I have checked journalctl and it doesn’t yield any culprits either.

garuda-inxi:

System:
Kernel: 6.10.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=6de1dd91-b470-4769-a1e9-494d87b1146c rw rootflags=subvol=@
loglevel=3 nvidia_drm.modeset=1 nvidia_drm.fbdev=1 ibt=off
Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_wayland with: polybar vt: 1 dm: SDDM Distro: Garuda
base: Arch Linux
Machine:
Type: Laptop System: TUXEDO product: TUXEDO Stellaris Intel Gen5 v: Standard
serial: <superuser required>
Mobo: NB02 model: GMxPXxx v: Standard serial: <superuser required>
part-nu: STELLARIS1XI05 uuid: <superuser required> UEFI: American
Megatrends LLC. v: N.1.09A12 date: 09/25/2023
Battery:
ID-1: BAT0 charge: 99.2 Wh (100.0%) condition: 99.2/99.2 Wh (100.0%)
volts: 17.2 min: 15.5 model: standard type: Li-ion serial: <filter>
status: full
CPU:
Info: model: 13th Gen Intel Core i9-13900HX bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x123
Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 881 high: 1124 min/max: 800/5200:5400:3900 scaling:
driver: intel_pstate governor: powersave cores: 1: 1100 2: 852 3: 1036
4: 800 5: 1029 6: 1088 7: 955 8: 800 9: 1023 10: 800 11: 1124 12: 800
13: 1046 14: 800 15: 1048 16: 1091 17: 800 18: 799 19: 800 20: 800 21: 800
22: 801 23: 800 24: 800 25: 800 26: 800 27: 801 28: 800 29: 800 30: 800
31: 800 32: 800 bogomips: 154828
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: Tongfang Hongkong
driver: i915 v: kernel alternate: xe arch: Gen-13 process: Intel 7 (10nm)
built: 2022+ ports: active: eDP-2 empty: DP-3, DP-4, HDMI-A-2, HDMI-A-3,
HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0 chip-ID: 8086:a788 class-ID: 0300
Device-2: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile]
vendor: Tongfang Hongkong driver: nvidia v: 555.58.02
alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
ports: active: none empty: DP-1, DP-2, HDMI-A-1, eDP-1 bus-ID: 01:00.0
chip-ID: 10de:2860 class-ID: 0300
Device-3: SunplusIT FHD Webcam driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 2b7e:c664
class-ID: 0e02 serial: <filter>
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris gpu: i915
display-ID: 0
Monitor-1: eDP-2 model: BOE Display 0x0a99 built: 2021 res: 2560x1600
dpi: 181 gamma: 1.2 size: 366x229mm (14.41x9.02") diag: 422mm (16.6")
ratio: 16:10 modes: 2560x1600
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.4-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788 memory: 15.17 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 11 device: 0 type: integrated-gpu
name: Intel Graphics (RPL-S) driver: mesa intel v: 24.1.4-arch1.2
device-ID: 8086:a788 surfaces: xcb,xlib,wayland device: 1
type: discrete-gpu name: NVIDIA GeForce RTX 4070 Laptop GPU driver: nvidia
v: 555.58.02 device-ID: 10de:2860 surfaces: xcb,xlib,wayland device: 2
type: cpu name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
v: 24.1.4-arch1.2 (LLVM 18.1.8) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Tongfang Hongkong
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA AD106M High Definition Audio vendor: Tongfang Hongkong
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 10de:22bd class-ID: 0403
API: ALSA v: k6.10.2-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.1 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 Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Tongfang Hongkong driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 3a:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp58s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-39d5bcdee49f state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
IF-ID-3: virbr0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:6 chip-ID: 8087:0033
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 sub-v: 3678 hci-v: 12 rev: 3678 class-ID: 6c010c
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: peripheral accept service-classes: rendering, capturing, audio,
telephony
Drives:
Local Storage: total: 3.18 TiB used: 1.53 TiB (48.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung model: SSD 980 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 3B4QFXO7 temp: 41.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B4QFXO7 temp: 35.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000P3SSD8
size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.2
spd: 10 Gb/s lanes: 1 mode: 3.2 gen-2x1 tech: SSD serial: <filter>
fw-rev: 1.00 scheme: GPT
Partition:
ID-1: / raw-size: 224.52 GiB size: 224.52 GiB (100.00%)
used: 148 GiB (65.9%) fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:8
ID-2: /boot/efi raw-size: 558.9 MiB size: 557.8 MiB (99.80%)
used: 612 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p5 maj-min: 259:6
ID-3: /home raw-size: 224.52 GiB size: 224.52 GiB (100.00%)
used: 148 GiB (65.9%) fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:8
ID-4: /var/log raw-size: 224.52 GiB size: 224.52 GiB (100.00%)
used: 148 GiB (65.9%) fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:8
ID-5: /var/tmp raw-size: 224.52 GiB size: 224.52 GiB (100.00%)
used: 148 GiB (65.9%) fs: btrfs dev: /dev/nvme1n1p7 maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.08 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
ID-2: swap-2 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p6 maj-min: 259:7
Sensors:
System Temperatures: cpu: 51.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 31.08 GiB used: 4.82 GiB (15.5%)
Processes: 525 Power: uptime: 12m states: freeze,mem,disk suspend: s2idle
avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.39 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 2133 libs: 560
tools: octopi,paru Compilers: clang: 18.1.8 gcc: 14.1.1 Shell: garuda-inxi
default: Zsh v: 5.9 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2023-12-12
Last full system update: 2024-08-01
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Here is the output of journalctl -b -1 when I tried to shutdown:

Aug 01 08:14:26 stellaris wpa_supplicant[1454]: wlo1: PMKSA-CACHE-ADDED c4:b2:39:0d:40:42 0
Aug 01 08:14:45 stellaris brave[6581]: [6581:6581:0801/081445.759813:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_WyTJioiyHW4", source: chrome-extension://mnojpmjd>
Aug 01 08:14:45 stellaris brave[6581]: [6581:6581:0801/081445.760016:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_WyTJioiyHW4", source: chrome-extension://mnojpmjd>
Aug 01 08:14:46 stellaris brave[6581]: [6581:6581:0801/081446.564908:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_2JDYSEheXHU", source: chrome-extension://mnojpmjd>
Aug 01 08:14:46 stellaris brave[6581]: [6581:6581:0801/081446.565229:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_2JDYSEheXHU", source: chrome-extension://mnojpmjd>
Aug 01 08:15:03 stellaris systemd[1]: snapperd.service: Deactivated successfully.
Aug 01 08:15:35 stellaris systemd[2429]: Reached target Bluetooth.
Aug 01 08:15:36 stellaris wireplumber[2886]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+BTRH?
Aug 01 08:15:36 stellaris kernel: input: MOMENTUM 4 (AVRCP) as /devices/virtual/input/input26
Aug 01 08:15:37 stellaris (udev-worker)[87354]: input26: Process '/bin/input-remapper-control --command autoload --device ' failed with exit code 2.
Aug 01 08:15:37 stellaris (udev-worker)[87354]: event22: Process '/bin/input-remapper-control --command autoload --device /dev/input/event22' failed with exit code 5.
Aug 01 08:15:37 stellaris systemd-logind[1323]: Watching system buttons on /dev/input/event22 (MOMENTUM 4 (AVRCP))
Aug 01 08:15:38 stellaris bluetoothd[1312]: /org/bluez/hci0/dev_80_C3_BA_1F_90_D6/fd0: fd(32) ready
Aug 01 08:15:39 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:15:43 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:15:44 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:19:04 stellaris systemd[1]: Starting Cleanup of Temporary Directories...
Aug 01 08:19:04 stellaris systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Aug 01 08:19:04 stellaris systemd[1]: Finished Cleanup of Temporary Directories.
Aug 01 08:19:04 stellaris systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Aug 01 08:19:05 stellaris mullvad-daemon[1453]: [mullvad_daemon::api_address_updater][DEBUG] Fetched new API address 45.83.223.196:443. Fetching again in 24 hours
Aug 01 08:20:52 stellaris wpa_supplicant[1454]: wlo1: RSN: Group rekeying completed with a4:b4:39:f6:e8:ad [GTK=CCMP]
Aug 01 08:24:36 stellaris wpa_supplicant[1454]: wlo1: PMKSA-CACHE-ADDED 5c:e1:76:df:41:22 0
Aug 01 08:27:52 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:27:55 stellaris kwin_wayland[2650]: file:///home/rishin/.local/share/kwin/scripts/polonium/contents/code/main.mjs:2739: TypeError: Value is undefined and could not be converted to an object
Aug 01 08:27:55 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:28:31 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Aug 01 08:28:53 stellaris brave[6581]: [6581:6581:0801/082853.007250:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_vdd_Lk5-St4", source: chrome-extension://mnojpmjd>
Aug 01 08:28:53 stellaris brave[6581]: [6581:6581:0801/082853.007495:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_vdd_Lk5-St4", source: chrome-extension://mnojpmjd>
Aug 01 08:28:53 stellaris brave[6581]: [6581:6581:0801/082853.246175:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_vdd_Lk5-St4", source: chrome-extension://mnojpmjd>
Aug 01 08:28:53 stellaris brave[6581]: [6581:6581:0801/082853.246214:ERROR:CONSOLE(1)] "Failed to handle media duration metadata: missing publisher key for media key youtube_vdd_Lk5-St4", source: chrome-extension://mnojpmjd>
Aug 01 08:34:23 stellaris NetworkManager[1309]: <info>  [1722497663.8103] dhcp4 (wlo1): state changed new lease, address=172.25.42.73
Aug 01 08:34:23 stellaris systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 01 08:34:23 stellaris systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 01 08:34:33 stellaris systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Aug 01 08:34:44 stellaris fcitx5[2962]: I2024-08-01 08:34:44.191918 instance.cpp:1222] Running autosave...
Aug 01 08:34:44 stellaris fcitx5[2962]: I2024-08-01 08:34:44.206637 instance.cpp:1224] End autosave
Aug 01 08:36:44 stellaris plasmashell[3111]: The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.

The cached device pixel ratio error doesn’t seem to be the culprit because the error appears even when I was using the system normally. I am using Nvidia with Wayland but this error existed even with Nvidia with Xorg. When I switched to wayland, I thought this issue was somewhat mitigated but that doesn’t seem to be the case.

Have you tried using nvidia-open-dkms? Nvidia recently recommend all Turing (20-series cards) and later use them going forward. This has seemed to solve a similar sounding issue here:

Be sure to also read the post that comes after the marked solution since you are using a laptop system as well.

Another related thread that might have some useful information regarding nvidia-open-dkms :

1 Like

Ok, thanks for the help. I will let you know how this pans out. Since this issue is so inconsistent it’ll take a while for me to know the results.

1 Like

Yeah, Switching to nvidia-open-dkms did solve the issue of system crashing when shutting down, but NVIDIA introduced some new issues in the latest version of the drivers for people that were using wayland and an external monitor connected to the dGPU.
Long story short, I ended up switching to nvidia-535xx-dkms. This version seems the most stable. I had to do some tweaking with flatseal to run some flatpak applications that needed GPU acceleration to stop some apps from crashing on wayland. I have only been using it for two days and I am still in the testing phase, but I have not experienced any crash yet.

1 Like

Any further details on the flatseal thing?

I have had an absolutely terrible time with plasma + NVIDIA lately.

It’s just a GUI to control variables for flatpaks. If you’re not using flatpak, you don’t need it.

This problem has been annoying me , it appeared after the last plasma update, laptop never shuts down, have to hit the power off button on the laptop.

Did you try

?

2 Likes

I’m on AMD cpu, and its already set to , start with an empty session, so not sure here…

I did the opposite, last log out, just performed first clean shutdown in weeks, thanks for this

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