Ubuntu
ubiquity package

Logged in on the installer page but u1 control panel needed me to login

Bug #1220770 reported by Dave Morley
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
High
Unassigned

Bug Description

I've been told that u1 and deja-dupe shouldn't need login details if you have signed in on the installer page.

I have installed from the 20130904 current iso image on amd64.

I logged into u1 from the installer page. On opening u1-control-panel to setup sync I had to login. I was under the impression that this wouldn't be necessary.

Steps:
1. install ubuntu
2. during the install login to your u1 account
3. complete the install
4. login to your fresh install
5. open u1-control-panel

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-sso-client 13.08-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Wed Sep 4 16:04:48 2013
InstallationDate: Installed on 2013-09-04 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-sso-client
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Dave Morley (davmor2) wrote :
Changed in ubuntu-sso-client (Ubuntu):
assignee: nobody → Rodney Dawes (dobey)
importance: Undecided → High
status: New → Confirmed
description: updated
Revision history for this message
dobey (dobey) wrote :

Moving this to ubiquity as it seems to be that the installer is either not creating the keyring correctly, or failing to copy it over correctly. I've installed in a VM and logged into U1 with the installer, but the resulting install has an empty keyring (according to the file command), which gnome-keyring-daemon doesn't seem to be pulling in (seahorse shows an empty list for both the list of keyring/cert stores, and the list of stored keys).

affects: ubuntu-sso-client (Ubuntu) → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
assignee: Rodney Dawes (dobey) → nobody
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Can you please attach /var/log/installer/syslog ?

Revision history for this message
Jason Robinson (jaywink) wrote :

Affected by this too, just tried the latest image via Testdrive (64bit Ubuntu). Signed in successfully(?) during install but no Ubuntu One running when logging in the first time. Also credentials asked when launching Ubuntu One manually.

Syslog attached from VM.

Revision history for this message
Jason Robinson (jaywink) wrote :

Devices on Ubuntu One account page shows this though, so something happened;

> Ubuntu One @ jason-VirtualBox
> Linked on 11 Oct 2013, last used on 14 Oct 2013

Interesting that it has "11th Oct" as linked. I did try installing Saucy in this VM before, but that failed due to another bug which has been fixed, so I guess this was linked to that. Still, if everything was successful linking the VM to my Ubuntu One, the client should not require logging in any more.

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.