gnome-screensaver-gl-helper crashed with SIGSEGV

[Noorez]

Binary package hint: gnome-screensaver

This crash happened while I was performing an update. The screen saver came on, I unlocked it and then received the crash message.

I am working on a Toshiba Satellite A100-SK900E with nvidia graphics card using the latest driver listed in Restricted Drivers.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 22 20:42:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.29.92-0ubuntu1
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-gl-helper
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
SegvAnalysis:
 Segfault happened at: 0xd7fb36: movl $0xdb8c40,(%edx)
 PC (0x00d7fb36) ok
 source "$0xdb8c40" ok
 destination "(%edx)" (0x8bdcc815) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-screensaver
Stacktrace:
 #0 0x00d7fb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
StacktraceTop: ?? () from /usr/lib/nvidia-current/libGL.so.1
ThreadStacktrace:
 .
 Thread 1 (Thread 4857):
 #0 0x00d7fb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
Title: gnome-screensaver-gl-helper crashed with SIGSEGV
Uname: Linux 2.6.32-16-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1606): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1757): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:2386): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00d7fb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf
StacktraceTop: ?? () from /usr/lib/nvidia-current/libGL.so.1
ThreadStacktrace:
 .
 Thread 1 (process 4857):
 #0 0x00d7fb36 in ?? () from /usr/lib/nvidia-current/libGL.so.1
 No symbol table info available.
 Cannot access memory at address 0xf

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.4.3-4ubuntu2, latest version: 1:4.4.3-4ubuntu5
libssl0.9.8: installed version 0.9.8k-7ubuntu6, latest version: 0.9.8k-7ubuntu8
libk5crypto3: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1
libudev0: installed version 151-5, latest version: 151-7
mountall: installed version 2.8, latest version: 2.10
python2.6: installed version 2.6.5-1ubuntu2, latest version: 2.6.5-1ubuntu4
python-minimal: installed version 2.6.4-0ubuntu2, latest version: 2.6.5-0ubuntu1
libcups2: installed version 1.4.2-9, latest version: 1.4.2-10
libpango1.0-common: installed version 1.26.2-1, latest version: 1.28.0-0ubuntu1
libldap-2.4-2: installed version 2.4.21-0ubuntu2, latest version: 2.4.21-0ubuntu3
tzdata: installed version 2010e-1, latest version: 2010g-0ubuntu1
libgnomekbd-common: installed version 2.29.92-0ubuntu3, latest version: 2.30.0-0ubuntu1
base-files: installed version 5.0.0ubuntu10, latest version: 5.0.0ubuntu14
libplymouth2: installed version 0.8.0~-17, latest version: 0.8.1-4ubuntu1
libgtk2.0-common: installed version 2.19.7-0ubuntu2, latest version: 2.20.0-0ubuntu3
klibc-utils: installed version 1.5.15-1ubuntu4, latest version: 1.5.17-4ubuntu1
gconf2: installed version 2.28.0-1ubuntu5, latest version: 2.28.1-0ubuntu1
libpango1.0-0: installed version 1.26.2-1, latest version: 1.28.0-0ubuntu1
sensible-utils: installed version 0.0.1ubuntu1, latest version: 0.0.1ubuntu2
python: installed version 2.6.4-0ubuntu2, latest version: 2.6.5-0ubuntu1
dbus: installed version 1.2.16-2ubuntu3, latest version: 1.2.16-2ubuntu4
libglib2.0-0: installed version 2.23.5-1ubuntu3, latest version: 2.24.0-0ubuntu1
libklibc: installed version 1.5.15-1ubuntu4, latest version: 1.5.17-4ubuntu1
libgtk2.0-bin: installed version 2.19.7-0ubuntu2, latest version: 2.20.0-0ubuntu3
cpp-4.4: installed version 4.4.3-4ubuntu2, latest version: 4.4.3-4ubuntu5
libgssapi-krb5-2: installed version 1.8+dfsg~alpha1-7, latest version: 1.8+dfsg~alpha1-7ubuntu1
libgnome-menu2: installed version 2.29.92-0ubuntu2, latest version: 2.30.0-0ubuntu2
sysv-rc: installed version 2.87dsf-4ubuntu16, latest version: 2.87dsf-4ubuntu17
gcc-4.4-base: installed version 4.4.3-4ubuntu2, latest version: 4.4.3-4ubuntu5
udev: installed version 151-5, latest version: 151-7
upstart: installed version 0.6.5-5, latest version: 0.6.5-6
xkb-data: installed version 1.7-2ubuntu2, latest version: 1.8-1ubuntu4
libgnomekbd4: installed version 2.29.92-0ubuntu3, latest version: 2.30.0-0ubuntu1
initramfs-tools: installed version 0.92bubuntu69, latest version: 0.92bubuntu71
libsasl2-2: installed version 2.1.23.dfsg1-3ubuntu1, latest version: 2.1.23.dfsg1-5ubuntu1
libstdc++6: installed version 4.4.3-4ubuntu2, latest version: 4.4.3-4ubuntu5
dbus-x11: installed version 1.2.16-2ubuntu3, latest version: 1.2.16-2ubuntu4
librsvg2-common: installed version 2.26.0-1build1, latest version: 2.26.2-0ubuntu1
libdbus...

[Dawning (dawning)]

May be relevant that I seem to also be experiencing this error, but my video driver is the proprietary ATI video driver.

[G. Dargan (george-georgedargan-deactivatedaccount)]

This is a first with this particular error, I am uncertain as to the cause of the error. I was not in update, however, I have had some issues with my Nvidia drivers. I am not sure if this could be related or not.