SyncDaemon - WARNING - Please don't run the syncdaemon as root

Bug #930398 reported by Joshua Hoover on 2012-02-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Status tracked in Trunk
Stable-3-0
High
Brian Curtin
Trunk
High
Brian Curtin

Bug Description

Some Windows users on ubuntuone-2.99.3 are seeing the following logged in syncdaemon.log:

2012-02-10 10:13:00,802 - ubuntuone.SyncDaemon - WARNING - Please don't run the syncdaemon as root.2012-02-10 10:13:00,806 - ubuntuone.SyncDaemon - INFO - not starting twisted.manhole

In some cases syncdaemon does not start.

Related to bug #784450?

Related branches

Joshua Hoover (joshuahoover) wrote :

Based on support requests, it looks like at least some of the users we've heard back from experiencing this issue are running as Administrator.

Changed in ubuntuone-client:
assignee: Ubuntu One Desktop+ team (ubuntuone-desktop+) → Brian Curtin (brian.curtin)
Brian Curtin (brian.curtin) wrote :

Do we have more information on the OS'es that users are reporting this from?

I'm able to reproduce this on Win7 only if I explicitly start ubuntuone-syncdaemon.exe from an Administrator elevated command prompt (which you need to specify when starting it up - it's not normal to do so). My user account has admin privileges, but unless I explicitly specify to start U1 (or anything) as Administrator, it'll run with regular user access. Even if I shut down all U1 services and then start the control panel as Admin, it doesn't start the syncdaemon as admin.

Basically, yeah, I can get this to happen if I go out of my way, but I don't really see how it's actually happening in the wild at least on Win7.

Brian Curtin (brian.curtin) wrote :

I'm running just fine on XP as the Administrator account with no root warning to speak of. In fact, doing a "Run as..." explicit administrator command prompt and starting syncdaemon doesn't even cause the root warning.

Changed in ubuntuone-client:
status: Confirmed → In Progress
Brian Curtin (brian.curtin) wrote :

It was brought to my attention that I was running the wrong installer, so ignore that last comment :)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers