I have emerged world and now GNOME is not allowing enlightenment to start. I normally use startx with the WINDOW_MANAGER variable set to /usr/bin/e16 and it has always worked fine. I tried the gnome-e16 session selection using the gui login xdm/gdm, and the result was still no enlightenment and disfunctional gnome menu items, as if no window manager was running at all, but I couldn't confirm that because it became unusable. I was able to start enlightenment without gnome running so I know enlightenment is ok.
Steps to Reproduce:
1. emerge latest GNOME
2. set env variable WINDOW_MANAGER to /usr/bin/e16
Enlightenment doesn't start. Metacity starts.
Enlightenment should start.
- What about /desktop/gnome/session/required_components/windowmanager ?
You've to change this entry.
- Then, because metacity is an autostart app, started by the session manager, you need to add enlightenment in your startup applications . (the windowmanager must replaces metacity)
It works like a charm here with GNOME+fvwm ;) (or compiz)
I have converged on what I believe is the best solution at this time. As Romain suggested, I edited:
(see below for why I changed this parameter also)
and replaced each entry with: e16
However, e16 doesn't have a desktop file, so I had to create this using metacity.desktop as an example:
---------my e16.desktop file
# name of loadable control center module
# name we put on the WM spec check window
# back compat only
I placed this file in:
I then removed the enlightenment startup apps entry. Gnome now starts e16 without needing to explicitly specify it as a startup application. Starting everything this way enables Gnome to display a nice background over the top of the enlightenment default background. Enlightenment is still complaining about another window manager running, but that's a fairly minor weakness and possibly there is a config option I haven't set correctly.
I configured e16 as the filemanager also because nautilus (and x-server overhead) was chewing up anywhere between 40% and 60% or more of my cpu on a continuous basis. Its now back down to normal, less than 5%.
I hope someone else finds these suggestions useful.
Thanks for the help.
the solution look like the new way of doing things. Unfortunately, with e16 ebuild starting to change gconf values, it's time we write thing down in our documentation so users and devs alike can do the right thing (and drop unneeded elogs from ebuilds).
Then we should probably reset the window manager to metacity by default in the gnome-session provided .desktop file and it will most likely also allow us to provide a .desktop file to start with mutter/gnome-shell.
This has probably changed a lot with Gnome3, maybe other team members using it could confirm the status of this one there
The method has changed completely with GNOME 3. This is on the todo list for documenting GNOME 3.
Changing subject and blocking GNOME 3 release...
*** Bug 436392 has been marked as a duplicate of this bug. ***
I need someone to tell me (or do) what exactly needs to be documented in:
to handling this *with gnome 3.8* (if still needed)