Re: The situation with xdg-open

2017-02-20 Thread Oliver Grawert
hi, Am Montag, den 20.02.2017, 16:16 +0300 schrieb Vasilisc: > 20.02.2017 15:32, Gustavo Niemeyer пишет: > > > > Hi there, > > > > The problem there is that the confined xdg-open currently depends > > on > > snapd-xdg-open, which is a server listening on dbus for the calls. > > > > We're changin

Re: The situation with xdg-open

2017-02-20 Thread Vasilisc
20.02.2017 15:32, Gustavo Niemeyer пишет: Hi there, The problem there is that the confined xdg-open currently depends on snapd-xdg-open, which is a server listening on dbus for the calls. We're changing that mechanism in the short term so snapd will implement that logic internally, precisely to

Re: The situation with xdg-open

2017-02-20 Thread Gustavo Niemeyer
Hi there, The problem there is that the confined xdg-open currently depends on snapd-xdg-open, which is a server listening on dbus for the calls. We're changing that mechanism in the short term so snapd will implement that logic internally, precisely to remove that extra moving piece and "flakine

The situation with xdg-open

2017-02-20 Thread Vasilisc
Snapcraft.yaml - name: test2 version: "1" summary: TEst description: | TEST confinement: strict architectures: [amd64] apps: test2: command: xdg-open "http://google.com"; plugs: [network, network-bind, x11, home, unity7, gsettings] parts: integration: plugi