after installing enlightment-1.0.1 and try to login in gdm with session E16-GNOME, the e16 wm is started also if i change the session back to GNOME, but i expect metacity start instead e16 with normal GNOME SESSION
Steps to Reproduce:
1. install enlightment
2. change gdm SESSION to E16-GNOME, login and logout
3. change again the SESSION to GNOME and login
e16 start instead metacity
metacity start instead e16
Created attachment 221953 [details]
I doubt anyone in gnome has any idea what e16 is doing here. Re-assigning to e16 maintainers...
the e16-gnome session sets the default WM to e16:
test -x /usr/bin/gconftool-2 && gconftool-2 --set /desktop/gnome/session/required_components/windowmanager --type string e16
if there's a better way, feel free to mention it, otherwise i dont see anything changing
(In reply to comment #3)
> the e16-gnome session sets the default WM to e16:
> test -x /usr/bin/gconftool-2 && gconftool-2 --set
> /desktop/gnome/session/required_components/windowmanager --type string e16
> if there's a better way, feel free to mention it, otherwise i dont see anything
Strange that starting gdm with GNOME (and not with e16-gnome) session keep e16 as wm.
Anyway thanks a lot for the info, now i go to change it immediately
Maybe we can go through WINDOW_MANAGER env var, so that gnome-wm would launch it based on that, not get user gconf tweaked away from metacity and probably never put back or not ensured to be put back always when needed.
But I'm not sure what the status of gnome-wm wrapper and WINDOW_MANAGER is in 2.28 and in the future
i like to point out that this issue also affects logins with KDM.
those with e16 and gnome on the same system, can fix this bug by removing 'e16' from ~/.gconf/desktop/gnome/sessions/required_components/%gconf.xml with 'metacity'
This might have occurred if you compiled e16 before gnome perhaps. Thanks to dabbott for pointing this out.
i don't run GNOME anywhere. can anyone verify that deleting the gconf line from /usr/share/e16/misc/starte16-kde and still using the e16-gnome session still utilizes e16 as the WM ? the script already sets up $WINDOW_MANAGER ...
What is the status of this with GDM 3.8? (that has changed completely)