| Summary: | Kickoff sometimes loses its shortcut | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | medin <med.medin.2014> |
| Component: | Application Launcher (Kickoff) | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | agurenko, bharadwaj.raju777, bugseforuns, demm, hasezoey, indecisiveautomator, katyaberezyaka, liubomirwm, mikel5764, nate, nicolas.fella, p.r.worrall, plasma-bugs, postix |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.23.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=444343 https://bugs.kde.org/show_bug.cgi?id=391322 |
||
| Latest Commit: | Version Fixed In: | ||
|
Description
medin
2022-01-05 09:07:56 UTC
meta stopped working on my Arch Linux after update to frameworks 5.90. alt+F1 shortcut was removed from kickoff settings and I had to set it again manually. > alt+F1 shortcut was removed from kickoff settings and I had to set it again manually.
I have experienced this myself recently. I haven't managed to find the cause though.
*** Bug 448335 has been marked as a duplicate of this bug. *** This used to happen to me regularly. I'm not sure of the cause though. *** This bug has been marked as a duplicate of bug 448609 *** Turns out this is not related to Bug 448609; my mistake. *** Bug 448335 has been marked as a duplicate of this bug. *** *** Bug 449284 has been marked as a duplicate of this bug. *** Nicolas, some files you requested from a reporter of this issue are available at https://bugs.kde.org/show_bug.cgi?id=449284#c5. I think this just happened after i changed the System Global theme (incl. Desktop Layout) to Breeze theme. Plasma 5.25.0. 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 444343, bug 437979 M +29 -9 shell/shellcorona.cpp M +1 -0 shell/shellcorona.h https://invent.kde.org/plasma/plasma-workspace/commit/40d6e18b0f153464a64b3e21c1224e13511632d2 With that change, losing the default Alt+F1 shortcut no longer has any effect on whether the Meta key activates the widget, so this bug is mostly limited to people who have customized the shortcut to be something else. Lowering priority. (In reply to Nate Graham from comment #13) > With that change, losing the default Alt+F1 shortcut no longer has any > effect on whether the Meta key activates the widget, so this bug is mostly > limited to people who have customized the shortcut to be something else. > Lowering priority. Hm, kind of disagree here, I've just got fresh installation of Fedora 36, got all updates without logging in into the GUI and yet those does not work "out of the box"... That's on 5.25.4 + KF 5.97 Plasma 5.25.4 doesn't have the change that makes losing the default shortcut irrelevant to whether or not the Meta key opens Kickoff. That change is in Plasma 5.26. (In reply to Nate Graham from comment #15) > Plasma 5.25.4 doesn't have the change that makes losing the default shortcut > irrelevant to whether or not the Meta key opens Kickoff. That change is in > Plasma 5.26. Sorry, my bad... Closing since Meta activation no longer depends on Kickoff having Alt+F1. That's true, but it's still a valid bug that it loses its shortcut--whatever it is. The user could set it to something else and that would be lost too. So this is still a valid bug IMO. That said, I suspect the bug is related to what happens because of Bug 450068, so fixing that (which is planned for Plasma 5.27) might fix this too. Maybe. Hopefully! |