Ubuntu
gnome-panel package

gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

Bug #1214434 reported by Cavsfan on 2013-08-20

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

It just popped up after logging in after a reboot.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-panel 1:3.6.2-0ubuntu12
ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 20 10:06:18 2013
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges:

InstallationDate: Installed on 2013-06-30 (50 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130630)
MarkForUpload: True
ProcCmdline: gnome-panel
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f23d4e07348: mov 0x98(%rax),%edx
PC (0x7f23d4e07348) ok
source "0x98(%rax)" (0xaaaaaaaaaaaaab42) 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

Cavsfan (cavsfan) wrote on 2013-08-20:

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

Revision history for this message

Apport retracing service (apport) wrote on 2013-08-20: 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.