| Summary: | screen saver & TDEpowersave ignore certain user time settings | ||
|---|---|---|---|
| Product: | TDE | Reporter: | ThoMaus <thomas.maus> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | bugwatch, deloptes, michele.calgaro, slavek.banko, thomas.maus |
| Priority: | P5 | ||
| Version: | R14.1.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2696 | ||
|
Description
ThoMaus
2016-04-19 13:19:49 CDT
Hi Thomas, could you post a screenshot of tdepowersave settings and one for the tde screensaver settings in the TDE control center? I would like to try to simulate the bug and work on it. By the way, is this for R14.1.x or for R14.0.3? Thanks (In reply to Michele Calgaro from comment #1) > Hi Thomas, > could you post a screenshot of tdepowersave settings and one for the tde > screensaver settings in the TDE control center? I'll give you the specific config file (sections): from 'kdesktoprc' the ScreenSaver section: ---8<----------------------------------------- [ScreenSaver] DelaySaverStart=true Enabled=true HideActiveWindowsFromSaver=true HideCancelButton=false Lock=true LockGrace=60000 Saver=KBlankscreen.desktop Timeout=2040 UseTDESAK=true UseUnmanagedLockWindows=false VibrateUnlock=true ---8<----------------------------------------- the complete 'tdepowersaverc' -- the system is running in 'Performance' mode: ---8<----------------------------------------- [Acoustic] autoInactiveAction=Suspend to RAM autoInactiveActionAfter=99 autoSuspend=true blankSs=false brightnessPercent=80 disableNotifications=false specSsSettings=false [General] ActionOnLidClose=SUSPEND2RAM ActionOnPowerButton=LOGOUT_DIALOG AlreadyStarted=true batteryCritical=3 batteryCriticalAction=SUSPEND2DISK batteryWarningAction=CPUFREQ_POWERSAVE [Performance] autoDimm=true autoDimmAfter=15 autoInactiveAction=Suspend to RAM autoInactiveActionAfter=99 autoSuspend=true blankSs=false brightnessPercent=90 cpuFreqPolicy=PERFORMANCE disableNotifications=false disableSs=false powerOffAfter=45 standbyAfter=15 suspendAfter=30 [Powersave] autoDimmSchemeBlacklistEnabled=false autoInactiveAction=Suspend to RAM autoInactiveActionAfter=15 autoSuspend=true brightnessPercent=60 cpuFreqPolicy=POWERSAVE disableNotifications=false [Presentation] blankSs=false cpuFreqPolicy=PERFORMANCE disableNotifications=false ---8<----------------------------------------- > I would like to try to simulate the bug and work on it. > By the way, is this for R14.1.x or for R14.0.3? The report is for the most current version available in the recommended repository for OpenSuSE Tumbleweed, i.e. R14.0.3. If you can point me to a more leading edge repository I'll test more recent versions. Cheers! On debian R14.0.3, not using suspend2disk, everything else is working as expected. There was something related to upower 0.99 and dbus interface. Not sure if that changed recently in debian. I hope this helps TDEPowersave logic was pretty buggy before R14.0.4, especially the part regarding timers and action. Quite a bit of work went into it in bugs 2412, 2599, 2603 and 2632, especially bug 2603. I have tried to replicate the problem again on buster/R14.1-dev, both using the exact settings provided in comment 2 and several other arbitrary settings. I have never run into any problem or unexpected actions after R14.0.4. Since I believe the cause of the problem was fixed in bug 2603 and everything seems to be working fine, I am closing this bug. Feel free to reopen it if you run into any problem, and in that case please provide a mean to reproduce it. *** This bug has been marked as a duplicate of bug 2603 *** |