I'm trying to install Ubuntu (version does not matter to me) alongside my Windows Vista Operating System. My laptop does NOT have a disk drive, so I have to use the bootable flash drive option. Anyway, I tried installing Ubuntu 14.04 LTS, because when I tried with 14.14 (or whatever the newest version is) I couldn't log in due to an error. (it failed with the "test out Ubuntu", I couldn't log in because it asked for a username and password that did not exist.)
I thought that installing 14.04 LTS would go smoothly, but it didn't. I basically can't log in due to a system error, that I can go into detail about should it become relevent. However, right now, I just want to get a working version of Ubuntu on here; my biggest worry is that since I already have one installed (that doesn't work), how will I re-use the same partition for a different version of Ubuntu? (Bearing in mind I can't update from within Ubuntu because I can't log in.)(Also I can't use an installation C.D.)
Is there any trick to this? Could someone walk me through it? (I'm using a different computer to keep in touch on these here forums.)
I would think that the most obvious issue might be that my computer is 64 bit (Windows Vista, if you want an idea of how old it is) and I installed the 32 bit version of the OS. I would prefer to do that in the end, if possible, as the computer has ONLY 2 GB ram, and I want to make it stretch. But I'm open to any feedback or knoledge!
Edit: Since it is now relevant, due to the fact that it prevents me from using Ubuntu tools, I am going to explain my issue with 14.04 in detail.
You know that little Bar at the top that has all the file, edit, and power down buttons? It doesn't show up, either at the top of the screen or on the individual window. The Launcher bar is also missing. There are no icons on the desktop. The only way I could run things (before the login error locked me out completely) was to right-click on the desktop and select "Change desktop background", using the interface to navigate backwards to the main settings page.
Edit: Using the console, I'm currently trying to install Gparted, so I can (maybe?) do whatever I need to do to install/unistall Ubuntu as needed.
Edit: After following mchid's answer, the terminal spit back the following info (and it didn't open anything when I hit Ctrl+alt+f7):
Inavlid MIT-MAGIC-COOKIE-1 key/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/int.py:57: GtkWarning: could not open display
Traceback (most recent call last):
File "/usr/bin/ccsm", line 94, in
Import ccm
File "/usr/lib/python2.7/dist-packages/ccm/init.py", line 1, in
from ccm.Conflicts import *
File "/usr/lib/python2.7/dist-packages/ccm/Conflicts.py", line 26, in
from ccm.Constants import *
File "usr/lib/python2.7/dist-packages/ccm/Constants.py", line 30, in
CurrentScreenNum = gtk.gdk.display_get_default().get_default_screen().get_number()
AttributeError: 'NoneType' object has no attribute 'get_default_screen'
Edit: I noticed it said my problem was similar to "Unity is not appearing on my desktop" Or something like that. the fix didn't work for me. I ran
dconf reset -f /org/compiz/
unity --reset-icons &disown
Result: it seems to have set my backend to gsettings, I noticed it was like this on a working machine running 14.04 LTS. It also said: info: Unity is fully supported by your hardware. Info: Unity is not supported by your hardware. Enabling software rendering instead (slow). Info: Starting plugin: opengl
(machine is hung up here, it's not giving me the line showing that I can start a new command)
I used CTRL ALT F1 (previous termnal was in CTRL ALT F2) to force a sudo-reboot, the result was.... no change in status.
If it's any help, I have acess to the bar at the top (shutdown, speaker volume, etc.) prior to loggin in. Just thought I'd mention that.
Edit: SOLVED: My hardware was not compatible with Ubuntu. I installed Lubuntu, and all my problems seems to be fixed. All of the ones in this thread, anyway....
The system kicks me back to my login screen within 2 seconds of that showing up, so there's really no way for me to actually "read the error" or something.
– Trey White Jun 21 '15 at 16:24