gnome-screensaver crashed with SIGSEGV in update_clock()

[Fabio Duran Verdugo]

This crash appear always when the screensaver goes in action.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Sep 14 16:45:00 2011
ExecutablePath: /usr/bin/gnome-screensaver
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcCmdline: /usr/bin/gnome-screensaver --no-daemon
SegvAnalysis:
 Segfault happened at: 0x950ec3 <update_clock+35>: mov 0xc(%eax),%eax
 PC (0x00950ec3) ok
 source "0xc(%eax)" (0xaaaaaab6) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
 update_clock (data=0x8a5e380) at gnome-wall-clock.c:167
 g_datetime_source_dispatch (source=0x8a5ec98, callback=0x950ea0 <update_clock>, user_data=0x8a5e380) at gnome-datetime-source.c:142
 g_main_dispatch (context=0x899eb70) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:2441
 g_main_context_dispatch (context=0x899eb70) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:3011
 g_main_context_iterate (context=0x899eb70, block=8532992, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.29.90/./glib/gmain.c:3089
Title: gnome-screensaver crashed with SIGSEGV in update_clock()
UpgradeStatus: Upgraded to oneiric on 2011-07-31 (45 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #849600, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.