gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

Bug #1156166 reported by Sebastian Wendowski
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
New
Undecided
Unassigned

Bug Description

Happend at login

Ubuntu Raring Ringtail (development branch)
Release: 13.04

gnome-panel:
  Installed: 1:3.6.2-0ubuntu3
  Candidate: 1:3.6.2-0ubuntu3
  Version table:
 *** 1:3.6.2-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages
        100 /var/lib/dpkg/status

expected to happen: Nornal Login
happened instead: Crash

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-panel 1:3.6.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Sun Mar 17 11:37:48 2013
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges:

InstallationDate: Installed on 2013-03-05 (11 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130301)
MarkForUpload: True
ProcCmdline: gnome-panel
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe3dc2da468: mov 0x80(%rax),%edx
 PC (0x7fe3dc2da468) 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

Revision history for this message
Sebastian Wendowski (sebwen-deactivatedaccount-deactivatedaccount) 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.

information type: 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.