Aide, verrouillé hors de mon ordinateur


Eh bien, j'ai de nouveau foiré mon installation d'Ubuntu, j'ai eu la millième fois, et j'espérais que quelqu'un pourrait m'aider.

En gros, j'ai modifié le fichier de configuration xorg, qui semble entrer en conflit avec le fichier synaptique.

Quoi qu'il en soit, je suis bloqué sur l'écran de démarrage, où il est dit Ubuntu, et j'ai vraiment juste besoin de supprimer ce fichier.

Je me demande donc s'il serait possible d'accéder au terminal lors du démarrage.

Est-il possible d'accéder au terminal à partir de cet écran de démarrage?J'ai essayé ctrl + alt + f1, mais en vain.


Well, I screwed up my installation of Ubuntu again

Happens to the best of us.

Basically, I altered the xorg configuration file

Still not a problem even if you make a mistake.

What you do need to do is to always make a backup before you mess around. That way you can always replace the modified file with the one you altered. Anything related to grub, boot, xorg: better to have 1 extra backup that wastes a few kB discspace than not have one.

Now for a method:

If the system does not boot but you can reach grub it is possible to boot to rescue mode. It is a bit complicated and there is 1 very easy method:

Boot up with the live dvd you used to install, select try ubuntu, open a terminal and remove the file you want removed. (if you need more direction alter your question please to include what it is you need to know).


If everything is locking up (and recovery mode doesn't work), I'd just:

  1. Boot back into your install CD/USB (assuming it's the Live version, not the Alternate or Server)
  2. Mount the hard disk and move the xorg.conf out the way:

    sudo mount /dev/sda1 /mnt
    sudo mv /mnt/etc/X11/xorg.conf{,-OLD}
  3. Reboot.

Almost all systems shouldn't need an xorg.conf file to boot graphically so this should get to back to a desktop of some sort which you can then tweak.

If you can get in via recovery mode, that's obviously going to be quicker... And if you can't, it's probably more than a dodgy xorg.conf file to blame.