Hello James, I'm the electricsheep's Debian maintainer and am contacting you about a bug we have.
If we let electricsheep running for days, sooner or later there are not any X Display available anymore (maximum number reached). At the begining, we thought it was related to electricsheep's code, but after speaking with upstream author, this bug is not reproducible elsewhere (than Debian). Then, we were told that this bug can be reproduced with just using xloadimage: > This is another 'I don't know if it helps but...' message. > > I was led to this page because I have a simple screensaver script that > just uses xloadimage to paint into the root window and it has the same > resource leakage problem. This leakage is reproducable if you just > put > xscreensaver.programs: xloadimage -quiet -onroot -center file.jpg > in your .Xresources. Set the cycle time to something short and run > xscreensaver-command -activate, wait for it to cycle (in this case > just reloads the same image). Then check with xrestop and there's a > new <unknown>. Repeat; same result, each cycle adds another > <unknown>. If you don't wait for the cycle timeout, no <unknown> is > created. The fact is that electricsheep does use xsetbg, and then it might be the cause of the bug appearing here. You can see all the comments on the bug #325689 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325689 I'm going to reassign this bug to xloadimage, but I'd like to have some of your points of view before. Best Regards. -- Alexis Sukrieh <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
