https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #26 from Nate Graham ---
There's no real way for us to know whether a person set the time they did
because that's the way they wanted it and they never noticed the bug, or
because they did notice the bug and were manually working around it.
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #25 from Paul Gideon Dann ---
Nah; this isn't enough of a problem for me for it to be worth delaying the fix.
But thanks for confirming that there's no config migration. I'll just keep an
eye on the behaviour when upgrading.
--
You are
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #24 from Konstantin Kharlamov ---
(In reply to Paul Gideon Dann from comment #23)
> Is there some migration so that the currently-configured timeout doesn't
> suddenly double at the next upgrade? Some of us have since configured our
>
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #23 from Paul Gideon Dann ---
Is there some migration so that the currently-configured timeout doesn't
suddenly double at the next upgrade? Some of us have since configured our
systems to compensate for the 50% time behaviour.
--
You are
https://bugs.kde.org/show_bug.cgi?id=304696
Konstantin Kharlamov changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=304696
Nate Graham changed:
What|Removed |Added
Version Fixed In|5.27.8 |6.0
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=304696
Nate Graham changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=304696
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
CC|
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #20 from Nate Graham ---
*** Bug 473562 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=304696
Bug Janitor Service changed:
What|Removed |Added
Priority|NOR |HI
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=304696
Konstantin Kharlamov changed:
What|Removed |Added
CC||hi-an...@yandex.ru
--- Comment #19 from
https://bugs.kde.org/show_bug.cgi?id=304696
Tim Siegel changed:
What|Removed |Added
Version|5.2.0 |5.24.4
CC|
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #17 from Paul Gideon Dann ---
If the behaviour is not changed, it would be nice to have the actual behaviour
explained in the config panel. The current experience certainly isn't as
intuitive as it could be.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=304696
Kai Uwe Broulik changed:
What|Removed |Added
CC||certainlya...@gmail.com
--- Comment #16 from
https://bugs.kde.org/show_bug.cgi?id=304696
Christoph Feck changed:
What|Removed |Added
CC||yst...@posteo.net
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=304696
Chris Holland changed:
What|Removed |Added
CC||zrenf...@gmail.com
--- Comment #14 from Chris
https://bugs.kde.org/show_bug.cgi?id=304696
S changed:
What|Removed |Added
CC||sb56...@gmail.com
--- Comment #13 from S ---
Created
https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #12 from da-kdebugs...@abelonline.de ---
This is still open. Setting "Dim screen" to "3 min" makes the display dim after
90s (instead of 180s). Unchecking "Dim screen" disables dimming, so it is
likely due to this setting.
System settings
https://bugs.kde.org/show_bug.cgi?id=304696
da-kdebugs...@abelonline.de changed:
What|Removed |Added
CC||da-kdebugs...@abelonline.de
---
https://bugs.kde.org/show_bug.cgi?id=304696
Kai Uwe Broulik k...@privat.broulik.de changed:
What|Removed |Added
Component|powermanagement |general
20 matches
Mail list logo
