Regression: Unity not launched on boot (no launcher/dash/panel)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Confirmed
|
High
|
Unassigned | ||
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After upgrading from 11.10 beta 1 to more recent packages, the launcher/dash/panel no longer launch on boot. I get just the desktop background with a nautilus menu at the very top of the screen. Unity itself seems to be not running:
steve@steve-
1936 ? S 0:00 /usr/bin/
steve@steve-
Compiz is still running, and I can start a terminal and launch applications that way. The apps work normally. Notifications work too.
I reproduced this with both Unity 4.16 and 4.18.
I see this in ~/.xsession-errors, which is a bit suspicious:
Initializing fade options...done
process 1833: arguments to dbus_message_
This is normally a bug in some application using the D-Bus library.
I/O warning : failed to load external entity "/home/
Initializing session options...done
Starting unity-window-
Process 1833 is compiz. I've attached the full .xsession-errors file.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.18.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
Date: Mon Sep 26 14:47:55 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (24 days ago)
Changed in unity: | |
status: | New → Confirmed |
I launched ccsm and found the Unity compiz plugin had been disabled. I did not do anything intentional to disable this plugin. When I tried to enable the plugin via ccsm, it said that a number of keys conflicted with existing keys - for example the GNOME compatibility plugin, which used the same key for 'Run Dialog'. I don't have the exact error messages handy; there were about 6 conflicts. After getting through the conflicts, the plugin was enabled and unity launched in my running session.