| 2006-08-20 23:58:13 |
Anthony Mercatante |
knetworkmanager: statusexplanation |
|
Since knetworkmanager uses, as you say, Kwallet, there is no other choice to let it start correctly that ensuring that kwallet is started, which required most kde components to be started and libs loaded.
There is no solution to your problem unfortunatelly, except removing the kwallet integration to store passwords, which would be a non-sense.
Anyway, 10 seconds to wait to get automatically connected looks, at least, reasonnable :)
If you want sooner connections, better playing with wpasupplicant manually. |
|
