kdelibs-4.9.98-1.fc18.x86_64
I have set in screen locker:
start auto after 10 min require pw after 60 sec
And in battery monitor settings
screen energy saver: switch off after 10 min
Same as I've always had.
But this morning, I see that pw prompt is still sitting on screen, it had not switched off. Can you spell "burn in"?
Neal Becker wrote:
kdelibs-4.9.98-1.fc18.x86_64
I have set in screen locker:
start auto after 10 min require pw after 60 sec
And in battery monitor settings
screen energy saver: switch off after 10 min
Same as I've always had.
But this morning, I see that pw prompt is still sitting on screen, it had not switched off. Can you spell "burn in"?
Mind filing a bug @ bugs.kde.org?
-- rex
Rex Dieter wrote:
Neal Becker wrote:
kdelibs-4.9.98-1.fc18.x86_64
I have set in screen locker:
start auto after 10 min require pw after 60 sec
And in battery monitor settings
screen energy saver: switch off after 10 min
Same as I've always had.
But this morning, I see that pw prompt is still sitting on screen, it had not switched off. Can you spell "burn in"?
Mind filing a bug @ bugs.kde.org?
It's battery mon. I can disable screen locker, but battery mon is not blanking the screen.
But what component would I file the bug on?
Neal Becker wrote:
Rex Dieter wrote:
Neal Becker wrote:
kdelibs-4.9.98-1.fc18.x86_64
I have set in screen locker:
start auto after 10 min require pw after 60 sec
And in battery monitor settings
screen energy saver: switch off after 10 min
Same as I've always had.
But this morning, I see that pw prompt is still sitting on screen, it had not switched off. Can you spell "burn in"?
Mind filing a bug @ bugs.kde.org?
https://bugs.kde.org/show_bug.cgi?id=314250
BTW, I find that the issue is an interaction with google-chrome (as I say in the BR).