On Fri, Jan 16, 2004 at 02:26:01PM +0100, Uwe Pross wrote: > Hi there, > > On 16 Jan 2004 at 13:52:17 +0100, Dominik Vogt wrote: > > > > Okay. Is there a way to find out which application has > > > grabbed the pointer? > > > > Perhaps if you describe exactly what you are doing. > > Nothing special I guess: > > Fvwm is running. A couple of applications have been started. > I do a middle click on the root window which is defined as: > > Mouse 2 R A Module FvwmWinList -transient > Mouse 2 A 4 Module FvwmWinList -transient > > (http://www-user.tu-chemnitz.de/~uwp/Ablage/beep.jpg) > > When FvwmWinList is opened I wait for 2 seconds while moving > the mouse pointer up and down over FvwmWinList until 2 beeps > occur.
Um, it's FvwmWinList of course. It grabs the pointer when run in transient mode, forcing you to close it before you can continue working on the desktop. The -transient option is meant to be used this way: 1. Click to open FvwmWinList. 2. Drag pointer to item you want to activate. 3. Select entry by releasing the mouse. 4: FvwmWinList closes and releases the pointer. You probably have soething running that sends commands to fvwm while the pointer is grabbed. Maybe FvwmWinList should grab the whole X server. > The problem does not occur if I run fvwm with an empty > config. If I find the time I could try to find out which > parts of my config causes this problem. Ciao Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
