e16-gnome not working with jaunty 9.04

Bug #366166 reported by MikeMiller69 on 2009-04-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Binary package hint: gdm

Under Intrepid 8.10, I was using e16-gnome (Enlightenment with Gnome on top of it) as my window manager(s). After upgrading to Jaunty 9.04, e16-gnome no longer work. If I "change session" from the gdm login manager to "gnome" it logs works fine. If I change it to "E16", then it works fine (using only Enlightenment). But if select "e16-gnome" I get only Gnome.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: gdm 2.20.10-0ubuntu2
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm
Uname: Linux 2.6.28-11-server i686

summary: - e16-gnome not working with jaunty 9.04 ... Under Intrepid 8.10, I was
- using e16-gnome (Enlightenment with Gnome on top of it) as my window
- manager(s). After upgrading to Jaunty 9.04, e16-gnome no longer work. If
- I "change session" from the gdm login manager to "gnome" it logs works
- fine. If I change it to "E16", then it works fine (using only
- Enlightenment). But if select "e16-gnome" I get only Gnome.
+ e16-gnome not working with jaunty 9.04
Sebastien Bacher (seb128) wrote :

the issue is a e16-gnome one whatever that one is not a GNOME bug

affects: gdm (Ubuntu) → ubuntu

Never said it was a Gnome bug. I assume it's a gdm bug, since the user would select "e16-gnome" from within the gdm login screen.

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

Monkey (monkey-libre) on 2010-03-22
tags: added: jaunty
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Fabio Marconi (fabiomarconi) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers