Package: src:libgl1-mesa-dri
Followup-For: Bug #743035
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
FWIW I had the same chrome issue with the following error:
libGL error: MESA-LOADER: could not create udev device for fd 13
(Albeit for radeon)
After tracing this a bit, I resolved it by removing the old libudev0 which was
still installed.
The bug is that chrome is linked against both libudev0 and libudev1 and was
resolving both
in an interfering manner.
Starting chrome with --no-sandbox I got this additional hint:
not in sys :/sys/dev/char/226:0
Which is from this udev check and doesn't make any sense at all as
"/sys/dev/char/226:0"
is part of the /sys tree and also present in there.
/* path starts in sys */
len = strlen(udev_get_sys_path(udev));
if (strncmp(syspath, udev_get_sys_path(udev), len) != 0) {
info(udev, "not in sys :%s\n", syspath);
return NULL;
I then found that chrome links against both udev versions:
$ ldd /opt/google/chrome/chrome | grep udev
libudev.so.0 => /lib/x86_64-linux-gnu/libudev.so.0 (0x00007f4698510000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f468fe78000)
And trying purging libudev0 using "aptitude purge libudev0" which didn't
complain
about any remaining users of this lib.
Now 3D acceleration is working fine again.
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12.3 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFTQHiX5q/seprH4LwRAozeAJ98wCtZH6uTS2VJMhMw/R8qpFeFngCcDdso
RIz87szg3tFf3CTLrpmjRpY=
=mXsj
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
