https://bugs.kde.org/show_bug.cgi?id=436597
Bug ID: 436597
Summary: META key opens "Application Launcher" after reboot,
but quits working
Product: lattedock
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: lin...@gmail.com
Target Milestone: ---
SUMMARY
My Meta key works to open Application Launcher after a reboot, but quits
working sometime during the day. Will work again after a reboot. Other META
key bindings work (i.e. META-TAB opens Activity Switcher). In my Google
searching, most of the threads I found imply the META key not working at all.
Most of the google searches lead to
https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-can-i-use-my-super-key-to-open-the-app-launcher.
Following the instructions on there, I verified that;
[ModifierOnlyShortcuts]
Meta=org.kde.lattedock,/Latte,org.kde.LatteDock,activateLauncherMenu
Is in my ~/.config/kwinrc
I also reran the commands to put that in there, and restart Kwin.
STEPS TO REPRODUCE
1. Fresh boot, META Activity Launcher working normally.
2. After an unknown amount of time, the META Application Launcher quits
working.
3. Reboot fixes it.
OBSERVED RESULT
The META Activity Launcher isn't working
EXPECTED RESULT
The META Activity Launcher should be working.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Garuda Linux (Rolling Version, full system update as of
5/1/2021)
(available in About System)
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
I'm using the Garuda default latte config, 'Dr460nized', minorly customized. I
added an activity launcher to the middle, along with a full long date. I then
duplicated that 'Dr460nized' layout into my own layout. That way, any system
updates wouldn't wipe out my changes. Switching between the layouts does not
seem to effect this behavior either.
I am having a hard time determining exactly when it quits working. I've
noticed this behavior going on for a few weeks now (since Garuda Linux
install). I'll try to test if it happens when the laptop goes to sleep.
Reboot, ensure its working, then perform a manual sleep. If that works, I'll
set a low sleep timer and let that kick in, see if it quits then. If sleep has
no effect, I'm really not sure what the trigger is that makes it quit working.
--
You are receiving this mail because:
You are watching all bug changes.
