gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

Bug #962315 reported by Stéphane Charette
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
New
Undecided
Unassigned

Bug Description

Happened about 20? seconds after I rebooted (auto-login). Other than a dialog window telling me something had crashed, I have no idea what application actually crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 22 09:34:19 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-panel
SegvAnalysis:
 Segfault happened at: 0x7f69ca8aadb5: mov 0x78(%rax),%edx
 PC (0x7f69ca8aadb5) ok
 source "0x78(%rax)" (0xaaaaaaaaaaaaab22) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.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-panel crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to precise on 2012-03-19 (3 days ago)
UserGroups: admin vboxusers

Revision history for this message
Stéphane Charette (stephanecharette) 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 this software better. This particular crash has already been reported and is a duplicate of bug #948667, 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
visibility: private → public
tags: removed: need-amd64-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.