Summary: | KNetworkManager crashed after attempting to connect to a network twice (WirelessSecuritySettingWidget::writeConfig, ConnectionSecretsJob::dialogAccepted) | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | Jonathan Thomas <echidnaman> |
Component: | general | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 0xwille, 2_post_2, abreusecuritas, agilulfo53, alexander.hardman, andresbajotierra, andyprough, baditoiuvalentin, contact, dani.nh, dl.zerocool, ea.grassete, EagleScreen, edwinvanitou, g63marty, ggendron, henrygr, johann-nikolaus, jose.urband, kde-bugreport, kde, kenlewis, klaus.moelln, krishnakumar85.p, Larry.Finger, maninred, mavidal, mgr1, morgenstern.daniel, morris.cavestro, roldean, schmecklecker137, zegratman |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jonathan Thomas
2009-10-16 15:06:35 UTC
*** Bug 209280 has been marked as a duplicate of this bug. *** *** Bug 211219 has been marked as a duplicate of this bug. *** *** Bug 212612 has been marked as a duplicate of this bug. *** From bug 212861: What I was doing when the application crashed: I was configuring my wifi wpa pass when knetworkmanager crashed, I had tried 3 to 4 times after this happen. The wifi network is the one at home No other app was running that I remember. *** Bug 212861 has been marked as a duplicate of this bug. *** *** Bug 212845 has been marked as a duplicate of this bug. *** From bug 213396: -- What I was doing when the application crashed: Was trying to connect to a WPA2 Entreprise, EAP/TLS with cl.pem, ca.pem and key.prv. (choosed TLS security) After the first try, the window askin again the certificates appeared and System ca certificate was check and my own ca.pem wasn't present. So I unchecked system certificate, added again the ca.pem and tried to reconnect, then it crashed. (ca.pem, cl.pem and .prv perfectly working on wicd client) (connection sucessful) *** Bug 213396 has been marked as a duplicate of this bug. *** *** Bug 213511 has been marked as a duplicate of this bug. *** *** Bug 214203 has been marked as a duplicate of this bug. *** *** Bug 214220 has been marked as a duplicate of this bug. *** From bug 214878: --- What I was doing when the application crashed: I open Network managemet tool and change wlan connection parameters when system use wlan0. I push "Ok" and Network management tool show bug report. *** Bug 214878 has been marked as a duplicate of this bug. *** *** Bug 211494 has been marked as a duplicate of this bug. *** This bug can be reproduced with different kinds of network nics like PRISM2-USB, Intel 2200bg. If no crash happens the entered wireless key is not stored either using kwallet or without kwallet. *** Bug 215196 has been marked as a duplicate of this bug. *** From bug 215196: --- I tried to get a connection to my home wlan because i had changed some options just before and for that changed the interface (eth1, wlan0) and other options that should have made the connection work, i thought. Then the KNetworkManager crashed, but after the reload of the manager it worked and i had a connection. *** Bug 215300 has been marked as a duplicate of this bug. *** From bug 215722: --- What I was doing when the application crashed: The KNetworkManager has made a connection to my home WLAN, but there was still no traffic to my Aplications(firefox, software installation). I checked the passphrase for the WPA1 Network, allowed KNetwork to get everytime acces to KWallet, saved the settings an used the OK button. After that I recognised that there was still the password configuration window open (may be a second???). I used the OK Button, may be. Than KNetworkManager crashed. *** Bug 215722 has been marked as a duplicate of this bug. *** From bug 216403: --- wireless connection is not authenticated, continues to require the passphrase wireless connection to an access point without WPA security is done regular *** Bug 216403 has been marked as a duplicate of this bug. *** *** Bug 217395 has been marked as a duplicate of this bug. *** *** Bug 216893 has been marked as a duplicate of this bug. *** I've managed to create a workaround. Start using knetworkmanager -- this will not work. Then edit kwallet settings made by knetworkmanager and save them. After that wifi works with all settings as usual. I think that knetworkmanager ist not able to store values in kwallet. Jochen *** Bug 218009 has been marked as a duplicate of this bug. *** *** Bug 218208 has been marked as a duplicate of this bug. *** *** Bug 218959 has been marked as a duplicate of this bug. *** *** Bug 219517 has been marked as a duplicate of this bug. *** I'm trying to reproduce this with a Karmic installation since I cannot reproduce this on openSUSE, but I can't make it crash, nor does valgrind report any problems. What am I missing? Is everyone using KWallet here? Do you have a password set on the wallet? Do you have 'always allow' set on KNM on KWallet? Ok, nailed it down with trunk. To reproduce: 1) Start a connection attempt (or let connect automatically connection activate) 2) Connection fails, for whatever reason, and the connection secrets dialog is shown 3) Edit the connection in the KCM, not in the shown connection secrets dialog 4) Ok the connection secrets dialog 5) Crash. Classic case of interleaved actions exposing unsafe assumptions about when stuff gets deleted. Fixed by commit 1065133. " r1065133 | wstephens | 2009-12-22 17:03:54 +0100 (Tue, 22 Dec 2009) | 4 lines If the user edits or deletes a connection while a ConnectionSecretsJob (GetSecrets dialog) is running, kill the job (and replace it with a new job if the job was edited, so the GetSecrets call is answered). " Kubuntu packagers, please add this as a patch a lot of your users are suffering from it. *** Bug 219829 has been marked as a duplicate of this bug. *** *** Bug 220163 has been marked as a duplicate of this bug. *** *** Bug 220282 has been marked as a duplicate of this bug. *** *** Bug 221183 has been marked as a duplicate of this bug. *** *** Bug 221276 has been marked as a duplicate of this bug. *** *** Bug 221807 has been marked as a duplicate of this bug. *** *** Bug 222989 has been marked as a duplicate of this bug. *** *** Bug 225709 has been marked as a duplicate of this bug. *** *** Bug 227581 has been marked as a duplicate of this bug. *** *** Bug 228083 has been marked as a duplicate of this bug. *** *** Bug 230610 has been marked as a duplicate of this bug. *** please remove me from this thread... non-issue now... my laptop died! *** Bug 233225 has been marked as a duplicate of this bug. *** |