On 2008-04-01 (Tue) 22:16:24 [-0400], Giovanni Tumiati wrote:
> slakmagik wrote:
>>
>> I'll pile on and say that with 2.5.25 on Slackware 12.0 I get a problem
>> that I've gotten (and reported) before, which is to say that a click on
>> the desktop with the mouse produces no effect until the mouse is moved
>> at least a pixel and that holding a menu open results in 100% CPU usage
>> for the duration of the hold. Using the pager does not cause this and a
>> 'torn off' (backspaced) menu does not cause this unless the mouse is
>> moved into the torn off menu. IOW, some kind of 'grabbing the X server
>> == grabbing the CPU' and 'mouse is inactive until moved' problem or
>> something. I don't know if this is related to the OPs issue, but sounded
>> related enough to remind me of my issues.
>>
> Regarding the 100% cpu usage problem: I experienced that as well with
> 2.5.25, and actually it occurs with 2.5.23 and 2.5.24. But I think it is
> related to X rather than fvwm. Reason I say that, is because after I
> upgraded from Slackware 12.0 to Slackware-current, (with all the X lib
> updates) that problem disappeared. If you can, try upgrading to -current
> and see if the problem persists.
Well, that's ironic, or something. Guess what I'd been trying to get
around to on one machine for awhile and finally did today? And you're
right - it's gone away on that system. Doesn't help with the others but
they'll soon be at 12.1 anyway and at least I know it's not fvwm's
fault. Thanks for the reply. :)
