indicator-multiload segfaults immediately

Bug #942859 reported by Bradley M. Froehle
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
System Load Indicator
Fix Released
Medium
Michael Hofmann
indicator-multiload (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu & Package Information

$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

$ apt-cache policy indicator-multiload
indicator-multiload:
  Installed: 0.2-0ubuntu1
  Candidate: 0.2-0ubuntu1
  Version table:
 *** 0.2-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status

What Happens
============

Running indicator-multiload immediately segfaults::

$ indicator-multiload
Segmentation fault

Debugging
=========

$ gdb indicator-multiload
[snip]
Reading symbols from /usr/bin/indicator-multiload...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/indicator-multiload
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
__strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32
32 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory.
 in ../sysdeps/x86_64/multiarch/../strlen.S
(gdb) bt
#0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:32
#1 0x000000000040c12d in main_main ()
#2 0x00007ffff5d8d30d in __libc_start_main (main=0x4056c0 <main>, argc=1,
    ubp_av=0x7fffffffe248, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe238) at libc-start.c:226
#3 0x0000000000405709 in _start ()
(gdb)

description: updated
description: updated
Revision history for this message
Bradley M. Froehle (brad-froehle) wrote :

The crash is because $XDG_DATA_DIRS was not set when the program was run.

For example,

$ XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/ indicator-multiload

works fine.

Changed in indicator-multiload (Ubuntu):
status: New → Invalid
Revision history for this message
Josh Lee (jleedev) wrote :

Why is segfaulting the correct behavior in this case?

The XDG Base Directory Specification gives a default value for XDG_DATA_DIRS. If the variable is unset or empty, the default value should just be used.

Revision history for this message
Bradley M. Froehle (brad-froehle) wrote :

Yes, easily reproduced with

  $ env -u XDG_DATA_DIRS indicator-multiload

I can confirm this is still an issue on Ubuntu 13.04.

Revision history for this message
Michael Hofmann (mh21) wrote :

Hi Bradley,

could you check whether you can reproduce it with the version at ppa:indicator-multiload/daily?

Thanks!
  Michael

Changed in indicator-multiload (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Bradley M. Froehle (brad-froehle) wrote :

Michael:

Thanks! The issue is resolved in the daily ppa.

-Brad

Michael Hofmann (mh21)
Changed in indicator-multiload (Ubuntu):
status: Incomplete → Fix Committed
affects: indicator-multiload (Ubuntu) → indicator-multiload
affects: indicator-multiload → indicator-multiload (Ubuntu)
Changed in indicator-multiload:
status: New → Fix Committed
milestone: none → 0.4
Changed in indicator-multiload (Ubuntu):
status: Fix Committed → Confirmed
Michael Hofmann (mh21)
Changed in indicator-multiload:
status: Fix Committed → Fix Released
Michael Hofmann (mh21)
Changed in indicator-multiload:
importance: Undecided → Medium
assignee: nobody → Michael Hofmann (mh21)
Michael Hofmann (mh21)
Changed in indicator-multiload (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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