Ubuntu One Unable to connect or sync using WICD network manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
dacorr@
ERROR:dbus.
FoxyProxy settingsDir: /home/dacorr/
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
(firefox:5733): Gdk-WARNING **: XID collision, trouble ahead
ProblemType: Bug
.home.dacorr.
2009-11-16 08:07:09,444 - dbus.proxies - ERROR - Introspect error on org.freedesktop
2009-11-16 08:07:09,505 - ubuntuone.
.home.dacorr.
[ubuntuone]
bookmarked = True
connected = True
connect = 0
show_applet = 1
Architecture: i386
Date: Mon Nov 16 08:07:53 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitec
ProcEnviron:
LANGUAGE=
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-14-generic i686
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.