Comment 4 for bug 273373

Bug fixed, there was a problem in the compatibility of the configuration
package compared with the Live CD version of the distro. Of course, I cannot
test every update with both my already updated system and the Live CD
version every time. The problem did not occur in a normal upgrade from an
already updated installed OpenGEU.

The problem was that since E17 changed the directory structure, the postinst
script was trying to copy the files into a folder that wasn't there.
You can now apt-get update and upgrade, it will restore your E. Also, if
from GDM your default session is now a terminal session, just change the
session before you log in. Enlightenment is experimental, and this is
specified in the Home Page, in the Wiki, everywere. I and my Team do our
best to make it very stable and compatible from update to update with the
previous versions of the system but the problem is that sicne Enlightenment
is in development, even big core parts of the system can change from an
upgrade to another.

I'll post in the forums a poll or something to ask people if they prefer to
keep a single E17 version with every OpenGEU release or if they prefer me to
keep trying to upgrade E17 from time to time in the same OpenGEU version.
The first choice would be a complete E17 feature freeze in every OpenGEU
release. Both ways could be prefered by people. Ubuntu at the moment keeps
still with a single Gnome version per release, for example.

Thanks for posting,

Luca D.M.

2009/1/9 Nik Reist <email address hidden>

> Just to provide some information to this bug, I recently installed the
> available 8.04 disc and noticed a couple of issues with the update for
> e17. First the key is not included in the distro so the update on the
> "greenie" repo does not take place. When I add the key from the Wiki
> instructions (which are wrong the syntax should be:
>
> wget -q <site> -O- | sudo apt-key add -
>
> ) and begin to update, I get errors updating package opengeu-default-
> configurations stating that it cannot copy to destination
> /../../../../other because it is a directory (which could be bad copy
> syntax or incorrect path specified).
>
> Given this second issue, even the fix to remove e17 and e17-data (again
> this is wrong in the wiki it should be:
>
> sudo apt-get remove e17 e17-data (instead of install)
>
> ) and then:
>
> sudo apt-get install opengeu-desktop
>
> there is no possible way to fix the issue. The package I specified can
> not be installed properly so the WM doesn't function properly.
> Basically when the update takes place e17 segfaults and issues a recover
> or exit prompt. THIS instance does not allow you to recover e17. In
> fact, when you attempt to log back in the profile the WM appears to be
> missing or corrupt because you only get an xconsole. If you specify in
> gdm to use enlightenment (and perhaps after deleting .e from the user's
> home directory) you are able to receive a prompt to configure your e17
> session and then enlightenment has no problems running.
>
> I like the concept of this distribution and would feel comfortable using
> it as a production system, but not if these updates are not thoroughly
> verified before being posted to an update server.
>
> --
> latest updates break e17
> https://bugs.launchpad.net/bugs/273373
> You received this bug notification because you are subscribed to
> OpenGEU.
>
> Status in OpenGEU: When a Gnome reaches Enlightenment: New
>
> Bug description:
> As reported here: http://forum.intilinux.com/index.php?topic=594.new#new
>
> I'll update today and see if they break E17.
>
> Joseph
>
> WHAT HE SAID:
>
> "I should have known better than to simply 'ok' installation of presumably
> the latest e17 and modules/libs from update manager considering the
> Dunnewind snafu last time, but the system and myself did it again...fool me
> twice...(you can't fool me?!?) At any rate, on reboot the e17 popup stated
> that 'this is bad'. Options F1 & F2 yielded nothing and sent me back to the
> login screen where I am stuck.
>
> Out of my five computers I have this distro on three and am quite satisfied
> despite still not being able to get cups into line/print to my server and my
> post regarding that issue has garnered no replies by the way.
>
> I am simply going to have to choose very carefully any updates from here on
> out. At least the other OpenGEU machines are not updated and working fine.
> Any suggestions for fixing this new 'and improved' e17 problem are
> appreciated
>
> All the best."
>