| Summary: | After replacing kickoff with classic kickoff, it does not open with the Meta key | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | David <david.cortes.rivera> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | katyaberezyaka, nate, plasma-bugs, postix |
| Priority: | NOR | ||
| Version: | 5.23.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=447962 https://bugs.kde.org/show_bug.cgi?id=391322 |
||
| Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/commit/40d6e18b0f153464a64b3e21c1224e13511632d2 | Version Fixed In: | 5.26 |
| Sentry Crash Report: | |||
|
Description
David
2021-10-24 19:50:53 UTC
And BTW this would solve it: https://forum.manjaro.org/t/kde-application-launcher-doesnt-open-when-meta-key-is-pressed/34257/11 But it seems that configuration change is not being done automatically by KDE. Does the applet get the default Alt+F1 shortcut applied in its settings window, or is the shortcut empty there? (In reply to Nate Graham from comment #2) > Does the applet get the default Alt+F1 shortcut applied in its settings > window, or is the shortcut empty there? It did have the shortcut, and nothing changed by removing it. OK, then this may be an issue in KWin with how it detects the applet to assign it the meta key. Does it open if you hit Alt+F1 (or whatever the shortcut is listed as in the settings window)? (In reply to Nate Graham from comment #4) > OK, then this may be an issue in KWin with how it detects the applet to > assign it the meta key. > > Does it open if you hit Alt+F1 (or whatever the shortcut is listed as in the > settings window)? It did open with Alt+F1, and would also open with a different shortcut if I change it, but the default one opened with "meta". Also BTW would be better if it had a checkbox right there to make it open with "meta", as otherwise one tries to set that as a shortcut but it does not take it as a single key, which is confusing, and the kwin trick is not even available in the system settings. (In reply to Nate Graham from comment #4) > OK, then this may be an issue in KWin with how it detects the applet to > assign it the meta key. > > Does it open if you hit Alt+F1 (or whatever the shortcut is listed as in the > settings window)? Another issue: after using the workaround to make the launcher menu open with Meta, now krunner does not open with ctrl+space anymore. (In reply to David from comment #6) > (In reply to Nate Graham from comment #4) > > OK, then this may be an issue in KWin with how it detects the applet to > > assign it the meta key. > > > > Does it open if you hit Alt+F1 (or whatever the shortcut is listed as in the > > settings window)? > > Another issue: after using the workaround to make the launcher menu open > with Meta, now krunner does not open with ctrl+space anymore. EDIT: alt+space. A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1937 Git commit 40d6e18b0f153464a64b3e21c1224e13511632d2 by Nate Graham, on behalf of David Redondo. Committed on 04/08/2022 at 16:23. Pushed by ngraham into branch 'master'. Take active screen in account and remove shortcut requirement for activating launcher With the information about the active screen we can make an educated guess about where the attention of the user is and where they could expect the launcher to open. If on the screen no launcher could be activated, look at all launchers. Also remove the requirement for launchers to have a shortcut. This is needed to make this feature work reliably and should reduce the instances of "Meta key stopped working" happening in general. Related: bug 391322, bug 437979, bug 447962 M +29 -9 shell/shellcorona.cpp M +1 -0 shell/shellcorona.h https://invent.kde.org/plasma/plasma-workspace/commit/40d6e18b0f153464a64b3e21c1224e13511632d2 |