Ubuntu One client connection broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
Ubuntu version: Xubuntu 9.10 (dist-upgraded from 9.04)
UbuntuOne version: 1.0.2-0ubuntu2
The client will not connect to the cloud. Moreover, it's not the failure to connect as outlined in the FAQ, since it won't report even trying to connect. Wireshark doesn't detect any activiity on the software's part.
I tried reinstalling U1 as outlined in the FAQ using Karmic repository, but to no change.
Attempting to remove the machine from U1 account via web, i was unable to reconnect it later. Another attempt at reinstalling did not help again.
Canceling and restarting the subscription via web had no effect either.
The symptoms are:
The applet will start, and show a "disconnected" state and report "Your files are up to date". Left-clicking and selecting "Connect" doesn't yield any response at all. From the right-click menu, everything will work, but there are no options that would help to connect.
The software will not report any errors, nor cause any crashes. In fact, it just ignores me.
A few suspicions: Last time i used U1 was on 9.04, and it was with NetworkManager running. Now that i'm up to 9.10, i'm forced to use wvdial for my USB stick since the NM included in 9.10 will not operate it (it did work in 9.04, and the bug is filed). Maybe this has something do do with this?
ProblemType: Bug
.home.anarchid.
.home.anarchid.
[ubuntuone]
show_applet = 1
connected = True
connect = 0
bookmarked = True
Architecture: amd64
Date: Thu Feb 4 14:32:51 2010
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-17-generic x86_64
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 357395, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.