Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Simon Huggins
Hiya Jamie, On Tue, Nov 13, 2007 at 04:12:17PM -0800, Jamie Zawinski wrote: > >Which whole log? It doesn't seem to be logging to .xsession-errors > >sadly just spamming which ever xterm it was run from... > RTFAQ - http://www.jwz.org/xscreensaver/bugs.html It's easy to reproduce so here you go:

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Jamie Zawinski
Which whole log? It doesn't seem to be logging to .xsession-errors sadly just spamming which ever xterm it was run from... RTFAQ - http://www.jwz.org/xscreensaver/bugs.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Jamie Zawinski
On Nov 13, 2007, at 4:00 PM, Simon Huggins wrote: This workrave program is in Debian so you can find out whatever it is at: http://packages.debian.org/sid/workrave Ok, but I'm not going to because I don't care. I have no idea if it's changed the name of windows but I get the message a lo

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Simon Huggins
Hi Jamie, On Tue, Nov 13, 2007 at 04:08:14PM -0800, Jamie Zawinski wrote: > On Nov 13, 2007, at 4:00 PM, Simon Huggins wrote: > >This workrave program is in Debian so you can find out whatever it is > >at: http://packages.debian.org/sid/workrave > Ok, but I'm not going to because I don't care. >

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Simon Huggins
Hi Jamie, On Tue, Nov 13, 2007 at 03:51:31PM -0800, Jamie Zawinski wrote: > I don't understand how that's possible, unless 0x2a78886 is, in fact, > the xscreensaver virtual root window, and this workrave program > (whatever that is) has for some reason changed the *name* of the root > window

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Simon Huggins
Salut Jamie! On Tue, Nov 13, 2007 at 03:51:31PM -0800, Jamie Zawinski wrote: > I don't understand how that's possible, unless 0x2a78886 is, in fact, > the xscreensaver virtual root window, and this workrave program > (whatever that is) has for some reason changed the *name* of the root > win

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Jamie Zawinski
I don't understand how that's possible, unless 0x2a78886 is, in fact, the xscreensaver virtual root window, and this workrave program (whatever that is) has for some reason changed the *name* of the root window. See xscreensaver.c line 1619: that message is not printed out unless window ==

Bug#191530: It's still spamming the console with these...

2007-11-13 Thread Simon Huggins
found 191530 5.03-3 thanks xscreensaver: 16:44:17: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:44:17: 0: for window 0x2a78886 (workrave / WorkraveBreak) xscreensaver: 16:44:17: 0: unrecognised ClientMessage "_NET_WM_STATE" received xscreensaver: 16:44:17: 0: for window