Bug#783637: Installation fails because starting colord fails on missing libudev.so.0
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.
libudev0 package is not in jessie, only wheezy. jessie has libudev1.
The other missing library was reported as :
linux-vdso.so.1
objdump: 'linux-vdso.so.1': No such file
dpkg-query: no path found matching pattern *linux-vdso.so.1*
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?
Michael
On Tue, 05 May 2015 15:42:08 +0300 Michael Tokarev <mjt@tls.msk.ru> wrote:
> 05.05.2015 14:55, Michael Lager wrote:
> > This was an upgrade from debian wheezy to jessie and a report (as
requested) on how it went. I just hope this can be put right for others
wishing to upgrade and finding it doesn't work. My work-around was to
create a symbolic link (result as below) for the missing file based on
the pattern for symbolic links elsewhere: jessie now works OK.
> >
> > $ ll|grep udev
> > lrwxrwxrwx 1 root root 21 Apr 16 16:53 libgudev-1.0.so.0 ->
libgudev-1.0.so.0.2.0
> > -rw-r--r-- 1 root root 42920 Apr 16 16:53 libgudev-1.0.so.0.2.0
> > lrwxrwxrwx 1 root root 38 Apr 16 16:53 libudev.so ->
/lib/x86_64-linux-gnu/libudev.so.1.5.0
> > lrwxrwxrwx 1 root root 10 Apr 28 11:10 libudev.so.0 -> libudev.so
> > lrwxrwxrwx 1 root root 12 Apr 29 10:34 libudev.so.1 -> libudev.so.0
>
> So for someone who finds this, don't do this, this is WRONG. The libs are
> named the way they are for a purpose, because symbols in libudev.so.0 are
> not compatible with these in libudev.so.1 and so on. Sometimes such
symlinking
> makes some executable to start so seemingly this smells like a
solution, but
> it is quite possible that this executable will just crash when asked
to do
> something real. Sometimes this doesn't work at all.
>
> This has nothing to do with upgrade from wheezy to jessie really. You
have
> locally installed alternative libusb-1.0.so.0. This library is not
recorded
> in the dpkg database so apt/dpkg doesn't know about it and doesn't know
> that it needs libudev.so.0. This is a library you installed manually.
>
> The solution is to either install libudev0 package to make your
libusb-1.0 to
> work (and maybe record that libudev0 is needed so it wont be removed by a
> chance), or, better yet, just remove your libusb-1.0, because jessie
comes
> with its own, most likely never version, and together with support.
>
> Your situation is rare, because it is uncommon to install 3rd party
libraries
> like this, and even less common to come across such an issue.
>
> But the "solution" you offered is _wrong_.
>
> Thanks,
>
> /mjt
>
> > On Mon, 4 May 2015 18:04:02 +0200 Samuel Thibault
<sthibault@debian.org> wrote:
> >> Michael Lager, le Mon 04 May 2015 12:54:14 +0100, a écrit :
> >> > /usr/local/lib/libusb-1.0.so.0
> >> > NEEDED libudev.so.0
> >> > NEEDED librt.so.1
> >> > NEEDED libpthread.so.0
> >> > NEEDED libc.so.6
> >> > dpkg-query: no path found matching pattern
/usr/local/lib/libusb-1.0.so.0
> >>
> >> We can not support the dependencies of locally-installed software.
> >> Either remove that software, or install the required dependencies
(here,
> >> fetch the libudev0 package from wheezy)
> >>
> >> Samuel
> >>
> >>
> >
> >
>
>
>
Reply to: