Thomas Adam schrieb am 01.08.2010 01:02:
> On Thu, Jul 29, 2010 at 03:09:05PM +0000, Georg Wittig wrote:
>> Hello FVWM community,
>>
>> I don't know if my problem is related to FVWM at all, but I'll try in
>> this newsgroup. I'm running a fully updated Fedora 13 with the newest
>> Fvwm RPM (fvwm-2.5.26-4.fc12.x86_64).
>
> Then it's not the newest. FVWM 2.5.30 is.
Well, as it happens upto that moment I wrote my original question
fvwm-2.5.26-4.fc12.x86_64 was the newest fvwm RPM that was
provided by Fedora (I don't fiddle with Makefiles). A couple of
hours later, Fedora released the fvwm-2.5.30-2.fc13.x86_64 RPM.
As far as I have tested, the problem did not go away with that
newer version.
>> The problem occurs, when xscreensaver jumps in (gnome-screensaver is
>> disabled). When I return to my workststation and enter my password to
>> xscreeansaver, then the screen is unlocked and my windows are shown
>> again. But then the keyboard is completely unresponsive.
>
> Yes, this seems like an annoyingly intermittent problem which other window
> managers have had reports of (XMonad being the main one). If you could try
> to see if:
>
> fvwm -f /dev/null
>
> ... also exhibits the problem you describe, then we can rule it out as a
> FVWM bug.
With "-f /dev/null" I wasn't able to reproduce the problem. But I
didn't test it thoroughly, because fvwm is pretty unusable to me
in that mode. :-)
Thomas, If I understand you correctly you suspect the cause of
the problem not to be in fvwm, but somewhere else (xscreensaver?
the X server? xkb?).
--Georg
