https://bugs.kde.org/show_bug.cgi?id=409075
--- Comment #6 from Dan Thompson <dan_j_thomp...@hotmail.com> --- (Seems dubious to resolve as "fixed", since I repro'ed the problem.) emohr: Sorry; I don't have the exact text of the error available any longer--after I deleted all the config, the error went away. Intercepting the error and offering to reset config for you would be a good step... it would prevent people from getting completely blocked. But of course the ideal solution would be to properly upgrade config so that you don't end up with the situation in the first place. But even if we implemented the ideal solution... there is always a possibility of a mistake there (a mistake during config upgrade). So it may still be good to have the "do you want to try resetting configuration to see if it helps?" safety net as well. -- You are receiving this mail because: You are watching all bug changes.
