Carsten Haitzler (The Rasterman) wrote:
On Sat, 06 Aug 2005 12:40:36 -0400 Robert May <[EMAIL PROTECTED]>
babbled:
Whenever I run xscreensaver I receive the following messages:
xscreensaver: 12:39:27: 0: for window 0x22e (root)
xscreensaver: 12:39:30: 0: unrecognised ClientMessage "WM_PROTOCOLS"
received
xscreensaver: 12:39:30: 0: for window 0x22e (root)
xscreensaver: 12:39:31: 0: unrecognised ClientMessage "WM_PROTOCOLS"
xscreensaver being noisy and not understanding the netwm ping protocol. it
should just shut up and ignore it if it doesnt understand it.
Actually, this is not correct.
The NetWM spec says:
> A Client SHOULD indicate that it is willing to participate in this protocol
by listing _NET_WM_PING in the WM_PROTOCOLS property of the client window.
Quote from Jamie Zawinski, maintainer of xscreensaver:
"Obviously, xscreensaver has not indicated its desire to participate in this
protocol, so I think it's an Enlightenment bug that these messages are getting
sent."
Christoph
--
echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" [EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
