screenshot of error message

This happened after last night I was stubborn and sleepy enough to not read that it's best to install the missing dependencies from the var/logs and was lazy enough to just Google and try the first (quick) answer that came up.

I use Debian Gnome Jessie.

The order of was the following:

sudo apt-get remove python

Gnome not booting, terminal appeared.

cd /var/cache/apt/archives
dpkg --unpack *.deb



Now when I hit exit from initramfs, this appears.

booting to busybox shell

Please help. I have Gnome Live Usb but nothing is working. Initramfs is still showing up.

  • 5
    Removing python from a Linux system will break it. Too many things depend on it. Try using the instructions here (only steps 1-3, just create the chroot) to set up a chroot environment and run sudo apt install python from there. Does that fix it? – terdon May 8 '17 at 12:51
  • It says that python is already the newest version but the following packages have unmet depenendecies. You might want to run 'apt-get -f install' to correct these. Wonderful. Sadly, wireless internet doesn't work in Live Boot. – Gabriel Balan May 8 '17 at 13:10
  • Hmm, it should. It might be simpler to use a live Ubuntu CD which is likely to have wireless working out of the box instead. Alternatively, can you use an ethernet cable? Also, are you 100% sure you ran the commands from the chroot environment? The message suggests you ran them from the live session instead. You need to follow the steps I gave and then, from the same terminal as the chroot command, run the apt install. – terdon May 8 '17 at 13:13
  • Terdon, I have followed steps 1,2,3 and I observed that at step 2 (sudo mount --bind) it would not go through and got only a closed bracket (>). Is this normal? It's no problem. I will make a Ubuntu Live USB right away. It's complicated with the internet cables because my router from Virgin Media uses some weird kind of cables. I live in the UK so everything is kind of backwards. – Gabriel Balan May 8 '17 at 13:18
  • Ah, yes, you need to copy/paste that entire block of commands directy into the terminal. The > you see is because of the trailing && which is a locial AND connecting each of the mount --bind commands given. If you wantr to run them one by one, don't copy the && but it is simpler to just paste the entire set of 4 lines at once. So, that means you didn't run the apt command from within the chroot environment. However, if you don't have internet access, the point is moot anyway. That's the first thing to sort out. – terdon May 8 '17 at 13:22

When force removing Python, everything that depends on Python probably also was removed - and that is a lot. I'm pretty sure it warned you of not doing that... and judging from that first screenshot, you may have wiped your system way more than just removing python...

Eitherway, dpkg --unpack is not sufficient to reinstall a package (there is also "install"...), and the cache in /var will only contain recently downloaded files. There may well be some missing.

You can try to do the dpkg thing correctly, but most likely you will still be missing some dependencies.

As for the last error - it just says that you exited process 1. The operating system cannot continue then, process 1 is supposed to launch everything and not exit. No need to further think about it - rather you need to find a way to get your wireless up and the missing packages installed.

If you really intend to do the chroot recovery, first try to understand what you need to mount where. When done correctly, you may be able to do simply apt install python to get python back. First try if the recovery function of the installer can set up the chroot for you... once you have the chroot, inspect the damage first before making it worse...

Remember, chroot is not trivial to set up properly: https://superuser.com/questions/111152/whats-the-proper-way-to-prepare-chroot-to-recover-a-broken-linux-installation

  • I got the wireless running on Debian Jessie and tried to create a environment with chroot where I could fix python and I got this: root@debian:/etc/apt# sudo chroot /mnt sudo: unable to resolve host debian chroot: failed to run command ‘/bin/bash’: No such file or directory – Gabriel Balan May 10 '17 at 9:14
  • You don't appear to have understood what "sudo" does... nor what the chroot is for. Did you mount the right partitions? Where is /bin/bash? – Anony-Mousse May 10 '17 at 19:20

One suggestion that might work:

Use the Debian installer disc (or probably the live CD) in rescue mode. Select the option to execute a shell in the target system. Then run:

dpkg --configure -a

Exit out, and reboot. dpkg --unpack asks dpkg to install things w/o configuring them; dpkg --configure -a tells it to configure everything that isn't. Note you may get some errors from broken dependencies...

If that doesn't work, get back to the shell in the target system and try:

update-initramfs -u

Then exit out, and reboot.

If either of these gets you booted (probably just to text mode—try the single user option in Grub), then next apt-get install -f will hopefully fix the dependency mess. Then you can apt-get install task-gnome-desktop.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.