dbus activation running wrong binary

[Michael Hall]

Assuming the daemon's snap package is called feedreader-daemon and it
has an app of the same name, you can call it using either of these:

/snap/bin/feedreader-daemon

or

snap run feedreader-daemon

That will work regardless of what revision feedreader and
feedreader-daemon are.

--
Michael Hall
mhall119 at ubuntu.com

On 12/08/2016 01:15 PM, lightonflux wrote:
> Hello snapcrafter,
> 
> i need a bit of help when starting a daemon via dbus service within the
> snap.
> 
> The app i try to package is feedreader. Feedreader is a GUI RSS reader.
> When you start `feedreader` it calls a dbus function. Then dbus starts
> `feedreader-daemon` via it's service file (1). The path defined in the
> snap is the following.
> 
> ---
> [D-BUS Service]
> Name=org.gnome.feedreader
> Exec=/usr/bin/feedreader-daemon
> ---
> 
> The problem is when the user has feedreader already installed (self
> compiled or distro package) the wrong binary gets started. On my system
> dbus starts `/usr/local/bin/feedreader-daemon` which is not mentioned or
> existing in the snap.
> 
> Is there a way to force $SNAP/bin/feedreader-daemon without removing
> dbus activation?
> 
> Greetings and thanks for your help!
> lightonflux  | lof
> 
> PS: The problem here is that the snapped version of feedreader and
> feedreader-daemon may not be the same.
> 
> 
> 1:
> https://github.com/jangernert/FeedReader/blob/4764222c33322e7a6867422615bed8606a6803ff/data/feedreader.service.in
> 
> 2: https://github.com/lightonflux/feedreader-snap/blob/master/snapcraft.yaml
>