indicator-applet-appmenu crashed with SIGSEGV in __libc_free()

Bug #674320 reported by YunQiang Su
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
BAMF
Confirmed
Critical
Jason Smith
Unity
Confirmed
Critical
Unassigned
unity-2d
Invalid
Critical
Unassigned
bamf (Ubuntu)
Confirmed
Critical
Unassigned
unity (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

Binary package hint: indicator-application

it suddenly crashed.

I dont know why.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-application 0.2.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-2.10-generic 2.6.37-rc1
Uname: Linux 2.6.37-2-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Nov 12 09:16:03 2010
ExecutablePath: /usr/lib/indicator-applet/indicator-applet-appmenu
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100812)
ProcCmdline: /usr/lib/indicator-applet/indicator-applet-appmenu --oaf-activate-iid=OAFIID:GNOME_IndicatorAppletAppmenu_Factory --oaf-ior-fd=22
ProcEnviron:
 LANG=zh_CN.utf8
 LANGUAGE=zh_CN:zh_TW:zh:en
 PATH=(custom, user)
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6b53b00c2d <__libc_free+29>: mov -0x8(%rdi),%rsi
 PC (0x7f6b53b00c2d) ok
 source "-0x8(%rdi)" (0xaaaaaaaaaaaaaaa2) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-application
StacktraceTop:
 __libc_free (mem=0xaaaaaaaaaaaaaaaa) at malloc.c:3709
 ?? () from /usr/lib/libbamf.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: indicator-applet-appmenu crashed with SIGSEGV in __libc_free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
YunQiang Su (wzssyqa) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_free (mem=0xaaaaaaaaaaaaaaaa) at malloc.c:3709
 bamf_view_set_flag (view=0x20bd100, flag=34328784,
 marshal_dbus_message_to_g_marshaller (
 g_closure_invoke (closure=0x2142a90,
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-application (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
affects: indicator-application (Ubuntu) → bamf (Ubuntu)
visibility: private → public
Revision history for this message
Rico Tzschichholz (ricotz) wrote :

I am seeing a similar crash using bamf which happens after some usage on an application-close.
Using natty (20110204) with bamf 0.2.76

Neil J. Patel (njpatel)
Changed in bamf:
assignee: nobody → Jason Smith (jassmith)
Alex Launi (alexlauni)
Changed in unity:
status: New → Confirmed
Changed in bamf:
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in bamf (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue?

Changed in unity (Ubuntu):
importance: Undecided → Low
Changed in unity:
importance: Undecided → Low
Changed in unity-2d:
status: New → Confirmed
Changed in unity:
importance: Low → Critical
Changed in unity (Ubuntu):
importance: Low → Critical
Changed in bamf:
importance: Undecided → Critical
Changed in bamf (Ubuntu):
importance: Medium → Critical
Changed in unity-2d:
importance: Undecided → Critical
Changed in unity-2d:
status: Confirmed → Invalid
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.