ValueError in Hardware Sensors: empty string for float()

Bug #723916 reported by Alessandro Ghione
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Awn Extras
Fix Released
Low
Gabor Karsay

Bug Description

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()

Related branches

Revision history for this message
onox (onox) wrote :

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: nobody → Grega Podlesek (muscardinus)
Revision history for this message
Alessandro Ghione (alex81) wrote : Re: [Bug 723916] Re: ValueError in Hardware Sensors: empty string for float()

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

Revision history for this message
onox (onox) wrote :

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

Revision history for this message
Alessandro Ghione (alex81) wrote :

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?
>

Revision history for this message
Alessandro Ghione (alex81) wrote :

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()

Revision history for this message
Gabor Karsay (gabor-karsay) wrote :

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

Revision history for this message
Alessandro Ghione (alex81) wrote :

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
>

Revision history for this message
Gabor Karsay (gabor-karsay) wrote :

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()

Revision history for this message
Alessandro Ghione (alex81) wrote :

  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.

Revision history for this message
Alessandro Ghione (alex81) wrote :

"\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()
>

Revision history for this message
Gabor Karsay (gabor-karsay) wrote :

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.)

Changed in awn-extras:
assignee: Grega Podlesek (muscardinus) → Gabor Karsay (gabor-karsay)
importance: Undecided → Low
milestone: none → 0.4.2
status: Incomplete → Fix Committed
Povilas Kanapickas (p12)
Changed in awn-extras:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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