Skype snap on Bionic: libGL error on Intel GPU

[Sam Van den Eynde]

I am testing Bionic (upgraded from artful, regular ubuntu) and the Skype snap will no longer start. The relevant error:

$ cat ./snap/skype/common/.config/skypeforlinux/logs/skype-startup.log
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
/snap/skype/19/usr/share/skypeforlinux/skypeforlinux --executed-from=/home/sam --pid=6944: relocation error: /lib/x86_64-linux-gnu/libnss_dns.so.2: symbol __resolv_context_get, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

This is strange, as I assumed snaps fix exactly this, i.e. the core snap should provided the layer to make everything work.

I also have Telegram installed as a snap, that works fine.

System info attached to the bug, my GPU:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller
 Flags: bus master, fast devsel, latency 0, IRQ 26
 Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
 Memory at c0000000 (64-bit, prefetchable) [size=256M]
 I/O ports at 2000 [size=64]
 [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

And I'm running X.

[Ian Turner (vectro)]

I'm not sure this is limited to Bionic. Skype snap stopped working for me and a few others a few days ago even on Artful. Doesn't seem to be related to a libc6 upgrade as the last change was in January.

See here for more discussion: https://forum.snapcraft.io/t/cant-launch-skype-snap-relocation-error/4536

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I believe this is a duplicate of bug 1756793

[Sam Van den Eynde (samvde)]

Yep, seems related to the link in #2. I hadn't noticed yet, but indeed it also fails on my 17.10 desktop machine.

[Sam Van den Eynde (samvde)]

Working again after new version as described in forumpost mentioned in comment #2