UbuntuOne does not automatically connect on startup

[Matthew Horr]

Binary package hint: ubuntuone-client

Even with UbuntuOne Preferences "Connect on Start Automatically" selected, I must manually connect UbuntuOne on startup.
Using Ubuntu 9.10 Beta (karmic) on MacBookPro1,1.

Expect: Automatically connect on startup
Happens: Must manually connect.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: fa1350c091dd65e55a67fb73aeae1c2c
CheckboxSystem: 91945207d732350068f2b1aa7b5d7083
Date: Mon Oct 12 21:28:46 2009
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 0.96.0-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-13-generic i686

[Matthew Horr (matthorr)]

Using ubuntuone-client version 0.96.0-0ubuntu1

[Joshua Hoover (joshuahoover)]

Hi Matthew,

Thank you for taking the time to file this bug report. Can you upgrade to our latest release (put out yesterday) and let me know if you continue to see this problem?

Thank you,

Joshua

[Eugene Crosser (crosser)]

Is Bug #441362 duplicate of this?

[Steve Holmes (bouncysteve)]

I have the same problem with ubuntuone-client v 1.0.0-0ubuntu1.

[Steve Holmes (bouncysteve)]

.home.bouncysteve..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.bouncysteve..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: i386
CheckboxSubmission: b9c2d7dd42fbb05820b04aec6e4dacb6
CheckboxSystem: 83cd0157b919c4049631a35cc04da999
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.0-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev sambashare scanner tape video

[Matthew Horr (matthorr)]

I updated ubuntuone-client to the latest release (1.0.0-0ubuntu1) and now I cannot connect at all.
When I logged in, the icon was an exclamation point, and then it showed the disconnected symbol.
This might be an issue bigger than ubuntuone, as I cannot log into either gnome-gmail-notifier 0.9.4 or CheckGmail v1.13svn.
Please let me know if there is any more information I can upload that would be helpful.

[Matthew Horr (matthorr)]

Sorry, the updated release is 1.0.1-0ubuntu1

[Eugene Crosser (crosser)]

Same here: ubutnuone-client 1.0.1-0ubuntu1 on karmic - still no automatic connection, and when I try to connect manually, briefly shows an exclamation mark and goes back to unconnected.

[Matthew Horr (matthorr)]

Half the problem has corrected itself - I can manually connect. Upon log in this morning, firefox opened asking me to log into Launchpad and add my computer to authorise my computer to my UbuntuOne account. Once I (re)authorised my computer, UbuntuOne was able to connect on its own. It seems that the computer authorised on the account was no longer synched with the token on my computer.

When I restarted, though, I had to manually connect again. indicator-applet is also crashing which may or may not be related.

On a side note, I cannot click on the bottom-most file on the website (it is covered up by the "cloud").

[Darren Worrall (dazworrall)]

I started a fresh this morning after a bit of a turbulent time with the client (ie, rm -r ~/.config/ubuntuone && rm -r ~/.local/share/ubuntuone && rm -r ~/cache/ubuntuone)

I (re)authorised my machine, connected and synced without issue, but the client doesn't autoconnect on startup. All I have in oath-login.log is 'Starting Ubuntu One client version 1.0.1'. Initiate a connection manually and all is fine.

[Ed Hewitt (edhewitt-deactivatedaccount)]

I am running the latest version of Ubuntu one, suffering same issue.

[Eugene Crosser (crosser)]

After some update (on the server side?) a few days ago, the problem no longer exists for me, both karmic/1.0.1-0ubuntu1 and 1.0.1+r257-0ubuntu1~ppa1~jaunty work fine

[Matthew Horr (matthorr)]

I have notice UbuntuOne will occasionally sign in automatically on start up. However, the problem still remains for me. I have not noticed anything that would explain why it works when it works.

[AdamL (admlzu)]

I installed the Beta today and I am experiencing this issue. The client starts at startup, however, it does not connect - showing an exclamation mark. I can immediately instruct the client to connect manually after startup and it always succeeds. When editing preferences the options do not save, no matter how many times I change the options!

[Dan (dorjedan)]

I am also experiencing this. The client will start up but does not automatically connect (even though I have "connect on start" set to "automatically"). The icon in the panel shows an exclamation mark. I can, however, connect manually.

[Eugene Crosser (crosser)]

Contrary to my comment #17, I continue to experience this problem with 1.0.2-0ubuntu1on karmic: on startup, the icon shows the exclamation mark, but can be connected manually. On two jaunty machines, 1.0.1+r257-0ubuntu1~ppa1~jaunty autoconnects all right.

[Nick Barcet (nijaba)]

Problem still here with 1.0.2-0ubuntu2.

[AdamL (admlzu)]

I am continuing to experience this problem too, even with the latest release of the client (above)
Do you require any further details?

[Joshua Hoover (joshuahoover)]

For those who are seeing the client not connect automatically, only when you manually connect. Does this happen every time you start the client? I know for some, it won't auto connect the first time after updating to 1.0.2-ubuntu2. Can some of you attach the following file from your computers that are having this problem? ~/.config/ubuntuone/ubuntuone-client.conf

Thank you,

Joshua

[Nick Barcet (nijaba)]

Here is the requested file.

Please note that the problem only occurs when logging in to my session. It does not occur if I quit and start ubuntuone-client again in a running session. It looks like it first does not connect on login because network-manager has not yet finished setting up the connection and then it does not get the event that the connection is up.

[Matthew Horr (matthorr)]

After the latest upgrade (1.1+r273-0ubuntu1) it would still not auto-login on start up. It would auto-login after switching users or restarting Xserver.

I then de-authorized my computer on the UbuntuOne website, connected to UbuntuOne and re-authorized my computer and Tomboy notes.

Since then, UbuntuOne has been automatically logging in on start up.

The config file is attached.

[Matthew Horr (matthorr)]

I have to recall my last comment, ubuntuOne is still not connecting on startup.

The Tomboy notes and Evolution contacts don't seem to update either - they only synch when I initially set them up. Anyone else having these issues? I might submit a separate bug report.

[ec (ecroes)]

Ubuntu 9.10 \n \l
Linux cd-a03-5 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux

ubuntuone-client:
  Geïnstalleerd: 1.0.2-0ubuntu2
  Kandidaat: 1.0.2-0ubuntu2
  Versietabel:
 *** 1.0.2-0ubuntu2 0
        500 http://nl.archive.ubuntu.com karmic-updates/main Packages
        100 /var/lib/dpkg/status
     1.0.2-0ubuntu1 0
        500 http://nl.archive.ubuntu.com karmic/main Packages

This also occurs on 64 bit karmic

[dan o'neil (dan-aquariuscoaching)]

I'm having the same problem. Is it possible that the automatic connect is trying to happen before the wireless (or wired) network connection is coming up?

[KDontenville (kevin-keepnet)]

This is another me-too comment. Connects fine manually but no auto-connecting possible. Karmic 32bit, Ubuntu and fully patched as of this morning.

[merovius (merovius)]

Same her manually connect fine, no automatic. Everything else is fine.

[T. Dalbo (tdalbo)]

Automatic connections are few and far between, so I mainly have to manually connect on boot.

[Andre (ajx)]

No automatic connect on all my machines after boot. Have to click on "connect". One machine with LAN has network available before desktop starts, the other is a notebook with WiFi connection. Both machines running 32bit Karmic (1x fresh install, 1x upgraded from Jaunty).

[RavanH (ravanhagen)]

Funny:

After a fresh boot login, U1 does not autoconnect (yes, that is a "me too" ;) ). However, when I subsequently log out and back in again, U1 connects automatically without any probs!

[Ilya Melehin (melehin-81)]

Doesn`t connect automatically at startup. And me too! :)

[Norbert Moldován (moldovannorbert)]

Same situation on my system.

[airamana (ana-ochia)]

At first when I was using my karmic, the ubuntu cloud was working fine since it automatically connects, but after performing some upgrades, I cannot connect to my Ubuntu Cloud anymore including on startup

[Chad Miller (cmiller)]

I have a request for people who are affected by this bug, namely that the applet runs, and fails to connect, and does then connect after one explicitly asks it to connect.

I'd like you to attach the files ending in ".log" inside ~/.cache/ubuntuone/log/ . Then, kill all processes named "ubuntuone-client-applet", and open a terminal and run it manually. Finally, when you run "ubuntuone-client-preferences", what do you see?

[Eugene Crosser (crosser)]

On login, the ubuntu-one applet showed with exclamation mark, i.e. unconnected.

>I'd like you to attach the files ending in ".log" inside
~/.cache/ubuntuone/log/ .

attached; there was also an zero-length syncdaemon-exceptions.log

>Then, kill all processes named "ubuntuone-
client-applet", and open a terminal and run it manually.

When I did that, the applet came up in connected state.

>Finally, when you run "ubuntuone-client-preferences", what do you see?

The usual -
Show icon: Always
Connect on start: Automatically
[unchecked] Limit Bandwidth Usage
speed selectors greyed out

Could it be a timing issue, the applet trying to come up before the networkmanager has set up the network?..

[Victor Vargas (kamus)]

@Matthew, please could you upgrade your ubuntuone-client version to latest included in Karmic and check if this issue is still affecting you? Thanks in advance.

[iGadget (igadget)]

Logs attached. Will now try the rest of the instructions.

[iGadget (igadget)]

>Then, kill all processes named "ubuntuone-
client-applet", and open a terminal and run it manually.

Same with me - when I did that, the applet came up in connected state.

>Finally, when you run "ubuntuone-client-preferences", what do you see?

Nothing out of the ordinary:
Show icon: When updating (translated from Dutch)
Connect on start: Automatically
[unchecked] Limit Bandwidth Usage
speed selectors greyed out

[iGadget (igadget)]

One more interesting aspect - since I ran the client from a terminal, I can see some of it's output. It's showing the following:

DBusException(dbus.String(u'Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.'),)

The Ubuntu One icon is still present in the tasktray, but it doesn't respond to any of my mouseclicks. When I abort the client in the terminal (and confirmed that no more ubuntuone-client-applet process is running) and start it again, no client icon appears and no message is displayed in the terminal.

[RavanH (ravanhagen)]

Same on Karmic 64bit with UO 1.0.3 and Wicd 1.6.x

> I'd like you to attach the files ending in ".log" inside ~/.cache/ubuntuone/log/ .
See attached files above

> Then, kill all processes named "ubuntuone-client-applet", and open a terminal and run it manually.
Client comes up and connects automatically (as reported by others)

> Finally, when you run "ubuntuone-client-preferences", what do you see?
Again, same as others: the usual...
Show icon: When updating (also translated from Dutch here)
Connect on start: Remember last time (translated from Dutch again; same happens with Automatic setting)
[unchecked] Limit Bandwidth Usage
speed selectors greyed out

[RavanH (ravanhagen)]

Some observations on the matter:

I have noticed some irregularities with auto-connect. After a fresh boot, most of the times it does not work but sometimes it does. However, after logout and login, U1 auto-connect works just fine.

I tried auto-starting U1 with a delay by editing the auto-start entry from:
ubuntuone-client-applet

to:
sh -c "sleep 60 && ubuntuone-client-applet"

but that did not seem to make much of a difference. When changing the sleep time to 120 seconds, I noticed an increase in successful auto-connections after fresh boot-ups.

Now normally, when I boot my PC, I log in as soon as the GDM login screen appears but when I wait for a few minutes (and have a coffee) before logging in, U1 auto-connect works 100%... up till now anyway... remarkable.

Can anyone confirm this or is it just a fluke behavior?

[RachaelB (8-launchpad-rlb-me)]

I suspect that the client isn't waiting for the network to become
available and giving up after its first (unsuccessful) attempt to
connect.

This would explain why it works after logging out/in.

I don't have any data to support this theory - it's just an idea!

Rachael

On 15 Feb 2010, at 10:46, ravanhagen <email address hidden> wrote:

> Some observations on the matter:
>
> I have noticed some irregularities with auto-connect. After a fresh
> boot, most of the times it does not work but sometimes it does.
> However,
> after logout and login, U1 auto-connect works just fine.
>
> I tried auto-starting U1 with a delay by editing the auto-start
> entry from:
> ubuntuone-client-applet
>
> to:
> sh -c "sleep 60 && ubuntuone-client-applet"
>
> but that did not seem to make much of a difference. When changing the
> sleep time to 120 seconds, I noticed an increase in successful auto-
> connections after fresh boot-ups.
>
> Now normally, when I boot my PC, I log in as soon as the GDM login
> screen appears but when I wait for a few minutes (and have a coffee)
> before logging in, U1 auto-connect works 100%... up till now anyway...
> remarkable.
>
> Can anyone confirm this or is it just a fluke behavior?
>
> --
> UbuntuOne does not automatically connect on startup
> https://bugs.launchpad.net/bugs/450082
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “ubuntuone-client” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubuntuone-client
>
> Even with UbuntuOne Preferences "Connect on Start Automatically"
> selected, I must manually connect UbuntuOne on startup.
> Using Ubuntu 9.10 Beta (karmic) on MacBookPro1,1.
>
> Expect: Automatically connect on startup
> Happens: Must manually connect.
>
> ProblemType: Bug
> Architecture: i386
> CheckboxSubmission: fa1350c091dd65e55a67fb73aeae1c2c
> CheckboxSystem: 91945207d732350068f2b1aa7b5d7083
> Date: Mon Oct 12 21:28:46 2009
> DistroRelease: Ubuntu 9.10
> Package: ubuntuone-client 0.96.0-0ubuntu1
> PackageArchitecture: all
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
> SourcePackage: ubuntuone-client
> Uname: Linux 2.6.31-13-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/450082/+subscribe

[Eugene Crosser (crosser)]

> I have noticed some irregularities with auto-connect. After a fresh boot, most of the times it does not work but sometimes it does. However, after logout and login, U1 auto-connect works just fine.

I believe that I see this behaviour too.
I did not try to delay login after boot.

[Patrick Ulbrich (pulb)]

it seems the problem is indeed a missing internet connection.
i created this wrapper script which is called at startup instead of the ubuntu-one default one:

"
#!/bin/bash

# wait for active internet connection
while [ "$(ifconfig | grep 192.168)" == "" ]; do
 sleep 2
done

ubuntuone-client-applet
"