Do you find the any line likes `WakeLockTopic::DBusUninhibitFailed()` or `WakeLockTopic::DBusInhibitFailed(...)` in the log? I suspect PowerManager over DBus may fail several times for uninhibiting (>= 5). And, Firefox disables wake lock from this point at all. We should retry here instead of just disabling it. Please check the log.
Here we have two cases, failures for inhibit and failures for uninhibit. For inhibit, it will try next wakelock type unitl all wakelock types has been tried, then it will disable wakelock from this point. One of issue is when we had one of types available at beginning and fails at one point later, it will try next type. That means once one and only one available wakelock type on a machine fail even just one time, wakelock will be disabled totally. We should stick at the same type forever once it success for once. And, keep retrying it. For the uninhibit case, it tolerates 5 failures and disables wakelock after that. We should not have this threshold. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047262 Title: Firefox stopped inhibiting screensaver on video playback To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/2047262/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
