Author Topic: Enlightenment error  (Read 1276 times)

Offline anlem

  • Full Member
  • ***
  • Posts: 127
Enlightenment error
« on: May 10, 2010, 12:31:48 PM »
Hello,

I installed PCLinuxOS E-17 some time ago and so far I have been very satisfied. Only one little annoying thing has occured. During the boot process just before the desktop opens comes this error message:

"Enlightenment error.
This is very bad. Enlightenment SIGABRT'd. This is not meant to happen and is likely a sign of a bug in Enlightenment or the libraries it relies on. You can gdb attach to this process now to try debug it or you could exit, or just hit restart to try and get your desktop back the way it was. Please compile everything with -g in your CFLAGS".

Options given are F1 (Recover) and F2 (Exit). If I choose F1, soon after that desktop opens. If I choose F2, login window opens and I have to login and wait some time until the desktop finally opens.

So has anybody else experienced this? Is there a way to fix it? Those terms like "SIGABRT", "gdb", or "CFLAGS" don't say nothing to me... ???
Acer Aspire 7530, AMD Athlon 64 X2 dual-core-processor, 250 GB HDD, PCLinuxOS KDE4-Minime

Offline Brizglace

  • New Friend
  • *
  • Posts: 5
Re: Enlightenment error
« Reply #1 on: May 10, 2010, 12:54:57 PM »
Sometime, I have this error message too, I choose F1 (Recover) to continue and everything work.  :-\

Offline Agust

  • Hero Member
  • *****
  • Posts: 983
Re: Enlightenment error
« Reply #2 on: May 10, 2010, 02:57:38 PM »
Well , this error is quite common in e17 , there is any application that does not work well with E17, look at who are working to learn exactly what causes this error application.
Pressing F1 is usually sufficient, only restart Enlightenment, do not lose any work they are doing.
Anyway, I work very hard with E17 and I have not had a single reboot with this version.
Do not worry it's nothing major is only one possible application is incompatible with e17.
Formerly we were making a theme, borders had one that turned red when something was wrong at Enlightenment.

Greetings:
Agust

PCLinuxOS e17 Club Member

Pclos user since 2005!

Offline anlem

  • Full Member
  • ***
  • Posts: 127
Re: Enlightenment error
« Reply #3 on: May 10, 2010, 10:12:00 PM »
Nice to know it's nothing too serious. I can bare few error messages every now and then if everything else works well.
Acer Aspire 7530, AMD Athlon 64 X2 dual-core-processor, 250 GB HDD, PCLinuxOS KDE4-Minime

Linuxera

  • Guest
Re: Enlightenment error
« Reply #4 on: May 14, 2010, 07:39:07 AM »
What if any applications do you have to open at 'start' ?  Could be one of them is causing that error.  I've seen it once in a blue moon, but keep on working and nothing majorly bad, actually nothing at all bad happens, enlightenment resets itself and we go merrily on our way. 

Please look at any applications you have set to run at start and let us know so we can try to duplicate the error.

Thanks,

Cindy aka Linuxera

Offline Brizglace

  • New Friend
  • *
  • Posts: 5
Re: Enlightenment error
« Reply #5 on: May 15, 2010, 12:22:39 AM »
I reinstalled E17 4 days ago and I installed all the same programs.
I did several log out and reboot voluntary and this error message has never appeared.  8)

This time, I did not change the original Theme  ;D, maybe this error is caused by
a different Theme. (maybe when the theme start, this error appear)  ???

Offline smurfslover

  • Hero Member
  • *****
  • Posts: 811
Re: Enlightenment error
« Reply #6 on: May 15, 2010, 12:27:27 AM »
These errors are mainly caused by enabling extra modules, not all the modules are quite stable yet, photo gadget for example never worked fine for me on any distribution, e17 is still far from ready!
Registered Linux User 440970

Every windows machine has an un-patchable critical vulnerability... Its called "Power ON" switch.

Linuxera

  • Guest
Re: Enlightenment error
« Reply #7 on: May 15, 2010, 06:22:53 AM »
I reinstalled E17 4 days ago and I installed all the same programs.
I did several log out and reboot voluntary and this error message has never appeared.  8)

This time, I did not change the original Theme  ;D, maybe this error is caused by
a different Theme. (maybe when the theme start, this error appear)  ???


That could be for the particular theme you chose.. But then I change themes often and don't get that message. Hum.. :-\ :-\

Offline Brizglace

  • New Friend
  • *
  • Posts: 5
Re: Enlightenment error
« Reply #8 on: May 15, 2010, 10:04:33 PM »
I found a way to replicate this error message.  :P

In the Module Settings, I unloaded Pager Gadget,
I rebooted the computer and I had my first error message.

After that, I rebooted several times and this error appear sometime.

After that, I loaded Pager Gadget, I rebooted the computer several times
and I did not see any error message.  ;D

Linuxera

  • Guest
Re: Enlightenment error
« Reply #9 on: May 16, 2010, 05:55:44 AM »
So, now you know you need pager gadget.  Unless you have flipping enabled or only 1 desktop, how would you move from desktop to desktop?  I find pager handy as it shows I have applications open on other desktops too.

Thanks for the great investigation work.  :D

Offline anlem

  • Full Member
  • ***
  • Posts: 127
Re: Enlightenment error
« Reply #10 on: May 16, 2010, 06:32:26 AM »
Only programs I set run at start were auto login and 3G mobile broadband connection, so I don't believe these could cause those errors.

But it came to my mind that enabling some extra modules really might be the reason for those errors. After fresh install there were no errors. Troubles begun when I started experimenting with those modules.. ;D

Eventually those errors went so bad that I had no access to settings anymore. "Configure Computer" was one of them. Every time I clicked the icon in panel there came error and I couldn't change anything. That's why I had no other choice but do the fresh install of LXDE which I tried first when I found out of PCLinuxOS. When I have enough time I will do a reinstall of E17 on SDHC card and do some serious testing. I will add those extra modules one by one and maybe then I can dig out the one whose causing those errors.
Acer Aspire 7530, AMD Athlon 64 X2 dual-core-processor, 250 GB HDD, PCLinuxOS KDE4-Minime