Couldn't add machine to U1 account

there is the following output in syncdaemon.log

2011-01-02 19:24:05,181 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: <State: 'READY' (queues IDLE connection 'With User Not Network')>; queues: metadata: 0; content: 0; hash: 0, fsm-cache: hit=18 miss=5) ----
2011-01-02 19:24:45,477 - ubuntuone.SyncDaemon.DBus - INFO - u'CredentialsFound': callbacking with credentials (token_name: None).
2011-01-02 19:24:45,477 - ubuntuone.SyncDaemon.DBus - INFO - connect: credential request was successful, pushing SYS_USER_CONNECT.

Hello,
connection: With User Not Network means that syncdaemon has queried the network manager and it asserted syncdaemon that there is no network configuration.
Please check whether you still have network manager installed and running. In case network manager is running you will most likely need to uninstall it to use wicd.
Marking as Incomplete, in case your network manager is not running, please set back to New and we will continue debugging.

removing network-manager solves the problem, we can assume to mark this bug as resolved

I'm running LTSP at home and getting this from 'u1sdtool -s':

connection: With User Not Network
description: ready to connect
is_connected: False
is_error: False
is_online: False
queues: WORKING

Since removing network-manager might cause future problems, I'm not that comfortable removing it. Since gnome main package depends on network-manager I'm guessing future upgrades could suffer.

It would be nice if there's any way to get Ubuntu One accepting that there's a network connection, even though the client has Network Manager installed. Does anyone know if that's possible at this moment.

I managed to fix this in /usr/share/pyshared/ubuntuone-client/ubuntuone/syncdaemon/interaction_interfaces.py by calling self.network_connected() in network_state_changed() even if STATE is not ONLINE. Hackish, but maybe a lead to the developers.

It's syncing on my LTSP client now, anyway...

Johan, I'm not sure which package you say requires network-manager, but doing an apt-get remove on my machine, only the packages network-manager and network-manager-gnome are selected for removal. There's no harm in removing it if you aren't using it, and if you aren't using it, you probably should remove it. Ubuntu One isn't the only thing that will be affected by a false description of connectivity from the service.

The thing is, I am using it on the Server. It seems unnecessary to require NetworkManager. These are the packages that will be removed if I 'sudo apt-get remove network-manager':

gnome
gnome-core
network-manager
network-manager-gnome

The gnome and gnome-core packages are meta-packages, and do not include any functionality themselves. We do not require NetworkManager in Ubuntu One, but do use it if it is available. If there is no NetworkManager service running, then it will not be used. So it is safe to remove it, if you are not using it.

But I am using NetworkManager - on the LTSP server. Maybe that's why Ubuntu One is not recognizing my network connection on the client. As I describe above, changing this file makes U1-sync work on my setup:

/usr/share/pyshared/ubuntuone-client/ubuntuone/syncdaemon/interaction_interfaces.py

Sure, I can remove NM from the server and maybe that would fix the problem for me, but that's already accomplished. I'm just trying to help so that other LTSP-users (or non-NM users) can use this fantastic U1 service.

How are you using NM on the LTSP server exactly? It seems pretty clear that you are not using it, because it says you have no network.

Well, I have one user logged in on the server. This user has a NM applet showing.

Then I have other users logged in through clients. These do not (and should not) have NM applets showing.

If I understand this correctly, U1 syncdaemon (running in userspace) tries to ask NM (running in userspace) whether there is an Internet connection. But on the clients, there is no NM in userspace.

So, what I did was to always tell the syncdaemon it's online - whatever the NM-check said. That's the only way I could get U1 working on thin clients so far.

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