Garuda Dock (previously Latte dock?) doesn't auto hide nor gets hidden behind windows

Hi there!

The App Dock that comes with Garuda refuses to auto-hide or be hidden behind windows, which is highly bothering when I maximize a window. Changing the options in the edit menu doesn’t seem to affect it in any way.

Any ideas? I really like this dock and don’t really want to have to replace it with something else.

System:
Kernel: 6.6.2-zen1-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=b652edd7-a598-45e7-bbe6-99791107dfbd rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 info: docker wm: kwin_x11
vt: 2 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B550M AORUS ELITE
serial: <superuser required> UEFI: American Megatrends LLC. v: F16a
date: 11/03/2022
CPU:
Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2952 high: 3586 min/max: 2200/4662 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3355 2: 2200
3: 2872 4: 3208 5: 3140 6: 2906 7: 2200 8: 3586 9: 3518 10: 2873 11: 2863
12: 3069 13: 2933 14: 2200 15: 2924 16: 3400 bogomips: 108601
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 545.29.02
alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
2023-10; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s bus-ID: 05:00.0 chip-ID: 10de:1f06 class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting,nouveau,nvidia
alternate: fbdev,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3520x1080 s-dpi: 90 s-size: 993x301mm (39.09x11.85")
s-diag: 1038mm (40.85")
Monitor-1: DVI-D-0 pos: left res: 1600x900 hz: 60 dpi: 92
size: 443x249mm (17.44x9.8") diag: 508mm (20.01") modes: N/A
Monitor-2: HDMI-0 pos: primary,right res: 1920x1080 hz: 60 dpi: 102
size: 477x268mm (18.78x10.55") diag: 547mm (21.54") modes: N/A
Monitor-3: None-1-1 size-res: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060
SUPER/PCIe/SSE2 memory: 7.81 GiB
API: Vulkan v: 1.3.269 layers: 8 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2060 SUPER driver: nvidia v: 545.29.02 device-ID: 10de:1f06
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 16.0.6 256
bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM 16.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA TU106 High Definition Audio driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 10de:10f9
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 07:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.6.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.85 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: 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: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-209a26951ddc state: up speed: 10000 Mbps duplex: unknown
mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
IF-ID-3: veth2eb9d02 state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-4: veth7745b1c state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-5: vetha85d0df state: up speed: 10000 Mbps duplex: full
mac: <filter>
IF-ID-6: vethb426775 state: up speed: 10000 Mbps duplex: full
mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:5
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 1.78 TiB used: 1.09 TiB (60.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS480G2G0C-00AJM0 size: 447.13 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 231800WD temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: K1B3 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000VM002-1CT162
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: SC23 scheme: MBR
Partition:
ID-1: / raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 20.51 GiB (16.3%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 27.4 MiB (28.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 20.51 GiB (16.3%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 20.51 GiB (16.3%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 125.59 GiB size: 125.59 GiB (100.00%)
used: 20.51 GiB (16.3%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.24 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 54.9 C mobo: 37.0 C gpu: nvidia temp: 44 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 29%
Info:
Processes: 440 Uptime: 2h 58m wakeups: 0 Memory: total: 32 GiB
available: 31.24 GiB used: 10.08 GiB (32.2%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1421 libs: 412 tools: octopi,pamac,paru Shell: fish
v: 3.6.1 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-19
Last full system update: 2023-11-23 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

You mean you already tried something like this and it doesn’t work?

1 Like

That is correct!

Both the “Auto Hide” and “Windows can Cover” options do not change the way the dock behaves, sadly. It always remains at the top and unhidden.

I guess you have already logged out and in? You have also a pending reboot. Just in case…

2 Likes

Turns out I was being dumb. The dock was being held open by unread skype notifications. Clearing them makes the dock hide correctly.

I’m sorry for wasting your time lol.
Thanks for your help!

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