Summary: | KDE's screensaver does not "listen" to Inhibit Dbus command. | ||
---|---|---|---|
Product: | [Unmaintained] kscreensaver | Reporter: | firewalker <firew4lker> |
Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | arthur, clearmartin, firew4lker, matteorr, oliver.henshaw |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
firewalker
2012-05-04 12:44:50 UTC
I am having the same issue. Neither totem nor Caffeine prevent screen from turning off. 1. Media players should use the org.freedesktop.ScreenSaver interface - see https://trac.videolan.org/vlc/ticket/7824 for vlc (fixed in the upcoming 2.1) and http://bugzilla.mplayerhq.hu/show_bug.cgi?id=1887 for mplayer (seems to have stalled). 2. The qdbus method won't work because the inhibition only lasts until qdbus exits and so disappears from the session bus. The Inhibit-calling process needs to stay alive and on the session bus for the duration of the movie. Perhaps you could use the battery applet or per-activity power management in the meantime? See http://drfav.wordpress.com/2011/10/04/power-management-a-new-screencast/ for example. (In reply to comment #1) > I am having the same issue. Neither totem nor Caffeine prevent screen from > turning off. I'm not sure about totem but I think Caffeine should work. Can you re-test both in kde 4.10? Just for extra info. How can someone keep it alive on the system bus? SMPlayer is successfully inhibiting screensaver since KDE version 4.10 (or sooner). VLC has still the issue. I'm using KDE 4.11.0. I don't know about Caffeine (is that the inhibit screen saver panel applet?) - I use "Enable Power Management" checkbox on battery popup to do the work. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug. Please re-test and file a new bug with kscreenlocker if the issue persists. |