Latte Dock unmaintained

Hi there

I've been noticing some instability and high cpu usage from latte-dock. I've installed aur/latte-dock-git which I believe builds it from the latest commit to the git repo and this has improved it somewhat.

The reason for my posting is that I have found out that latte-dock is now unmaintained. I was wondering if the garuda community would have anyone interested in stepping up to be its maintainer, due to it being a core component of the garuda dragonized desktop layout?


garuda-inxi below (though not really relevant)

Kernel: 6.0.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=a482c594-4d61-4743-9ab9-09fb9704b827 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=d99f068c-64e6-4bce-80fd-072d05bfe0c5 loglevel=3
nvidia-drm.modeset=1 mitigations=off
Desktop: KDE Plasma v: 5.26.1 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_wayland vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 4403
date: 04/27/2022
Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 4142 high: 4284 min/max: 2200/4672 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4284 2: 4275
3: 4203 4: 4272 5: 4274 6: 4275 7: 3800 8: 3800 9: 4270 10: 4275 11: 3800
12: 4275 13: 3800 14: 3800 15: 4271 16: 4275 17: 4269 18: 4274 19: 4275
20: 4125 21: 4178 22: 3800 23: 4266 24: 4280 bogomips: 182418
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
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 status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 status: Vulnerable: __user pointer sanitization and
usercopy barriers only; no swapgs barriers
Type: spectre_v2 status: Vulnerable, IBPB: disabled, STIBP: disabled,
PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: NVIDIA GA102 [GeForce RTX 3090] driver: nvidia v: 520.56.06
alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current (as of
2022-10) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22
pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
off: DP-1,DP-2,DP-3 empty: HDMI-A-1 bus-ID: 09:00.0 chip-ID: 10de:2204
class-ID: 0300
Device-2: ASUSTek GC21 Video type: USB driver: uvcvideo bus-ID: 3-1.1:4
chip-ID: 0b05:9d08 class-ID: 0e02 serial: <filter>
Display: wayland server: v: with: Xwayland v: 22.1.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 11520x2160
display-ID: 0
Monitor-1: DP-1 pos: primary,left res: 3840x2160 size: N/A modes: N/A
Monitor-2: DP-2 pos: center res: 3840x2160 size: N/A modes: N/A
Monitor-3: DP-3 pos: right res: 3840x2160 size: N/A modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 3090/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06 direct render: Yes
Device-1: NVIDIA GA102 High Definition Audio driver: snd_hda_intel
v: kernel pcie: bus-ID: 1-1:2 chip-ID: 12ba:00ff gen: 4 speed: 16 GT/s
class-ID: 0300 lanes: 16 bus-ID: 09:00.1 chip-ID: 10de:1aef
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Licensed by Sony Entertainment America Rocksmith Guitar Adapter
type: USB driver: hid-generic,snd-usb-audio,usbhid
Device-4: ASUSTek GC21-Audio type: USB driver: snd-usb-audio
bus-ID: 3-1.2:6 chip-ID: 0b05:9d09 class-ID: 0102
Sound API: ALSA v: k6.0.2-zen1-1-zen running: yes
Sound Interface: sndio v: N/A running: no
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: down mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp7s0 state: down mac: <filter>
IF-ID-1: br-324bc655645d state: down mac: <filter>
IF-ID-2: br-ddc6f765b722 state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-3: docker0 state: down mac: <filter>
IF-ID-4: veth2c70b07 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-5: veth7f01c56 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-6: veth7f70423 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-7: veth892a621 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-8: vethb241810 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-9: vethde366e9 state: up speed: 10000 Mbps duplex: full
mac: <filter>
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-6:11 chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Local Storage: total: 12.73 TiB used: 1.83 TiB (14.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Western Digital
model: WDS200T1X0E-00AFY0 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 613200WD temp: 46.9 C
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS200T1X0E-00AFY0 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 613200WD temp: 49.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Seagate model: Backup+ Hub
BK size: 9.1 TiB block-size: physical: 4096 B logical: 512 B type: N/A
serial: <filter> rev: D781
ID-1: / raw-size: 1.75 TiB size: 3.57 TiB (203.86%) used: 906.16 GiB
(24.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 612 KiB
(0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:2
ID-3: /home raw-size: 1.75 TiB size: 3.57 TiB (203.86%) used: 906.16 GiB
(24.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-4: /var/log raw-size: 1.75 TiB size: 3.57 TiB (203.86%) used: 906.16
GiB (24.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
ID-5: /var/tmp raw-size: 1.75 TiB size: 3.57 TiB (203.86%) used: 906.16
GiB (24.8%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 62.71 GiB used: 24.5 MiB (0.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 68.98 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:4
System Temperatures: cpu: 54.9 C mobo: 43.0 C
Fan Speeds (RPM): N/A
Processes: 549 Uptime: 1h 24m wakeups: 0 Memory: 62.71 GiB used: 29.07 GiB
(46.4%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 Packages: pm: pacman pkgs: 1782 libs: 500
tools: octopi,paru pm: flatpak pkgs: 0 Shell: Zsh v: 5.9
running-in: konsole inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-09-30
Last full system update: 2022-10-21 ↻
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       No/Undetected
Snapshots:               Snapper
Failed units:

Firstly, hello and welcome to the forums!

We have had a lengthy forum thread about this at Latte Dock Maintainer Bids A Farewell

Also, Latte-dock has been buggy for quite a lot of people lately as I've seen an influx of posts on this topic, so it isn't just you. Even resetting the configuration using Garuda Assistant doesn't fix it for some.

I am unsure what the team is going to do about this in the future if things with latte-dock get worse.
I however do know you can get really close to the default latte-dock feel in base Plasma using either the same or similar widgets (got one going right now on one of my machines so I have a "backup plan" if latte-dock starts messing up really bad)


Yes, Plasma's built in/turn-a-bar into a dock keeps improving and it seems like they are trying to get to the Latte Dock place. With that said, Latte Dock just got a new upgrade today, so someone must be working on it. I haven't had the time to go down that rabbit hole to get an update on the situation. Also to note, I haven't had any issues with it (knocking on EVERY piece of wood I can find, including @c00ter 's ukulele. :violin:)


@RodneyCK The KDE devs are not trying to "get to the Latte place". The KDE devs have made that very clear. As for a new updatye it is a bug fix only not an actual update. The KDE devs have been kind enough to at least handler Latte bugs as they crop up, but out and out maintain Latte no.

@Kayo It actually depends on your setting in Latte if you can set a default panel to be close to Latte since Latte does have a lot more custom setting than the defauklt panel.

1 Like

Maybe you can install garuda/latte-dock ?
Apparently there are a few patches the team has included in that version.

Better to install latte-dock-git cause it's the one the the KDE devs are doing the bug fixes for.


Well then they are sending mixed messages, because introduced in KDE 5.25/5.26... "as well as a new floating mode for the panel that detaches it from the bottom of the screen to look more like a dock."

I hope the KDE team step up and realize the importance of Latte Dock to KDE. I mean, if memory serves me, a fresh Dragon-ized Garuda install used Latte Dock as all their panels.

1 Like

Correct, the Plasma version of Garuda of course.


A default panel sadly misses a few features that Latte set apart for me personally. I do a lot of top bar dragging to move my windows like GNOME offers it and the dock feels more alive than other alternatives to name two of them :thinking: I'm just very much hoping maintenance isn't stalling as much as it needs to cause issues :confused:


They're not sending mixed messages cause the feature set is in all the versions. It's just as far as I know they are only pushing bug fixes for one of the.

As for the KDE team stepping up I completely agree cause Latte is so superior to the default panels and docks.

Stop posting fud.Latte is for all intents and purposes is dead.

Pretty sure the only fud here is your post.

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