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

Bug #832970 reported by darren
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-appmenu (Ubuntu)
New
Undecided
Unassigned

Bug Description

fresh instal 11.10 A3
heaps o bugs

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-appmenu 0.2.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 24 23:53:04 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7439282e29 <bamf_window_get_window_type+201>: mov 0x8(%rax),%rcx
 PC (0x7f7439282e29) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 bamf_window_get_window_type () from /usr/lib/x86_64-linux-gnu/libbamf3.so.0
 ?? () from /usr/lib/indicators3/6/libappmenu.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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
Title: unity-panel-service crashed with SIGSEGV in bamf_window_get_window_type()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
darren (dazndom-gmail) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #819150, 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.