powersaving detection fails 8 times before success
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Caffeine |
Fix Released
|
High
|
Isaiah Heyer | ||
Bug Description
The first time I click the Caffeine icon, I get some spew, and nothing much else happens. The spew seems to be broken into two categories, which I've de-interlaced below from a run where I clicked the icon three times. Once it has finally detected DPMS power-save mode (which takes about five minutes), everything works as expected, though the icon may be out-of-sync with reality.
I've also included below the output from dbus-monitor during a run (not the same run).
output category one: trying to figure out the powersave method:
(23 Oct 2009) 03:31:35 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:31:50 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:32:05 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:32:20 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:32:35 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:32:50 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:33:05 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:33:20 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:33:35 INFO: Attempting to detect screensaver/
(23 Oct 2009) 03:33:35 INFO: Successfully detected screensaver and powersaving type: DPMS
(23 Oct 2009) 03:33:35 INFO: Caffeine is now preventing powersaving modes and screensaver activation (DPMS)
output category two: clicks
(23 Oct 2009) 03:31:35 INFO: User has clicked the Caffeine icon
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
TypeError: cannot concatenate 'str' and 'NoneType' objects
(23 Oct 2009) 03:31:39 INFO: User has clicked the Caffeine icon
(23 Oct 2009) 03:31:39 INFO: Caffeine is now dormant; powersaving is re-enabled
(23 Oct 2009) 03:32:07 INFO: User has clicked the Caffeine icon
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
TypeError: cannot concatenate 'str' and 'NoneType' objects
output from dbus-monitor:
signal sender=
string ":1.159"
method call sender=:1.159 -> dest=org.
string "type='
method call sender=:1.159 -> dest=org.
string "type='
method call sender=:1.159 -> dest=org.
string "type='error'"
signal sender=
string ":1.160"
string ""
string ":1.160"
method call sender=:1.160 -> dest=org.
method call sender=:1.160 -> dest=org.
method return sender=:1.148 -> dest=:1.160 reply_serial=2
string "IOR:0100000016
signal sender=
string ":1.161"
string ""
string ":1.161"
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
method call sender=:1.161 -> dest=org.
| pragmattica (bnsmith) wrote | #1 |
| Changed in caffeine: | |
| status: | New → Confirmed |
| Changed in caffeine: | |
| importance: | Undecided → High |
| Changed in caffeine: | |
| assignee: | nobody → Isaiah Heyer (freshapplepy) |
| milestone: | none → 1.0.1 |
| Changed in caffeine: | |
| status: | Confirmed → Fix Committed |
| Changed in caffeine: | |
| status: | Fix Committed → Fix Released |
If the icon can get out of sync with reality, that's especially worrying. We were aware that it made multiple attempts to detect dbus before going to DPMS, but I had thought that the icon should never get out of sync...