hud-service crashed with SIGSEGV in hud_string_list_get_tail()

Bug #953579 reported by Aaron Miller
160
This bug affects 19 people
Affects Status Importance Assigned to Milestone
indicator-appmenu (Ubuntu)
Fix Released
High
Allison Karlitskaya

Bug Description

Ubuntu's update manager crashed, then the "apport" crashed when trying to submit the issue. Restarted Ubuntu, "indicator-appmenu" crashed. No issues since.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Mon Mar 12 19:57:31 2012
ExecutablePath: /usr/lib/indicator-appmenu/hud-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/lib/indicator-appmenu/hud-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x8051ba4: mov (%eax),%eax
 PC (0x08051ba4) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: hud-service crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-12 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
Aaron Miller (nocannedmeat) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 hud_string_list_get_tail (list=0x0) at /build/buildd/indicator-appmenu-0.3.92/./src/hudstringlist.c:152
 hud_item_format_tokens (string=0x98c1850, tokens=0x0) at /build/buildd/indicator-appmenu-0.3.92/./src/huditem.c:101
 hud_item_setup_usage (item=0x98c1758) at /build/buildd/indicator-appmenu-0.3.92/./src/huditem.c:118
 hud_item_construct (g_type=159620736, tokens=0x0, desktop_file=0x985fa40 "/usr/share/applications/kde4/kate.desktop", enabled=0) at /build/buildd/indicator-appmenu-0.3.92/./src/huditem.c:155
 hud_dbusmenu_item_new (context=<optimized out>, desktop_file=0x985fa40 "/usr/share/applications/kde4/kate.desktop", menuitem=0x987a8f0) at /build/buildd/indicator-appmenu-0.3.92/./src/huddbusmenucollector.c:197

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-appmenu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: hud-service crashed with SIGSEGV

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-appmenu (Ubuntu):
status: New → Confirmed
visibility: private → public
summary: - hud-service crashed with SIGSEGV
+ hud-service crashed with SIGSEGV in hud_string_list_get_tail()
Changed in indicator-appmenu (Ubuntu):
importance: Medium → High
assignee: nobody → Ryan Lortie (desrt)
tags: added: hud
tags: added: bugpattern-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-appmenu - 0.3.92-0ubuntu2

---------------
indicator-appmenu (0.3.92-0ubuntu2) precise; urgency=low

  * Backport desrt's r216, r217, r218, should fix:
    - "don't setup usage data for disable items or those without labels"
       (lp: #953579)
    - "remove all items from the dbusmenucollector on free" (lp: #953771)
    - "check the window title from bamf for being NULL before comparing
       on it" (lp: #953620)
 -- Sebastien Bacher <email address hidden> Tue, 13 Mar 2012 16:07:06 +0100

Changed in indicator-appmenu (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
joehill (joseph-hill) wrote :

I'm having continuous problems with compiz crashing and its keyboard settings not working since the last update. This crash happened while I was disabling a compiz plugin to try to get things to be a bit more stable.

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.