Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#31955 - [xorg-server] Window focus does not follow clicks after X upgrade
Attached to Project:
Arch Linux
Opened by Teo Mrnjavac (teo) - Sunday, 14 October 2012, 15:42 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 26 October 2012, 12:25 GMT
Opened by Teo Mrnjavac (teo) - Sunday, 14 October 2012, 15:42 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 26 October 2012, 12:25 GMT
|
DetailsDescription:
After an upgrade to xorg-server 1.13.0-2, window focus does not follow mouse clicks any more. The only way to change focus is alt-tabbing, and right-clicking to focus mouse events, though that doesn't work consistently. This happens at least under KWin and OpenBox, and in the KDM login screen (one can't open the login manager's session menu on first click for example), so it's very likely not a WM issue but further upstream. The issue remains also when disabling compositing in KWin. This forum post seems to describe the same issue https://bbs.archlinux.org/viewtopic.php?id=148991 While setting SWcursor in /etc/X11/xorg.conf.d/10-monitor.conf does work around the issue, the cursor starts to flicker so much that it's unusable. Unlike the forum post, no xrandr trick seems to do anything for me. Additional info: * package version(s) extra/xorg-server 1.13.0-2 extra/nvidia 304.51-3 * config and/or log files etc. My Xorg log: http://paste.kde.org/569192/ Steps to reproduce: I'm not sure. Upgrade X on my machine I guess? The issue happens in an X session right from the start. |
This task depends upon
What about the nouveau driver? I think upstream x is not too keen on debugging proprietary drivers.
In fact, the issue went away by itself about a week ago, and I haven't been able to reproduce ever since. I don't know how or why, because I didn't perform any updates.