PDA

View Full Version : [other] [elbuntu, Enlightenment DR17] Rather Strange Issue



Genotrius
November 10th, 2008, 12:13 AM
Every now and then, my Elbuntu (Ubuntu using Enlightenment DR17) hits a wall and crashes, defaulting to a wall of code made up of the repetitive message here: http://pastebin.com/m7f4e1260 Is this something that is easily solved, or am I going to have to file a bug with Enlightenment?

Sometimes, before I get that message, my system will appear to run fine, but my keyboard seems to lag (I type too quickly and characters get left out) and I'm unable to start any new applications, though those that are still running usually don't have any problems.

Skripka
November 10th, 2008, 12:20 AM
I ran e17 until last week, when the instabilities (on a fresh 64-bit install) just ticked me off enough to go back to something more mainstream. E17 is still beta-officially 16.999.050 last I knew, it sure is pretty and can do beautiful things, but none of the DEs which sport is as a window manager have a large enough support or dev base for my tastes, when things go ill.


Have you posted a message to the devs or on an Elbuntu dev board? That would be the 1st thing I'd try.

Genotrius
November 10th, 2008, 12:25 AM
No, I haven't tried that. I'll post this there as well.
I really like Elbuntu and I've gotten very used to it now, so if I can find some way to fix this without having to learn a programming language, I'd really love to.

worldwithoutgurus
November 10th, 2008, 04:54 AM
Hi,

Elbuntu is dead and no more maintained.

http://e17blog.tuxfamily.org/

Genotrius
November 10th, 2008, 05:18 AM
Hi,

Elbuntu is dead and no more maintained.

http://e17blog.tuxfamily.org/

Well, it's not exactly Elbuntu as they were trying to develop it there, just Ubuntu Intrepid Ibex with the e17 packages from e17.dunnewind.net installed over it.
Do you know how to fix this issue, or whether it's user-fixable?

loell
November 10th, 2008, 05:37 AM
I think you can only wait for updates from the repo where you got it (e17.dunnewind.net).

compiling directly from CVS is another option.

Genotrius
November 10th, 2008, 10:53 PM
I think you can only wait for updates from the repo where you got it (e17.dunnewind.net).

compiling directly from CVS is another option.

I'm not sure that an update would solve it, though. What I'm asking is if anyone knows whether or not this is an issue that can be fixed with some sort of a configuration file, or if it's strictly a problem with the content of the packages that I would have to patch their source and install them in order to fix.

loell
November 10th, 2008, 11:33 PM
I don't think this is just a matter of config files, you can always delete /.e to test if its a wrong config or not.

e17 core code is constantly updated, they either introduce a fix or made a new feature which eventually broke some parts of it, you could hardly apply a patch for it too, since the code itself has an unpredictable changes over time.