discord
discord copied to clipboard
Published
20 hours ago •
snapcrafters
snapcrafters
[Bug]: Failing to start on Linux 6.0 kernel
What happened?
The app crashes on startup. Tested on current edge and stable branches (noted below in snap info output).
What should have happened?
It should not crash ;)
Output of snap info discord
name: discord
summary: All-in-one voice and text chat for gamers
publisher: Snapcrafters
store-url: https://snapcraft.io/discord
contact: https://github.com/snapcrafters/discord/issues
license: unset
description: |
All-in-one voice and text chat for gamers that's free, secure, and works on both your desktop and
phone.
Snaps are confined, as such Discord may be unable to perform some of the tasks it typically does
when unconfined. This may result in the system log getting spammed with apparmor errors. Granting
access to the system-observe interface when in the snap will enable the features, and thus reduce
the logging.
snap connect discord:system-observe
This snap is maintained by the Snapcrafters community, and is not necessarily endorsed or
officially maintained by the upstream developers.
commands:
- discord
snap-id: qHVefGEBezeuCeSfTND40uoUD6GRw8BO
tracking: latest/stable
refresh-date: today at 01:46 CEST
channels:
latest/stable: 0.0.20 2022-09-23 (143) 85MB -
latest/candidate: ↑
latest/beta: ↑
latest/edge: 0.0.20 2022-10-05 (144) 85MB -
installed: 0.0.20 (143) 85MB -
Output of snap connections discord
Interface Plug Slot Notes
audio-playback discord:audio-playback :audio-playback -
audio-record discord:audio-record :audio-record -
camera discord:camera :camera -
content[gnome-42-2204] discord:gnome-42-2204 gnome-42-2204:gnome-42-2204 -
content[gtk-3-themes] discord:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] discord:icon-themes gtk-common-themes:icon-themes -
content[sound-themes] discord:sound-themes gtk-common-themes:sound-themes -
desktop discord:desktop :desktop -
desktop-legacy discord:desktop-legacy :desktop-legacy -
gsettings discord:gsettings :gsettings -
home discord:home :home -
mount-observe discord:mount-observe - -
network discord:network :network -
network-observe discord:network-observe - -
opengl discord:opengl :opengl -
process-control discord:process-control - -
removable-media discord:removable-media - -
screen-inhibit-control discord:screen-inhibit-control :screen-inhibit-control -
shared-memory discord:shmem :shared-memory -
system-observe discord:system-observe - -
unity7 discord:unity7 :unity7 -
wayland discord:wayland :wayland -
x11 discord:x11 :x11 -
Output of snap version
snap 2.57.4-1
snapd 2.57.4-1
series 16
manjaro -
kernel 6.0.2-2-MANJARO
Relevant log output
[23960.726968] getent[37322]: segfault at 559b6f04d000 ip 0000559b6f04d000 sp 00007ffe366a2538 error 15 in getent[559b6f04d000+3000]
[23960.727002] Code: Unable to access opcode bytes at RIP 0x559b6f04cfd6.
Teminal output of app
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: date: no version information available (required by date)
date: symbol lookup error: date: undefined symbol:
xdg-user-dirs-update: error while loading shared libraries: xdg-user-dirs-update: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
/snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libffi.so.7: version `LIBFFI_BASE_7.0' not found (required by /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0)
/snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: error while loading shared libraries: /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0: unsupported version 0 of Verneed record
/snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0: unsupported version 0 of Verneed record
rm: error while loading shared libraries: rm: unsupported version 0 of Verneed record
/snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: error while loading shared libraries: libthai.so.0: object file has no dynamic section
ERROR: /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 exited abnormally with status 127
ERROR: compile_giomodules /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu exited abnormally with status 127
ERROR: /snap/discord/143/gnome-platform/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders exited abnormally with status 127
/snap/discord/143/bin/disable-updater.sh: line 4: /root/snap/discord/143/.config/discord/settings.json: No such file or directory
cat: /root/snap/discord/143/.config/discord/settings.json: No such file or directory
/snap/discord/143/bin/disable-updater.sh: line 7: /root/snap/discord/143/.config/discord/settings.json: No such file or directory
/snap/discord/143/usr/share/discord/Discord: error while loading shared libraries: libthai.so.0: object file has no dynamic section
Seems like this is a general kernel issue with snap, also affecting other applications. So there might not be anything that can be done currently until this is resolved in the new kernels.
See: https://lore.kernel.org/lkml/[email protected]/
