Comment 104 for bug 453697

(In reply to comment #94)
> Created an attachment (id=57837) [details]
> New crash information added by DrKonqi
>
> kded4 ($Id$) on KDE Platform 4.6.1 (4.6.1) using Qt 4.7.0
>
> - What I was doing when the application crashed: kdm frozeup ... i restarted
> kdm and network manager did not restart. i restarted kdm manually ... and it
> still did not restart. i dialed via vwdial to report the bug.

This is odd. If you restarted kdm all kde session should have been restarted as well, including kded. It is very unlikely this bug happens on an fresh starting kded. NetworkManager is not supposed to restart because any of its clients (Plasma NM, nm-appplet, whatever) have restarted. Are you sure what you restarted was kdm? You said kdm frozen, I have never seem kdm freezing. What were you doing before the freezing?

> -- Backtrace (Reduced):
> #7 ref (this=0x9b18aa8) at /usr/include/qt4/QtCore/qatomic_i386.h:120
> #8 QString (this=0x9b18aa8) at /usr/include/qt4/QtCore/qstring.h:728
> #9 Knm::Activatable::deviceUni (this=0x9b18aa8) at
> ../../../libs/internals/activatable.cpp:51
> #10 0x02829300 in compareDevices (first=0x9b1ec10, second=0x9b18aa8) at
> ../../../libs/service/sortedactivatablelist.cpp:263
> #11 0x0282940c in activatableLessThan (first=0x9b1ec10, second=0x9b18aa8) at
> ../../../libs/service/sortedactivatablelist.cpp:172