Connection starts late in the boot sequence
Bug #50199 reported by
Tom Chance
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| knetworkmanager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Apologies if this concerns network-manager not the kde frontend, but the timing makes me think it's possibly the latter.
Basically knetworkmanager only starts connecting to my wireless network once KDE has loaded (presumably once it has access to KWallet). It takes a while to connect, so I have to sit and wait before I can use my desktop. It would be much better if it could start connecting earlier so that I have network availability as soon as KDE is up and running.
Revision history for this message
| Anthony Mercatante (tonio) wrote | #1 |
| Changed in knetworkmanager: | |
| status: | Unconfirmed → Rejected |
Revision history for this message
| Luka Renko (lure) wrote | #2 |
To post a comment you must log in.
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.