With a keyring created after F8 Test2, applications are not able to get data out
of the keyring, or they dont' think they did and repeatedly prompt for the
passphrase. Apps like nm-applet actually seg-fault.
I saw the nm-applet crash, but then i updated it to get debuginfo, and the new
version is acting generally weirdly, so i can't reproduce it. (In fact, i can't
find my wireless network even!)
Did you see this in any other app?
Ok. This is due to a change in gnome-keyring behaviour.
When searching for an item that doesn't exist it used to return a DENIED error.
This is a bit weird, as that indicates that the item exists, but the user
doesn't have access to it.
So, in the bug http://bugzilla.gnome.org/show_bug.cgi?id=447315
This was changed to return a non-error result, but a list of zero items.
nm-applet doesn't look at the list and promptly dereferences the list.
A patch for nm-applet is availible in the ubunty bug:
(Patch is at http://launchpadlibrarian.net/8137066/01_fix_keyring_crash.patch)
Did you see this for any other apps? If so we should fix them too.
CCing dcbw for network manager feedback.
I'm told that evolution would cycle over and over again when trying to get keys
out, so it also is likely not updated to handle the new return value.
Unfortunately I don't have anything else that uses the keyring.
Patch applies to 0.6.x applet; I think 0.7 should be OK here because it does "if
(g_slist_length (found_list) == 0)" which should work fine with a NULL found
list. So if we ship with 0.6.x in F8 I'll make sure the patch gets in, and if
we ship with 0.7 I think we're OK.
This no longer happens, closing.