Bug 276652 - Keyboard shortcuts don't work on multiscreen setup
Summary: Keyboard shortcuts don't work on multiscreen setup
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_khotkeys (show other bugs)
Version: 5.20.3
Platform: Gentoo Packages Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Michael Jansen
URL:
Keywords:
: 288102 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-28 06:42 UTC by Ojec Borec
Modified: 2021-03-11 21:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ojec Borec 2011-06-28 06:42:09 UTC
Version:           unspecified (using Devel) 
OS:                Linux

I've just installed new KDE 4.6.90 using Gentoo layman and after I logged in I found out, that my global shortcuts don't work anymore. Well, they work, but sometimes they don't.

Reproducible: Didn't try

Steps to Reproduce:
1. Log in
2. Press Alt + F2 (Run Command Interface > Run Command)
3. Nothing appears (I expect panel where I can type my command)
4. Click on desktop
5. Press Alt+F2, panel finally appears
6. Press Esc
7. Panel doesn't appear

Same with Ctrl+F1, F2, ... (To switch desktop). First I must click on desktop or any window.



Expected Results:  
Shortcuts like Alt+F2 or Ctrl+F1 (F2, F3, ...) must work, when no window is active.
Comment 1 Ojec Borec 2011-06-28 06:48:56 UTC
Additional information regarding to shortcuts. I use Ctrl+Shift+s to show/hide kopete main window. When no window is active, this combination doesn't show kopete window, it shows Run Command panel.

Steps to reproduce:
1. Activate any window (just click on it)
2. Press Ctrl+Shift+s (Kopete window appears as expected)
3. Press Ctrl+Shift+s (Kopete window hides as expected), now no window is activated
4. Press Ctrl+Shift+s, Run Command panel appears, but kopete window is expected
Comment 2 Christoph Feck 2011-06-28 10:54:19 UTC
Bug 276658 might be a related issue. Does this happen on a freshly created user account?
Comment 3 Ojec Borec 2011-06-28 11:44:01 UTC
Yes. It happens with new user account too. And I've just found that Alt+Tab (walk through windows) doesn't work. But Meta+Tab (next activity) works.
Comment 4 Christoph Feck 2011-06-28 14:31:49 UTC
Thanks for the update. I hope someone can find out what's happening on your system (I cannot reproduce).
Comment 5 Ojec Borec 2011-06-28 20:23:20 UTC
Another thing. I used to switch to third desktop by Ctrl+F3 on my LCD monitor and start "DISPLAY=:0.1 vlc ..." command, so that film can appears on my TV. Than I switched by Ctrl+F1 to first desktop, but I still could see film on my TV.
Now I've made KDE update (4.6.4 -> 4.7 RC1) and when I switch desktop by Ctrl+F1, it changes desktop on :0.0 and 0.1 display as well. But if I use Pager widget, it only changes desktop on :0.0 display and desktop on :0.1 stays the same.
Comment 6 Christoph Feck 2011-06-28 21:29:45 UTC
I doubt that the pager handles multiple displays yet, but you could report that bug separately to product "plasma", if you are speaking of the Plasma pager widget. For KPager, the bug is already reported, see bug 32911 and bug 134713.
Comment 7 Ojec Borec 2011-06-29 06:08:11 UTC
Well, I'm happy that pager handles only active display. At least we've found, that all these problems are multiple displays related. With only one display everything works just fine. Even very important Alt+Tab. Now if only bottom panel could change it's 100% width when resolution changes. But it's a different bug.
Comment 8 Christoph Feck 2011-12-21 16:06:02 UTC
*** Bug 288102 has been marked as a duplicate of this bug. ***
Comment 9 Thomas Lübking 2015-10-10 22:05:33 UTC
dual head (zaphod, you cannot move windows across screens) setup?
=> bug #284424
Comment 10 Justin Zobel 2021-03-09 23:51:03 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.