Plasmashell not loading on Wayland after nVidia 535 update

System:
Kernel: 6.4.11-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=799d91f8-68f8-4174-bb7e-25031dc3fba3 rw rootflags=subvol=@
quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
libata.force=noncq nvidia-drm.modeset=1 sysrq_always_enabled=1
resume=UUID=4ddecf56-e123-41a2-8712-9d84b140542d ibt=off
Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: Z97N-WIFI v: x.x
serial: <superuser required> UEFI: American Megatrends v: F7
date: 09/18/2015
CPU:
Info: model: Intel Core i7-4790K 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: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 4381 high: 4400 min/max: 800/4400 scaling:
driver: intel_cpufreq governor: performance cores: 1: 4399 2: 4400 3: 4400
4: 4400 5: 4400 6: 4400 7: 4331 8: 4322 bogomips: 64001
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti] vendor: Gigabyte driver: nvidia
v: 535.98 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-08) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: none
off: DP-1,DP-2,HDMI-A-1 empty: HDMI-A-2 bus-ID: 01:00.0 chip-ID: 10de:2486
class-ID: 0300
Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4.3.3:9
chip-ID: 045e:0779 class-ID: 0102
Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.0
compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia
d-rect: 5548x4231 display-ID: 0
Monitor-1: DP-1 pos: top-right res: 912x1623 size: N/A modes: N/A
Monitor-2: DP-2 pos: bottom-c res: 2560x1440 size: N/A modes: N/A
Monitor-3: HDMI-A-1 pos: middle-l res: 2076x1168 size: N/A modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.98 renderer: NVIDIA GeForce RTX 3060
Ti/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GA104 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228b
class-ID: 0403
Device-2: GYROCOM C&C Fiio E10 driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4.2:6
chip-ID: 1852:7022 class-ID: 0102
Device-3: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4.3.3:9
chip-ID: 045e:0779 class-ID: 0102
Device-4: Realtek Audio USB driver: snd-usb-audio type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4.3.4:10 chip-ID: 0bda:4938
class-ID: 0102 serial: <filter>
API: ALSA v: k6.4.11-zen2-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.77 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-V vendor: Gigabyte driver: e1000e v: kernel
port: f040 bus-ID: 00:19.0 chip-ID: 8086:153b class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:08b1 class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Device-4: Microsoft Xbox Wireless Adapter for Windows driver: mt76x2u
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3
chip-ID: 045e:02e6 class-ID: 0000 serial: <filter>
IF: wlp0s20u5 state: down mac: <filter>
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:5 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: 7c0104
Drives:
Local Storage: total: 2.17 TiB used: 294.02 GiB (13.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 045 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Transcend model: TS128GSSD370
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0516 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung
model: SSD PM830 2.5 7mm 256GB size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 3D1Q
scheme: GPT
Partition:
ID-1: / raw-size: 101.84 GiB size: 101.84 GiB (100.00%)
used: 74.95 GiB (73.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 580 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 101.84 GiB size: 101.84 GiB (100.00%)
used: 74.95 GiB (73.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 101.84 GiB size: 101.84 GiB (100.00%)
used: 74.95 GiB (73.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 101.84 GiB size: 101.84 GiB (100.00%)
used: 74.95 GiB (73.6%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.54 GiB used: 146 MiB (0.9%) 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.11 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdb3 maj-min: 8:19
Sensors:
System Temperatures: cpu: 64.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 281 Uptime: 6h 44m wakeups: 0 Memory: total: 16 GiB
available: 15.54 GiB used: 4.84 GiB (31.1%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1678 libs: 400 tools: gnome-software,octopi,pamac,paru
Shell: fish v: 3.6.1 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.29
Garuda (2.6.16-1):
System install date:     2022-10-11
Last full system update: 2023-08-20
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)

Ever since the nVidia 535 update, wayland wouldn’t login.
There would be a black screen and the mouse pointer would leave a trail when moved.
I never bothered troubleshooting and kept using X11.
But after the recent minor update in driver. I had a go again, only to realise that Krunner was actually working and was able to get things running. I soon figured that restarting plasma

plasmashell --replace

actually gets it to work again.

Is there a way to troubleshoot why plasma crashes on login only the first time.
Also note this line

journalctl -b 0 --grep “plasmashell”

Aug 21 09:45:29 DevBox dbus-daemon[23636]: [session uid=1000 pid=23636] Successfully activated service 'org.kde.ActivityManager'
Aug 21 09:45:29 DevBox systemd[23598]: Started KActivityManager Activity manager Service.
Aug 21 09:45:29 DevBox plasmashell[26469]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 21 09:45:29 DevBox plasmashell[26469]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Aug 21 09:45:29 DevBox plasmashell[26469]: kf.plasma.quick: Applet preload policy set to 1
Aug 21 09:45:30 DevBox systemd[23598]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 09:45:30 DevBox systemd[23598]: plasma-plasmashell.service: Failed with result 'exit-code'.

journalctl -b 0 --grep “kactivitymanager”

Aug 21 09:42:16 DevBox dbus-daemon[2257]: [session uid=1000 pid=2257] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.23' (uid=1000 pid=2928 comm="/usr/bin/plasmashell --no-respawn")
Aug 21 09:42:16 DevBox systemd[2167]: Starting KActivityManager Activity manager Service...
Aug 21 09:42:17 DevBox plasmashell[2928]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 21 09:42:17 DevBox systemd[2167]: Started KActivityManager Activity manager Service.
Aug 21 09:42:17 DevBox plasmashell[2928]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 21 09:45:13 DevBox systemd[2167]: Stopped KActivityManager Activity manager Service.
Aug 21 09:45:29 DevBox dbus-daemon[23636]: [session uid=1000 pid=23636] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.22' (uid=1000 pid=26469 comm="/usr/bin/plasmashell --no-respa>
Aug 21 09:45:29 DevBox systemd[23598]: Starting KActivityManager Activity manager Service...
Aug 21 09:45:29 DevBox plasmashell[26469]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 21 09:45:29 DevBox systemd[23598]: Started KActivityManager Activity manager Service.
Aug 21 09:45:29 DevBox plasmashell[26469]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 21 09:45:30 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 09:45:30 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Aug 21 09:45:31 DevBox dbus-daemon[23636]: [session uid=1000 pid=23636] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.64' (uid=1000 pid=26816 comm="/usr/lib/org_kde_powerdevil")
Aug 21 09:45:31 DevBox systemd[23598]: Starting KActivityManager Activity manager Service...
Aug 21 09:45:31 DevBox systemd[23598]: Started KActivityManager Activity manager Service.
Aug 21 09:45:33 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 09:45:33 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Aug 21 09:45:34 DevBox dbus-daemon[23636]: [session uid=1000 pid=23636] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.92' (uid=1000 pid=27104 comm="/usr/lib/org_kde_powerdevil")
Aug 21 09:45:34 DevBox systemd[23598]: Starting KActivityManager Activity manager Service...
Aug 21 09:45:34 DevBox systemd[23598]: Started KActivityManager Activity manager Service.
Aug 21 09:45:36 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 09:45:36 DevBox systemd[23598]: plasma-kactivitymanagerd.service: Failed with result 'exit-code'.
Aug 21 09:45:37 DevBox dbus-daemon[23636]: [session uid=1000 pid=23636] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.116' (uid=1000 pid=27374 comm="/usr/lib/org_kde_powerdevil")
Aug 21 09:45:37 DevBox systemd[23598]: Starting KActivityManager Activity manager Service...
Aug 21 09:45:37 DevBox systemd[23598]: Started KActivityManager Activity manager Service.

I’m a bit of a novice here and I don’t understand what is going on. Can someone give me an explanation.

Also there weren’t any issues like this on the previous nVidia driver version. This issue began late last year when the driver version changed from 525.xx to 535.xx

Thanks for any inputs.

Anyone ?
Is it okay to bump a thread ?

no, no

1 Like

Maybe there is a bug in that driver. Try using the LTS kernel for now and see how it goes.

1 Like

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