Ubuntu
gnome-screensaver package

gnome-screensaver-dialog crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #807660 reported by rolmops on 2011-07-08

This bug report is a duplicate of: Bug #804195: gnome-screensaver-dialog crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	New	Undecided	Unassigned

Bug Description

gnome-screensaver-dialog crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-screensaver 3.0.0-2ubuntu2
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Jul 8 05:37:06 2011
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-dialog
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-dialog --status-message= --enable-switch
ProcEnviron:
SHELL=/bin/bash
LANG=ru_RU.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_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-screensaver-dialog crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

rolmops (dr150259) wrote on 2011-07-08:

XsessionErrors.txt Edit (3.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-07-15: This bug is a duplicate

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.