dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #19793
[Bug 721289] Re: Sync problems when restarting Unity place daemons
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-place-files in Ubuntu.
Matching subscriptions: dx-packages, dx-packages, dx-packages
https://bugs.launchpad.net/bugs/721289
Title:
Sync problems when restarting Unity place daemons
Status in Dee:
Fix Released
Status in Unity:
Fix Released
Status in Unity Applications Lens:
Fix Released
Status in Unity Files Lens:
Fix Released
Status in “dee” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Status in “unity-place-applications” package in Ubuntu:
Fix Released
Status in “unity-place-files” package in Ubuntu:
Fix Released
Bug description:
When any of the Unity place daemons are restarted you'll see something
like:
-----------
$ src/unity-applications-daemon
(process:2494): unity-applications-daemon-DEBUG: daemon.vala:346: Building initial application menu
(process:2494): unity-applications-daemon-DEBUG: daemon.vala:367: Indexing application menu
(process:2494): libunity-DEBUG: unity-place.vala:772: No browser to export
(process:2494): dee-CRITICAL **: clone_leader: assertion
`self->priv->revision_queue == NULL' failed
(process:2494): dee-CRITICAL **: clone_leader: assertion
`dee_model_get_n_rows (DEE_MODEL (self)) == 0' failed
(process:2494): dee-WARNING **: Transaction from
com.canonical.Unity.ApplicationsPlace.ResultsModel is in the future.
Ignoring transaction.
(process:2494): dee-WARNING **: Transaction from
com.canonical.Unity.ApplicationsPlace.SectionsModel is in the past.
Ignoring transaction.
(process:2494): dee-WARNING **: Transaction from com.canonical.Unity.ApplicationsPlace.GroupsModel is in the past. Ignoring transaction.
---------
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::synchronized" GObject signal from the models.
2.2) Implement a read-only DBus model that doesn't own the swarm name. See bug #675565
To manage notifications about this bug go to:
https://bugs.launchpad.net/dee/+bug/721289/+subscriptions