Comment 3 for bug 273373

Revision history for this message
Nikolas Reist (zeroability) wrote :

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.