gDesklets

gDesklets Gauge

Bug #161943 reported by Carl
4
Affects Status Importance Assigned to Milestone
gDesklets
Fix Released
Medium
Bjoern Koch
gDesklets release-of-0.36

Bug Description

Gauge does not respond. Will display 100% regardless of fill value. Examples that work with gDesklets 0.35 are SideCandy CPU and SideCandyWireless desklets. These will not not display the gauge properly with 0.36 beta.

Revision history for this message
Bjoern Koch (h.humpel) wrote :

Can't be confirmed here.
SideCandyCPU isn't working on 0.36beta anyway and I have no Wireless, so I couldn't test the examples mentioned above.
But any other desklet I have tried here using Gauges are working properly.

Could you please post more information like the logs and test some other desklets with gauges (like SideCandyHDD, FTB-mem-gauge, FTB-disk-gauge, FTB-cpu-gauge) ?

Changed in gdesklets:
assignee: nobody → h.humpel
status: New → Incomplete
Revision history for this message
Bjoern Koch (h.humpel) wrote :

OK, just upgraded to the latest beta (rev. 82). Still was using rev. 74 or 75 before and the gauges were working there fine.
Now the gauges are stuck at 100%. But now the SideCandy-CPU is finally starting/working again ;).

Will take a deeper look into this one!
Changing status to confirmed.

Changed in gdesklets:
importance: Undecided → Medium
milestone: none → release-of-0.36
status: Incomplete → Confirmed
Revision history for this message
Martin Grimme (martin-grimme) wrote :

The gauges bug is now fixed in the 0.3x branch.

Changed in gdesklets:
status: Confirmed → Fix Committed
Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 161943] Re: gDesklets Gauge

I thought I was taking care of the the problem. Since we don't support <
gtk2.10 anymore...what was wrong. Still a bit clueless...

Revision history for this message
Martin Grimme (martin-grimme) wrote :

I have GTK 2.10 and PyGTK 2.10 and it shows the same broken behavior regarding GTK-Clipping (at least on Ubuntu Feisty). No difference to GTK 2.8, so it looks like we have to keep this ugly workaround. :(

Revision history for this message
Robert Kubík (Pastierovič) (just-me) wrote :

Christian: as I understand the problem was that you didn't remove the right file:

if (gtk.gtk_version >= (2, 8, 0)):
    from TargetGroup2 import TargetGroup
else:
    from TargetGroup import TargetGroup

TargetGroup2 workaround works in gtk >=2.8
We may consider removing TargetGroup.py instead.

Revision history for this message
Christian Meyer (chrisime) wrote :

Ahh, you're right. Quite an embarassing overlook. I agree to remove
TargetGroup.py if there are no further problems.

Robert Kubík (Pastierovič) (just-me)
Changed in gdesklets:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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