Comment 1 for bug 1017275

The problem is that the udisks daemon takes about 1 minute until it checks the temperature of the disk - so when we first query udisks at login it returns 0 as it hasn't actually checked it yet - there is no way for indicator-sensors to tell though that this 0 is invalid since udisks doesn't return any error - so from the point of view of indicator-sensors it just looks like a really low reading... we may be able to try and work around it but I don't really like the idea of having to put some hack in which makes maintaining the code harder in the future.