https://bugs.kde.org/show_bug.cgi?id=486506
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|UPSTREAM |---
--- Comment #16 from Jakob Petsovits <jpe...@petsovits.com> ---
https://bugs.kde.org/show_bug.cgi?id=472541#c8 had an interesting observation,
in that KDE implements Wayland inhibition locks correctly but some apps or
inhibit helpers don't associate them to focused Wayland surfaces and thus the
lock is not respected by the compositor.
https://codeberg.org/river/river/issues/1079#issuecomment-2013817 has another
comment about this. https://bugzilla.mozilla.org/show_bug.cgi?id=1877022 was a
Firefox issue for that problem.
This leads to the actual source code in
https://hg.mozilla.org/mozilla-central/file/tip/widget/gtk/WakeLockListener.cpp
which shows that Firefox does implement support for the xdg portal D-Bus API,
however only as a fallback after the old-school `org.freedesktop.Inhibit` D-Bus
API has been tried. The aforementioned Wayland API is yet different and only a
last-resort fallback, so probably not further relevant for the purpose of this
bug.
In theory, Firefox should be trying the various D-Bus interfaces in order, and
switch to the next candidate if the previous ones don't work. We should trace
D-Bus calls via dbus-monitor before punting responsibility onto Firefox,
especially if a "blocking sleep and screen locking" message appears in the
Battery applet.
--
You are receiving this mail because:
You are watching all bug changes.
