Open sillysloft opened 13 years ago
any special stuff (mouse related) in your .fluxbox/keys?
Original comment by: akir
I have in .fluxbox/keys lines like "OnTitlebar Mouse1 :HideMenus" - nothing more special than that.
Besides, I started fluxbox as a different user, with no ~/.fluxbox directory at all - same problem.
Original comment by: *anonymous
I am also seeing this bug in Ubuntu 11.04 when using fluxbox 1.3.1 and the builds on the nightly repository. Here is a pastebin with the xev output for all the buttons on my mouse (Logitech G500) http://pastebin.com/yS9RNFF2 . Here is a link to my .fluxbox/keys file if you want to check it for something strange http://pastebin.com/kBp5cbW8 . This is the only cause I can think of for this bug in hugin (left click not detected when trying to drag in the fast preview window) which I only see when using fluxbox https://bugs.launchpad.net/hugin/+bug/797370 .
Original comment by: arclance
Original comment by: akir
This bug also affects me. I get the following event order when clicking the xev window:
LeaveNotify EnterNotify KeymapNotify ButtonPress ButtonRelease
I'm happy to do additional tests. So far I tried to disable clickRaises and enabled focus follows mouse – both didn't change anything.
Original comment by: houz
This is because fluxbox holds a passive grab an active windows (most WMs will only on inactive windows) - the event pattern is typical and nothing to worry about for this condition. To "fix" this, it would be required to have the keys definition smarter on knowing whether a passive grab on an active window is required (which will likely not be trivial and probably quite restrict the possible settings in the keys file - unless there's a OnInactiveWindow split)
Original comment by: baghira-style
Behaviour: When a window is clicked on by the left mouse button, the window receives these events, in this order: LeaveNotify, EnterNotify, KeymapNotify, ButtonPress, ButtonRelease. Expected result: The window should receive ButtonPress, then ButtonRelease. This is the result I get with other window managers (tried: xfce4's window manager, and lwm)
Pressing mouse buttons 2-5 produces the expected result. I have tested with a default fluxbox configuration, i.e. no ~/.fluxbox directory.)
Steps to reproduce: 1. start xev 2. click inside xev with mouse button 1
Fluxbox version: 1.1.1 X.org version: 1.9.2 Architecture: x86_64 Distro: Arch Linux
Sample xev output:
EnterNotify event, serial 34, synthetic NO, window 0x1c00001, root 0x15a, subw 0x0, time 4230384, (2,111), root:(729,134), mode NotifyUngrab, detail NotifyAncestor, same_screen YES, focus YES, state 256
KeymapNotify event, serial 34, synthetic NO, window 0x0, keys: 90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
ButtonPress event, serial 34, synthetic NO, window 0x1c00001, root 0x15a, subw 0x0, time 4230384, (2,111), root:(729,134), state 0x0, button 1, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x1c00001, root 0x15a, subw 0x0, time 4230888, (2,111), root:(729,134), state 0x100, button 1, same_screen YES
Note: the first value in the KeymapNotify event is sometimes 2, sometimes 90 and sometimes 0. It seems to change only after changing window focus.
Reported by: nobody