Thank you for making the snap available in edge. This is listed in
current snap declaration:
```
$ snap known snap-declaration snap-id=L0qubpVaz7pQaQjAbDf5RbOvfnGHTsct #
vivaldi's snap ID
...
allow-auto-connection: true
content:
allow-auto-connection:
-
plug-attributes:
content: $SLOT(content)
slot-snap-id:
- XXzVIXswXKHqlUATPqGCj2w2l7BxosS8
-
plug-attributes:
content: $SLOT(content)
slot-attributes:
content: gtk-3-themes
slot-snap-id:
- jZLfBRzf1cYlYysIjD2bwSzNtngY0qit
-
plug-attributes:
content: $SLOT(content)
slot-attributes:
content: icon-themes
slot-snap-id:
- jZLfBRzf1cYlYysIjD2bwSzNtngY0qit
-
plug-attributes:
content: $SLOT(content)
slot-attributes:
content: sound-themes
slot-snap-id:
- jZLfBRzf1cYlYysIjD2bwSzNtngY0qit
-
plug-attributes:
content: $SLOT(content)
slot-attributes:
content: gnome-42-2204
slot-snap-id:
- lATO8HzwVvrAPrlZRAWpfyrJKlAJrZS3
```
The declaration does not list gnome-46-2404 or mesa-2404 snaps. However,
I had a look at ohmygiraffe which uses the same content provider snaps
and none of them are listed there, yet the connections happen. I suspect
something is wrong with evaluation of declarations during auto connect.
At this point I proceeded to connect things manually. I obviously
connected the slots wrong on first attempt:
$ snap connect vivaldi:gpu-2404 mesa-2404
$ snap connect vivaldi:gpu-2404 gnome-46-2404
$ snap run --shell vivaldi.vivaldi-stable
Content snap command-chain for
/snap/vivaldi/325/gnome-platform/command-chain/desktop-launch not found: ensure
slot is connected
A vital observation, pay attention to connect plugs to correct slots.
After disconnecting, I discarded the mount ns to start afresh, connected
interfaces again I got a shell, which indicates that command chain
worked:
$ snap connect vivaldi:gpu-2404 mesa-2404
$snap connect vivaldi:gnome-46-2404 gnome-46-2404
$ snap run --shell vivaldi.vivaldi-stable
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0
0): cannot write to "/var/lib/snapd/hostfs/usr/local/share/doc" because it
would affect the host in "/var/lib/snapd"
<bunch of errors due to system-docs which I don't have on the host>
[maciek@galeon snapd]$
[maciek@galeon snapd]$ cd $SNAP
[maciek@galeon 325]$ ls
bin chromium-ffmpeg data-dir etc gnome-platform gpu-2404 gpu-2404-2 meta
opt snap usr var
[maciek@galeon 325]$ ls gnome-platform
command-chain data-dir etc gnome-platform lib meta snap usr var
[maciek@galeon 325]$ ls gpu-2404
X11 bin drirc.d libdrm meta snap usr
However, I still cannot run vivaldi:
$ snap run vivaldi.vivaldi-stable
/snap/vivaldi/325/opt/vivaldi/vivaldi: error while loading shared libraries:
libOSSlib.so: cannot open shared object file: No such file or directory
The library is in the snap at
/snap/vivaldi/current/usr/lib/x86_64-linux-
gnu/oss4-libsalsa/libOSSlib.so.
I tried to fix it by tweaking LD_LIBRARY_PATH inside the snap shell but only
got as far as:
[maciek@galeon 325]$ ./bin/vivaldi.launcher
/snap/vivaldi/325/opt/vivaldi/vivaldi: symbol lookup error:
/snap/vivaldi/325/opt/vivaldi/vivaldi: undefined symbol:
snd_device_name_get_hint, version ALSA_0.9
Perhaps a missing dependency?
In any case, I have not observed any issue with mounts. What I did observe
though was:
- missing auto connect - unclear why?
- error listed before but only after connecting plug to the wrong slot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072395
Title:
[snap] Chromium with core24 base won't start: desktop-launch not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2072395/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
