so i have been trying to run discord on my debian system and i keep getting this output
aesther@penguin:~$ snap run discord
Discord 0.0.17
No protocol specified
The futex facility returned an unexpected error code.Failed to generate minidump.Aborted (core dumped)
aesther@penguin:~$
my system
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
snap version
aesther@penguin:~$ snap version
snap 2.54.3
snapd 2.54.3
series 16
debian 11
kernel 5.10.92-14532-g179c52887ab5
also, i was trying to look at logs and my whole system froze up, and i had to delete snap completely, can you also help me correctly set it up so i get no invalid errors please
i am confused on why it is doing this
please help i need discord so i can do my chats
i have very little experience with snap and i just installed it today
bump-update- i have been reading logs and i havent found anything to fix it yet, please help
Google search shows it’s some error from glibc/electron. Can run tun SNAPD_DEBUG=1 snap run discord
?
i will run this in like an hour, i half to get some work done, but i will put it here
yeah ive done some research too, and there are very limited resources about this happening, and ive only seen 1 solution people say that it works
it something like
xhost +
idk if thats safe, but is there a safer alt to this, (this cmd is the only thing that allows my snapd apps to run right now, and i feel like there is an easier way to do it)
here are the logs
aesther@penguin:~$ SNAPD_DEBUG=1 snap run discord
2022/03/14 15:59:21.431902 tool_linux.go:204: DEBUG: restarting into “/snap/core/current/usr/bin/snap”
2022/03/14 15:59:21.499423 cmd_run.go:1026: DEBUG: executing snap-confine from /snap/core/12725/usr/lib/snapd/snap-confine
2022/03/14 15:59:21.508796 cmd_run.go:433: DEBUG: SELinux not enabled
2022/03/14 15:59:21.511008 tracking.go:46: DEBUG: creating transient scope snap.discord.discord
2022/03/14 15:59:21.512520 tracking.go:186: DEBUG: using session bus
2022/03/14 15:59:21.517817 tracking.go:319: DEBUG: create transient scope job: /org/freedesktop/systemd1/job/55
2022/03/14 15:59:21.521508 tracking.go:146: DEBUG: waited 8.823502ms for tracking
DEBUG: umask reset, old umask was 022
DEBUG: security tag: snap.discord.discord
DEBUG: executable: /usr/lib/snapd/snap-exec
DEBUG: confinement: non-classic
DEBUG: base snap: core18
DEBUG: ruid: 1000, euid: 0, suid: 0
DEBUG: rgid: 1000, egid: 1000, sgid: 1000
DEBUG: apparmor extensions to the system are not available
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope (global), uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: ensuring that snap mount directory is shared
DEBUG: unsharing snap namespace directory
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: releasing lock 5
DEBUG: opened snap-update-ns executable as file descriptor 5
DEBUG: opened snap-discard-ns executable as file descriptor 6
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: opening lock file: /run/snapd/lock/discord.lock
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: acquiring exclusive lock (scope discord, uid 0)
DEBUG: sanity timeout reset and disabled
DEBUG: initializing mount namespace: discord
DEBUG: setting up device cgroup
DEBUG: libudev has current tags support
DEBUG: no devices tagged with snap_discord_discord, skipping device cgroup setup
DEBUG: forked support process 994
DEBUG: helper process waiting for command
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: block device of snap core18, revision 2284 is 0:63
DEBUG: block device of snap core18, revision 2284 is 0:63
DEBUG: sanity timeout initialized and set for 30 seconds
DEBUG: joining preserved mount namespace for inspection
DEBUG: block device of the root filesystem is 0:63
DEBUG: sanity timeout reset and disabled
DEBUG: preserved mount is not stale, reusing
DEBUG: joined preserved mount namespace discord
DEBUG: joining preserved per-user mount namespace
DEBUG: unsharing the mount namespace (per-user)
DEBUG: sc_setup_user_mounts: discord
DEBUG: performing operation: (disabled) use debug build to see details
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: calling snapd tool snap-update-ns
DEBUG: waiting for snapd tool snap-update-ns to terminate
DEBUG: snap-update-ns finished successfully
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: NOT preserving per-user mount namespace
DEBUG: set_effective_identity uid:0 (change: no), gid:0 (change: yes)
DEBUG: set_effective_identity uid:0 (change: no), gid:1000 (change: yes)
DEBUG: moved process 977 to cgroup hierarchy /sys/fs/cgroup/freezer/snap.discord
DEBUG: releasing lock 7
DEBUG: sending command 0 to helper process (pid: 994)
DEBUG: waiting for response from helper
DEBUG: sanity timeout reset and disabled
DEBUG: helper process received command 0
DEBUG: helper process exiting
DEBUG: waiting for the helper process to exit
DEBUG: helper process exited normally
DEBUG: resetting PATH to values in sync with core snap
DEBUG: set_effective_identity uid:1000 (change: yes), gid:1000 (change: yes)
DEBUG: creating user data directory: /home/aesther/snap/discord/132
DEBUG: ruid: 1000, euid: 1000, suid: 0
DEBUG: setting capabilities bounding set
DEBUG: regaining SYS_ADMIN
DEBUG: loading bpf program for security tag snap.discord.discord
DEBUG: read 6336 bytes from /var/lib/snapd/seccomp/bpf//snap.discord.discord.bin
DEBUG: read 152 bytes from /var/lib/snapd/seccomp/bpf/global.bin
DEBUG: clearing SYS_ADMIN
DEBUG: execv(/usr/lib/snapd/snap-exec, /usr/lib/snapd/snap-exec…)
DEBUG: argv[1] = discord
DEBUG: umask restored to 022
DEBUG: working directory restored to /home/aesther
Discord 0.0.17
No protocol specified
The futex facility returned an unexpected error code.Failed to generate minidump.Aborted (core dumped)
The logs indicate that the sandbox was set up and then discord start. Were there any apparmor denials? Can you run sudo dmesg |grep DENIED
and paste the output?
i tried and i got no output from it
Well then there’s not much we can do. Try contacting the publisher directly and report the issue there. snap info discord
lists https://github.com/snapcrafters/discord/issues as the contact URL.
ok i reported but i found something that allows me to launch my apps
if i do
xhost +
it launches the app for me, is there a safer alt to this cause idk, it doesnt feel totaly secure
1 Like
Thank you sooooo much for the comment,