Screen no longer powers down.

Two or three days ago, I found my screen hadn’t powered down after the
set time. I eventually fixed it by altering the Screen Energy Saving
setting and re-booting a couple of times. Then yesterday evening, after
another re-boot, the problem reappeared and I’ve been unable to cure it.

Temperamental behaviour of the power settings has been a problem for
many years but this is the first time that I’ve been unable to fix it by
altering the setting and rebooting. Any suggestions as to what else I
can try?


Graham Davis, Bracknell, Berks., UK.
openSUSE 42.2; KDE Plasma 5.8.3; Qt 5.6.1; Kernel 4.4.36;
AMD Athlon X4 860K Processor; Sound: FCH Azalia;
Video: nVidia GeForce 210 (Driver: nouveau)

For what it is worth my screen blanks but does not lock if I have VirtualBox running but does with other programs.

On 15/01/17 13:26, gogalthorp wrote:
>
> For what it is worth my screen blanks but does not lock if I have
> VirtualBox running but does with other programs.
>

Thanks for the thought but I don’t use VirtualBox. Nothing has changed
regarding what applications I’m running. I’ll just try tweaking a few
things in the hope that I strike lucky; just altered screen locker as
well as power setting and will now wait and see.


Graham Davis, Bracknell, Berks., UK.
openSUSE 42.2; KDE Plasma 5.8.3; Qt 5.6.1; Kernel 4.4.36;
AMD Athlon X4 860K Processor; Sound: FCH Azalia;
Video: nVidia GeForce 210 (Driver: nouveau)

On 15/01/17 14:30, Graham P Davis wrote:
> On 15/01/17 13:26, gogalthorp wrote:
>>
>> For what it is worth my screen blanks but does not lock if I have
>> VirtualBox running but does with other programs.
>>
>
> Thanks for the thought but I don’t use VirtualBox. Nothing has changed
> regarding what applications I’m running. I’ll just try tweaking a few
> things in the hope that I strike lucky; just altered screen locker as
> well as power setting and will now wait and see.
>

And now screen-locker doesn’t work either! Sigh!

Tried another user on this machine and that had no trouble. Realised
that user was still using FF as a web browser whereas I’d switched to
Chromium for this one a few weeks ago. Tried logging on as myself
without launching Chromium and power-saving worked OK. Then launched
Chromium and the problem returned. Could it be Chromium to blame, in
which case why didn’t the problem appear immediately I started using the
application a few weeks ago?

As the nouveau driver had given a variety of problems in the past I
thought I’d give the nVidia driver a go but all that achieved was what
looked like a disaster for Chromium, though a restart of that
application sorted it out.

Still a few more things I can try so not giving up yet.


Graham Davis, Bracknell, Berks., UK.
openSUSE 42.2; KDE Plasma 5.8.3; Qt 5.6.1; Kernel 4.4.36;
AMD Athlon X4 860K Processor; Sound: FCH Azalia;
Video: nVidia GeForce 210 (Driver: nVidia)

On 16/01/17 09:01, Graham P Davis wrote:
> On 15/01/17 14:30, Graham P Davis wrote:
>> On 15/01/17 13:26, gogalthorp wrote:
>>>
>>> For what it is worth my screen blanks but does not lock if I have
>>> VirtualBox running but does with other programs.
>>>
>>
>> Thanks for the thought but I don’t use VirtualBox. Nothing has changed
>> regarding what applications I’m running. I’ll just try tweaking a few
>> things in the hope that I strike lucky; just altered screen locker as
>> well as power setting and will now wait and see.
>>
>
> And now screen-locker doesn’t work either! Sigh!
>
> Tried another user on this machine and that had no trouble. Realised
> that user was still using FF as a web browser whereas I’d switched to
> Chromium for this one a few weeks ago. Tried logging on as myself
> without launching Chromium and power-saving worked OK. Then launched
> Chromium and the problem returned. Could it be Chromium to blame, in
> which case why didn’t the problem appear immediately I started using the
> application a few weeks ago?
>
> As the nouveau driver had given a variety of problems in the past I
> thought I’d give the nVidia driver a go but all that achieved was what
> looked like a disaster for Chromium, though a restart of that
> application sorted it out.
>
> Still a few more things I can try so not giving up yet.
>

Those ‘few things’ involved trying an earlier version of 42.2 then 13.2
on this machine but results the same. Then I replaced Chromium with
Opera, using the same mass of windows and tabs, and the problem went
away. Now I just don’t see how something in, or related to, Chromium
could have caused this problem. Any ideas?


Graham Davis, Bracknell, Berks., UK.
openSUSE 42.2; KDE Plasma 5.8.3; Qt 5.6.1; Kernel 4.4.36;
AMD Athlon X4 860K Processor; Sound: FCH Azalia;
Video: nVidia GeForce 210 (Driver: nVidea)

Well my point was not specific about VirtualBox but that some programs may prevent the powerdown. Like running a movie in the past prevented start of screen saver.

On 16/01/17 16:56, gogalthorp wrote:
>
> Well my point was not specific about VirtualBox but that some programs
> may prevent the powerdown. Like running a movie in the past prevented
> start of screen saver.
>

OK, sorry for misunderstanding.

Latest is that Opera causes no trouble but then Opera keeps coming up
with ‘The media could not be played.’ Dunno about FF but that’s a
nightmare anyway - one of those where you’re running through treacle.

This all started a few days ago after I’d said how much better Linux was
than Windoze. Murphy’s Law wins out again.


Graham Davis, Bracknell, Berks., UK.
openSUSE 42.2; KDE Plasma 5.8.3; Qt 5.6.1; Kernel 4.4.36;
AMD Athlon X4 860K Processor; Sound: FCH Azalia;
Video: nVidia GeForce 210 (Driver: nVidia)

Actually, I subscribe to O’Malley’s Law: “Murphy was an optimist!”
:slight_smile: