Bug 436597

Summary:	META key opens "Application Launcher" after reboot, but quits working
Product:	[Unmaintained] lattedock	Reporter:	Mike Lindsay <lindsm>
Component:	application	Assignee:	Michail Vourlakos <mvourlakos>
Status:	RESOLVED DOWNSTREAM
Severity:	normal
Priority:	NOR
Version First Reported In:	git (master)
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mike Lindsay 2021-05-04 17:45:36 UTC

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.

Comment 1 Michail Vourlakos 2021-05-04 17:56:52 UTC

in my system it works always so this needs a proper way to reproduce even though I wouldnt be surprised if it is kwin fault and somehow it loses its settings.

Comment 2 Mike Lindsay 2021-05-04 18:13:56 UTC

(In reply to Mike Lindsay from comment #0)
 
> 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.

So a "Manual" sleep, it continued working.  I clicked on "Sleep" from the Application Launcher.  Waited for screen to shut off.  Gave it around a minute to finialize, then pushed a button to wake it up.

Set the Sleep to 5 minutes, stepped away to make a cup of coffee, and it quit working on the automatic sleep.

Comment 3 Mike Lindsay 2021-05-04 18:53:30 UTC

The sleep process isn't repeatable.  Just did a manual sleep, gave it 5 minutes this time.  META key still working.  Let it goto sleep naturally on its 5 minute timer.  Meta key still working.

Comment 4 Mike Lindsay 2021-05-06 04:11:13 UTC

Performed another system update, problems appears to have gone away.  KDE was updated to 5.21.5.