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

Bug #830836 reported by Carlos Vargas
10
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
NonfreeKernelModules: wl
Architecture: i386
CheckboxSubmission: d1ead686255e2c9ec7af0aa0ce839d7b
CheckboxSystem: d00f84de8a555815fa1c4660280da308
CrashCounter: 1
Date: Sun Aug 21 23:49:34 2011
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-dialog
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-dialog --status-message= --enable-switch
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_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: Upgraded to oneiric on 2011-08-10 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Carlos Vargas (cvrvargas) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.