viewing a video, FF does not disable "lock screen" and "screen saver" in kde environment
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: epistemepromeneur, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
I am viewing a video:
- A youtube one
or - a video from https://www.france.tv/france-3/les-enquetes-de-morse/
or - a video from https://www.dailymotion.com
Actual results:
In KDe environment, "lock screen" and "screen saver" features are not disabled.
KDE gears 21.12.1
plasma : 5.23.5
kde frameworks : 5.90.0
qt 5.15.2
Expected results:
In KDE environment, "lock screen" and "screen saver" features are disabled.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
What do you mean those features are not disabled? Do you mean the screen went off while you're watching those videos?
Would you mind to capture a debug log with MOZ_LOG=LinuxWakeLock:5,nsMediaElement:5?
Thank you.
Comment 3•4 years ago
|
||
By checking the wakelock implementation on Linux, we support using wakelock on different desktop environments already.
(In reply to Alastor Wu [:alwu] from comment #2)
What do you mean those features are not disabled? Do you mean the screen went off while you're watching those videos?
The screen is switched off.
Comment 5•4 years ago
•
|
||
But could you help us to capture debug log like what I mentioned in comment2?
In addition, would you mind to update info from about:support as well?
Thanks.
Here is the log of
x@localhost:> export MOZ_LOG=LinuxWakeLock:5,nsMediaElement:5> export MOZ_LOG_FILE=
x@localhost:/FFlog.txt> firefox
x@localhost:
You can see with the plasmoid "battery and light" that lock screen and screen saver are not disabled.
Comment 8•4 years ago
|
||
When you captured the log, were all other files empty? Because the wakelock log should suppose to be in another file because the wakelock should be called in the chrome process.
In addition, would you mind to help me use mozregression to find out if this is a regression issue? Now it looks like bug 1745179 (caused by bug 1733796), but I am not sure.
Thank you.
(In reply to Alastor Wu [:alwu] from comment #8)
When you captured the log, were all other files empty?
yes
| Reporter | ||
Comment 10•4 years ago
|
||
After many experiments, I conclude that it is not a Firefox problem. I am waiting for a big update of KDE in February.
Description
•