Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possible Duplicate:
How to fix “The system is running in low-graphics mode” error?

To prevent my brother from using my computer, I disabled the guest user account in by following the instructions from this post.

During reboot, my brother pressed the down key and Ubuntu booted into recovery mode, I then hit the "continue boot" option it then 'as the popup warned it would' booted into low graphics mode with a black screen. I could not see the mouse pointer so i could not continue the boot (couldn't press ok) and so had to power down the computer externally (with the button). Upon reboot, again it runs in low graphics mode but this time I was able to use the mouse. I then intended to boot and then reboot.( as it said to do after the system recovery mode was run) (it warned that it would probably try to boot in low graphics mode because using the system recovery boot option causes it to, but to just boot for one session the reboot and it would be fine) but when I clicked OK to go into low graphics mode it goes to the boot screen (The one that says "Ubuntu" with the dots under it) and stays there--it just stays there-- so eventually I had to shut down my computer again.

I really want my GUI back I'm only here now because i used Ctrl+Alt+F1 then logged in then StartX (which brought me to my desktop background with no dock options or anything but the pic) where I proceeded to use Ctrl+Alt+T to open terminal and then browser from there.

As of now I now have access to a Ctrl+Alt+F1 terminal as well as a regular terminal achieved through the startx command. Everything was working fine before this. I don't want to lose all my programs and documents. If anyone can help, please do.

share|improve this question

marked as duplicate by jokerdino, stephenmyall, con-f-use, hexafraction, Mik Oct 26 '12 at 14:17

This question was marked as an exact duplicate of an existing question.

Which key did he press? – Amith KK Jul 15 '12 at 5:33
the down key, sorry someone edited that out of my post.(not that i don't appreciate your editing it, thank you btw you really cleaned it up) I added back some of the important things (such as witch key presses) that accidentally removed. it is fised now – antonio Jul 15 '12 at 18:20

Thanks for reading my post but I have fixed the problem. As it turns out the problem didn't lie in the system recovery or low graphics or spontaneous shutdown as I had expected. I went up in my terminal log and found the commands for when I disabled the guest account (beginning of my post) and suspecting that this could be possibly be the reason for the boot problem (also why I included it in my post) I deleted the changes I made and everything now works fine. I suspect it was because i was in a hurry and my brother was trying to stop me so I ended up adding the new line of code in the wrong place, (probably cause i didn't read the instructions carefully, in a hurry and all) anyway i ended up adding it at the top of the page/codeing before anything else. this is what screwed my computer up as deleting the line of code i added fixed everything. My computer is now fixed and working in pristine condition, its now running great again, same as before all of this happened.

Thank you for your consideration and what we can all learn from this. Don't add lines of code in the wrong place or order, don't add them in a hurry and follow instructions exactly. (Unless the instructions were just wrong 0_0.) Otherwise you can end up with a big problem that takes hours to fix. Otherwise you could end up with a problem that looks like another problem and seems like it is being caused by something else (low graphics mode) but in reality is all being causes by that little eency thing you did, that tiny little insignificant change or code in the wrong order or something that seems almost unimportant or insignificant that caused so many problems all the while it seems these problems were caused by this big thing that looks like its a much more probable cause. Then, you spend time on what seems to be the cause all the while forgetting all about that small thing you did. Not to mention the problem itself could be huge, i mean i spent 2 hours and much research, just trying to start my computer and get to the point where I could access a terminal or fix the problem. If I hadn't been able to do these well, my computer wouldn't even start. I would be out of luck and have to go to windows. I figured out Ctrl+Alt+F1 but there wasn't much I could to from there. I then had a half hour's worth of problems with the startx command and until I was able to access the terminal I couldn't get online with anything but my phone. Anyway i digress thanks for reading.

share|improve this answer

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