desktopcouch replication and org.desktopcouch.CouchDB.service are NOT started on desktopcouch.records calls
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
desktopcouch |
Fix Released
|
High
|
Chad Miller | ||
desktopcouch (Ubuntu) |
Fix Released
|
High
|
Chad Miller | ||
ubuntuone-client (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When CouchDatabase object is created in /usr/lib/
However, neither replication nor dbus service to advertise the port is started.
This is happening because the replication process and dbus service to advertise the port are created in /usr/lib/
<aquarius> CardinalFang, desktopcouch.
<aquarius> Also, this may explain why some people don't have replication happen.
<rye> aquarius, those who have don't have applet set to automatic login
<aquarius> *nod*
<rye> aquarius, the replication is started via e.g. evolution calling dbus method to find the port, etc.
Related branches
- Chad Miller (community): Approve
- Vincenzo Di Somma (community): Approve
- Eric Casteleijn (community): Approve
-
Diff: 51 lines (+12/-17)2 files modifieddesktopcouch/application/migration/tests/test_migration.py (+4/-0)
desktopcouch/application/platform/linux/__init__.py (+8/-17)
Changed in desktopcouch: | |
status: | New → Confirmed |
importance: | Undecided → High |
summary: |
desktopcouch replication and org.desktopcouch.CouchDB.service are NOT - started on desktopcouch.records call + started on desktopcouch.records calls |
Changed in desktopcouch: | |
assignee: | nobody → Chad Miller (cmiller) |
Changed in desktopcouch (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in ubuntuone-client (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+) |
Changed in desktopcouch: | |
milestone: | none → 1.0 |
Changed in desktopcouch: | |
status: | Confirmed → In Progress |
Changed in desktopcouch (Ubuntu): | |
status: | Confirmed → In Progress |
milestone: | none → natty-alpha-1 |
Changed in desktopcouch: | |
status: | In Progress → Fix Committed |
Changed in desktopcouch (Ubuntu): | |
milestone: | natty-alpha-1 → natty-alpha-2 |
Changed in desktopcouch: | |
status: | Fix Committed → Fix Released |
Changed in desktopcouch (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in ubuntuone-client (Ubuntu): | |
assignee: | Ubuntu One Desktop+ team (ubuntuone-desktop+) → nobody |
status: | Triaged → Invalid |
Ideally I think ubuntuone-client should ensure desktopcouch replication starts before syncdaemon, giving it a head start. Perhaps even make syncdaemon wait until the first desktopcouch sync is done. This shouldn't take too long, but sharing bandwidth when you are downloading a lot of data could really hurt the user experence for apps that depend on that data from desktopcouch.