Problems with latte-docks?

anyways, do you recommend me putting patte-dock-git to the held back packages within /etc/pacman.conf? I would like to update sometimes without having to worry about stuff not working afterwards anymore
also, is there something to mute those warnings if i'm upgrading regarding "held back package"? i would like to be as red-free during upgrades as possible

Whether to ignore the upgrades for that package should be your decision.
You have to balance the annoyance of clicking into the search field with the risk of staying with a non-updated package.
As regards the warnings, I don't think they could be removed (but it would be necessary to read the pacman man and wiki in details), but I think they are very imporant, since ignoring upgrades should be a temporary exception and should not be forgotten.

1 Like

i don't know whether it's still like this or if it got changed, but i recall the first time i opened the pacman.conf and i found multiple entries on the ignorepkg line... something along the lines of garuda, pacman and a couple other things... that makes me wonder why that is like this... anyways i'd let it in the ignorepkg for now, because of if it's not in there it's gonna upgrade and then it's literally useless, a search bar which you can't search stuff with... thanks, i'd consider this done for now

Fine with the decision to ignore latte, of course, but I suggest rechecking this.
This is really weird, and could create problems...

1 Like

In such cases that users do not remember what they have seen or done, it is very important that they post actual information, as requested from the initial post template (they usually delete it without reading).
Are you one of those users? :slightly_smiling_face:

Is there any chance you run on Wayland?

1 Like

i do not record everything i do nor what i see, i thought it was odd so i put it in there too, what do you mean by wayland?

In this context, the request was to provide (as usual as text, formatted with ~~~ before and after the text block):

  • the outcome of inxi -Faz (according to the template shown when you create a topic)
  • the /etc/pacman.conf, or at least the HoldPkg, IgnorePkg, etc.

Wayland is a display server protocol. It is aimed to become the successor of theX Window System.
I don't think you are using it, but it could be confirmed with echo $XDG_SESSION_TYPE resulting in x11.

2 Likes

the echo does indeed exit with x11, but as i said, i changed it because of i thought why would that be the standard, therefore i don't have the "unchanged" file... anyways what do you need me to do with wayland?


both of those outputs:

[[email protected] ~]$ inxi -Faz && cat /etc/pacman.conf
System:    Kernel: 5.14.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=c004acea-73f0-4fe1-9afc-7ab18ce1c3d0 rw
[email protected]
Desktop: KDE Plasma 5.23.1 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:   Type: Desktop Mobo: MSI model: MSI X58 Pro-E (MS-7522) v: 3.0 serial: <filter> BIOS: American Megatrends v: 8.14B8
date: 11/09/2012
CPU:       Info: Quad Core model: Intel Core i7 930 bits: 64 type: MT MCP arch: Nehalem family: 6 model-id: 1A (26)
stepping: 5 microcode: 1D cache: L2: 8 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 44911
Speed: 2031 MHz min/max: 1600/2800 MHz boost: enabled Core speeds (MHz): 1: 2031 2: 1684 3: 1857 4: 1935 5: 1912
6: 1660 7: 2583 8: 1618
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 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 status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GM204 [GeForce GTX 970] driver: nvidia v: 470.74 alternate: nouveau,nvidia_drm bus-ID: 03:00.0
chip-ID: 10de:13c2 class-ID: 0300
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 101 s-size: 966x272mm (38.0x10.7") s-diag: 1004mm (39.5")
Monitor-1: HDMI-0 res: 1920x1080 dpi: 94 size: 520x290mm (20.5x11.4") diag: 595mm (23.4")
Monitor-2: DP-5 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.8x10.6") diag: 547mm (21.5")
OpenGL: renderer: NVIDIA GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74 direct render: Yes
Audio:     Device-1: Intel 82801JI HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:3a3e class-ID: 0403
Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 03:00.1 chip-ID: 10de:0fbb
class-ID: 0403
Device-3: JMTek LLC. USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 4-1:2
chip-ID: 0c76:161e class-ID: 0300
Sound Server-1: ALSA v: k5.14.12-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.38 running: yes
Network:   Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel bus-ID: 04:00.0 chip-ID: 8086:095a class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e800 bus-ID: 06:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 6-1:2 chip-ID: 8087:0a2a
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: no
address: <filter>
Drives:    Local Storage: total: 2.27 TiB used: 793.74 GiB (34.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-00WN4A0 size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Silicon Power model: SPCC Solid State Disk size: 238.47 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 9A0 scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 041 scheme: MBR
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Toshiba model: MQ01ABD050 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter> scheme: MBR
ID-5: /dev/sdf maj-min: 8:80 type: USB vendor: Seagate model: ST500LX005-1CW162 size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter> scheme: GPT
Partition: ID-1: / raw-size: 206.39 GiB size: 206.39 GiB (100.00%) used: 82.17 GiB (39.8%) fs: btrfs dev: /dev/sdc1
maj-min: 8:33
ID-2: /home raw-size: 206.39 GiB size: 206.39 GiB (100.00%) used: 82.17 GiB (39.8%) fs: btrfs dev: /dev/sdc1
maj-min: 8:33
ID-3: /var/log raw-size: 206.39 GiB size: 206.39 GiB (100.00%) used: 82.17 GiB (39.8%) fs: btrfs dev: /dev/sdc1
maj-min: 8:33
ID-4: /var/tmp raw-size: 206.39 GiB size: 206.39 GiB (100.00%) used: 82.17 GiB (39.8%) fs: btrfs dev: /dev/sdc1
maj-min: 8:33
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 17.18 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc2 maj-min: 8:34
ID-2: swap-2 type: zram size: 15.62 GiB used: 4.5 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A gpu: nvidia temp: 53 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 31%
Info:      Processes: 280 Uptime: 17m wakeups: 0 Memory: 15.62 GiB used: 5.04 GiB (32.3%) Init: systemd v: 249 tool: systemctl
Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: 1592 pacman: 1587 lib: 381 flatpak: 5 Shell: Bash v: 5.1.8
running-in: konsole inxi: 3.3.07
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg      = pacman glibc garuda-system
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = latte-dock-git
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
Color
ParallelDownloads = 10
CheckSpace
ILoveCandy
VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

[chaotic-aur]
#SigLevel = Never
Include = /etc/pacman.d/chaotic-mirrorlist

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..

3 Likes

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.

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

4 Likes

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.

4 Likes

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.

3 Likes

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 [email protected] 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

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).

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

1 Like

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

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.

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?

1 Like

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

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:

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

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