gnome-panel crashed with SIGSEGV in g_signal_emit_valist()

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

Bug Description

I was running apt-get --auto-remove purge linux-image-3.2.0-19-generic linux-headers-3.2.0-19
just a minute after the system start up

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: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 6a005c47a693737f8a587c2893ed61f5
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
CrashCounter: 1
Date: Thu Mar 22 18:41:05 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-panel
SegvAnalysis:
 Segfault happened at: 0x7f695d552db5: mov 0x78(%rax),%edx
 PC (0x7f695d552db5) 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-02-21 (30 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

Revision history for this message
Eyad Salah (eyad-salah) wrote :
visibility: private → public
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.

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.