Version: 2.0-beta1 (using KDE 4.5.85) OS: Linux In this blog entry there is a hint, how this can be fixed: http://drfav.wordpress.com/2010/11/10/updates-from-kde-power-management-land-for-users-and-developers/ Reproducible: Always OS: Linux (i686) release 2.6.37-7-generic-pae Compiler: cc
The bug is still present in KDE 4.6 R1. I see this bug is unassigned. Would be nice this still would be fixed for release, since it makes using of Dragon Player pretty annoying. According to the link above fixing this bug means 3 lines of code.
Created attachment 55678 [details] Explanation of the issue and idea to solve it It's a quote from blog content which is describe the Bug and an idea to solve it
Next time when you posting an issue / Bug, please provide full information and NEVER post a link. The dev team wouldn't or don't have plenty of time if all the Bug reports using "links" to other place which is explain the Bug. Regards
You are right, sorry for that. But is creating an attachment with the explanation really better? Both is one click, for the attachment one even has to scroll down.
Well, attachment is mean that "something" you need to read or open. Try open my attachment and your link. :) It isn't the main poin with this bug anyway. Let's hope the dev-team will fix this issue before release-date. Regards
Commit 1217599 (see bug 243035) might be related to this report.
if (m_stopSleepCookie == -1) m_stopSleepCookie = Solid::PowerManagement::beginSuppressingSleep(QLatin1String( "watching a film" )); if (m_stopScreenPowerMgmtCookie == -1) m_stopScreenPowerMgmtCookie = Solid::PowerManagement::beginSuppressingScreenPowerManagement(QLatin1String( "watching a film" )); if (!m_stopScreenSaver) m_stopScreenSaver = new KNotificationRestrictions(KNotificationRestrictions::ScreenSaver); I if it not working then that'd be a bug in Solid or KNotificationRestrictions respectively.