https://bugs.kde.org/show_bug.cgi?id=512861

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #2 from [email protected] ---
Still reproducible with Dragon 26.04.3.

System:
- Dragon Player 26.04.3 (Gentoo, kde-apps/dragon-26.04.3)
- Plasma 6.7.3, KDE Frameworks 6.28.0, Qt 6.11.1
- Wayland session (XDG_SESSION_TYPE=wayland), KScreenLocker + PowerDevil 6.7.3
- Qt Multimedia backend: FFmpeg (libffmpegmediaplugin.so)

Steps to reproduce:
1. Set "Dim screen" / "Turn off screen" to a short timeout in System Settings
->
   Power Management.
2. Open a video file in Dragon and let it play without touching keyboard or
mouse.
3. The screen dims at the configured timeout and subsequently locks, while
   playback continues.

Additional observation: while a video is playing, the Power and Battery applet
lists no active inhibition.

Looking at the 26.04.3 sources, this appears to be because the application does
not request any inhibition at all.

Regarding the pending fix: merge request
https://invent.kde.org/multimedia/dragon/-/merge_requests/70 ("introduce system
inhibition") adds a SystemInhibitor with Suspend | Idle wired to the player's
playing state, which would cover this report. It has been open since 2025-12-03
and is not merged; master's src/qml/PlayerPage.qml still contains no
inhibition.

One note that may help unblock it: the MR vendors a backport of the inhibitor
because KGuiAddons did not ship it at the time. KSystemInhibitor and the QML
SystemInhibitor type are now part of KGuiAddons (since 6.23) and are present
here in 6.28.0, at /usr/include/KF6/KGuiAddons/ksysteminhibitor.h and
/usr/lib64/qt6/qml/org/kde/guiaddons/. So the vendored copy and its version
guard could likely be dropped in favour of a plain KF6::GuiAddons dependency,
subject to the project's minimum-framework policy.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to