Bug#783637: Installation fails because starting colord fails on missing libudev.so.0

[Michael Lager]

The reason the upgrade failed when starting X was that colord couldn't start because it was missing libudev.so.0 as reported: "/usr/lib/colord/colord: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory" colord also depends on libusb-1.0.so.0 in /usr/local/lib, see below: $ ldd /usr/lib/colord/colord|grep -E libudev\|libusb     libusb-1.0.so.0 => /usr/local/lib/libusb-1.0.so.0 (0x00007f08bcd66000)     libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f08bb256000) So why does colord complain about missing libudev.so.0 when ldd says it depends on libudev.so.1? So I think colord is looking for libusb-1.0.0.so.0 in the wrong place, using /usr/local/lib although you say nothing in debian uses /lib/local. libusb-1.0.so.0 is provided by package libusb-1.0-0: "File list of package libusb-1.0-0 in jessie of architecture amd64  /lib/x86_64-linux-gnu/libusb-1.0.so.0  /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0  /usr/share/doc/libusb-1.0-0/README  /usr/share/doc/libusb-1.0-0/changelog.Debian.gz  /usr/share/doc/libusb-1.0-0/changelog.gz  /usr/share/doc/libusb-1.0-0/copyright" A symlink in /usr/local/lib to /usr/x86_64-linux-gnu/libusb-1.0.0.so.0 should be a valid fix, the files being the same:  $ sudo ln -s /lib/x86_64-linux-gnu/libusb-1.0.so.0 /usr/local/lib/libusb-1.0.so.0 X starts correctly after doing this. (Others have had similar issues elsewhere: eg https://github.com/LightTable/LightTable/issues/161, and been rightly warned off linking different versions of libraries.) Probably this needs to be moved to a colord bug? Michael   On Tue, 05 May 2015 23:29:06 +0300 Michael Tokarev <m...@tls.msk.ru> wrote: > 05.05.2015 21:13, Michael Lager wrote: > > I can't remove libusb-1.0-0 package which provides libusb-1.0.so.0 because 93 packages depend on it including gdm3, gnome, cups and many others and that would render jessie practically useless. The version required by jessie is given as 2:1.0.19-1:amd64 and this is what is installed. So the symlink works. > > I told you the solution is to remove the library you installed > manually in /usr/local/lib which is named libusb-1.0.so.0. > No package in debian provides any library in /usr/local, all > libs are installed to /usr/lib or /lib. The library you have > in /usr/local/lib is not from debian, it is something you > installed most likely from source. You shouldn't remove > the debian-supplied library but the one you installed outside > of debian. > > [] > > Anyway, the whole point was to say that the upgrade failed when trying to start the display manager and to suggest a cure. I don't think it was anything I installed that caused this. Have you a better one? > > The whole point is that what you did is WRONG. So if you > don't listen to advise several people offered to you, at > least others hopefully wont repeat your mistake after finding > your "fix" in this bugreport. > > Thanks, > > /mjt > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org