Arch Linux

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!
Tasklist

FS#22233 - [xorg] Mouse clicks won't focus windows/sometimes mouse is completely ignored.

Attached to Project: Arch Linux
Opened by maxexcloo (maxexcloo) - Tuesday, 28 December 2010, 01:39 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 08 February 2014, 12:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Over the last two days I have had trouble with Openbox. The computer starts as normal and X starts fine. I unlock it (I have XScreensaver set to lock on login) and the computer works fine for about 40 seconds. After that time however, Openbox stops accepting mouse clicks on all but one application (the last focused before the issue occurs. Global shortcuts like opening Guake still work but again, I can't right click or scroll the window because Openbox doesn't believe it's in the foreground. Dragging windows and the desktop right click menu also don't work.
Sometimes I am able to fix it by running the "openbox --exit" command which logs me out and drops me into Slim which allows me to restart the session. For some reason the new session works fine.

Additional info:
Version: 3.4.11.2-2
Config attached.

I can attach any config/log files people need.
   rc.xml (8.7 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 08 February 2014, 12:18 GMT
Reason for closing:  Works for me
Comment by Faelar (Faelar) - Wednesday, 05 January 2011, 21:41 GMT
Sometimes I can't focus windows with the same openbox version (3.4.11.2-2). It appears to be quite random ATM. I also use Slim (1.3.2-1), and I'm on a x86_64 desktop as well.
Comment by maxexcloo (maxexcloo) - Wednesday, 05 January 2011, 22:08 GMT
I haven't had the issue in a while, it seems to be random :|
Comment by dmitry (Dr.X) - Saturday, 19 February 2011, 18:13 GMT
Faelar, Openbox can't focus child window (for example, window with tools in gimp, which appers on panel).
Ghost1227, I think it cause by XScreensaver, on Openbox and gnome-screensaver this works fine.
Comment by Faelar (Faelar) - Saturday, 19 February 2011, 18:43 GMT
@dmitry : I'm talking about windows openbox CAN focus when everything is working fine.
Comment by Jelle van der Waa (jelly) - Tuesday, 22 February 2011, 10:35 GMT
this is most likely an upstream bug, report it on the openbox bugtracker or find out what xscreensaver does.

So check:
-Xorg.log aka startx 2&> check.log
-check if it's an xscreensaver related or not
Comment by soomsoom (soomsoom) - Tuesday, 22 February 2011, 18:41 GMT
@jelly - I already did that, and they also respond... I got to dead end: https://bugzilla.icculus.org/show_bug.cgi?id=4910

Edit:
I tried to run XFCE instead OpenBox. and the same problem here, its any chance there is problems with X?
Comment by maxexcloo (maxexcloo) - Sunday, 27 February 2011, 04:45 GMT
Just had the issue again for the first time in a month or so. It's weird.
Comment by soomsoom (soomsoom) - Sunday, 27 February 2011, 05:45 GMT
@maxexcloo - me too... something weird here.
Comment by Faelar (Faelar) - Sunday, 27 February 2011, 20:48 GMT
Same here, it reappeared just a few days ago...
Comment by Greg (dolby) - Thursday, 05 May 2011, 09:04 GMT
Can you provide the output of dmesg, Xorg.log and /var/log/messages? And please state specific package versions. Since it happens outside of openbox its not an openbox bug.
Comment by Jelle van der Waa (jelly) - Sunday, 12 June 2011, 15:11 GMT
Assigned to JGC, maybe he knows what's up with X :)
Comment by maxexcloo (maxexcloo) - Monday, 13 June 2011, 11:18 GMT
The issue actually went away for a while but came back today. I remember updating nvidia drivers and the kernel (might be related)...
I'm on a new install (same PC) with KDE now. No screensavers running at all...
Comment by Nikhil Bysani (nikron) - Monday, 10 October 2011, 23:10 GMT
I have this issue too, except with gnome-shell.

I can attach any files/information needed, I'm just at loss as
to why it is happening
Comment by maxexcloo (maxexcloo) - Tuesday, 11 October 2011, 09:43 GMT
I just had this issue again on my desktop, it was completely out of the blue (I haven't changed or updated in a few weeks!)
Comment by mattia (nTia89) - Wednesday, 22 February 2012, 10:07 GMT
if you don't use xscreensaver, does the issue happen ?

i'm on openbox and i've never had this issue
Comment by Allan McRae (Allan) - Saturday, 02 June 2012, 12:24 GMT
Status?
Comment by maxexcloo (maxexcloo) - Saturday, 02 June 2012, 12:25 GMT
Haven't had the issue in months but it only comes up every few months if that. It's a very very odd issue...
Comment by maxexcloo (maxexcloo) - Monday, 15 April 2013, 01:58 GMT
  • Field changed: Percent Complete (100% → 0%)
The issue just occurred again on the same computer after a reinstall.
Comment by v00ra (v00ra) - Saturday, 20 April 2013, 19:24 GMT
I too have been having this issue. I installed Arch with openbox + tint2 + conky and was having issues where after a first 30s or so, my mouse pointer would respond and move, but i was unable to execute any form of clicking (left, right, wheel, and the browser navigation buttons mouse4-5).
As mentioned above, logging out and logging back in seems to sometimes fix the issue.
I reinstalled Arch again and this time am getting the same problem, but even more frequently. I have since changed from Openbox to Awesome (window manager). Since the change I have noticed some odd things...

1. If the mouse doesn't freeze up within the first 1-2 minutes, it won't happen throughout the rest of the session.
2. From what I've noticed so far, it only happens after I perform "xrandr --output HDMI-0 --auto --primary --right-of LVDS". That is to say that, after I perform the xrandr command, my mouse seems to have a 50/50 chance of freezing where as I have yet to notice it when I simply run "xrandr --output HDMI-0 --auto"
3. It seems to be MORE prevalent now that I am using Awesome WM as opposed to Openbox WM.

My system is a relatively new gaming laptop with an ATI 58xx m card. I am using the opensource ati drivers (xf86-video-ati). I use an external mouse, the Cyborg R.A.T 7

Sorry for the trouble, thank you for looking into this issue.
If there is any more information that I could give to help, I would glady do so.
Comment by Timothy Wallis (tjwallis) - Thursday, 03 October 2013, 10:03 GMT
I'm having this issue as well, I was using Awesome, but switched too cinnamon and it still occurred. The mouse would work for the first 30 sec or so then it would be stuck focused on a window or panel, I could switch the focus with the keyboard, logging out would fix the issue until i restarted again.

Let me know if you need more info.
Comment by Andreas Radke (AndyRTR) - Sunday, 26 January 2014, 14:57 GMT
This could be almost everything, from kernel to Xorg to mouse driver.

Someone who's affected needs to locate the issue by checking log files, using a debugger or checking for known upstream issues for certain hardware.

Maybe you all have different bugs. They all don't seem to be a packaging issue - so going to close this one as works for me or upstream issue soon.

Loading...