Created attachment 1025930 [details]
password dialog after trying to unlock the keyring with a passwordless user
Description of problem:
If I create password-less user (either during anaconda installation, or manually in terminal), that user can't access gnome keyring. The keyring is locked, and every attempt to unlock it (or to write to it, which implies unlocking) shows a dialog:
Enter password to unlock your login keyring
The login keyring did not get unlocked when you logged into your computer.
This is very confusing for the user, because the user was created password-less, it never had a password, and so there is nothing to input here.
Providing any value or no value at all does not unlock the keyring, cancel button cancels the whole operation.
In the end, password-less users can't store or read anything into/from the keyring, and every applications that tries to do so (even on the background, I suppose) makes the aforementioned dialog pop up.
Easily testable with Online Accounts, Empathy, Evolution, ABRT (try to set up bugzilla credentials). Anything that uses gnome-keyring is broken and can't be used (well, you can't save the password, so you would have to repeat it for every launch. not applicable for online-accounts, of course).
PLEASE NOTE: For some reason, if you don't create any user in anaconda, and use gnome-initial-setup on first boot to do that, you can create a passwordless user which *works* - his gnome-keyring password is empty, and keyring can be unlocked ok. I have no idea why that is.
Version-Release number of selected component (if applicable):
F22 TC4 Workstation Live x86_64
Steps to Reproduce:
1. create a passwordless user. either create it in anaconda (there's a checkbox), or use `useradd user; passwd -d user`, or use gnome-control-center to create a user and then run `passwd -d user`
2. reboot, log in as that user
3. try to use any of those apps to save a password, you'll see that dialog and it won't work
4. run seahorse and see your login keyring locked, try to unlock it, same dialog
passwordless users have a very degraded experience, can't save passwords in any app supporting gnome-keyring
passwordless users have an empty password in gnome-keyring, things just work out of the box
Proposing as a blocker:
"Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops. "
Please note that this is violated only for passwordless users, and just those created by anaconda or manually. The first system user, which can be created by gnome-initial-setup (as passwordless) is not affected.
It turns out that the default keyring password is "gis", and g-i-s makes sure it gets updated during user creation. But if you create the user outside of g-i-s (or gnome-control-center), i.e. in anaconda or with useradd and passwd, nothing updates the default password.
For all that cases mentioned above, I can unlock the login keyring for passwordless users, if I use "gis" as a password.
I'm probably -1 blocker +1 FE on this, nice catch though. Passwordless user case isn't the default or (I think) very common, and we can document the 'gis' password.
Some more info:
This problem is actually present on F21 installer as well. There are these package versions:
However, later on, this seems to have been *fixed* in F21. On my updated F21 machine, if I create a user using useradd & passwd, no login keyring is created for him. After an app wants to access a keyring, I'm presented with a dialog asking me to create a 'default' keyring with my chosen password - or I can choose to create it passwordless. This is a great behavior - everything is clear and the user is given a choice whether to encrypt his passwords or not. The package versions on this F21 system are:
Maybe the minor change in gnome-initial-setup fixed it?
On F22, though, everything is back to be broken. I've also tried F22 Beta and F22 Alpha, all broken.
It depends on how fast GNOME team thinks they can fix this (i.e. introduce the same behavior as in updated F21). I'd rather slip a week than release it this way (that makes me a conditional +1). However, if this would be a complex change or people are generally -1 to this, we can document this and require this to be fixed for F23 at latest (hopefully sooner as an update).
(In reply to Kamil Páral from comment #4)
> However, later on, this seems to have been *fixed* in F21.
I take this back, I can't repeat it on the same system (now it fails the same way as in all other cases). I have no explanation for it, unless there is some kind of race condition involved.
I'm -1 blocker on this: password-less installations are rare and the recommended approach is "set a password, then turn on auto-login" anyway.
I'm actually -1 Freeze Exception in this case, since messing with the default password configuration and the keyring seems rather risky for this point in the development cycle. I'd prefer to document the limitation in Common Bugs and move on.
Created attachment 1026755 [details]
create new keyring dialog
I have tested this patch:
There is no change in behavior for users having a password (that's correct). For password-less users, the behavior changed to the one described in comment 4 - by default, there is no login keyring at all. After first attempt to access it (e.g. saving login credentials in abrt), the user is asked to create a 'default' keyring with desired password (it is possible to create it unprotected as well).
I'm attaching screenshots for you to have an idea how it looks like.
Created attachment 1026756 [details]
create new unprotected keyring dialog
gnome-initial-setup-3.16.3-1.fc22 has been submitted as an update for Fedora 22.
Discussed at today's blocker review meeting .
This bug was rejected as blocker but accepted as freeze exception: This bug could easily cause confusion for users who don't set up a password for their accounts, but is not common enough to warrant
This hasn't been included in RC1 by accident. If there's no RC2, we'll need to document this in common bugs.
This seems to be fixed in RC2. I created a passwordless user in anaconda and after installation it didn't have any keyring pre-defined and I was asked to create one on my first attempt to use it.
gnome-initial-setup-3.16.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.