Yes, but no X (just a blinking cursor top left) and CTRL+ALT+F1 doesn't work. Now logged in through SSH.
osmo@Daisy:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: libc6-dev : Depends: libc6 (= 2.13-38) but 2.13-37 is installed Depends: libc-dev-bin (= 2.13-38) libc6-dev:i386 : Depends: libc6:i386 (= 2.13-38) but 2.13-37 is installed Depends: libc-dev-bin:i386 (= 2.13-38) libc6-dev-i386 : Depends: libc6-dev (= 2.13-37) but 2.13-38 is installed E: Unmet dependencies. Try using -f.
Definitely something wrong with that "libc6"
Last edited by OsmoHyttinen (2013-03-09 21:56:04)
Update works, upgrade and dist-upgrade stop at that unmet dependencies problem.
yeah I am at the same place, but without login in ssh - there is also another user on #debian that has the exact same problem.
If you do the apt-get upgrade -f you will probably get the problem with zlib. You can try that if you want
Are you running multiarch too ? (yes you are from the code you pasted)
Last edited by damaru (2013-03-09 22:06:33)
osmo@Daisy:~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: libc-bin libc-dev-bin libc6 libc6:i386 libc6-amd64:i386 libc6-dev-i386 libc6-i386 libc6-i686:i386 Suggested packages: glibc-doc glibc-doc:i386 locales:i386 Recommended packages: gcc-multilib The following packages will be upgraded: libc-bin libc-dev-bin libc6 libc6:i386 libc6-amd64:i386 libc6-dev-i386 libc6-i386 libc6-i686:i386 8 upgraded, 0 newly installed, 0 to remove and 479 not upgraded. 5 not fully installed or removed. Need to get 0 B/21.0 MB of archives. After this operation, 3,072 B of additional disk space will be used. Do you want to continue [Y/n]?
And as it didn't say it'd remove anything I tried.
The last screen I could copy:
Processing triggers for man-db ... Setting up libc-bin (2.13-38) ... (Reading database ... 249446 files and directories currently installed.) Preparing to replace libc6:amd64 2.13-37 (using .../libc6_2.13-38_amd64.deb) ... De-configuring libc6:i386 ... Unpacking replacement libc6:amd64 ... dpkg-deb: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory dpkg: error processing /var/cache/apt/archives/libc6_2.13-38_amd64.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 127 dpkg-deb: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory dpkg: error processing /var/cache/apt/archives/libc6_2.13-38_i386.deb (--unpack): subprocess dpkg-deb --control returned error exit status 127 Errors were encountered while processing: /var/cache/apt/archives/libc6_2.13-38_amd64.deb /var/cache/apt/archives/libc6_2.13-38_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) osmo@Daisy:~$
At the starting point again
osmo@Daisy:~$ sudo ldconfig sudo: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory osmo@Daisy:~$ ls ls: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory osmo@Daisy:~$ /sbin/ldconfig /sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied osmo@Daisy:~$ sudo /sbin/ldconfig sudo: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory
Next time I will sudo su before upgrading as sudo won't work if the problem reappears.
This might have typos but posting it anyway:
Loading, please wait... /sbin/init: error while loading shared libraries: libsepol.so.1: cannot open shared object file: No such file or directory [ 2.360383] Kernel panic - not syncing: Attempted to kill init! [ 2.360463] Pid: 1, comm: init Not tainted 3.2.0-4-amd64 #1 Debian 3.2.35-2 [ 2.360537] Call Trace: [ 2.360610] [<ffffffff813467bc>] ? panic+0x95/0x1a5 [ 2.360689] [<ffffffff81049b14>] ? do_exit+0x95/0x713 [ 2.360765] [<ffffffff8104a412>] ? do_group_exit+0x74/0x9e [ 2.360837] [<ffffffff8104a44c>] ? sys_exit_group+0x10/0x10 [ 2.360911] [<ffffffff81352012>] ? system_call_fastpath+0x16/0x1b
yeah that is what happen when you reboot without the ldconfig.
If you cannot login anymore you need a rescue disk, then mount your drive, chroot into it and ldconfig before rebooting.
here is what is happening :
# upgrading from a pre-multiarch libc to a multiarch libc; we have
# to blow away /etc/ld.so.cache, otherwise the old unpacked libc
# is still first in the cache and segfaults when combined with
# our newly-unpacked ld.so. Do this last to avoid slowing down the
# rest of the upgrade. Version number bumped to 2.13-38 to also
# cover cache format upgrades for ARM.