[4422] in testers

home help back first fref pref prev next nref lref last post

xss and WM_CHANGE_STATE

daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Tue Jun 6 01:33:55 2000

Date: Tue, 6 Jun 2000 01:33:46 -0400 (EDT)
From: Jacob Morzinski <jmorzins@MIT.EDU>
To: testers@mit.edu
Message-ID: <Pine.GSO.4.21L.0006060108400.1183-100000@x15-cruise-basselope.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I'm not sure if anything can come of this, but it's weird,
and I thought I'd report it here.

I'm using a 8.4-beta sun.  I start xss-button my .startup.X file.
When I iconify an X application using a method _other_ than my
windowmanager, I get error/warning output from xss, as in the
last two lines of the log below (I logged in at 23:51).

I've never seen these WM_CHANGE_STATE messages on 8.3 machines:

23:51 xss disabling server builtin screensaver.
23:51 xss: you can re-enable it with "xset s on".
01:06 xss: unrecognised ClientMessage type WM_CHANGE_STATE received
01:06 xss: unrecognised ClientMessage type WM_CHANGE_STATE received


Typing C-z in an emacs will trigger this, as will running
"wm iconify ." in an interactive wish shell.

I happened to stumble across a mention of WM_CHANGE_STATE in section
4.1.4 of the Scheifler and Gettys X book (it's not in the index).
The book says that a client which iconifies itself should send
the root window a ClientMessage event of type WM_CHANGE_STATE.
Given that the event is supposed to go to the root window, I'm not
sure why xss is getting it.

 -Jacob



home help back first fref pref prev next nref lref last post