Bug 1035548

Summary: Adding online account during initial setup causes keyring password prompt, account is not properly configured
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: gnome-initial-setupAssignee: Jasper St. Pierre <jstpierr>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: jstpierr, kevin, mclasen, rmatos, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: AcceptedFreezeException
Fixed In Version: gnome-initial-setup-3.10.1.1-4.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-10 06:55:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 980657    

Description Adam Williamson 2013-11-28 03:59:03 UTC
Upstream report: https://bugzilla.gnome.org/show_bug.cgi?id=719458 . Filed downstream to propose as a Final freeze exception: this is obviously bad behaviour in an initial-setup utility which cannot be fixed with a post-release update.

With Fedora 20 Final TC3 - https://dl.fedoraproject.org/pub/alt/stage/20-TC3/ -
I've reproduced this three times in a row. Also happens with TC2. 

1. Install, setting a root password but not creating a user account (DVD or
live, doesn't matter)
2. Boot, go through gnome-initial-setup. I set my user account with name
'test', password 'test'.
3. At the online accounts step, configure an Owncloud account.

Result: after entering the URL, username and password for the Owncloud account,
I am prompted to enter a keyring password. mclasen tells me this is not
expected behaviour (typically a user's keyring is locked with the user
account's password, and I already set one of those in an earlier step). Also,
if I set a password as it asks and complete g-i-s, when I'm logged into the
desktop, the configured account doesn't work right: if I run Nautilus and click
on the bookmark for the Owncloud account, it claims the credentials are
invalid. If I go to the Control Center's 'Online Accounts' panel, I see
'Credentials have expired. Sign in to enable this account.'

Comment 1 Rui Matos 2013-11-29 18:00:47 UTC
After discussion on IRC we decided to just disable the GOA page in new user mode for F20. The page is still there and fully functional for first time logins on regular accounts.

Comment 2 Fedora Update System 2013-11-29 18:22:29 UTC
gnome-initial-setup-3.10.1.1-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gnome-initial-setup-3.10.1.1-4.fc20

Comment 3 Fedora Update System 2013-12-01 17:40:42 UTC
Package gnome-initial-setup-3.10.1.1-4.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-initial-setup-3.10.1.1-4.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22523/gnome-initial-setup-3.10.1.1-4.fc20
then log in and leave karma (feedback).

Comment 4 Adam Williamson 2013-12-03 01:18:47 UTC
what the hell? somehow I never actually proposed this as a freeze exception. proposing. can I get some votes so we can pull this into TC4?

Comment 5 Kevin Fenzi 2013-12-03 01:20:19 UTC
+1 FE

Comment 6 Dennis Gilmore 2013-12-03 01:21:18 UTC
+1 to FE from me

Comment 7 Adam Williamson 2013-12-03 01:22:21 UTC
thanks folks, that's +3, setting accepted FE.

Comment 8 Adam Williamson 2013-12-03 01:24:26 UTC
verified with gnome-initial-setup-3.10.1.1-4.fc20 - the online account step is indeed gone from the 'creating a new user account' path. sad we had to lose it :(

Comment 9 Fedora Update System 2013-12-10 06:55:43 UTC
gnome-initial-setup-3.10.1.1-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.