-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: undefined symbol
when launching using /snap/bin/signal-desktop
, no error when launching using /snap/signal-desktop/463/opt/Signal/signal-desktop
#113
Comments
It looks like a symlink is causing the apparmor issue (similar issue reported here: pop-os/pop#1850).
But this does not explain why launching the more specific |
I see, the
|
The reason that launching via 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: pop-os/pop#2146 |
making
|
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
The text was updated successfully, but these errors were encountered: