| 2011-02-28 15:36:07 |
Roman Yepishev |
bug |
|
|
added bug |
| 2011-02-28 15:36:45 |
Roman Yepishev |
branch linked |
|
lp:~rye/desktopcouch/lockfile-0.6.4 |
|
| 2011-03-01 14:46:13 |
Joshua Hoover |
bug task added |
|
desktopcouch (Ubuntu) |
|
| 2011-03-01 14:46:26 |
Joshua Hoover |
desktopcouch: status |
New |
In Progress |
|
| 2011-03-01 14:46:30 |
Joshua Hoover |
desktopcouch: importance |
Undecided |
High |
|
| 2011-03-01 14:46:40 |
Joshua Hoover |
desktopcouch: assignee |
|
Roman Yepishev (rye) |
|
| 2011-03-01 14:46:49 |
Joshua Hoover |
desktopcouch (Ubuntu): status |
New |
In Progress |
|
| 2011-03-01 14:46:59 |
Joshua Hoover |
desktopcouch (Ubuntu): importance |
Undecided |
High |
|
| 2011-03-01 14:47:13 |
Joshua Hoover |
desktopcouch (Ubuntu): assignee |
|
Roman Yepishev (rye) |
|
| 2011-03-01 14:47:29 |
Joshua Hoover |
nominated for series |
|
Ubuntu Lucid |
|
| 2011-03-01 14:47:29 |
Joshua Hoover |
bug task added |
|
desktopcouch (Ubuntu Lucid) |
|
| 2011-03-01 14:49:07 |
Joshua Hoover |
nominated for series |
|
desktopcouch/0.6-stable |
|
| 2011-03-01 14:49:07 |
Joshua Hoover |
bug task added |
|
desktopcouch/0.6-stable |
|
| 2011-03-01 14:49:19 |
Joshua Hoover |
desktopcouch/0.6-stable: status |
New |
In Progress |
|
| 2011-03-01 14:49:32 |
Joshua Hoover |
desktopcouch/0.6-stable: importance |
Undecided |
High |
|
| 2011-03-01 14:49:44 |
Joshua Hoover |
desktopcouch/0.6-stable: assignee |
|
Roman Yepishev (rye) |
|
| 2011-03-01 14:50:44 |
Joshua Hoover |
tags |
|
desktop+ support |
|
| 2011-03-01 14:59:26 |
Joshua Hoover |
description |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance) |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
This bug prevents CouchDB pairing with Ubuntu One from working, which prevents users from syncing contacts and bookmarks in Lucid with CouchDB from backports installed. |
|
| 2011-03-01 14:59:45 |
Joshua Hoover |
description |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
This bug prevents CouchDB pairing with Ubuntu One from working, which prevents users from syncing contacts and bookmarks in Lucid with CouchDB from backports installed. |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
This bug prevents CouchDB pairing with Ubuntu One from working consistently, which prevents users from syncing contacts and bookmarks in Lucid with CouchDB from backports installed. |
|
| 2011-03-01 17:58:14 |
Brian Murray |
desktopcouch (Ubuntu Lucid): importance |
Undecided |
High |
|
| 2011-03-01 17:58:14 |
Brian Murray |
desktopcouch (Ubuntu Lucid): status |
New |
In Progress |
|
| 2011-03-02 15:00:09 |
Roberto Alsina |
bug |
|
|
added subscriber Roberto Alsina |
| 2011-03-03 18:10:35 |
Chad Miller |
branch linked |
|
lp:~cmiller/ubuntu/lucid/desktopcouch/lp726597 |
|
| 2011-03-03 20:52:13 |
Roman Yepishev |
description |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
This bug prevents CouchDB pairing with Ubuntu One from working consistently, which prevents users from syncing contacts and bookmarks in Lucid with CouchDB from backports installed. |
ubuntuone-preferences and ubuntuone-login both wait for CredentialsFound signal (in Lucid).
Both processes will interact with couchdb upon receiving of the signal, the first one will read replication exclusion, the latter will put a pairing record to the db.
It turns out that they are running so head-to-head that they initialize 2 desktopcouches. Desktopcouch checks the pid and if it is not there it will start the couchdb, however, since there are 2 simultaneous calls both processes start their own couchdb. Eventually only one pid will be written to the file, and only one couchdb will be contacted (because of dbus response being returned only by one desktopcouch instance)
This bug prevents CouchDB pairing with Ubuntu One from working consistently, which prevents users from syncing contacts and bookmarks in Lucid with CouchDB from backports installed.
TEST CASE:
1. Ensure that no couchdb and desktopcouch-service processes are running:
1.1 /usr/lib/desktopcouch/desktopcouch-stop
1.2 killall desktopcouch-service
1.3 killall beam
1.4 killall beam.smp
2. Ensure that ubuntuone-syncdaemon is running (we need ubuntuone-login to be running to test for double start)
3. Open ubuntuone-preferences from terminal
4. Run sudo netstat -lntp | grep beam, there should be only one process with beam / beam.smp
5. Verify that there is only one "Apache CouchDB has started on http://127.0.0.1:$port" line in ~/.cache/desktop-couch/desktop-couchdb.log.1 |
|
| 2011-03-04 20:08:21 |
Joshua Hoover |
desktopcouch (Ubuntu Lucid): status |
In Progress |
New |
|
| 2011-03-08 17:55:56 |
Chad Miller |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2011-03-14 20:35:33 |
Chad Miller |
desktopcouch (Ubuntu Lucid): status |
New |
Fix Committed |
|
| 2011-03-15 13:44:48 |
Joshua Hoover |
desktopcouch/0.6-stable: status |
In Progress |
Fix Committed |
|
| 2011-03-15 14:43:59 |
Joshua Hoover |
desktopcouch: status |
In Progress |
Fix Released |
|
| 2011-03-15 14:44:09 |
Joshua Hoover |
desktopcouch/0.6-stable: status |
Fix Committed |
Fix Released |
|
| 2011-03-15 14:53:21 |
Joshua Hoover |
desktopcouch (Ubuntu): status |
In Progress |
Fix Released |
|
| 2011-03-15 14:53:33 |
Joshua Hoover |
desktopcouch: assignee |
Roman Yepishev (rye) |
Chad Miller (cmiller) |
|
| 2011-03-15 14:53:47 |
Joshua Hoover |
desktopcouch/0.6-stable: assignee |
Roman Yepishev (rye) |
Chad Miller (cmiller) |
|
| 2011-03-15 14:54:01 |
Joshua Hoover |
desktopcouch (Ubuntu): assignee |
Roman Yepishev (rye) |
Chad Miller (cmiller) |
|
| 2011-03-15 14:54:23 |
Joshua Hoover |
desktopcouch/0.6-stable: status |
Fix Released |
Fix Committed |
|
| 2011-03-30 21:07:52 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2011-03-30 21:07:59 |
Martin Pitt |
tags |
desktop+ support |
desktop+ support verification-needed |
|
| 2011-03-31 18:27:51 |
Pedro Villavicencio |
tags |
desktop+ support verification-needed |
desktop+ support verification-done |
|
| 2011-04-07 21:41:34 |
Launchpad Janitor |
desktopcouch (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2011-04-08 13:53:39 |
GRADY A.SMITH |
desktopcouch (Ubuntu Lucid): assignee |
|
GRADY A.SMITH (gradysmith8712) |
|
| 2011-09-19 21:47:16 |
Ubuntu Foundations Team Bug Bot |
tags |
desktop+ support verification-done |
desktop+ support testcase verification-done |
|
