[Linux] "firefox is currently inhibiting power management" and OS doesn't suspend
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: kjur, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:132.0) Gecko/20100101 Firefox/132.0
Steps to reproduce:
Updated FF via Mozilla repo.
Currently it's version 132.0~build1 (64-bit) installed from Mozilla repo: https://packages.mozilla.org/apt mozilla main
Actual results:
Some recent Firefox versions cause "firefox is currently inhibiting power management" message in Power Manager in XFCE (Xubuntu 24.10) and block system to suspend (FF is not running or still open, but a plain text website is open, no videos playing).
Expected results:
Firefox shouldn't inhibit power management when laptop lid is closed.
Comment on attachment 9434344 [details]
image.png
the message "Firefox is currently inhibiting power management" is there and I can't get rid of it. Sometimes it appears twice.
Comment 3•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 4•1 year ago
|
||
duplicate of: https://bugzilla.mozilla.org/show_bug.cgi?id=1862159
Comment 5•1 year ago
|
||
Please run Firefox on terminal, try to reproduce the issue and attach a log with MOZ_LOG="LinuxWakeLock:5" env variable so we can check why Wake lock is applied.
Run as:
MOZ_LOG="LinuxWakeLock:5" firefox > log.txt 2>&1
and attach the log here.
Thanks.
Comment 6•1 year ago
|
||
Also please test latest nightly with clean profile:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_Nightly_binaries
Thanks.
Updated•1 year ago
|
This is the log for around 10 minutes of running Firefox. I closed the lid once and then watch something on Youtube.
Let me know if this is suffice.
Not sure if I'm right, but since upgrading to version 133 it looks like it may be fixed. Need to test more and report back here.
Updated•1 year ago
|
Comment 10•1 year ago
|
||
Yes, 133.0 should have the fix.
Description
•