i dont know

[Wes]

Binary package hint: ubuntuone-client

i dont know

ProblemType: Bug
.home.wes..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 0
 write_limit = 0
 on = False
.home.wes..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 0
 bookmarked = True
Architecture: amd64
CheckboxSubmission: 2a1d9d821b52ccb615d456415fb68133
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Wed Apr 21 12:34:20 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic x86_64

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Mitch Towner (kermiac)]

I'm sorry to hear Ubuntu One is not working properly for you. Can you please advise if you have network-manager installed or if you are using another connection manager (such as wicd) to manage your network connections? To find out if network-manager is installed, please run "apt-cache policy network-manager" (without the quotes) from a terminal window. Network-manager is not installed if the output of that command shows "Installed: (none)".

If you have removed network-manager, please follow the instructions outlined in https://answers.edge.launchpad.net/ubuntuone-client/+faq/836 to install an updated version of ubuntuone-client from the PPA that does not depend on network-manager.

Thanks in advance!

[Mitch Towner (kermiac)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Mitch Towner (kermiac)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!