[prev in list] [next in list] [prev in thread] [next in thread]
List: enlightenment-users
Subject: Re: [e-users] e17 cvs - e segfault after menu regen
From: Laurence Vanek <lvanek () charter ! net>
Date: 2006-09-24 23:37:04
Message-ID: 451716A0.6020600 () charter ! net
[Download RAW message or body]
Paul Stejskal wrote:
> Laurence Vanek wrote:
>> Laurence Vanek wrote:
>>
>>> updated my cvs tree & rebuilt all EFL then E. no problems until I
>>> decided to see what would happen by rebuilding the application menu.
>>> This created an E seg fault that I could not recover from. At the
>>> moment I cannot start e from entrance. I get the "e seg faulted - this
>>> is a very bad thing..." screen which offers to recover. Recover not
>>> possible. entrance is fine, in fact I typing this from (choke) gnome
>>> enviroment which entrance fires up.
>>>
>>> Im guessing that the menu regen operation seriously corrupted something
>>> but I have no clue what.
>>>
>>> I rebuilt e, no joy. Deleted the ~/.e/e/config files, still no joy. I
>>> trying to avoid gutting my system of e related files & starting over.
>>> any advice would be appreciated.
>>>
>>> Im running Fedora Core 5 (updated).
>>>
>>>
>> UPDATE:
>>
>> Heres a backtrace. I hope it is helpful (first time I've tried this).
>> Used debugging guidelines on get-e.org.
>>
>> ==============
>> #0 0x0080e402 in ?? ()
>> #1 0x008eb40d in poll () from /lib/libc.so.6
>> #2 0x003bd779 in XProcessInternalConnection () from /usr/lib/libX11.so.6
>> #3 0x003bdb5f in _XRead () from /usr/lib/libX11.so.6
>> #4 0x003bf4f1 in _XReadEvents () from /usr/lib/libX11.so.6
>> #5 0x003a84cb in XNextEvent () from /usr/lib/libX11.so.6
>> #6 0x080d0c23 in e_alert_show (
>> text=0x8147cdc "This is very bad. Enlightenment has recieved an
>> abort.\nThis could be for many reasons - accessing memory not in\nits
>> available address space or unable to be paged in.\n\nYou can gdb attach
>> to this proces"...)
>> at e_alert.c:129
>> #7 0x080b750e in e_sigabrt_act (x=6, info=0xbfb19dfc, data=0xbfb19e7c)
>> at e_signals.c:155
>> #8 <signal handler called>
>> #9 0x0080e402 in ?? ()
>> #10 0x00853ee9 in raise () from /lib/libc.so.6
>> #11 0x008554f1 in abort () from /lib/libc.so.6
>> #12 0x0088853b in __libc_message () from /lib/libc.so.6
>> #13 0x0088fa68 in _int_free () from /lib/libc.so.6
>> #14 0x00892f6f in free () from /lib/libc.so.6
>> #15 0x00235a82 in ecore_desktop_tree_del (tree=0x9d15738)
>> at ecore_desktop_tree.c:379
>> #16 0x00237086 in _ecore_desktop_menu_get0 (
>> file=0x9d156d0 "/etc/xdg/menus/applications.menu",
>> merge_stack=0x9d15738,
>> ---Type <return> to continue, or q <return> to quit---
>>
>> ======================
>>
> Sometimes I get that kind of error when I run an outdated module
> (taskbar). If you push the first option to continue it might bring up
> the modules dialog and disable the ailing module.
>
> Paul
>
Paul -
thanks but e wont let me proceed. only allows exit (no recover). that
takes me back to entrance where Im able to choose another type of
session like gnome or kde.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic