Author Topic: MiniMe 2010: Power management/screen saver settings have no effect over reboot  (Read 1337 times)

Offline ds1062

  • Jr. Member
  • **
  • Posts: 22
Not sure if this goes under MiniMe or kde4 but my power management screen settings dont appear to survive reboot. All works fine as long as I leave the PC on but when I turn it off at night and back on the next day, the screen saver and power management need to be reset. The settings don't change, they just don't seem to have any effect. All I have to do is change something...anything in power management screen tab and screen saver then apply and all works fine until I shut down the PC again. Settings are:
Power management:
Enable power management: on
Standby after 9-10
Suspend after 19-20
Power off after 29-30 - this has never worked even in previous releases.

Screen saver is set to slideshow with directory set to my home dir/wallpaper changing every 5-6 min.

I found a related post about just turning the monitor off manually...which always works but prefer to find another solution as well. Any ideas?

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
I seem to have the same issue, though with two differences: firstly, I am on the full 2010 KDE4, and secondly, reboot or not, the settings just don't seem to have any effect.

I would like to know if anyone else is seeing this...

(I too found the thread about turning off monitor, which was for a minime release as well.)

Cheers!
CJ

Offline Chomp

  • Full Member
  • ***
  • Posts: 173
I'm starting to despise power management in KDE 4.  I don't want power management.  I've been using KDE 4 since 4.3 and still haven't found a way to prevent my screen shutting off when it wants.  I've tried bash scripts at startup, removing powerdevil, changing powerdevil options to do nothing, turning off powerdevil, removing it from startup...  nothing works.

I know this post doesn't help, but hopefully someone who understands the secret of power management in KDE 4 will enlighten us as to how to control it, rather than having (the) power devil control us.

Offline Hawkeye

  • Full Member
  • ***
  • Posts: 161
Well I'm in the same situation as you Chomp
Full 2010KDE and I've tried all sorts of changes trying to get it to just place my monitor into standby first (20mins) then turn it off (45mins)
Just can't seem to get it to work.
Would be nice if could get a 'mine works' response from someone - at least then we would have an idea weather its across the board problem with KDE 4x or just odd cases.
Shall keep diggin.

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
Fully updated 4.6.2 and I've got the same problem.

mikkl

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15310
  • ┌∩┐(◕_◕)┌∩┐
Quote
Would be nice if could get a 'mine works' response from someone - at least then we would have an idea weather its across the board problem with KDE 4x or just odd cases.

Works fine on this system and the HP laptop my wife use's.  The odd thing is (or mebbe  not actually) is these all work from default settings - just timings tweaked to suit.  Haven't added anything over and above the power management that comes with the main install (and updates of course)

Currently running KDE 4.6.2 with the kernel-2.6.38.4-pclos1.pae.bfs kernel.

Have you tried adding a new profile and setting that one to suit?
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline Hawkeye

  • Full Member
  • ***
  • Posts: 161
Well, that fixed mine for now  ;D
Had a serious udev crash whilst rebooting after last update and never got it back.
Decided to reinstall so here I am old home and fully updated, still need to install most apps etc and got to 'fight' KDE4 yet again. After been forced back to using my 2009 KDE3 with Compiz I am not sure any longer if this is where I wana be  :-\
Even installed E17 on an old box to mess with  ::)

Hope that you guy's find what's causing the problem ( just in case I become 'inflicted' again )  :D