KDE/Latte not launching properly after `garuda-update` + reboot

My desktop environment, dragonized, broke after garuda-update, Latte is not working either:

Latte icon shows the following error when I press on it:

file:///usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml:17:1: plugin cannot be loaded for module "org.kde.plasma.private.taskmanager": Cannot load library /usr/lib/qt/qml/org/kde/plasma/private/taskmanager/libtaskmanagerplugin.so: (/usr/lib/libprocesscore.so.9: file too short)

I had to launch my applications through the start-menu, which luckily still works.

inxi:

╰─λ garuda-inxi
System:
Kernel: 6.0.1-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=cd218c4a-cd87-436a-a31d-1f94c11b73ca rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=9a65ace2-c064-49fe-a16d-7da701bbdb7d loglevel=3 ibt=off
systemd.unified_cgroup_hierarchy=1
Desktop: KDE Plasma v: 5.26.0 tk: Qt v: 5.15.6 info: latte-dock vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B350-F GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 6042
date: 04/28/2022
CPU:
Info: model: AMD Ryzen 7 1700 bits: 64 type: MT MCP arch: Zen level: v3
note: check built: 2017-19 process: GF 14nm family: 0x17 (23) model-id: 1
stepping: 1 microcode: 0x8001138
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 2831 high: 3197 min/max: 1550/3000 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 2558 2: 3109
3: 2739 4: 2557 5: 2573 6: 3000 7: 3197 8: 3000 9: 3000 10: 3000 11: 2578
12: 3000 13: 2561 14: 2687 15: 2553 16: 3184 bogomips: 95816
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: eVga.com.
driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-10) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 07:00.0 chip-ID: 10de:1b06 class-ID: 0300
Device-2: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-5:3 chip-ID: 046d:0843 class-ID: 0102
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X:
loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 109 s-size: 802x333mm (31.57x13.11")
s-diag: 868mm (34.19")
Monitor-1: DP-2 res: 3440x1440 dpi: 109 size: 800x330mm (31.5x12.99")
diag: 865mm (34.07") modes: N/A
OpenGL: renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06 direct render: Yes
Audio:
Device-1: NVIDIA GP102 HDMI Audio vendor: eVga.com. driver: snd_hda_intel
bus-ID: 1-5:3 v: kernel pcie: chip-ID: 046d:0843 gen: 3 class-ID: 0102
speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 10de:10ef class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 09:00.3
chip-ID: 1022:1457 class-ID: 0403
Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
Device-4: SAVITECH JDS Labs Element DAC type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-3:2 chip-ID: 262a:1048
class-ID: 0102
Sound API: ALSA v: k6.0.1-zen2-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-e102d34c0b28 state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-2: docker0 state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-3: veth1812dc9 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-4: veth2895b67 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-5: veth82c9c50 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-6: vethaec8be2 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-7: vethba6cb55 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-8: vethbee0af9 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-9: vetheda49e7 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-10: virbr0 state: down mac: <filter>
IF-ID-11: virbr1 state: down mac: <filter>
RAID:
Supported mdraid levels: raid0
Device-1: md0 maj-min: 9:0 type: mdraid level: raid-0 status: active
size: 849.75 GiB
Info: report: N/A blocks: 891025408 chunk-size: 512k super-blocks: 1.2
Components: Online:
0: sdb1 maj-min: 8:17 size: 425 GiB
1: sdc1 maj-min: 8:33 size: 425 GiB
Drives:
Local Storage: total: 2.54 TiB used: 1017.14 GiB (39.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 950 PRO
512GB size: 476.94 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B0QBXX7
temp: 42.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:9 vendor: Samsung model: SSD 960 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 3B7QCXE7
temp: 27.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT525MX300SSD1
size: 489.05 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: R060 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q scheme: GPT
Partition:
ID-1: / raw-size: 121.64 GiB size: 121.64 GiB (100.00%) used: 114.96 GiB
(94.5%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 596 KiB
(0.2%) fs: vfat dev: /dev/nvme0n1p8 maj-min: 259:8
ID-3: /home raw-size: 250.86 GiB size: 250.86 GiB (100.00%) used: 75.74
GiB (30.2%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-4: /var/log raw-size: 121.64 GiB size: 121.64 GiB (100.00%) used: 114.96
GiB (94.5%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-5: /var/tmp raw-size: 121.64 GiB size: 121.64 GiB (100.00%) used: 114.96
GiB (94.5%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.53 GiB used: 770.5 MiB (4.8%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 7.91 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p5 maj-min: 259:5
Sensors:
System Temperatures: cpu: 38.4 C mobo: 32.0 C gpu: nvidia temp: 40 C
Fan Speeds (RPM): cpu: 291 fan-2: 260 fan-3: 254 fan-4: 272 fan-6: 0
gpu: nvidia fan: 17%
Power: 12v: N/A 5v: N/A 3.3v: 3.31 vbat: 3.27
Info:
Processes: 513 Uptime: 4m wakeups: 0 Memory: 15.53 GiB used: 6.19 GiB
(39.8%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: pm: pacman pkgs: 2078
libs: 549 tools: octopi,paru Shell: fish v: 3.5.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-04-08
Last full system update: 2022-10-14
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:            shadow.service
2 Likes

I would like to report a similar problem, after the latest kernel update latte dock is crashing on start and need to manually start it. My whole desktop gets messed up.
When I return a snapshot before the kernel update there are no issues.

1 Like

Could you give the updated package a try?

1 Like

Same results after garuda update and a reboot on my end.

Sad. I can't reproduce the problem locally :confused: It might also be due to using plasma-git tho.

libprocesscore.so.9 is owned by ksysguard, might try to reinstall that package since it clearly seems to be an issue with that shared library :eyes:

1 Like
Application: Latte Dock (latte-dock), signal: Segmentation fault

[KCrash Handler]
#4  0x00005642a51fa0a3 in  ()
#5  0x00005642a5210925 in  ()
#6  0x00005642a5210a61 in  ()
#7  0x00005642a5210b45 in  ()
#8  0x00005642a5210bdd in  ()
#9  0x00005642a51192c7 in  ()
#10 0x00005642a5143946 in  ()
#11 0x00005642a5143ac5 in  ()
#12 0x00007fb560154381 in  () at /usr/lib/libQt5Core.so.5
#13 0x00007fb5601259ff in QCoreApplication::aboutToQuit(QCoreApplication::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#14 0x00007fb560125a62 in QCoreApplicationPrivate::execCleanup() () at /usr/lib/libQt5Core.so.5
#15 0x00007fb560126e72 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#16 0x00005642a50b9fae in  ()
#17 0x00007fb55f9b4290 in  () at /usr/lib/libc.so.6
#18 0x00007fb55f9b434a in __libc_start_main () at /usr/lib/libc.so.6
#19 0x00005642a50c18b5 in  ()
[Inferior 1 (process 4181) detached]

This ^^^ is something you should definitely investigate.

Also try implementing a three second delay starting Latte dock at login

1 Like

This ^^^ is something you should definitely investigate.

Will look into it, thanks.

Also try implementing a three second delay starting Latte dock at login

Are you saying this should be default? Or something I should try locally? Both? How do I do it?

Got this:

╭─[email protected] in ~ via  v18.11.0
╰─λ systemctl status shadow.service
○ shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: inactive (dead)
TriggeredBy: ● shadow.timer

╭─[email protected] in ~ via  v18.11.0 took 21ms
[🔴] × systemctl status shadow.service
○ shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: inactive (dead)
TriggeredBy: ● shadow.timer

╭─[email protected] in ~ via  v18.11.0 took 8ms
[🔴] × systemctl start shadow.service
ca⏎                                                                                                           
╭─[email protected] in ~ via  v18.11.0 took 5s
╰─λ systemctl status shadow.service
× shadow.service - Verify integrity of password and group files
Loaded: loaded (/usr/lib/systemd/system/shadow.service; static)
Active: failed (Result: exit-code) since Sat 2022-10-15 19:39:30 CEST; 5s ago
Duration: 13ms
TriggeredBy: ● shadow.timer
Process: 15232 ExecStart=/bin/sh -c /usr/bin/pwck -r || r=1; /usr/bin/grpck -r && exit $r (code=exited, s>
Main PID: 15232 (code=exited, status=1/FAILURE)
CPU: 7ms

Oct 15 19:39:30 Pyramidal systemd[1]: Started Verify integrity of password and group files.
Oct 15 19:39:30 Pyramidal sh[15237]: user 'ntp': directory '/var/lib/ntp' does not exist
Oct 15 19:39:30 Pyramidal sh[15237]: pwck: no changes
Oct 15 19:39:30 Pyramidal systemd[1]: shadow.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 19:39:30 Pyramidal systemd[1]: shadow.service: Failed with result 'exit-code'.

Do you think the issue is in here?

I am not using plasma-git, which is an AUR package

This was more for the users comment below:

This is a known fix for Latte crashing at startup. You simply add sleep 3 at the beggining of Latte's startup script. However, this sounds like a different issue than you are experiencing.

Have you tried a system rollback using a snapshot yet?

If that is successful, then try a full system upgrade afterwards to see if anything improves.

This would seem to be a big concern as "shadow" is a huge part of the authentication process for access rights/user credentials.

1 Like

Yes I tried a system rollback and than full system upgrade afterwords an situation is the same.
This is why I assumed that the problem lies in the latest kernel.
I also think my issue is different, since latte is starting but it seems very broken, I need to kill it and start it again and after I do this it's fixed.
By broken I mean that some texts are missing from the start menu, title bars are missing on the windows, it's strange.
Should I try to open a new post about this in order to not mix the problems ?