Latte-Dock Breaking randomly

Issues & Assistance Latte Dock
#1 
╰─λ garuda-inxi
System:
Kernel: 5.16.13-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ba2fb729-b4b9-49f0-8223-47f0378d19c9 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Console: pty pts/1 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ROG Strix G513QM_G513QM v: 1.0
serial: <filter>
Mobo: ASUSTeK model: G513QM v: 1.0 serial: <filter>
UEFI: American Megatrends LLC. v: G513QM.314 date: 09/03/2021
Battery:
ID-1: BAT0 charge: 23.1 Wh (29.0%) condition: 79.7/90.0 Wh (88.5%)
volts: 14.5 min: 15.9 model: AS3GWAF3KC GA50358 type: Li-ion
serial: <filter> status: Discharging
CPU:
Info: model: AMD Ryzen 9 5900HX with Radeon Graphics socket: FP6 bits: 64
type: MT MCP arch: Zen 3 family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000B
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: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 3300 min/max: 1200/4889 boost: enabled
base/boost: 3300/4650 scaling: driver: acpi-cpufreq governor: performance
volts: 1.2 V ext-clock: 100 MHz cores: 1: 3300 2: 3300 3: 3300 4: 3300
5: 3300 6: 3300 7: 3300 8: 3300 9: 3300 10: 3300 11: 3300 12: 3300
13: 3300 14: 3300 15: 3300 16: 3300 bogomips: 105402
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: 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: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: ASUSTeK
driver: nvidia v: 510.54 alternate: nouveau,nvidia_drm pcie: gen: 3
speed: 8 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: none empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:2520
class-ID: 0300
Device-2: AMD Cezanne vendor: ASUSTeK driver: amdgpu v: kernel pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
active: eDP-1 empty: HDMI-A-1 bus-ID: 06:00.0 chip-ID: 1002:1638
class-ID: 0300
Display: server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: amdgpu,ati,nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP res: 1920x1080 hz: 144 dpi: 142
size: 344x193mm (13.5x7.6") diag: 394mm (15.5")
OpenGL: renderer: AMD RENOIR (DRM 3.44.0 5.16.13-zen1-1-zen LLVM 13.0.1)
v: 4.6 Mesa 21.3.7 direct render: Yes
Audio:
Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 3 speed: 8 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:228e class-ID: 0403
Device-2: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
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: 06:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
driver: N/A
alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x
pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s
bus-ID: 06:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-4: AMD Family 17h/19h HD Audio vendor: ASUSTeK
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: 06:00.6 chip-ID: 1022:15e3
class-ID: 0403
Sound Server-1: ALSA v: k5.16.13-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
lanes: 1 bus-ID: 03:00.0 chip-ID: 14c3:7961 class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Bluetooth:
Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8
bus-ID: 3-4:2 chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 1.4 TiB used: 337.51 GiB (23.6%)
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: SK Hynix model: HFM001TD3JX013N
size: 953.87 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 41000C20
temp: 33.9 C scheme: GPT
SMART: yes health: PASSED on: 110d 23h cycles: 4,488
read-units: 8,318,059 [4.25 TB] written-units: 10,393,032 [5.32 TB]
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Intel model: SSDPEKKW512G8
size: 476.94 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: 004C
temp: 37.9 C scheme: GPT
SMART: yes health: PASSED on: 1y 205d 16h cycles: 6,263
read-units: 64,392,834 [32.9 TB] written-units: 63,688,273 [32.6 TB]
Partition:
ID-1: / raw-size: 476.94 GiB size: 476.94 GiB (100.00%)
used: 337.49 GiB (70.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p1
maj-min: 259:1
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.5 MiB (26.6%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:3
ID-3: /home raw-size: 476.94 GiB size: 476.94 GiB (100.00%)
used: 337.49 GiB (70.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p1
maj-min: 259:1
ID-4: /var/log raw-size: 476.94 GiB size: 476.94 GiB (100.00%)
used: 337.49 GiB (70.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p1
maj-min: 259:1
ID-5: /var/tmp raw-size: 476.94 GiB size: 476.94 GiB (100.00%)
used: 337.49 GiB (70.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p1
maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.12 GiB used: 2.8 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 56.0 C mobo: N/A gpu: amdgpu temp: 48.0 C
Fan Speeds (RPM): cpu: 0
Info:
Processes: 419 Uptime: 21m wakeups: 13 Memory: 15.12 GiB
used: 4.46 GiB (29.5%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1842 lib: 552
Shell: garuda-inxi (sudo) default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.13
Garuda (2.5.5-1):
System install date:     2022-02-21
Last full system update: 2022-03-12
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Yes
Snapshots:               Snapper
Failed units:

Every few days latte-dock seems to break and I have to reset it. I don't change anything on the default settings except removing a few things from the dock at the bottom. I reset everything again today and tried to check the Dragonized theme settings and noticed this.

image
image1915×1009 83.3 KB

#3

If you have not already updated your system use

garuda-update

As it is out off date and may help

#5

Updated and it's still showing same error

Error #E103: Different Applets With Same Id 

In your layout there are two or more applets with same id. Such situation can create crashes, abnormal behavior and data loss when you activate and use this layout.

Applets:
  • Vaults [#101] inside System Tray [#13]
  • Printers [#102] inside System Tray [#13]
  • Window Buttons [#101] inside Third screen top [#17]
  • Application Launcher [#102] inside Third screen top [#17]

Possible Solutions:
  1. Activate this layout and restart Latte
  2. Remove the mentioned applets from your layout
  3. Update manually the applets id when the layout is not active
  4. Remove this layout totally
#6

Maybe this'll help somewhat?

Close Latte

Run Latte from command line with, latte-dock -d

Open Layouts editor and observe the errors appear in command line.

That error appears when two or more applets or containments use the same ID, and this is problematic.

#7

Open garuda assistant and restore the config for latte-dock using the checkboxes at the bottom of the main page.

Then logout and log back in.

3 Likes
#8

@umbrachimera did you get this solved? Follow up is important as it helps others in the future.

2 Likes
#9

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