Binary package hint: gnome-screensaver
Binary package hint: gnome-screensaver
All I did was boot the PC from the daily live cdimage (karmic-desktop-amd64 from today 9th July 2009), choose to use nonfree driver for my Nvidia card when asked, run (and finished) the System Testing from Administration and decided to look at the screen savers. I opened the Screensaver preferences and the crash occured. I didn't even click on anything.
ProblemType: Crash
Architecture: amd64
Date: Thu Jul 9 21:53:38 2009
DistroRelease: Ubuntu 10.04
Exe...
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 24 22:24:27 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
InstallationMedia: Error: [Errno 13] Permiso denegado: '/var/log/installer/media-info'
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.28.0-1ubuntu5
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
PATH=(custom, no user)
LANG=es_VE.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SegvAnalysis:
Segfault happened at: 0x7f6ce5cc2210: mov (%rax),%r12d
PC (0x7f6ce5cc2210) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
?? () from /usr/lib/nvidia-current/libGL.so.1
_fini () from /usr/lib/nvidia-current/libGL.so.1
?? () from /lib64/ld-linux-x86-64.so.2
exit () from /lib/libc.so.6
__libc_start_main () from /lib/libc.so.6
Title: gnome-screensaver-gl-helper crashed with SIGSEGV in _fini()
Uname: Linux 2.6.32-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: metacity
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.