Comment 0 for bug 357556

Binary package hint: xscreensaver

This happens with all the computers that I have, both under Intrepid and under Jaunty. The symptom is that after the screensaver has been running for a short time (between 30 seconds and half an hour), the screen will go black and no longer run the screensaver. Unlocking the screen and re-locking the screen (to restart the screensaver) causes the screensaver to display normally for the same period of time, and then once again crash and go back to a black screen.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/xscreensaver/phosphor
NonfreeKernelModules: vmmon
Package: xscreensaver-data-extra 5.07-0ubuntu3
ProcCmdline: phosphor -root -delay 0 -scale 2 -ticks 20
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: xscreensaver
Stacktrace:
 #0 0xb7ca61d1 in fileno_unlocked () from /lib/tls/i686/cmov/libc.so.6
 #1 0x0804a6a4 in ?? ()
 #2 0x0804dd6e in ?? ()
 #3 0xb7c55775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x08049f81 in ?? ()
StacktraceTop:
 fileno_unlocked () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: phosphor crashed with SIGSEGV in fileno_unlocked()
Uname: Linux 2.6.28-11-generic i686
UserGroups: