KWin shortcuts don't work on second monitor

Bug #975056 reported by Zoffix Znet
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Base Workspace
kde-workspace (Ubuntu)

Bug Description

I have a dual-monitor setup, and I added CTRL+SHIFT+F shortcut to maximize windows. It works fine on my left (main) monitor, but doesn't work on my second monitor.

I opened the system settings, and the shortcut *is* set there.

I also have Meta+G shortcut setup to lunch Gimp, if I press it on the second monitor (where CTRL+SHIFT+F doesn't work), this shortcut does work, but launches Gimp on the "wrong" monitor (that is on the left).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plasma-desktop 4:4.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Fri Apr 6 07:32:51 2012
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
SourcePackage: kde-workspace
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
In , Alex Crazy (k0l0b0k) wrote :

Version: 4.7 (using KDE 4.7.2)
OS: Linux

Hi there. I have a dual-head environment, with separately configured screens (X.Org manually configured, config attached). In this case global shortcuts (like audio player or volume controls) does not work, if mouse pointer (or input focus) placed on Screen1, if I move pointer to Screen0, and click there - global hotkeys works fine.
May be any workarrounds for it?

Reproducible: Always

Steps to Reproduce:
1. configure X.Org to use separate screens (ZaphodHeads for radeon)
2. start KDE
3. try o use global shortcuts on secondary screen

Actual Results:
System does not react on pressing global shortcut keys

Expected Results:
Global shortcuts should work on every screen

If any needed - I can provide any log, output, debug info, or debug it by self.

Revision history for this message
In , Alex Crazy (k0l0b0k) wrote :

Michael, what can I do to help fix it? I'm really don't know, what is start point to debug this really annoying issue?

Revision history for this message
In , Kde-michael-jansen (kde-michael-jansen) wrote :

Currently? Whatever you want. I am without internet (landline) for 2 month now and no end to be seen. so do not expect anything from me for the foreseeable future.

Sorry. Mike

Revision history for this message
In , Sogerc1-5 (sogerc1-5) wrote :

I can confirm this bug with one addition. KWin shortcuts when pressed on the second screen have no effect but when pressed on the first screen the action is initiated on each screens (for example Show Desktop Grid, Switch One Desktop to the Left, etc). An exception to this behavior that I noticed is Walk Through Windows which on the second screen does nothing, but if you press it on the first screen sometimes works correctly but some other times a box saying "*** No Windows ***" appears on the second screen. (By the way this makes Alt+Tab completely unusable, I've replaced it with some ugly hacks using xbindkeys+xdotool+wmctrl but they can never function as good as the window manager)

Revision history for this message
Zoffix Znet (zoffix) wrote :
Changed in kdebase-workspace:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
In , Wheel (wheel) wrote :

I can confirm that this broken behaviour is still present in KDE 4.9.1.

Revision history for this message
In , Thomas-luebking (thomas-luebking) wrote :

This is *not* a bug in KWin, but nevertheless see bug #256242 for a vast discussion on the matter (also briefly covering kglobalaccel)

The basic problem here is that kglobalaccel operates on head-unaware dbus and only runs on one head.

Changed in kdebase-workspace:
status: New → Unknown
Revision history for this message
In , Justin Zobel (justin-zobel) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.