gnome-screensaver-dialog crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crv
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.0.0-2ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-8-generic i686
NonfreeKernelMo
Architecture: i386
CheckboxSubmission: d1ead686255e2c9
CheckboxSystem: d00f84de8a55581
CrashCounter: 1
Date: Sun Aug 21 23:49:34 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=es_AR.UTF-8
SegvAnalysis:
Segfault happened at: 0x8050618: mov 0x8,%eax
PC (0x08050618) ok
source "0x8" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
?? ()
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: gnome-screensav
UpgradeStatus: Upgraded to oneiric on 2011-08-10 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #804195, 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.