Bug 425326 - Shortcuts meta+<number> don't work
Summary: Shortcuts meta+<number> don't work
Status: RESOLVED DUPLICATE of bug 408310
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.4
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-13 22:57 UTC by Andrei Rybak
Modified: 2020-08-14 01:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of relevant shortcuts (240.34 KB, image/png)
2020-08-13 22:57 UTC, Andrei Rybak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Rybak 2020-08-13 22:57:34 UTC
Created attachment 130860 [details]
Screenshot of relevant shortcuts

SUMMARY
Default shortcuts for switching between "Task Manager Entries" (applications), which is meta+<number> by default, has stopped working.

STEPS TO REPRODUCE
0. Open ten different applications.
1. Press Meta+1
2. Press Meta+2
3. Press Meta+3
4. Press Meta+4
5. Press Meta+5
6. Press Meta+6
7. Press Meta+7
8. Press Meta+8
9. Press Meta+9
10. Press Meta+0

OBSERVED RESULT
None of the ten shortcuts work.

EXPECTED RESULT
All ten shortcuts work.

ADDITIONAL INFORMATION
The weirdest results are when shortcuts are pressed when focus is inside the application Konsole:

  $ s1s2s3s4s5s6s7s8s9s0

This output is interspersed with bash autocompletion for some hostnames, which I don't understand.
Comment 1 Andrei Rybak 2020-08-14 01:06:18 UTC
The issue went away after reboot. I suspect, that the root cause was from one of the restarts of plasma & kwin that I did. That is, calling one of:

  kwin --replace &
  kquitapp5 plasmashell && kstart5 plasmashell

can sometimes break the shortcuts.

An possibly important point: all the other shortcuts with Meta key (including the infamous Meta key without anything else) continued working during that period of breakage.
Comment 2 Patrick Silva 2020-08-14 01:09:11 UTC

*** This bug has been marked as a duplicate of bug 408310 ***