ValueError in Hardware Sensors: empty string for float()

Could you tell us in which version of awn-extras this happens and when it happens?

Hi,
the version is 0.4.0+brz1372-0ubuntu3
I installed the awn dock yesterday in the evening

Il giorno gio, 24/02/2011 alle 01.43 +0000, onox ha scritto:
> Could you tell us in which version of awn-extras this happens and when
> it happens?
>
> ** Changed in: awn-extras
> Status: New => Incomplete
>
> ** Tags added: hardware-sensors traceback
>
> ** Changed in: awn-extras
> Assignee: (unassigned) => Grega Podlesek (muscardinus)
>

--
Inviata da Ubuntu

Does it happen when you start the applet or only when you interact with it in a certain way?

It say me that the applet is crash and it must be restart, but if i
restart the applet it crash

Il giorno gio, 24/02/2011 alle 15.44 +0000, onox ha scritto:
> Does it happen when you start the applet or only when you interact with
> it in a certain way?
>

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/awn/extras/awnlib.py", line 1391, in init_start
    applet_class(applet)
  File "/usr/share/avant-window-navigator/applets/hardware-sensors/hardware-sensors.py", line 97, in __init__
    self.update_all_sensors()
  File "/usr/share/avant-window-navigator/applets/hardware-sensors/hardware-sensors.py", line 164, in update_all_sensors
    sensor.read_sensor()
  File "/usr/share/avant-window-navigator/applets/hardware-sensors/interfaces/nvidiasensors.py", line 55, in read_sensor
    self.value = float(nv_sensor.group("value"))
ValueError: empty string for float()

No need to paste the traceback twice. Please paste the output of this command:
/usr/bin/nvidia-settings -q GPUCoreTemp

Attribute 'GPUCoreTemp' (alessandro-HP-Pavilion-dv7-Notebook-PC:0.0):
62.
    'GPUCoreTemp' is an integer attribute.
    'GPUCoreTemp' is a read-only attribute.
    'GPUCoreTemp' can use the following target types: X Screen, GPU.

Il giorno ven, 18/03/2011 alle 11.31 +0000, Gabor Karsay ha scritto:
> No need to paste the traceback twice. Please paste the output of this command:
> /usr/bin/nvidia-settings -q GPUCoreTemp
>

Formatting seems to be different in your output than the applet expects. To make sure, please run this in terminal:
python
# now you'r in the python console, it starts with >>>
import os
os.popen("/usr/bin/nvidia-settings -q GPUCoreTemp").read()
# here you get some output, paste it in the bug report
quit()

  Attribute 'GPUCoreTemp' (alessandro-HP-Pavilion-dv7-Notebook-PC:0.0): 55.
    'GPUCoreTemp' is an integer attribute.
    'GPUCoreTemp' is a read-only attribute.
    'GPUCoreTemp' can use the following target types: X Screen, GPU.

"\n Attribute
'GPUCoreTemp' (alessandro-HP-Pavilion-dv7-Notebook-PC:0.0): 55.\n
'GPUCoreTemp' is an integer attribute.\n 'GPUCoreTemp' is a read-only
attribute.\n 'GPUCoreTemp' can use the following target types: X
Screen, GPU.\n\n"

Il giorno ven, 18/03/2011 alle 14.31 +0000, Gabor Karsay ha scritto:
> Formatting seems to be different in your output than the applet expects. To make sure, please run this in terminal:
> python
> # now you'r in the python console, it starts with >>>
> import os
> os.popen("/usr/bin/nvidia-settings -q GPUCoreTemp").read()
> # here you get some output, paste it in the bug report
> quit()
>

Thanks for your help. The problem is kind of fixed in rev. 1520. The applet won't crash anymore. It crashed because it couldn't interpret the output of nvidia-settings but the output you gave in comment #10 is o.k. so I don't know what's the ultimate cause of this crash. (However the output in comment #7 might be problematic because the value 62 seems to be on a new line.)