hud-service crashed with SIGSEGV in g_variant_builder_add_value()

Bug #934473 reported by Anmar Oueja
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-appmenu (Ubuntu)
New
Undecided
Unassigned

Bug Description

1. Launch Emacs
2. Maximize window
3. Press "alt" to launch HUD
4. type "options"
5. Select one
6. boom
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 17 15:20:16 2012
ExecutablePath: /usr/lib/indicator-appmenu/hud-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120124)
ProcCmdline: /usr/lib/indicator-appmenu/hud-service
SegvAnalysis:
 Segfault happened at: 0x7fd4f4a7c962: testb $0x4,0x20(%rdi)
 PC (0x7fd4f4a7c962) ok
 source "$0x4" ok
 destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: hud-service crashed with SIGSEGV in g_variant_builder_add_value()
UpgradeStatus: Upgraded to precise on 2012-02-07 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Anmar Oueja (anmar) 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 #934429, 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
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.