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

Bug #829222 reported by Rostislav Dzinko
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
New
Undecided
Unassigned

Bug Description

It happened when I tried to start Skype

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 x86_64
Architecture: amd64
Date: Fri Aug 19 10:08:15 2011
ExecutablePath: /usr/lib/gnome-screensaver/gnome-screensaver-dialog
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
ProcCmdline: /usr/lib/gnome-screensaver/gnome-screensaver-dialog --status-message= --enable-switch
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=uk_UA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x409948: mov 0x8,%r8
 PC (0x00409948) ok
 source "0x8" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-screensaver
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-screensaver-dialog crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-08-15 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Rostislav Dzinko (rostislav-dzinko) wrote :
visibility: private → public
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 #828936, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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