sisyphus wrote: > On 04/01/2016 06:51 AM, Michael Großer wrote: >> Hi! Many thanks to all of you for your feedback. As I wrote in Bug >> 1259520, it must have something to do with FVWM conditions that are >> triggered everey few seconds by periodic Schedule commands. These >> conditions seem to interfere with Firefox versions newer than 12. > > This rings a bell. > > In my old setup, I have an FvwmButtons module that is updated every 3 > seconds via an fvwmperl module. The periodic command it sends to fvwm is > "UpdateGraphs", which happens to be a complex function from my fvwmrc. I > posted this setup back a bit... > > https://gist.github.com/dru8274/fd645f6309e6e50cd359 > > DestroyFunc UpdateGraphs > AddToFunc UpdateGraphs > + I SendToModule Graphs ChangeButton graph-cpu Icon graph-cpu.png > + I Schedule 150 SendToModule Graphs ChangeButton graph-mem Icon > graph-mem.png > + I Schedule 300 SendToModule Graphs ChangeButton graph-iow Icon > graph-iow.png > + I Schedule 450 SendToModule Graphs ChangeButton graph-disk Icon > graph-disk.png > + I Schedule 600 SendToModule Graphs ChangeButton graph-net Icon > graph-net.png > > Well, according to the manpage, "during execution of complex functions, > fvwm needs to take all input from the mouse pointer". Such that in > periodically running this complex function, the mouse pointer is being > grabbed every 3 seconds. And if I happen to have a firefox menu open, > then it suddenly disappears. It is as if firefox wants the mouse pointer > for its menu, but fvwm has grabbed it instead? > > So I have been mucking around with this. When I rewrote my fvwmperl > module to replace the complex function UpdateGraphs with simpler fvwm > commands, the interrupted firefox menus problem just disappeared. For me > at least.
Hi! Thank you for your conformation that you too were affected by such kind of bug. Also, the quotation from the man page could be helpful for me. I guess that I will need 2 weeks to build a Debian Jessie based scenario with FVWM 2.6.6 to show that the issue still exists with current versions of the involved software. Then, we can discuss who could do what to eliminate the issue: FVWM developers, Firefox developers or FVWM users like me. Best regards, Michael
