Closed lestephane closed 3 months ago
It looks like a symlink is causing the apparmor issue (similar issue reported here: https://github.com/pop-os/pop/issues/1850).
~ $ ls -la /etc/os-release
lrwxrwxrwx 1 root root 17 Oct 21 20:16 /etc/os-release -> pop-os/os-release
But this does not explain why launching the more specific /snap/signal-desktop/463/opt/Signal/signal-desktop
works. Should they not both fail?
I see, the /snap/bin/signal-desktop
is a symlink to a shared /usr/bin/snap
wrapper, which explains why the checksums differed. The wrapper must be trying to detect the os-release to decide how to launch the 'real' signal-desktop executable.
$ ls -la /snap/bin/signal-desktop
lrwxrwxrwx 1 root root 13 Mar 15 18:43 /snap/bin/signal-desktop -> /usr/bin/snap
The reason that launching via /snap/signal-desktop/463/opt/Signal/signal-desktop
behaves differently is that by calling that file you are completely bypassing the snap system so signal is loading libraries off your host. This negates all confinement and may lead to random errors that we, as the packagers, cannot fix.
As to the issue with the symlink this is unfortunately something we cannot fix either. It might be possible for snapd or apparmor to be altered to allow the symlink but this isn't supported by apparmor as an intentional decision, so we may not be able to get a fix for this for some time.
This is the upstream issue in pop-os: https://github.com/pop-os/pop/issues/2146 I'll set up a hard link on my machine for now.
making /etc/os-release
a hardlink does not make the original problem go away (ie the undefined symbol
is still there). Since there is now no apparmor violation, the problem must lie elsewhere...
~ $ signal-desktop
cat: error while loading shared libraries: cat: unsupported version 0 of Verneed record
/snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libtasn1.so.6: undefined symbol: , version GLIBC_2.2.5
Failed to load module: /home/lestephane/snap/signal-desktop/common/.cache/gio-modules/libgiognutls.so
g_module_open() failed for /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libuuid.so.1: unsupported version 0 of Verdef record
/snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libuuid.so.1: unsupported version 0 of Verdef record
/snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: error while loading shared libraries: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libuuid.so.1: unsupported version 0 of Verneed record
ERROR: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127
/snap/signal-desktop/463/opt/Signal/signal-desktop: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libuuid.so.1: unsupported version 0 of Verdef record
/snap/signal-desktop/463/opt/Signal/signal-desktop: error while loading shared libraries: /snap/signal-desktop/463/gnome-platform/usr/lib/x86_64-linux-gnu/libuuid.so.1: unsupported version 0 of Verneed record
unsupported version 0 of Verneed record
This error comes from your kernel containing a bug in the squashfs code, and will be the cause of your issue. I believe it was fixed in Linux 6.0.7 but you're still on 6.0.6.
This is very outdated by now, and I think unrelated to the snap packaging - at least where the application is being launched outside of the confinement. Closing for now, but can reopen if needed.
What happened?
I typed
signal-desktop <ENTER>
in the command line prompt, and got anundefined symbol
errorWhat should have happened?
The app should start normally, and indeed it does when I use the path to the executable mentioned in the error message:
Those two executables are definitely not the same as evidenced by running
sha256sum
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
Teminal output of app
No response