unity-panel-service crashed with SIGSEGV in g_hash_table_foreach()

Bug #1019850 reported by Francesco Fumanti on 2012-07-01
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Undecided
Unassigned

Bug Description

The problem happens quite often, when I want to open the menu of an appindicator.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-services 5.12-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 1 20:52:57 2012
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x4063c5: cmp %rax,(%rdx)
 PC (0x004063c5) ok
 source "%rax" ok
 destination "(%rdx)" (0x48db3153fd894855) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 g_hash_table_foreach (hash_table=0x7f0240, func=0x7fea3cf02230, user_data=0x7fff0dedb3b0) at /build/buildd/glib2.0-2.33.3/./glib/ghash.c:1524
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_hash_table_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

Francesco Fumanti (frafu) wrote :

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 #1015140, 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
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers