Comment 4 for bug 366166

Revision history for this message
MikeMiller69 (2-launchpad-net-mikemiller-net) wrote :

Ok, I've managed to get it working, but I still consider this a bug, so you can choose to do what you want with it. Let me explain, so maybe my information will assist you.

As I previously explained, when I would choose "E16-GNOME" from the session menu and log in, I would only get Gnome (and no E16/enlightenment). So I removed all my configuration files and found out it would work. So began copying things back one at a time, in a tedious, process-of-elimination fashion. In the end, if I kept my previous ~/.gconf/desktop/gnome/session directory in place, it would not work. But if I removed ~/.gconf/desktop/gnome/session, it worked fine. Here's the contents of the "offending" files. I have no clue this would keep E16 from starting up, but it does:

# ls -l ~/.gconf/desktop/gnome/session
total 4
-rw------- 1 mike mike 0 2009-01-28 00:18 %gconf.xml
drwx------ 2 mike mike 4096 2009-04-24 22:50 required_components

# cd required_components/

# ls -l
total 4
-rw------- 1 mike mike 178 2009-01-28 00:26 %gconf.xml

# cat %gconf.xml
<?xml version="1.0"?>
<gconf>
        <entry name="windowmanager" mtime="1233120310" type="string">
                <stringvalue>metacity</stringvalue>
        </entry>
</gconf>

I see it mentions metacity here, which is strange, since I've always used e16-gnome since I first loaded Ubuntu 8.10.

Anyway, hope this helps.

-Mike