Bugzilla Bug 140264

The 1.6 version works perfectly...

emerge --info:

Portage 2.1.1_pre2-r8 (default-linux/x86/2006.0, gcc-3.4.4/vanilla,
glibc-2.4-r3 , 2.6.17-gentoo-r2 i686)
=================================================================
                       System Settings
=================================================================
System uname: 2.6.17-gentoo-r2 i686 Intel(R) Celeron(R) CPU 2.00GHz
Gentoo Base System version 1.12.1
ccache version 2.4 [enabled]
app-admin/eselect-compiler: 2.0.0_rc2-r1
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r2
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.17
sys-devel/gcc-config: 2.0.0_rc1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r5
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shu tdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/eselect/compiler
/etc/gcon f /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox
s fperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/ distributions/gentoo"
LANG="hu_HU"
LC_ALL="hu_HU"
LINGUAS="hu en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude='/d istfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa apache2 apm arts avi berkdb bitmap-fonts bluetooth bzip2 cdr
cli  crypt cups dbus dlloader dri dvd dvdr eds emboss encode firefox foomaticdb
fort ran gdbm gif glibc-omitfp gnome gpm gstreamer gtk gtk2 hal imlib ipv6
isdnlog ja va jpeg kde libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls
nptl nptlonl y nsplugin nvidia ogg opengl oss pam pcre pdflib perl pic png pppd
python qt qt3  qt4 quicktime readline reflection sdl session spell spl sse sse2
ssl tcpd truet ype truetype-fonts type1-fonts udev unicode unicude usb
userlocales vorbis xml x mms xorg xv zlib elibc_glibc input_devices_mouse
input_devices_keyboard kernel_l inux linguas_hu linguas_en userland_GNU
video_cards_nv video_cards_nvidia"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA

Could you post the output when running it from a terminal:
/usr/libexec/sensors-applet

then add to panel...

Also if you could get a stack trace when the crash occurs that'd be great too
(see http://www.davyd.id.au/articles/debugging-gnome-applets.shtml)

I'm very sorry, but I have moved to debian yesterday... :-(

But it is possibly that  tomorrow I will move back to gentoo :-/

Don't ask, why...



I have ran '/usr/libexec/sensors-applet', but it haven't got an output.

It have just exited.

I can't, remember, if I have added it to the panel....

When running the executable from the command-line, then only time it will just
exit without waiting for you to add it to the panel is if it is ALREADY running
on the panel. 

SO the question is IF it is already running on the panel, isnt this bug invalid
- ie. it hasnt crashed when adding it to the panel?

Sensors-applet wasn't added to the panel, since, when I tried to add, it said
somethinglike: crashed WHEN adding to the panel. Then it asked, if I would like
to remove from the panel, and I selected yes.
One more question, (I hope, you won't be angry):
When I installed the system, my Celeron processor was overclocked from 2 GHz to
2.6GHz, but memtest86 doesn't reported an error.
Is it still possible, that my system produced wrong code, and this is why
sensors-applet crashed?
(Now I have a 2.8 GHz Celeron D, so it isn't overclocked.)

I wasn't angry, but you have provided conflicting information and so I am not
able to help resolve the issue if I can't understand what is going on.

Even though memtest reports no errors, it is possible the code could have been
actually incorrect but I think that is unlikely. More likely is that there is
an actual bug (although I would like to think not, in general this is more
likely).

Does the applet still crash when you try to add it to the panel?
Can you explain exactly what happens when you try to run it from the command
line?
Please try to provide as much information as possible.
Also can you please try to obtain a stack trace when the applet crashes as per
the supplied list (however for this to be useful please make sure you enable
the debug USE flag and reinstall sensors-applet).

ie:
USE="debug" emerge sensors-applet
gdb /usr/libexec/sensors-applet

then inside gdb type:
run

now you can add it to the panel and if it crashes, type:
bt
inside gdb and it will display the stack trace for the crash.
please then post this stack trace and I can then try and help to resolve the
issue more.

Created an attachment (id=92338) [details]
Gdb debug info for sensors-applet

Here you are. :)

Thanks for the stack trace - I have fixed the bug and will release a new
version later today most likely, in which this bug (and an number of others)
are fixed. Hopefully it won't take too long to make it into the portage tree.
Thanks for your help.

New version of GNOME Sensors Applet - 1.7.3 - released today. Please try this
and see if it the crash has been resolved.

Created an attachment (id=92391) [details]
Sensors-applet-1.7.3 debog log

I have copied sensors-applet-1.7.2-ebuild to sensors-applet-1.7.3.ebuild
in /usr/local/portage, so in a portage overlay.
I have issued an ebuild sensors.....ebuild digest .
Now the gdb log is a bit other then before.
I don't know what to do... :-/
Cause the homepage of Sen-app says that exactly this bug was fixed in this
release...
And i have issued an emerge --sync all before this, but it seems like, your new
ebuild wasn"t there.
The only change was, that gnome-panel said whether it should reload the applet,
and not if I want to remove the crashed app...

Hmmmm...
If I emerge like this:
USE="-lm_sensors debug" emerge sensors-applet
It works well, and I can still monitor Processor, Chipset and other
temperatures, which are part of the lm_sensors ... :-S
Interesting...
And this applies to 1.7.2 version too.

new version in portage that should fix this.

Ahh thanks for testing that.
Indeed clearly the bug was not fixed - after more investigating I have found
the real cause, and so am releasing version 1.7.4 to correct this.

Well..
Now it works.
But what is that "A" after the values?
And it writes: 43,00A .
How can I get back the normal 43, or 43C back?
However, I really thank you, for helping me! :-)

It would seem that there is perhaps a misconfiguration of your
/etc/sensors.conf file and so the libsensors interface is identifying the
sensors as current sensors (not temperature or fan or voltage sensors), or
perhaps the libsensors interface code is a bit buggy (although many
distributions (Ubuntu, Debian, Feodora) enable libsensors support by default
and I have not had a single bug report from them about it. So I think there is
most likely a problem with your sensors.conf file - try replacing this with a
known good version, and if it does not fix the issue, I think you should not
use the lm_sensors support and let Sensors Applet read the information
directly.

You are right.
I have re-emerged lm_sensors, so it had overwritten my modified sensors.conf.
(I have ignored some vents after the first lm_sensors emerge)
Now sensors-applet 1.7.4 works, and it is stable. :-)
The only problem left, is that hddtemp support is cimpiled in, however it
doesn't show up (the hddtemp daemon is running).
But that is because hddtemp doesn't really support my drive.
See Bug #141273 .
So this bug has been fixed.

Excellent. I am glad that I was able to fix the bug for you in the latest
version 1.7.4 (hint hint to Gentoo GNOME herd to please bump sensors-applet
1.7.3 to 1.7.4 in portage).

Thanks for your help with the debugging info along the way.

I would love to do the bump, but, I am having issues with it here (have for a
while, just haven't searched them out...) - whenever I try to add the applet to
my panel, my system simply becomes unresponsive - I can ssh in, and top shows
the applet doing something using up the cpu, then it stops, then repeats... 
The applet has always worked fine in Ubuntu (but I don't feel like reinstalling
Ubuntu to see what the options are that they used for it) - This is on a Dell
Inspiron 8100/C800 (it has a C800 motherboard in it) - as far as I can tell,
there are no lm_sensors, and I don't believe they were monitoring the hard
drive temperature either, so - I just recompiled my kernel with i8k as a module
rather than built in, and will attempt to load it again and see what we get
this time.

Weird, is that only with 1.7.4 or with 1.7.3 as well?

It has been with every version from 1.6.2 (When I installed Gentoo on here) and
up - i8kctl temp shows the correct temperature, so I do have i8k on here
correctly - just like to monitor it on my panel with the sensors applet like I
did in Ubuntu

Have any previous versions ever worked for you?

1.7.4 is now in the Portage tree.  Give it a couple of hours then sync.  Thanks
for all the help

no probs. glad I could help. thanks to all the Gentoo GNOME herd - In general I
think you guys do a great job managing such a complex set of packages and you
dont get the recognition you deserve. So thanks from me (as I say I am glad to
help in any way I can).