onsdagen den 17 juni 2015 21.07.40 skrev js: > I did an apt-get upgrade of my system which brought in libnettle6 but > did not remove the existing libnettle4. After this upgrade, many > applications including curl, opera-developer, claws-mail and amarok gave > segfaults in libnettle.so.4.7, when they had been working very well > before the upgrade (set portion of /var/log/messages below).
Installing a new SOversion of a library normally doesn't cause the old SOversion to be deinstalled. libnettle4 merely existing on the system cannot cause the segfaults; if it is loaded it's because something is linked with it. > After removing libnettle4, all these applications work perfectly again. Did removing libnettle4 not cause any other package to be removed or upgraded? > I saw that other libnettle bugs that reported this behavior on specific > applications, like bugs 788349 and 788572, recommend updating the > affected packages. But the applications above that segfaulted in my > system were all at their latest version for debian testing, so this is > not a practical solution. Note that it's not enough that the applications that crash are the latest version; the problem likely is that one of the intermediate libraries are not upgraded and still use libnettle4. > One solution that would have avoided this issue is if installing libnettle6 > caused an existing version of libnettle4 to be removed, for example by > making libnettle6 replace/conflict with libnettle4. Removing libnettle4 > worked with all the applications that segfaulted in my system. As noted, that shouldn't technically be necessary, but we may have to do it anyway to help the users. Now libgnutls-deb0-28, which is the most common culprit, has been made to conflict with libnettle4 and libhogweed2. -- Magnus Holmgren holmg...@debian.org Debian Developer
signature.asc
Description: This is a digitally signed message part.
