Ubuntu
gnome-panel package

gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

Bug #1045333 reported by Chrescht on 2012-09-03

This bug report is a duplicate of: Bug #948667: gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants(). Edit Remove

This bug affects 1 person

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

Bug Description

I installed gnome-shell and rebooted. Then I chose Gnome as Desktop.
This crash happened a couple of minutes after the login, whithout any other activity from my side.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-panel 1:3.5.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 3 15:17:12 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: gnome-panel
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7effc126ea45: mov 0x80(%rax),%edx
PC (0x7effc126ea45) ok
source "0x80(%rax)" (0xaaaaaaaaaaaaab2a) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Chrescht (sekateur) wrote on 2012-09-03:

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-09-03: 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.