Bug 292910 - kded crashes on login
Summary: kded crashes on login
Status: RESOLVED NOT A BUG
Alias: None
Product: Network Management
Classification: Unmaintained
Component: KDED Module (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Lamarque V. Souza
URL:
Keywords:
: 293876 294587 300218 300814 301513 303641 304731 304787 307453 310148 311977 314438 327899 328510 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-01-30 22:09 UTC by Robin Green
Modified: 2013-12-15 14:27 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
backtrace (8.38 KB, text/plain)
2012-01-30 22:09 UTC, Robin Green 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Robin Green 2012-01-30 22:09:33 UTC 
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
Comment 1 Lamarque V. Souza 2012-01-31 10:50:59 UTC 
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 :-(
Comment 2 Robin Green 2012-01-31 18:59:24 UTC 
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.
Comment 3 Lamarque V. Souza 2012-02-12 01:14:35 UTC 
Good that you have solved the problem. I will close this bug.
Comment 4 Lamarque V. Souza 2012-02-12 13:24:36 UTC 
*** Bug 293876 has been marked as a duplicate of this bug. ***
Comment 5 Lamarque V. Souza 2012-02-22 11:34:05 UTC 
*** Bug 294587 has been marked as a duplicate of this bug. ***
Comment 6 Lamarque V. Souza 2012-05-18 01:32:04 UTC 
*** Bug 300218 has been marked as a duplicate of this bug. ***
Comment 7 Lamarque V. Souza 2012-05-29 20:09:28 UTC 
*** Bug 300814 has been marked as a duplicate of this bug. ***
Comment 8 Lamarque V. Souza 2012-06-10 17:41:08 UTC 
*** Bug 301513 has been marked as a duplicate of this bug. ***
Comment 9 Lamarque V. Souza 2012-07-17 12:34:57 UTC 
*** Bug 303641 has been marked as a duplicate of this bug. ***
Comment 10 Lamarque V. Souza 2012-08-07 16:19:38 UTC 
*** Bug 304731 has been marked as a duplicate of this bug. ***
Comment 11 Lamarque V. Souza 2012-08-10 01:04:46 UTC 
*** Bug 304787 has been marked as a duplicate of this bug. ***
Comment 12 Lamarque V. Souza 2012-09-26 23:35:49 UTC 
*** Bug 307453 has been marked as a duplicate of this bug. ***
Comment 13 Lamarque V. Souza 2012-09-28 16:25:42 UTC 
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.
Comment 14 Lamarque V. Souza 2012-11-15 15:07:27 UTC 
*** Bug 310148 has been marked as a duplicate of this bug. ***
Comment 15 Lamarque V. Souza 2012-12-20 17:38:19 UTC 
*** Bug 311977 has been marked as a duplicate of this bug. ***
Comment 16 Lamarque V. Souza 2013-02-05 02:50:01 UTC 
*** Bug 314438 has been marked as a duplicate of this bug. ***
Comment 17 Lamarque V. Souza 2013-12-15 14:24:27 UTC 
*** Bug 328510 has been marked as a duplicate of this bug. ***
Comment 18 Lamarque V. Souza 2013-12-15 14:27:26 UTC 
*** Bug 327899 has been marked as a duplicate of this bug. ***