! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Tachometer tab in xfce4-sensors is not shown with some specific sensors selected
Status:
RESOLVED: WONTFIX
Product:
Xfce4-sensors-plugin
Component:
General

Comments

Description Heiko Baums 2011-05-10 08:41:00 CEST
If I start xfce4-sensors, select some specific sensors and try to switch to the tachometer tab it eats up the CPU resources on the first CPU core but doesn't display the tachometer tab and doesn't respond anymore. xfce4-sensors has to be killed.

This happens if one or more of these sensors of the module it8720-822 are selected:
in5
temp1
temp3

The temp3 sensor doesn't exist on my mainboard.

If I unselect these sensors the tachometer tab is shown as expected.

Unfortunately there's no error message.
Comment 1 Heiko Baums 2011-05-10 08:55:46 CEST
Forget to mention the version info. It happens with the 1.0.0 release and with the latest git snapshot.
Comment 2 Fabian Nowak editbugs 2011-05-10 11:52:32 CEST
What do you mean by "the sensors don't exist?". These sensor features are pulled from the libsensors library and will be shown with the "sensors" command as well (try multiple runs, grepping for this one sensor, does the value repeat al lthe time or is it 0 or 65536 sometimes?). So from the libxfce4sensors' perspective, this temp3 does exist.

Do you mean that really the tab at the top of the application vanishes only because of selecting this temp3 sensor feature? Never experienced such issues on my own with temp3, temp4, temp5 and so on.

Moreover, is there a real value shown in the treelist for temp3? Such as -45 or whatever? Because then there really *are* values (from libsensors perspective) and you will have to ask the libsensors people with your hardware setup and issue of not gaining values for temp3.
Comment 3 Heiko Baums 2011-05-10 23:42:08 CEST
(In reply to comment #2)
> What do you mean by "the sensors don't exist?". These sensor features are
> pulled from the libsensors library and will be shown with the "sensors" command
> as well (try multiple runs, grepping for this one sensor, does the value repeat
> al lthe time or is it 0 or 65536 sometimes?). So from the libxfce4sensors'
> perspective, this temp3 does exist.

Well, the BIOS (CMOS Setup Utility) only shows values for the "Current System Temperature" (temp1) and the "Current CPU Temperature" (temp2). So I guess that there are only these two sensors on the mainboard. temp3 always shows 79°C or 80°C. So I guess it's a default value of libsensors. If there is a third sensor I don't know for what it is.

But since the issue appears also if only temp1, which does exist on the mainboard, is selected, it's not important if temp3 does exist on the hardware. So I guess you can safely ignore this question.

> Do you mean that really the tab at the top of the application vanishes only
> because of selecting this temp3 sensor feature? Never experienced such issues
> on my own with temp3, temp4, temp5 and so on.

No, it vanishes - in fact it doesn't vanish, it just isn't shown while the first CPU core is working at maximum - if one or more of the three sensors in5, temp1 and temp3 is selected. With every other selected sensor the tab at the top of the application is shown correctly.

temp1 and most likely in5 do exist on the mainboard.

> Moreover, is there a real value shown in the treelist for temp3? Such as -45 or
> whatever? Because then there really *are* values (from libsensors perspective)
> and you will have to ask the libsensors people with your hardware setup and
> issue of not gaining values for temp3.

There's always shown a value for temp3. I don't think that there's an issue with libsensors as it gives a valid value (from the software's perspective). I guess there are some mainboards with the it8720-228 chip which have two temp sensors and some which have three. Like I said above, I guess you can safely ignore that.
Comment 4 Fabian Nowak editbugs 2011-05-30 22:12:51 CEST
(In reply to comment #3)
Is it possible that you have several older and newer versions of libxfce4sensors installed? Look at /usr/(local/)lib7xfce4/modules/ for libxfce4sensors* and delete all different versions; then reinstall the package.

It might work then, though not for sure.
Comment 5 Heiko Baums 2011-06-07 13:07:59 CEST
(In reply to comment #4)
> (In reply to comment #3)
> Is it possible that you have several older and newer versions of
> libxfce4sensors installed? Look at /usr/(local/)lib7xfce4/modules/ for
> libxfce4sensors* and delete all different versions; then reinstall the package.
> 
> It might work then, though not for sure.

No, there's only one version of libxfce4sensors installed.

In this directory there are only these files and symlinks:
libxfce4sensors.so -> libxfce4sensors.so.1.2.2
libxfce4sensors.so.1 -> libxfce4sensors.so.1.2.2
libxfce4sensors.so.1.2.2

They all belong to the package xfce4-sensors-plugin and are reinstalled by this package.
Comment 6 Fabian Nowak editbugs 2014-04-30 00:04:14 CEST
Sorry, couldn't reproduce. As no more comments appeared, but xfce4-sensors 12.5 is out meanwhile, I guess the issue is fixed anyway, if not even by a new computer.

Bug #7601

Reported by:
Heiko Baums
Reported on: 2011-05-10
Last modified on: 2014-04-30

People

Assignee:
Fabian Nowak
CC List:
0 users

Version

Version:
unspecified

Attachments

Additional information