On Wed, Feb 26, 2014 at 04:27:26PM +0200, David Baron wrote: > On Wednesday, 26 February, 2014 15:20:25 Aurelien Jarno wrote: > > On Wed, Feb 26, 2014 at 04:12:04PM +0200, David Baron wrote: > > > On Wednesday, 26 February, 2014 14:59:44 Aurelien Jarno wrote: > > > > On Wed, Feb 26, 2014 at 03:00:23PM +0200, David Baron wrote: > > > > > Package: libc6 > > > > > Version: 2.18-3 > > > > > Severity: normal > > > > > > > > > > --- Please enter the report below this line. --- > > > > > Get error on upgrade, whether or not one chooses to stop services and > > > > > proceed. In synaptic, says need to stop kdm. Did that, still got the > > > > > error > > > > > > > > > > Thankfully, 2.18-3 where it did get installed is OK and not breaking > > > > > because of what remains 2.17. > > > > > > > > Please describe the error you got (like copy and paste of the error > > > > message), without that it won't be possible to fix it. > > > > > > Preparing to unpack .../libc6_2.18-3_amd64.deb ... > > > Checking for services that may need to be restarted... > > > Checking init scripts... > > > dpkg: error processing archive > > > /var/cache/apt/archives/libc6_2.18-3_amd64.deb> > > > (--unpack): > > > subprocess new pre-installation script returned error exit status 1 > > > > > > Errors were encountered while processing: > > > /var/cache/apt/archives/libc6_2.18-3_amd64.deb > > > > > > [ Rootkit Hunter version 1.4.0 ] > > > > > > File updated: searched for 170 files, > > > found 146 > > > > > > > > > > E: > > > Sub-process /usr/bin/dpkg returned an error code (1) > > > > Thanks for this information. Is there anything in dmesg related to libc > > in dmesg during this upgrade? > > dmesg | grep libc yield nothing > > > > > Also what is the output of "ls -l /lib64 /lib/x86_64-linux-gnu" ? > ~$ ls -l /lib64 /lib/x86_64-linux-gnu > /lib64: > total 5468 > -rwxr-xr-x 1 root root 136744 Feb 24 05:48 ld-2.18.so > lrwxrwxrwx 1 root root 10 Feb 19 15:29 ld-linux-x86-64.so.2 -> ld-2.17.so
The problem is definitely this symlink which is wrong. Now i don't really understand how it happened that you have already a 2.18 libc in /lib64 and a 2.17 in /lib/x86_64-linux-gnu. Is your system really an i386 system with a 686-pae kernel like reported in the first mail or is it an amd64 one? Also what is the output of "dpkg -l 'libc6*'" and "dpkg -l libc-bin"? -- Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
