#107864 Window Maker keeps prodding the X server

Package:
wmaker
Source:
wmaker
Description:
NeXTSTEP-like window manager for X
Submitter:
Juliusz Chroboczek
Date:
2005-07-18 03:45:49 UTC
Severity:
normal
#107864#5
Date:
2001-08-06 23:32:55 UTC
From:
To:
Hi.

Here's another upstream bug.  Could you please forward it?

On a completely idle system, Window Maker keeps waking up to prod the
X server.  This is bad on laptop systems, where this prodding prevents
the APM idle call from ever being issued, thus making the CPU run at
full speed all the time.  (Of course, this happens even when WM is run
with -nopolling.)

I am attaching a fragment of an X protocol dump.  You will notice that
WM keeps checking the current input status.  I haven't checked the WM
main loop (sorry, don't have the sources handy), but I suspect that
whatever this is needed for could be achieved by selecting for
FocusChangeMask on the window that has the input focus, and then doing
a blocking select.

Thanks,

                                        Juliusz

75.02: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
75.02:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
75.02: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
75.02:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
75.52: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
75.52:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
75.52: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
75.52:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
76.02: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
76.02:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
76.02: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
76.02:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
76.52: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
76.52:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e
76.52: Client 2 -->    4 bytes
         ............REQUEST: GetInputFocus
76.52:                                    32 bytes <-- X11 Server 2
                                         ..............REPLY: GetInputFocus
                                                   revert-to: Parent
                                                       focus: WIN 0040000e