| Summary: | kded crashes on login | ||
|---|---|---|---|
| Product: | Network Management | Reporter: | Robin Green <greenrd> |
| Component: | KDED Module | Assignee: | Lamarque V. Souza <lamarque> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | chrismaple, gam.wild, imacoolkid, JaapEnIngrid.Douma, jan.olsfors, justlikeef, klaus, linux1357, mr.texnik666, null, Peter-Uwe.Fritz, pistachiosmakemyday, rfox, thomasbelvin |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | backtrace | ||
Why do all those DBus issues come out all of suden after years doing the same thing? The bad news is: to fix this bug I will have to re-work the NetworkManager backend, which will take some time. To workaround it I can add some waitForFinished calls, which will probably cause constant freezes in the plasma desktop (the entire desktop), which is very annoying :-( Sorry, I realised that this may be my fault. This is in an LXC container, and I could not get systemd to start in the container, so none of the following were running: * systemd * system dbus * NetworkManager I started the latter two manually, and retried, and this crash did not happen. Good that you have solved the problem. I will close this bug. *** Bug 293876 has been marked as a duplicate of this bug. *** *** Bug 294587 has been marked as a duplicate of this bug. *** *** Bug 300218 has been marked as a duplicate of this bug. *** *** Bug 300814 has been marked as a duplicate of this bug. *** *** Bug 301513 has been marked as a duplicate of this bug. *** *** Bug 303641 has been marked as a duplicate of this bug. *** *** Bug 304731 has been marked as a duplicate of this bug. *** *** Bug 304787 has been marked as a duplicate of this bug. *** *** Bug 307453 has been marked as a duplicate of this bug. *** For all of you: both system dbus and NetworkManager must be already started before you login into the KDE session. It seems systemd postpone the NetworkManager startup to until any program tries to contact it (in this case Plasma NM). That does not seem to work well and causes a race condition that causes this crash. So make sure system dbus and NetworkManager are started during boot time. Dbus is probably already started during boot time, for NetworkManager you can do: systemctl enable NetworkManager.service I have never been able to reproduce this bug so the command above may not solve the problem for you just yet. *** Bug 310148 has been marked as a duplicate of this bug. *** *** Bug 311977 has been marked as a duplicate of this bug. *** *** Bug 314438 has been marked as a duplicate of this bug. *** *** Bug 328510 has been marked as a duplicate of this bug. *** *** Bug 327899 has been marked as a duplicate of this bug. *** |
Created attachment 68352 [details] backtrace Version: 4.8 (using KDE 4.8.0) OS: Linux Stack trace attached. Reproducible: Always Steps to Reproduce: 1. Log in Actual Results: drkonqi pops up and tells me kded4 crashed Expected Results: No crash