Snaps to invoke external processes

Spencer Parkin spencertparkin at
Tue Nov 22 04:43:21 UTC 2016

Well, actually, not unless the customer also installs snapd-xdg-open.  Why
is it an add-on?  Why not just make it part of snapd?

On Mon, Nov 21, 2016 at 9:09 PM, Spencer Parkin <spencertparkin at>

> It's a miracle!  It works!  Now, for the first time ever, my users (all 0
> of them) can reach the help page by clicking on "help" from within the
> app!  Thanks, Didier.  You're a real pal.
> On Mon, Nov 21, 2016 at 12:08 AM, Didier Roche <didrocks at>
> wrote:
>> Le 21/11/2016 à 04:26, Spencer a écrit :
>> > It's been a few weeks now, but last I heard, the snapcraft team was or
>> did a sprint to address current limitations snaps have regarding the
>> invocation of external processes.  Specifically, it would be nice to launch
>> the user's default browser with a URL, or let a snap invoke another
>> instance of itself.  What's the status on this?
>> >
>> Hey Spencer,
>> Default browser should works for some months already if your application
>> (or toolkit, like Qt does) invoke the xdg-open to open the url. This is
>> then transmitted via dbus to an external process on your classic system
>> which then issues the real xdg-open command.
>> For the others, there are been indeed multiple discussions on this at
>> multiple places (here, on the bug report…), but no action or firm
>> decision. I'm CCing Gustavo as he was the one against a more generic
>> intermediate solutions.
>> Cheers,
>> Didier
>> --
>> Snapcraft mailing list
>> Snapcraft at
>> Modify settings or unsubscribe at:
>> an/listinfo/snapcraft
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Snapcraft mailing list