Bug#471920: xscreensaver: Crash at startup

2008-04-07 Thread Vincent Crevot
Just to wrap things up: both of the screens have identical size/coords (1280x1024+0+0) and both are discarded as enclosed and duplicated respectively. One way to keep one would be to skip the duplication/overlaping comparison if any of the two compared screens is already marked, like this: --- xsc

Bug#471920: xscreensaver: Crash at startup

2008-04-06 Thread Vincent Crevot
Ok I need some sleep/holidays/etc. When I tested the patch in #473681 the other day my second screen was disabled. With two screens and that patch it still fails the exact same way: one screen is detected as enclosed, the other as duplicated. Vincent Crevot a écrit : > On Thu, Apr 03, 2008 at 06:3

Bug#471920: xscreensaver: Crash at startup

2008-04-03 Thread Jamie Zawinski
I think this is fixed by the patch in bug 473681? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#471920: xscreensaver: Crash at startup

2008-03-20 Thread Vincent Crevot
Package: xscreensaver Version: 5.05-1 Severity: normal If the daemon is started with -nosplash, it runs properly but does not seem to work, i.e. the screen is never saved and xscreensaver-command, xscreensaver-demo etc. report: xscreensaver-command: no screensaver is running on display :0.0 When