Issue with discord snap in Arch

[Syntist]

Don’t know why, but it isn’t working on Arch Linux.

[syntist@archlinux ~]$ snap run discord

Gtk-Message: Failed to load module "canberra-gtk-module"
Discord 0.0.2
*** stack smashing detected ***: /var/lib/snapd/snap/discord/19/usr/share/discord/Discord --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=7,23,71 --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=9DBF76D78A8096E89B01C025E91C5144 --v8-natives-pas terminated
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Install path: /home/syntist/snap/discord/19/.config/discord/0.0.2/modules

And than no display and it just stuck there, Help please!! Thanks.

[ogra]

are all interfaces connected ? (check with “snap interfaces”)

[Syntist]

The output of snap interfaces:

[syntist@archlinux ~]$ snap interfaces
Slot                            Plug
:account-control                -
:alsa                           -
:autopilot-introspection        -
:avahi-observe                  -
:bluetooth-control              -
:browser-support                discord
:camera                         -
:classic-support                -
:core-support                   core:core-support-plug
:cups-control                   -
:dcdbas-control                 -
:docker-support                 -
:firewall-control               -
:framebuffer                    -
:fuse-support                   -
:gsettings                      discord
:hardware-observe               -
:hardware-random-control        -
:hardware-random-observe        -
:home                           discord
:io-ports-control               -
:joystick                       -
:kernel-module-control          -
:kubernetes-support             -
:libvirt                        -
:locale-control                 -
:log-observe                    -
:lxd-support                    -
:modem-manager                  -
:mount-observe                  -
:netlink-audit                  -
:netlink-connector              -
:network                        discord
:network-bind                   -
:network-control                -
:network-manager                -
:network-observe                -
:network-setup-control          -
:network-setup-observe          -
:ofono                          -
:opengl                         discord
:openvswitch                    -
:openvswitch-support            -
:optical-drive                  -
:physical-memory-control        -
:physical-memory-observe        -
:ppp                            -
:process-control                -
:pulseaudio                     discord
:raw-usb                        -
:removable-media                -
:screen-inhibit-control         discord
:shutdown                       -
:snapd-control                  -
:system-observe                 -
:system-trace                   -
:time-control                   -
:timeserver-control             -
:timezone-control               -
:tpm                            -
:uhid                           -
:unity7                         discord
:upower-observe                 -
:x11                            discord
gnome-3-24:gnome-3-24-platform  -
-                               discord:bluez
-                               discord:mount-observe

[ogra]

looks like all essential ones are connected … well, that was worth a shot …

for further debugging i guess “snap version” would be helpful … @zyga and idea about arch and graphical apps ?

EDIT: you dont happen to run a wayland desktop, do you (if so, try switching to X11 and see if that helps) ?

[Syntist]

I am using X11,

The output of snap version:

[syntist@archlinux ~]$ snap version
snap    unknown
snapd   unknown
series  16
arch    unknown
kernel  4.12.8-2-ARCH

I am getting the same error with chromium snap.

[zyga]

Hey, let me try this on my Arch installation (with a more recent snapd, I cannot get the maintainer to update). I’ll keep you posted.

[Syntist]

Thanks! i will be waiting

[Syntist]

Any way to get it working? did you find the problem?

[zyga]

Not yet, I spent time figuring out weird errors I was experiencing on Arch in the first place. I built a 2.27.3-1 package (I will attach it here) and I can now investigate the problem you were interested in.

[Syntist]

Were you able to regenerate the error?

[zyga]

Not yet, I just finished working on the update to snapd on Arch. You can get the updated package from the github release page https://github.com/snapcore/snapd/releases/download/2.27.3/snapd-2.27.3-1-x86_64.pkg.tar.xz

I will fetch discord next.

[popey]

I tried to install this on my Antergos. There are file conflicts with the existing snap-confine package. Can you provide good steps to do this for testing? I don’t want to bork my system (as the arch wiki suggests forcing this may bork it).

[alan@antergos-amd64 ~]$ sudo pacman -U snapd-2.27.3-1-x86_64.pkg.tar.xz 
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) snapd-2.27.3-1

Total Installed Size:  41.54 MiB
Net Upgrade Size:      14.90 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                          [##############################################################] 100%
(1/1) checking package integrity                                                                        [##############################################################] 100%
(1/1) loading package files                                                                             [##############################################################] 100%
(1/1) checking for file conflicts                                                                       [##############################################################] 100%
error: failed to commit transaction (conflicting files)
snapd: /usr/bin/ubuntu-core-launcher exists in filesystem
snapd: /usr/lib/snapd/snap-confine exists in filesystem
snapd: /usr/lib/snapd/snap-discard-ns exists in filesystem
snapd: /usr/lib/snapd/system-shutdown exists in filesystem
snapd: /usr/lib/udev/rules.d/80-snappy-assign.rules exists in filesystem
snapd: /usr/lib/udev/snappy-app-dev exists in filesystem
snapd: /usr/share/man/man5/snap-confine.5.gz exists in filesystem
snapd: /usr/share/man/man5/snap-discard-ns.5.gz exists in filesystem
Errors occurred, no packages were upgraded.
[alan@antergos-amd64 ~]$ pacman -Qo /usr/bin/ubuntu-core-launcher
/usr/bin/ubuntu-core-launcher is owned by snap-confine 2.26.1-1

[zyga]

Aha, then perhaps the recommended procedure for merging two packages (snap-confine and snapd) into one (snapd) is not really working today.

Can you try with -f which will force overwrite this?

[zyga]

Note, can we keep this thread focused on discord and the other thread on the general update to the arch package please.

[popey]

Ok, with that snapd, discord launches and works as expected…

[zyga]

Same here, it just finished downloading and it starts OK. Apart from me having insanely slow network I don’t see anything wrong anymore.

[Syntist]

Thanks!! I think its because arch linux was using older package.
Got Arch linux still got old snapd package.

But thanks for your hardwork.
I think arch linux should update there package by replacing there’s by yours

Edit: Just a small question, Where does discord download update?

[daniel]

stack smashing again. this sounds similar to Call for Testing: Gnome Twitch and Chromium snap doesn't work with the nvidia proprietary driver

[Syntist]

Though it’s fixed with the new release, but still facing this issue in chromium!!

No HW Acceleration on Chromium.

[zyga]

I think arch linux should update there package by replacing there’s by yours

I’m trying to resolve that issue. The problem is that the TU (trusted user) that maintains the snapd package became non-responsive and I cannot commit to the community repository directly.