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 rec
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
> system
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 r
