Hello Dominik, thanks for your reply. Since all this is cc'd to the fvwm-workers mailing list, I will continue to write in English although you seem to be from Germany, too.
> When exactly does this happen? Does it also happen if you release the mouse > button > befor the error message shows up? The error message, and the total non-responsiveness with it, happens while dragging, i.e. before I release the mouse button. If I manage to place the view and release the mouse button just quickly enough, it seems to work. > Try > > destroyfunc EWMHActivateWindowFunc > > as a workaround. If fvwm does not have that function, it won't try to grab > the > pointer. I actually tried that even before contacting you. The effect is just the same (except FvwmConsole now complains about not finding the function instead of displaying the error). But Fvwm hangs nevertheless. Sure hope this will help to clear things up. I'll be happy to assist in any way I can. Best regards, Tobias On Mon, Aug 11, 2014, at 13:44, Dominik Vogt wrote: > > Steps to reproduce: > > Just download any recent version of Eclipse, extract, and start it. Then > > try dragging > > a view tab from one place to another inside Eclipse. Fvwm will hang > > completely, one > > CPU core running at 100%; I have to switch to a console and kill the Java > > VM to make > > things work again. > > > > FvwmConsole (if opened beforehand) will display the following error: > > > > FvwmConsole version 2.6.5 > > [fvwm][ComplexFunction]: <<ERROR>> Grab failed in function > > EWMHActivateWindowFunc, > > unable to execute immediate action > > When exactly does this happen? Does it also happen if you release the mouse > button > befor the error message shows up? > > It looks like Eclipse has asked fvwm to activate some window while it has > grabbed > the pointer for dragging. Fvwm reacts to this situation by grabbing the > pointer > itself which could lead to a deadlock: Fvwm waits for the grab while Eclipse > waits > for some window to receive focus(?). This is only a theory yet. But an > application > that would refuse to continue its work because one of its windows does not > get the > focus would be pretty broken. > > > Since I'm using both Fvwm and Eclipse professionally, I would really > > appreciate any > > fixes and/or workaround suggestions. > > Try > > destroyfunc EWMHActivateWindowFunc > > as a workaround. If fvwm does not have that function, it won't try to grab > the > pointer. > > I'll try if I can get Java running at home. > > Ciao > > Dominik ^_^ ^_^ > > -- > > Dominik Vogt >
