Hi, as already reported here: https://bugs.kde.org/show_bug.cgi?id=355687 and here http://blog.broulik.de/2015/02/power-management-in-5-3/#comment-369 autosuspension stopped working on my wetab (https://en.wikipedia.org/wiki/WeTab#Technical_specifications). As at the same time (AC mode -> battery mode) the backlight was not being set properly, we first thought that the bug might be in powerdevil. However, that turned out to be a completely unrelated issue. So what happens? Nothing. ;) If I unplug the AC cable from the wetab, it does not autosuspend after the given time period. It worked flawlessly before with KDE4 (e.g. kdelibs kidletime). So maybe something changed in the KF5 version? Some tighter thresholds? Granted, the wetab is not very strong, so there is always a little pressure on the CPU. I did some tests, though: Linux 4.2.5-1-ARCH (wetab) 22.11.2015 _x86_64_ (2 CPU) 15:30:16 CPU %user %nice %system %iowait %steal %idle 15:30:18 all 0,51 0,00 2,28 0,00 0,00 97,21 15:30:20 all 0,00 0,00 2,79 0,00 0,00 97,21 15:30:22 all 0,51 0,00 1,79 0,00 0,00 97,70 15:30:24 all 3,32 0,00 4,86 1,28 0,00 90,54 15:30:26 all 0,26 0,00 1,79 0,00 0,00 97,96 15:30:28 all 5,41 0,00 3,87 0,00 0,00 90,72 15:30:30 all 0,26 0,00 1,29 0,00 0,00 98,46 15:30:32 all 0,77 0,00 2,04 0,00 0,00 97,19 15:30:34 all 0,51 0,00 2,81 0,00 0,00 96,68 15:30:36 all 0,77 0,00 2,30 0,00 0,00 96,93 15:30:38 all 0,51 0,00 1,28 0,00 0,00 98,21 15:30:40 all 0,25 0,00 2,29 0,00 0,00 97,46 15:30:42 all 0,26 0,00 2,04 0,00 0,00 97,70 15:30:44 all 1,02 0,00 2,30 0,00 0,00 96,68 15:30:46 all 1,28 0,00 2,81 0,00 0,00 95,92 15:30:48 all 0,00 0,00 2,30 0,00 0,00 97,70 15:30:50 all 0,00 0,00 2,54 0,00 0,00 97,46 15:30:52 all 0,51 0,00 2,54 0,00 0,00 96,95 15:30:54 all 3,31 0,00 4,33 1,02 0,00 91,35 15:30:56 all 0,00 0,00 1,55 0,00 0,00 98,45 Average: all 0,97 0,00 2,49 0,11 0,00 96,43 In my opinion, this should be idle 'enough'. Are there any thresholds? Any place to change them? Can I get some debug messages from files, kded5 or similar? Thanks in advance. If you need further information, let me know.
Marking as duplicate of the other bug report. If this issue is not fixed, please reopen. *** This bug has been marked as a duplicate of bug 355687 ***