https://bugs.kde.org/show_bug.cgi?id=405215
--- Comment #3 from Albert Astals Cid <aa...@kde.org> --- (In reply to Antonio Rojas from comment #2) > And how are packagers supposed to know that a feature is broken and should > not be enabled, if it is nowhere mentioned? It's not default, so if you enable things that are not default I would expect that you test them > With this option disabled, one gets a useless settings pane where one can > check and uncheck stuff with no visible way to apply changes - so either > way, it looks broken. Half agreed. > This should either be fixed, or the permissions settings tab completely > removed. It's still useful, it tells you that those things are wrong, sure doesn't help you in fixing them but highlights what needs changing. FWIW I have some local changes to fix it, but need polishing, so my suggestion is still you disable that, and once the permission code works, we'll just enable it by default, because as you say it doesn't make much sense not having it enabled. -- You are receiving this mail because: You are watching all bug changes.
