There is also a bug (which I've believe is fixed in the newer versions) where xscreensaver-getimage processes are not cleaned up with a wait() call once they complete. This means that leaving the screensaver running for a while (less than a day can do it, depending on the image change rate) will fill the process table. Once that happens you can't even unlock the screen anymore and all sorts of system processes start to fail. I've had to work around it by scheduling cron to call "xscreensaver-command -cycle" every hour (this changes the hack; cleaning up the zombie processes).
-- xscreensaver version is ancient https://bugs.launchpad.net/bugs/102678 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
