xscreensaver crashed with SIGSEGV

[Jānis Kangarooo]

Binary package hint: xscreensaver

i was away so dont know if screensaver started working but this crash was already waiting

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xscreensaver 5.10-3ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Mon Jul 5 23:07:35 2010
ExecutablePath: /usr/bin/xscreensaver
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: xscreensaver -no-splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x66c422 <__kernel_vsyscall+2>: ret
 PC (0x0066c422) ok
 destination "(%esp)" (0xbfa383d8) ok
 SP (0xbfa383d8) ok
 Reason could not be automatically determined. (Unhandled exception in kernel code?)
Signal: 11
SourcePackage: xscreensaver
StacktraceTop: ?? ()
Title: xscreensaver crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop: sleep_until_idle (si=Cannot access memory at address 0x6ddd08

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

I need a developer to check the stacktrace attached by apport-retracing-service. I do not know if it is complete enough to determine a cause for this crash.

Thanks for taking the time to make Ubuntu better!

[Tormod Volden (tormodvolden)]

This was most likely a one-off problem, maybe a hardware problem. Unless it can be reproduced or confirmed by others, the report can be closed.

[Tormod Volden (tormodvolden)]

Closing since it couldn't be reproduced and no further info from submitter.