Bugzilla – Bug 262447
KNetworkManager hangs on wallet unlock delay
Last modified: 2007-04-23 13:32:26 UTC
When I first log in, and I'm in an area with a preferred wireless network with security, KNetworkManager attempts to access my "wallet" for the network key. It pops up a dialog asking for my wallet password. If I enter that promptly, all is well. If I log in but then don't get around to actually doing anything for a few minutes, by the time I get around to it, the KNetworkManager space in the system tray is just grey (there's space reserved for the icon, but it's as if it's all transparent; it just shows through to the background). If I enter the wallet password at that point, nothing happens (the network connection is not made, and the KNetworkManager space in the system tray stays all grey). Right clicking on the space where the icon should be does not bring up the KNetworkManager menu. If I locate the KNetworkManager process, kill it, and rerun knetworkmanager, then it pops up and shows that I'm disconnected, and I can manually connect to my preferred network, and it does not require a wallet password at that time.
Helmut, we should discuss that issue at some point with a (large ;-) cup of coffee. Something we probably will have a fix for in 10.3. Moving to 10.3.
Hmm, I cannot reproduce this one. Perhaps it is our loved KWallet deadlock bug #206641 :-) Aaron, would it be possible to get a backtrace of KNetworkManager when it is locked up? Do you have other apps automatically started on login which require KWallet access?
I would be happy to, but how do I collect the backtrace? KNetworkManager is the only app I use that requires KWallet access. Also, if I kill and restart KNetworkManager, then it works fine, so it doesn't necessarily seem that KWallet is blocking things.
Open a terminal (e.g. konsole) and enter the following command: drkonqi --pid `pidof knetworkmanager` This opens a new dialog and on the second tab you can find a backtrace ;-)
Created attachment 133191 [details] KNetworkManager Backtrace Here's the trace as requested
(I should mention that I gathered that trace on openSUSE 10.2)
Thanks Aaron. Looks really like #206641 -> Duplicate. *** This bug has been marked as a duplicate of bug 206641 ***