Summary: | kde service ("KDE-Dienst" in german) crashes on startup | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | wkarl <werner> |
Component: | kded | Assignee: | Alex Fiestas <afiestas> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | dvratil, rameijer, tps |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | kscreen-console bug |
Description
wkarl
2013-05-03 05:46:28 UTC
Nested event loops all over the place. - colord uses synchronous D-Bus calls, see backtrace #65...#68 - KAuth uses local event loop, see backtrace #30...#31 This is a release-upgrade from (appr.) lucid (10.04) -> maverick -> natty -> oneiric -> precise -> quantal to raring. Could this be a problem? It shouldn't be, though, if the distros did their job well. Same with KDE on Windows. kded4 crashes at startup with message "[045463f8] main services discovery error: no suitable services discovery module". In tune amarok crashes too. Two processes are running after this crash: klauncher and dbus-daemon. The message is only seen if you start kde via "startkde" from a shell. Else it is lost and, if you are lucky, the crash-reporter dialog is shown. If you start amarok directly, without starting kded4 first: amarok starts kded4, kded4 crashes amarok crashes. Two crash report dialogs are shown: the first one for amarok, the second one (some seconds later) for kded4. amarok does not report any additional messages, kded4 does: "[045463f8] main services discovery error: no suitable services discovery module". Removing all unneccessary parts from "PATH" did not help. Same crash. Reinstalling the whole thing didn't help either. As didn't help to install it to a fresh install. Versions: - Windows XP, SP#3, latest fixes and hotfixes applied - KDE-Installer 1.0.0 - Amarok 2.7.0 - KDE 4.10.2 This is not windows realted at all, please fill a new bug for that. Reporter, can you add the output of kscreen-console bug And the version of kscreen you are using? Thanks. Yes, you are right. It is not Windows related at all. Seeing the very same crash on - Ubuntu 13.10 - Fedora 18,19,rawhide - openSuSE factory and - Windows what is crashing: kded4. Created attachment 80285 [details]
kscreen-console bug
Pls find attached the output of 'kscreen-console bug' if this is what you wanted.
kscreen is 0.0.92-0ubuntu0.2
*** This bug has been marked as a duplicate of bug 318936 *** |