Problems with latte-docks?

[filo]

As far as I can say (but take this as a comment from a non-technical person):

• For Wayland, I think that the question was more the other way round: if you used it, this could have been a possible cause of troubles; but I don't see any reason to move to it at the moment (at least with KDE)
• Hold Packages: I see "pacman glibc garuda-system" come from our standard ISO, so no problems for sure (although I think garuda-system could be removed, because I don't see any such package)

So, overall, I'd say no problem to leave this as is..

[petsam]

@anon25081990

deleting some index crap of baloo due to it taking literally hundreds of gigabyte…

Re-enable indexing. This is what fills the menu search function.
If you don’t want the search function to bring up files/folders, you may add exceptions in Indexing Settings, to minimize the database size.

@anon25081990

the search bar isn’t selected by default (which means every god damn time i need to use it i need to click on it with the mouse, tab won’t work either) and on top of that everything stays gray-ish

Review (and maybe alter) mouse focus (and possibly other) settings, in case it’s a window focus issue.

[petsam]

I would suggest posting a bug report upstream.
Then, I checked current bug issues and in one of them with a “Can’t click on Latte” problem, the Latte dev says:

I wont even look at it because Plasma is not really providing an official way to support screen scaling under X11. You can ask them if you want, the use of PLASMA_USE_QT_SCALING=1 is not advised and supported by Plasma team.

So for scaling related issues under x11 first Plasma should define which way is officially supported in order for Latte afterwards to follow.

Until then all scaling issues under x11 are considered irrelevant.

This confirms my perception of Plasma being on critical development phase.

Latte-dock freezing randomly

I was (and still am) fan of Latte project. For the most time, it was a path to overcome certain plasma disabilities and improve the daily work functionality, while using Plasma/KDE. Unfortunately, Plasma has not recovered yet, from the multihead management difficulty and since they have focused on this subject in order to solve it, they eventually get into subsequent issues because of the new fixes. That’s a development path for every program. I could not handle it and moved to other DEs, fo…

[psifidotos]

PLASMA_USE_QT_SCALING scenario under X11 was fixed today for Latte. I had responded to users that I will not look at it but a user presented some easy steps to setup and reproduce. At the same time I observed plenty of plasma code that trys to handle the situation. So plasma devs do not suggest it but on the hand they take it into account. Long story short, it was fixed today.

For some Latte freezes there is a chance that come from window buttons applet. Window buttons applet is recreating its buttons and internal decoration every time they change size because buttons were not painted correctly. Yesterday aftet years of searching I found the bug inside Breeze and Oxygen decoration. Fixes will be part of Plasma 5.23.2 and afterwards a new wimdows applet will be released 0.10.1 that will be much much more lightweight for cpu and hard disk usage.

[Hawpe]

@anon25081990

the search bar isn’t selected by default (which means every god damn time i need to use it i need to click on it with the mouse, tab won’t work either) and on top of that everything stays gray-ish if i search something, as if it does not exist

I can confirm that I now have the exact same problem.
To quickly exclude some of the things that have been mentioned in the thread:

• My system is up to date
• I haven’t disabled indexing
• I haven’t changed anything in pacman.conf
• I’m not using Wayland

Output of inxi -Faz:

System:    Kernel: 5.14.15-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=8a0a4f23-e4b4-468d-a55d-308b2de6b338
rw rootflags=subvol=@ quiet
cryptdevice=UUID=06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc:luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc
root=/dev/mapper/luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc splash rd.udev.log_priority=3
vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1
resume=/dev/mapper/luks-a775b892-c6c9-43c9-8c98-189505509025 loglevel=3
Desktop: KDE Plasma 5.23.2 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Laptop System: Dell product: XPS 13 9370 v: N/A serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: Dell model: 0W970W v: A06 serial: <filter> UEFI: Dell v: 1.15.0 date: 06/07/2021
Battery:   ID-1: BAT0 charge: 47.9 Wh (99.0%) condition: 48.4/52.0 Wh (93.1%) volts: 8.6 min: 7.6
model: LGC-LGC6.73 DELL H754V05 type: Li-ion serial: <filter> status: Charging
CPU:       Info: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake note: check
family: 6 model-id: 8E (142) stepping: A (10) microcode: EA cache: L2: 8 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999
Speed: 3853 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 3853 2: 3959 3: 3880 4: 3851
5: 3395 6: 3948 7: 3878 8: 3918
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0
chip-ID: 8086:5917 class-ID: 0300
Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-5:2
chip-ID: 0bda:58f4 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 5376x1080 s-dpi: 96 s-size: 1418x285mm (55.8x11.2") s-diag: 1446mm (56.9")
Monitor-1: eDP1 res: 1536x864 hz: 60 dpi: 135 size: 290x170mm (11.4x6.7") diag: 336mm (13.2")
Monitor-2: DP1-1 res: 1920x1080 hz: 60 dpi: 81 size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
Monitor-3: DP1-2 res: 1920x1080 hz: 60 dpi: 96 size: 510x290mm (20.1x11.4") diag: 587mm (23.1")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.4 direct render: Yes
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel
alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
Device-2: Realtek USB Audio type: USB driver: snd-usb-audio bus-ID: 3-1.3.4:8
chip-ID: 0bda:402e class-ID: 0102 serial: <filter>
Sound Server-1: ALSA v: k5.14.15-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.39 running: yes
Network:   Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: Rivet Networks Killer 1435 Wireless-AC driver: ath10k_pci v: kernel bus-ID: 02:00.0
chip-ID: 168c:003e class-ID: 0280
IF: wlp2s0 state: down mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 bus-ID: 4-1.4:4
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: enp57s0u1u4 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-3: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth: Device-1: Foxconn / Hon Hai type: USB driver: btusb v: 0.8 bus-ID: 1-7:3 chip-ID: 0489:e0a2
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 476.94 GiB used: 46.87 GiB (9.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: PC611 NVMe 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: 11002111 temp: 44.9 C scheme: GPT
Partition: ID-1: / raw-size: 459.81 GiB size: 459.81 GiB (100.00%) used: 46.87 GiB (10.2%) fs: btrfs
dev: /dev/dm-0 maj-min: 254:0 mapped: luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 708 KiB (0.3%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 459.81 GiB size: 459.81 GiB (100.00%) used: 46.87 GiB (10.2%) fs: btrfs
dev: /dev/dm-0 maj-min: 254:0 mapped: luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc
ID-4: /var/log raw-size: 459.81 GiB size: 459.81 GiB (100.00%) used: 46.87 GiB (10.2%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0 mapped: luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc
ID-5: /var/tmp raw-size: 459.81 GiB size: 459.81 GiB (100.00%) used: 46.87 GiB (10.2%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0 mapped: luks-06b5b85e-d9c6-4b3d-8ad4-9160c300f9fc
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.33 GiB used: 512 KiB (0.0%) priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 16.86 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1
maj-min: 254:1 mapped: luks-a775b892-c6c9-43c9-8c98-189505509025
Sensors:   System Temperatures: cpu: 53.0 C mobo: 41.0 C sodimm: SODIMM C
Fan Speeds (RPM): cpu: 4697
Info:      Processes: 289 Uptime: 17m wakeups: 26 Memory: 15.33 GiB used: 5.76 GiB (37.5%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1472 lib: 355
Shell: fish v: 3.3.1-523-g3abe21708 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.08

@psifidotos

Yesterday aftet years of searching I found the bug inside Breeze and Oxygen decoration. Fixes will be part of Plasma 5.23.2

Sorry to be the bearer of bad news but as you can see I have Plasma 5.23.2 and the problem is still present (and persists between reboots).

[psifidotos]

No idea what is your issue, the thread is related to Latte, if you have any issue with Latte report it at: Log in to KDE Bugtracking System

[Hawpe]

@psifidotos

No idea what is your issue

What do you mean? My issue is literally the same as the person who made this thread.

[psifidotos]

If you use a plasma panel with the same application launcher and you have the same issue then it is not Latte fault. My guess is that the fact that the search bar is not focused by default then this is not latte fault but the application launcher fault.

[filo]

Unfortunately this thread is a mix of several different problems (at least, focus on search field and missing indexing).
The OP was happy rolling back to an old latte release but in my humble opinion this might be some kind of "coincidence". In-fact there is another thread with the same initial issue (search field not getting the focus) which was not solved rolling back to that release.
For me, more than latte, maybe this could be an issue (search field focus) in the application launcher widget?

[Hawpe]

@psifidotos

If you use a plasma panel with the same application launcher and you have the same issue then it is not Latte fault. My guess is that the fact that the search bar is not focused by default then this is not latte fault but the application launcher fault.

That makes sense. I thought you were implying (from your previous reply) that OP’s bug was fixed recently.

@filo

Unfortunately this thread is a mix of several different problems (at least, focus on search field and missing indexing).

Although they are different problems they seem to be correlated judging by the fact that both of us have exactly the same issue. I assume you’re talking about Meta key and auto focus on searchbox? Seems like that user also experiences the “indexing” issue:

@Averell

Also, until yesterday I could look up KDE settings directly from the launcher like “shortcuts” or “composer” etc. Not anymore.

[anon25081990]

i doubt that is a coincidence, i think it is a problem with a iso file, because of i installed garuda on three devices (1desktop pc, 2laptops) with none of those had the same specs, and all of them had the same image on them