Sync problems when restarting Unity place daemons
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
High
|
Mikkel Kamstrup Erlandsen | ||
dee |
Fix Released
|
High
|
Mikkel Kamstrup Erlandsen | ||
unity-lens-applications |
Fix Released
|
High
|
Mikkel Kamstrup Erlandsen | ||
unity-lens-files |
Fix Released
|
High
|
Mikkel Kamstrup Erlandsen | ||
dee (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity-place-applications (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity-place-files (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When any of the Unity place daemons are restarted you'll see something like:
-----------
$ src/unity-
(process:2494): unity-applicati
(process:2494): unity-applicati
(process:2494): libunity-DEBUG: unity-place.
(process:2494): dee-CRITICAL **: clone_leader: assertion `self->
(process:2494): dee-CRITICAL **: clone_leader: assertion `dee_model_
(process:2494): dee-WARNING **: Transaction from com.canonical.
(process:2494): dee-WARNING **: Transaction from com.canonical.
(process:2494): dee-WARNING **: Transaction from com.canonical.
---------
and the shared models will fail to sync properly. There are two issues at play here:
1) DeeSharedModel doesn't accept seqnum > 0 for its first Commit, which it should
- This obviously needs to be fixed in Dee
2) Architecture problem between place daemons and unity shell - the shell should not hold a writable model. Can be fixed by one these measures:
2.1) Make sure the place daemons only start updating their models *after* they've received the "notify:
2.2) Implement a read-only DBus model that doesn't own the swarm name. See bug #675565
Related branches
Changed in dee: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in unity: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → High |
milestone: | none → 3.4.6 |
status: | New → Triaged |
Changed in dee (Ubuntu): | |
status: | New → Triaged |
Changed in dee: | |
status: | Triaged → Fix Committed |
Changed in unity-place-files: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in unity-place-applications: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in unity: | |
status: | Triaged → In Progress |
Changed in dee: | |
milestone: | none → 0.5.10 |
Changed in unity-place-applications: | |
status: | Triaged → Fix Committed |
Changed in unity-place-files: | |
milestone: | none → 0.5.38 |
status: | Fix Committed → Fix Released |
Changed in unity-place-applications: | |
milestone: | none → 0.2.34 |
status: | Fix Committed → Fix Released |
Changed in dee: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
status: | In Progress → Fix Released |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
This bug was fixed in the package dee - 0.5.10-0ubuntu1
---------------
dee (0.5.10-0ubuntu1) natty; urgency=low
* New upstream release. introspected languages (LP: #709240)
- Sync problems when restarting Unity place daemons (LP: #721289)
- libunity support gobject-
-- Didier Roche <email address hidden> Thu, 24 Feb 2011 20:07:48 +0100