Sorry for the confusion.
This is not a bug in either gnome-keyring or network manager.
I had started using transmission recently , and since it was among my
startup [auto-launch] apps, transmission would start fast and begin
using the bandwidth _completely_ , not allowing any other app to gain
acc
Sebastien Bacher mentioned [on irc] that this might be a network-manager
bug.
I'll do nm debugging and get a better report on this bug.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Incomplete
--
Slow to release wireless lock in auto-login sessions
https://bugs.launchpad.net/bugs/
The wireless network uses wep key[saved] for which the gnome-keyring has
a master keyring over , By lock , i meant this one.
Usually the keyring asks for user permissions to unlock the keyring and
connect to the network at every session start.
But I'v set the wireless connection as "Available to
thank you for your bug report, what do you call lock there?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-keyring (Ubuntu)
Status: New => Incomplete
--
Slow to release wireless lock in auto-login sessions
https://bugs.launchpad.net/bugs/526898
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39697837/Dependencies.txt
--
Slow to release wireless lock in auto-login sessions
https://bugs.launchpad.net/bugs/526898
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
