gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

Bug #955407 reported by Christopher Kyle Horton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was logged into GNOME Classic, then I logged out and logged back into Unity, then this crash came up.

I think this happened once before following these same steps, so I'd say this is reproducible.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 14 15:46:36 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f663d820e85: mov 0x78(%rax),%edx
 PC (0x7f663d820e85) 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-11 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Christopher Kyle Horton (christhehorton) 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.