[SOLVED] Startup fail -Always goes to command line Error: Cannot launch.-in Zorin/ubuntu

Hevithan · 06-10-2011, 03:22 PM

Using GNOME2.X (default) and Fluxbox on ZorinOS4(upgraded from ubuntu10.10 to 11.04)

When I boot up everything goes fine right up until the splash screen. Once I get to that, Screen goes black for 3 seconds or so, Then the command line pops up, Asks me for LOGIN: and PASSWORD:, and after I enter that it starts fsck then says something like:

Code:

/dev/sda5 mounted - sda5 mounted 22 times without check, Forcing check--
sda5 CLEAN Xnumberofblocks/Ynumberof blocks...
Error: cannot start Xserver

If needed I can reboot my machine and write the whole thing out and post it back.
sda5 shows it is filesystem, ext4, 25g ,mounted at /,Partition type Linux(0x83), partition flags: -
SO after it does a force check it brings me back to hevithan:$ ... I tried typing fluxbox to run that instead of GNOME and it says Error: failed to launch. Xserver is running.. So I reboot, and select: ubuntu-linux version(recovery mode). Look at the startup log it says what I already got in command: Failed to boot XServer is already running.
So I select Restart X and it works fine after that.

Things I have downloaded/installed recently:
*Used additional drivers to enable propitiatory drivers.
*Thunderbird
*Simdock (Which I didn't like) so...
*Docky
*A comic book reader (I forget the name but it was in the repos)
and a few upgrades to software/programs I already had.

So my questions are:

Why is X trying to start 2 times?

Why is it forcing FSCK every time?

Could anything I have downloaded changed my GRUB or Kernel info and confused the system?

is there anymore info needed?

Thanks for any help you guys can offer.

Hevithan · 06-16-2011, 02:27 PM

Problem solved, here is what it turned out to be:

Quote:

Things I have downloaded/installed recently:
*Used additional drivers to enable proprietary drivers.

Apparently the proprietary drivers that got installed, where NVIDIA. I have an intel chip set. Everytime NVIDIA tried to load it's module and screen setting, it forced a check because it couldn't find anything for NVIDIA. I booted in recovery, Changed configuration. # commented out the NVIDIA section, and changed NVIDIA to intel in the display section. Which led me to a new problem, that I will start a new thread for.