[linux] Delay claiming dbus name
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Moovida |
Invalid
|
Medium
|
Unassigned | ||
moovida (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Right now, elisa claims the well-known dbus name 'com.fluendo.Elisa' early on, in each plugin that uses dbus. It should only claim the name when the database is initialized.
This bug can be seen if you try to activate elisa via dbus (so elisa isn't running, you send dbus command, dbus starts elisa, elisa claims bus, dbus sends request to elisa). If elisa claims the bus too early, it may not be ready for the command and it will fail.
I'm attaching a patch that fixes this (I believe). I *think* that interface_
To test, run the following command without elisa running:
dbus-send --print-reply --dest=
This should print a list of all your photo albums.
Changed in elisa: | |
milestone: | none → 0.5.x |
Changed in elisa: | |
importance: | Undecided → High |
Changed in elisa: | |
importance: | High → Medium |
milestone: | 0.5.x → none |
tags: | added: oem-services |
tags: | added: patch-forwarded-upstream |
I can't reproduce here, all I get is:
Error org.freedesktop .DBus.Error. NoMemory: Launcher could not run (out of memory)
Anyway it would make sense to claim the bus name only once and store, maybe as an attribute of the application.
I can see one issue in claiming the bus name late: detecting whether an instance of Moovida is already running relies on dbus.