dapper to hardy update ldconfig wrong

Bug #224087 reported by Zenigata on 2008-04-29
Affects Status Importance Assigned to Milestone
gnome-themes (Ubuntu)

Bug Description

While upgrading to hardy frome dapper, I got an update failure message at the veruy en, before cleaning.

During the upgrade, it was complaning about symbol lookup errors for libgdk_pixbuf-2.2.0.so.0, and after fixing this I got some other symbol lookup errors with other libs...

Many graphics apps were broken (including gdm, kdm).

I correct this by editin /etc/ld.so.conf.d/libc.conf to use as default folder /usr/lib instead of /usr/local/lib but I'm not sure this the good way.


ringostar (slehembre) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in update-manager

Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Please attach the files in /var/log/dist-upgrade to this bugreport.
 Thanks Michael

Changed in update-manager:
status: New → Incomplete
Zenigata (drebon) wrote :
Zenigata (drebon) wrote :
Zenigata (drebon) wrote :
Zenigata (drebon) wrote :
Zenigata (drebon) wrote :

Here are the files, hope it may help.

By the way, I think that the way I fixed the problem is not the good one, it seems to me that because of the failure of the upgrade just before the clean-up, there were still old versions of the libs in /usr/local/lib, and thus ldconfig was pointing to those old versions instead of the correct ones.

So the change I made is sort of a work around, but removing the libs in /usr/local/lib should do the same without preventing people to install new versions of some lib in that folder...


Markus Korn (thekorn) wrote :

Set status to 'Triaged' as requested information has been added.

Changed in update-manager:
status: Incomplete → Triaged
Jean-Baptiste Lallement (jibel) wrote :

The cause of the failure is
Setting up gnome-themes (2.22.0-0ubuntu1) ...

gtk-update-icon-cache: symbol lookup error: /usr/lib/libgdk_pixbuf-2.0.so.0: undefined symbol: g_once_init_enter_impl

dpkg: error processing gnome-themes (--configure):

 subprocess post-installation script returned error exit status 127


affecting to gnome-themes

You've reported the bug a while ago, is it still an issue ?

Changed in update-manager:
status: Triaged → New
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in gnome-themes:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers