https://bugs.kde.org/show_bug.cgi?id=379254
--- Comment #17 from Lubos Lunak <l.lu...@kde.org> --- So I've intentionally broken one of my local autostart .desktop files and that does cause the problem, and it's indeed somewhat annoying that the whole startup is blocked by it. And, looking at KRun, this is caused by a dialog blocking the whole ksmserver in the autostart code. So I see basically 3 viable possibilities: - Leave master as it is. And I don't think this is such a bad choice, there are not supposed to be broken .desktop files after all. - Add some kind of "QString* error" argument to the KRun call, which would prevent KRun from showing the dialog itself and let ksmserver show it in a non-blocking way. - Make ksmserver have klauncher do the actual launching, like it was before (i.e. a DBus call to "start_service" or somesuch). But I don't know what was the exact idea with moving the autostart code to ksmserver. I intentionally didn't list "revert my commits in master". The code in KRun (or klauncher) does way more than just get the executable path from the .desktop file and launch it. I don't find it a good idea to either copy&paste a lof of code to ksmserver, or to trade a blatantly obvious problem (that's not even our problem) for a possible bunch of non-obvious problems. -- You are receiving this mail because: You are watching all bug changes.
