https://bugs.kde.org/show_bug.cgi?id=304696
--- Comment #24 from Konstantin Kharlamov <hi-an...@yandex.ru> --- (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 > systems to compensate for the 50% time behaviour. There isn't, but if you think it is a real problem I think it might be possible to revert the change from stable and just leave it be a breaking change for the next big 6.0 release… -- You are receiving this mail because: You are the assignee for the bug.
