This is probably the same basic issue as in https://bugs.launchpad.net/awn-extras/+bug/616246; the sequence of errors is the same (it raises a ValueError when I first add the applet, and IndexError each time I restart awn until I remove that applet instance).
The root cause for me is that the hddtemp server on port 7634 is spitting out a model name that contains garbage at the end. In particular, it looks something like "Mushkin MKNSSDCL240GB-DX \x10\x80". (With more spaces in the middle.) The applet passes that around internally without problems, but the gconf connection rejects the update to self.applet.settings["labels"]. Because the "ids" array is already set by that point, the partially-configured gconf values confuse later startups.
Both "hdparm -i /dev/sda" and "udisks --dump" show just "Mushkin MKNSSDCL240GB-DX" as the model. I will follow up with the author of hddtemp to figure out what the root cause is, and whether hddtemp is doing the expected thing.
This is probably the same basic issue as in https:/ /bugs.launchpad .net/awn- extras/ +bug/616246; the sequence of errors is the same (it raises a ValueError when I first add the applet, and IndexError each time I restart awn until I remove that applet instance).
The root cause for me is that the hddtemp server on port 7634 is spitting out a model name that contains garbage at the end. In particular, it looks something like "Mushkin MKNSSDCL240GB-DX \x10\x80". (With more spaces in the middle.) The applet passes that around internally without problems, but the gconf connection rejects the update to self.applet. settings[ "labels" ]. Because the "ids" array is already set by that point, the partially- configured gconf values confuse later startups.
Both "hdparm -i /dev/sda" and "udisks --dump" show just "Mushkin MKNSSDCL240GB-DX" as the model. I will follow up with the author of hddtemp to figure out what the root cause is, and whether hddtemp is doing the expected thing.