After updating Oneiric today, startup stops.

Log in to the Ubuntu Classic session and reinstate your3D drivers. If you cannot solve simple issues like this then you should NOT use Oneiric. It is not ready and not stable.

Well, we can not all have Your divine knowledge.
I am just human and even the most simpel things a have to learn at some point.

I apologize for wasting Your and others time.

Thanks.

-Lasse

Please press ctrl + alt + F2 login with your user and password then to install unity-2d type:

sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install unity-2d

Then please type

sudo reboot

 to reboot your system, then at login please select to use unity-2d

If you want an unstable OS and want to report bugs to get the release ready and don't mind feature holes and bugs then by all means, use Oneiric. It needs people to report the issues in it. If you need a stable OS which will work then use Natty. It's not about devine knowledge, it's about understanding the OS and it's packages that you have installed are not actually ready to be used and are under heavy development so you will get a tonne of issues.

Updated and upgraded today, unity-2d already installed.

I will log on using unity-2d.

I am so very sorry to be such a bother.

-Lasse

If you can use proprietary drivers with your video chip, you can install it there then log in to Unity normal.

Well, in the beginning with Oneiric i did not have to use proprietary drivers. So something must have changed in the later updates/upgrades.

I will wait to se if later upgrades/updates solves the problem (and solves the Jockey problem).

Thanks!

When running " compiz --replace & disown " in terminal, in 2d.

lasse@lasse-kontor:~$ compiz --replace & disown
[1] 2117
lasse@lasse-kontor:~$ Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...no
Backend : gconf
Integration : true
Profile : default
Adding plugins
Initializing core options...done
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing mousepoll options...done
Initializing vpswitch options...done
Initializing animation options...done
Initializing snap options...done
Initializing expo options...done
Initializing move options...done
Initializing place options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing wall options...done
Initializing ezoom options...done
Initializing workarounds options...done
Initializing staticswitcher options...done
Initializing resize options...done
Initializing fade options...done
Initializing scale options...done
Initializing session options...done
Starting unity-window-decorator

(unity-window-decorator:2138): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(unity-window-decorator:2138): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(unity-window-decorator:2138): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",

(unity-window-decorator:2138): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
GConf Error: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/apps/metacity/global_keybindings/panel_main_menu' set in a read-only source at the front of your configuration path
GConf Error: Configuration server couldn't be contacted: D-BUS error: Can't overwrite existing read-only value: Value for `/apps/metacity/global_keybindings/panel_run_dialog' set in a read-only source at the front of your configuration path
Initializing unitymtgrabhandles options...done
Initializing unityshell options...done
Setting Update "main_menu_key"
Setting Update "run_key"
Setting Update "main_menu_key"
Setting Update "run_key"
lasse@lasse-kontor:~$