knetworkmanager crashed with SIGSEGV in Knm::Activatable::deviceUni()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
knetworkmanager |
Fix Released
|
High
|
|||
plasma-widget-networkmanagement (Ubuntu) |
Incomplete
|
Low
|
Unassigned |
Bug Description
Binary package hint: plasma-
Crash looks similar to bug #408508, but that is reported as "fix released" on August 18th, and I just did a complete safe-upgrade of my Karmic system. Also, it happened while doing a restart of network-manager.
Opening a new bug so I can look at my stack trace again to compare to the bug #408508 stack trace.
ProblemType: Crash
Architecture: i386
Date: Sat Oct 17 06:23:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
Package: plasma-
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xe3b80e <_ZNK3Knm11Acti
PC (0x00e3b80e) ok
source "(%edx)" (0x20796c70) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plasma-
StacktraceTop:
Knm::Activatab
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
SortedActivata
Title: knetworkmanager crashed with SIGSEGV in Knm::Activatabl
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-
Kai Blin (kai.blin) wrote : | #1 |
- Dependencies.txt Edit (8.1 KiB, text/plain; charset="utf-8")
- Disassembly.txt Edit (959 bytes, text/plain; charset="utf-8")
- ProcMaps.txt Edit (27.1 KiB, text/plain; charset="utf-8")
- ProcStatus.txt Edit (760 bytes, text/plain; charset="utf-8")
- Registers.txt Edit (537 bytes, text/plain; charset="utf-8")
- Stacktrace.txt Edit (5.7 KiB, text/plain; charset="utf-8")
- ThreadStacktrace.txt Edit (5.7 KiB, text/plain; charset="utf-8")
Kai Blin (kai.blin) wrote : | #2 |
Apport retracing service (apport) wrote : Stacktrace.txt (retraced) | #3 |
- Stacktrace.txt (retraced) Edit (15.8 KiB, text/plain)
StacktraceTop:
compareDevices (first=0x87b8808, second=0x8768b30)
activatableLessThan (first=0x87b8808, second=0x8768b30)
qSortHelper<
SortedActivatab
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced) | #4 |
Changed in plasma-widget-networkmanagement (Ubuntu): | |
importance: | Undecided → Medium |
tags: | removed: need-i386-retrace |
Kai Blin (kai.blin) wrote : | #5 |
Thanks to the retracer, it's obvious that the "this" pointer in Knm::Activatabl
Jonathan Thomas (echidnaman) wrote : | #6 |
deviceUni is the only function that is the same between the two stacktraces. These are two separate crashes.
Changed in plasma-widget-networkmanagement (Ubuntu): | |
importance: | Medium → Low |
status: | New → Confirmed |
Jonathan Thomas (echidnaman) wrote : | #7 |
Oh, I missed your comment where you determined the two stacktraces were different. Excuse me. :)
Changed in plasma-widget-networkmanagement (Ubuntu): | |
status: | Confirmed → Triaged |
visibility: | private → public |
In KDE Bug Tracking System #210878, Jonathan Thomas (echidnaman) wrote : | #9 |
Version: (using KDE 4.3.2)
OS: Linux
Installed from: Ubuntu Packages
Using KNetworkManager 0.9 svn 1029786, originally reported at https:/
The user reported a KNetworkManager crash that occurred when NetworkManager restarted during an upgrade. The crash had the following backtrace:
.
Thread 1 (process 3868):
#0 Knm::Activatabl
at /usr/include/
No locals.
#1 0x0037e0e1 in compareDevices (first=0x87b8808, second=0x8768b30)
at /build/
firstIface = (class Solid::
secondIface = <value optimized out>
#2 0x0037e23c in activatableLessThan (first=0x87b8808, second=0x8768b30)
at /build/
i = <value optimized out>
#3 0x0037e502 in qSortHelper<
start=<value optimized out>, end=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
)
at /usr/include/
span = 12
#4 0x0037e6b7 in SortedActivatab
activatable
d = (SortedActivata
#5 0x0036cd23 in ActivatableList
activatable
at /build/
observer = (class ActivatableObserver *) 0xbf945fec
_container_ = {c = {{p = {static shared_null = {ref = {
array = {0x0}}, d = 0x87bb938}, d = 0x87bb938}}, brk = 0, i = {
i = 0x87bb970}, e = {i = 0x87bb974}}
d = <value optimized out>
#6 0x0036cdbc in ActivatableList
activatable
at /build/
No locals.
#7 0x00370db5 in WirelessNetwork
this=0x87e3fd0, addedConnection
at /build/
ifaceConnection = (class Knm::WirelessIn
network = (class Solid::
knmNetwork = (class Knm::WirelessNe
ourWicFound = false
ourHiddenWicFound = false
wirelessSetting = (class Knm::WirelessSe
__PRETTY_
#8 0x003710f9 in WirelessNetwork
(this=
at /build/
connection = (class Knm::Connecti...
In KDE Bug Tracking System #210878, Blin-q (blin-q) wrote : | #10 |
Actually I was manually restarting network manager as it had failed to pick up my IPv6 router advertisement and thus didn't assign a global IPv6 address. So the crash actually happened during "normal operation" rather than during an upgrade.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #11 |
*** Bug 212443 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #12 |
*** Bug 212441 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, X-wstephenson (x-wstephenson) wrote : | #13 |
I can't reproduce this on openSUSE; looks like I'm installing ubuntu this weekend then.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #14 |
*** Bug 213237 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Jonathan Thomas (echidnaman) wrote : | #15 |
*** Bug 213522 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Jonathan Thomas (echidnaman) wrote : | #16 |
*** Bug 213775 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #17 |
*** Bug 209092 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #18 |
*** Bug 214428 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, X-wstephenson (x-wstephenson) wrote : | #19 |
*** Bug 211586 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #20 |
*** Bug 215781 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #21 |
*** Bug 217089 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, ochach (ochach) wrote : | #22 |
Created attachment 39160
knetworkmanager
In KDE Bug Tracking System #210878, ochach (ochach) wrote : | #23 |
Comment on attachment 39160
knetworkmanager
restarting network-manager cause knetworkmanager crash every single time.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #24 |
*** Bug 219396 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #25 |
*** Bug 219689 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, X-wstephenson (x-wstephenson) wrote : | #26 |
See also bko#215918
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #27 |
From bug 222257:
---
Some more information: The crash happened on my laptop using wifi and a wpa
secured network. If I disable wireless connections or use a wired connection
instead, then knetworkmanager does not crash. As soon as I enable wireless and
restart network-manager the crash appears.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #28 |
*** Bug 222257 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #29 |
*** Bug 222322 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #30 |
Bug 224297 got some networkmanager-
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #31 |
*** Bug 224297 has been marked as a duplicate of this bug. ***
Changed in knetworkmanager: | |
status: | Unknown → In Progress |
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #32 |
*** Bug 224750 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #33 |
*** Bug 226015 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #34 |
*** Bug 226007 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #35 |
*** Bug 227090 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #36 |
*** Bug 231278 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #37 |
*** Bug 232104 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #38 |
*** Bug 231861 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Neoclust-kde (neoclust-kde) wrote : | #39 |
*** Bug 235675 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #40 |
*** Bug 242283 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #41 |
*** Bug 241678 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #42 |
*** Bug 235015 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Jc-castellani (jc-castellani) wrote : | #43 |
Created attachment 49295
New crash information added by DrKonqi
crash after "service NetworkManager restart" on fedora 13
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #44 |
*** Bug 246871 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #45 |
*** Bug 243887 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #46 |
*** Bug 245839 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #47 |
*** Bug 246176 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #48 |
*** Bug 244291 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Jonathan Thomas (echidnaman) wrote : | #49 |
*** Bug 248408 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Pino Toscano (pinotree) wrote : | #50 |
*** Bug 248662 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Rolf Eike Beer (kde-opensource) wrote : | #51 |
I just got the same one: Wifi, openSUSE 11.3, KDE 4.5.0.
In KDE Bug Tracking System #210878, Fave Arju (fave-arju) wrote : | #52 |
Created attachment 51448
New crash information added by DrKonqi
After I switch between ifup and KNetworkmanager 2 or 3 times with yast, the Manager crashes instantly.
In KDE Bug Tracking System #210878, Tuxgeok (tuxgeok) wrote : | #53 |
Created attachment 52472
New crash information added by DrKonqi
knetworkmanager (v0.9) on KDE Platform 4.5.2 (KDE 4.5.2) using Qt 4.7.0
The kNetworkManager crashes always on restart from hibernate on OpenSuse 11.2.
-- Backtrace (Reduced):
#7 ref (this=<value optimized out>) at /usr/include/
#8 QString (this=<value optimized out>) at /usr/include/
#9 Knm::Activatabl
#10 0xb6ec5374 in compareDevices (first=0x81c1ba8, second=0x8191640) at /usr/src/
#11 0xb6ec54c2 in activatableLessThan (first=0x81c1ba8, second=0x8191640) at /usr/src/
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #54 |
*** Bug 254993 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #55 |
*** Bug 254337 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #56 |
*** Bug 254112 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #57 |
*** Bug 253885 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #58 |
*** Bug 253726 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #59 |
*** Bug 252995 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #60 |
*** Bug 252712 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #61 |
*** Bug 256244 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #62 |
*** Bug 256165 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #63 |
*** Bug 256026 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #64 |
*** Bug 255945 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #65 |
*** Bug 255456 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #66 |
*** Bug 255159 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #67 |
*** Bug 254828 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #68 |
*** Bug 254344 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #69 |
*** Bug 253993 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #70 |
*** Bug 253521 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #71 |
*** Bug 253196 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #72 |
*** Bug 252410 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #73 |
*** Bug 250798 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #74 |
*** Bug 255368 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #75 |
*** Bug 257472 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #76 |
*** Bug 258539 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #77 |
*** Bug 258762 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Gjjohnson (gjjohnson) wrote : | #78 |
Created attachment 54192
New crash information added by DrKonqi
Network Manager consistantly crashes when the network is restarted. On initial bootup, network manager will not work. After it has crashed and been restarted, the wifi and ethernet devices are visible and can be managed through the network manager application.
In KDE Bug Tracking System #210878, Gjjohnson (gjjohnson) wrote : | #79 |
(In reply to comment #69)
> Created an attachment (id=54192) [details]
> New crash information added by DrKonqi
>
> Network Manager consistantly crashes when the network is restarted. On initial
> bootup, network manager will not work. After it has crashed and been
> restarted, the wifi and ethernet devices are visible and can be managed through
> the network manager application.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #80 |
*** Bug 258907 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #81 |
*** Bug 258956 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #82 |
*** Bug 259221 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #83 |
*** Bug 260324 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #84 |
*** Bug 260637 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #85 |
*** Bug 263968 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #86 |
*** Bug 261893 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #87 |
This problem is caused by dangling pointers left in ActivableLists before NM starts again. Last November I commited a patch to workaround this problem by emptying the ActivatableList when NetworkManager goes down. It fixed the problem in my tests. Please upgrade to a recent networkmanagement (Plasma NM) revision.
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #88 |
*** Bug 264185 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Dario Andres (andresbajotierra) wrote : | #89 |
*** Bug 264881 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #90 |
*** Bug 258168 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #91 |
*** Bug 263047 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #92 |
*** Bug 256631 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #93 |
*** Bug 265797 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #94 |
Git commit 47519cb76d62851
Committed on 10/02/2011 at 08:34.
Pushed by lvsouza into branch 'master'.
Another try to solve the dangling pointers problem.
CCBUG: 210878
M +0 -21 libs/service/
M +0 -2 libs/service/
M +1 -0 solidcontrolfut
http://
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #95 |
Git commit a8d87d386293681
Committed on 10/02/2011 at 20:39.
Pushed by lvsouza into branch 'master'.
Prevents a crazy flux of several networkDisappeared signals for the same ssid
when several Solid::
objects are deleted during wifi or NetworkManager turning off. The end
result is the same as using wirelessEnabled
is no signal being emitted.
CCBUG: 210878
M +24 -0 libs/service/
M +0 -1 solidcontrolfut
http://
In KDE Bug Tracking System #210878, Frank78ac (frank78ac) wrote : | #96 |
*** Bug 249226 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Frank78ac (frank78ac) wrote : | #97 |
*** Bug 249270 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Frank78ac (frank78ac) wrote : | #98 |
*** Bug 263487 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Frank78ac (frank78ac) wrote : | #99 |
*** Bug 258469 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #100 |
*** Bug 266079 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #101 |
Please try the latest Plasma NM snapshot and report if this bug still happens. I would like to close this bug if it does not happen anymore.
Changed in knetworkmanager: | |
importance: | Unknown → High |
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #102 |
*** Bug 267500 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, grawcho (grawcho) wrote : | #103 |
Created attachment 57837
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.
-- Backtrace (Reduced):
#7 ref (this=0x9b18aa8) at /usr/include/
#8 QString (this=0x9b18aa8) at /usr/include/
#9 Knm::Activatabl
#10 0x02829300 in compareDevices (first=0x9b1ec10, second=0x9b18aa8) at ../../.
#11 0x0282940c in activatableLessThan (first=0x9b1ec10, second=0x9b18aa8) at ../../.
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #104 |
(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/
> #8 QString (this=0x9b18aa8) at /usr/include/
> #9 Knm::Activatabl
> ../../.
> #10 0x02829300 in compareDevices (first=0x9b1ec10, second=0x9b18aa8) at
> ../../.
> #11 0x0282940c in activatableLessThan (first=0x9b1ec10, second=0x9b18aa8) at
> ../../.
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #105 |
*** Bug 256900 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #106 |
*** Bug 268795 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #107 |
*** Bug 215918 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #108 |
*** Bug 256552 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #109 |
*** Bug 270705 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #110 |
*** Bug 263827 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Matthew Flaschen (matthew-flaschen) wrote : | #111 |
Created attachment 58897
New crash information added by DrKonqi
kded4 ($Id: kded.cpp 1156841 2010-07-29 19:59:05Z zander $) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0
KNetworkManager widget crashed with a segfault when I restarted network-manager. I was not upgrading.
-- Backtrace (Reduced):
#6 ref (this=0x124a850) at /usr/include/
#7 QString (this=0x124a850) at /usr/include/
#8 Knm::Activatabl
#9 0x00007f709d3f6ddd in compareDevices (first=0x124a850, second=0xddfcc0) at ../../.
#10 0x00007f709d3f6f03 in activatableLessThan (first=
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #112 |
*** Bug 271666 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #113 |
*** Bug 249299 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #114 |
*** Bug 273684 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #115 |
Can someone reproduce this problem with a recent Plasma NM snapshot? Please keep in mind still today some distributions ship a very old version of Plasma NM from last year. When testing please use a recent version, in the past three months we fixed tens of bugs in Plasma NM, so you must test with a recent version.
In KDE Bug Tracking System #210878, Brunofr (brunofr) wrote : | #116 |
Not my case with a PNM 0.9.2.60git.
kde 4.6.3 openSUSE_Factory
In KDE Bug Tracking System #210878, Alexandr Kara (alexandr-kara) wrote : | #117 |
I think the issue is long gone, I haven't noticed it for maybe 6 months or a year. I have just verified in KDE 4.6.3 and found no problems.
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #118 |
Ok, closing this bug then.
Changed in knetworkmanager: | |
status: | In Progress → Fix Released |
In KDE Bug Tracking System #210878, Christoph-maxiom (christoph-maxiom) wrote : | #119 |
*** Bug 281685 has been marked as a duplicate of this bug. ***
Maarten Bezemer (veger) wrote : | #8 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 453697 and any other logs that are relevant for this particular issue.
Changed in plasma-widget-networkmanagement (Ubuntu): | |
status: | Triaged → Incomplete |
In KDE Bug Tracking System #210878, Lamarque (lamarque) wrote : | #120 |
*** Bug 325694 has been marked as a duplicate of this bug. ***
Hm, the stack trace looks very similar to bug 408508. Are we sure that bug is fixed?