Hardware monitor crashes when added to panel

Bug #367 reported by Dimos Dimoulis on 2005-04-12
4
Affects Status Importance Assigned to Milestone
hardware-monitor (Ubuntu)
Medium
Ubuntu GNOME

Bug Description

I have tested "hardware monitor" in the following platforms, where it worked without problems:

- Warty (Gnome 2.8), compiled from pristine source
- Warty, "backported" Hoary's source package
- Arch Linux (Gnome 2.10), compiled from pristine source

However, in Hoary both the binary package and compiled from source ver...

I have tested "hardware monitor" in the following platforms, where it worked without problems:

- Warty (Gnome 2.8), compiled from pristine source
- Warty, "backported" Hoary's source package
- Arch Linux (Gnome 2.10), compiled from pristine source

However, in Hoary both the binary package and compiled from source versions crash when added to the panel.

Since a) Hoary's source package works fine in Warty (Gnome 2.8) b) pristine source works fine in Arch (Gnome 2.10), I think that this is not caused by an incompatibility between hard. mon. and Gnome 2.10, nor a packaging problem. It has something to do with Gnome as shipped in Hoary.

Changed in hardware-monitor:
assignee: nobody → gnome
Sebastien Bacher (seb128) wrote :

can you provide a backtrace of the crash (you can get it from the dialog to send the bug upstream)?

Matt Edwards (mwedwards) wrote :

Backtrace was generated from '/usr/libexec/hardware-monitor'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228310848 (LWP 32628)]
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbfffe5bc in ?? ()
#2 0x00000000 in ?? ()
#3 0xbfffe51c in ?? ()
#4 0xb78f91a3 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#5 0xb7ad5d97 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 0x00000000 in ?? ()
#8 0x00000000 in ?? ()

Thread 1 (Thread -1228310848 (LWP 32628)):
#0 0xffffe410 in ?? ()
No symbol table info available.
#1 0xbfffe5bc in ?? ()
No symbol table info available.
#2 0x00000000 in ?? ()
No symbol table info available.
#3 0xbfffe51c in ?? ()
No symbol table info available.
#4 0xb78f91a3 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#5 0xb7ad5d97 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#6 <signal handler called>
No symbol table info available.
#7 0x00000000 in ?? ()
No symbol table info available.
#8 0x00000000 in ?? ()
No symbol table info available.
#0 0xffffe410 in ?? ()

SVAKSHA (svaksha) wrote :

The backtrace does not contain any symbols.
Please refer to https://wiki.ubuntu.com/DebuggingProgramCrash for more info.

Changed in hardware-monitor:
status: New → Fixed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers