Hi all,
I just found that there was nothing wrong with my project. After some
troubleshooting, I finally found the root cause of the problem. The
ubuntu-app-platform
is based on Qt 5.6.1 version. However, the Qt version on my desktop is Qt
5.5.1
As suggested by the blog
I think the port of snapd to a distro should handle ensuring that
"browse" works. How it does that is up to the port, as long as the
behaviour is clear it is easy to implement. We just to be clear what
expectaction a snap publisher can have. I would say "snap-browse" is the
command to use, and on
Hello,
Thanks Timo for the good example.
While I tried to write two snaps(server to share paths to client) that use
content interface to share files, I found "write" slot doesn't work.
The code snippet from server side snapcraft.yaml
slots:
test-share:
content: test-content-server
Unless dependencies such as snapd-xdg-open can be named in the yaml, I could
show a dialog telling the user that they may need to install it. Naming
dependencies of snaps, however, as I understand it, defeats the purpose of
snaps as they're supposed to bake all the dependencies into
Just an update here... I've had this happen to 3-4 different people in the
last couple of weeks.
Version info:
snap 2.16ubuntu3
snapd 2.16ubuntu3
series 16
ubuntu 16.04
On this latest case all packages are up to date. So no solution there.
Ideas?
On Sun, Oct 23, 2016 at 3:30 PM Sergio Schvezov
Hello, I am having troubles to launch my snap due to a missing connection
to ubuntu-app-platform:platform. No matter if I run "snap connect" always I
get the same message telling that I need to connect the app with
ubuntu-app-platform:platform.
I am running this in yakkety. Any idea about this
Le 22/11/2016 à 15:38, Gustavo Niemeyer a écrit :
> The problem is that snapd works in environments where the dependencies
> to make the browser-launcher work aren't available.
>
> The right fix is probably to make it a dependency of one of the debs
> that are always installed on a normal desktop
The problem is that snapd works in environments where the dependencies to
make the browser-launcher work aren't available.
The right fix is probably to make it a dependency of one of the debs that
are always installed on a normal desktop system, whether snapd is there or
not. It's a very minimal
On Tue, 2016-11-22 at 07:46 +0100, Didier Roche wrote:
> Le 22/11/2016 à 05:43, Spencer Parkin a écrit :
> > 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?
>
> I gues the idea was to keep it as a separate
Guru, please help me.
App in snap uses GTK/Perl/VTE (Terminal emulator widget - libvte9)
In snapcraft.yaml
---
integration:
plugin: nil
stage-packages:
- libvte9
- libvte-common
- libvte-2.91-common
---
VTE try open system file /etc/termcap and
1) if file not exist
OR
2) if
10 matches
Mail list logo
