[kde] [Bug 506015] Issue with system turning off screen

TraceyC bugzilla_noreply at kde.org
Tue Jun 24 23:39:41 BST 2025


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

TraceyC <kdedev at tlcnet.info> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdedev at tlcnet.info

--- Comment #1 from TraceyC <kdedev at tlcnet.info> ---
I'm not able to reproduce this on a system running git-master that has an
NVIDIA GPU

Running the dbus command, this is all that's written to the journal

`dbus-send --session --print-reply --dest=org.kde.kglobalaccel 
/component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut
string:'Turn Off Screen'`

Jun 24 17:11:56 tlc-xps17-solus dbus-broker[1249]: A security policy denied
:1.43 to send method call
/org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to
org.freedesktop.login1.
Jun 24 17:11:56 tlc-xps17-solus kwin_wayland[2247]: kwin_core: Failed to delay
sleep: Sender is not authorized to send message
Jun 24 17:11:56 tlc-xps17-solus dbus-broker[1249]: A security policy denied
:1.43 to send method call
/org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to
org.freedesktop.login1.
Jun 24 17:11:56 tlc-xps17-solus kwin_wayland[2247]: kwin_core: Failed to delay
sleep: Sender is not authorized to send message
Jun 24 17:11:56 tlc-xps17-solus dbus-broker[1249]: A security policy denied
:1.43 to send method call
/org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to
org.freedesktop.login1.
Jun 24 17:11:56 tlc-xps17-solus kwin_wayland[2247]: kwin_core: Failed to delay
sleep: Sender is not authorized to send message

The screens are turned off and stay off until I press a key or move the mouse.
I waited 30 seconds.
Same behavior on a system on git-master with an AMD GPU, and on that system
with a 6.3.5 Plasma session

I'll leave this open so others can try reproducing

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list