On 30 January 2013 15:51, elmar bucher <[email protected]> wrote: > hallo Camusensei and Alok, > > thank you for your reply. > > i kept on testing. > emacs crashes only at startup. > so, if emacs is proper started, i can move to any awful.layout and work with > emacs without crashing. > additionally i found out that emacs even in awful.layout tile.bottom, > tile.top, fair.horizontal only starts proper, if in this tag already another > program (tested with xterm and firefox) is start. (using Mod4+r emacs in a > empty tag will crash emacs too.)
According to https://bbs.archlinux.org/viewtopic.php?id=71040 recompiling it with USE=-gtk would solve your problem. You should try to debug emacs, see the answer on that post: http://stackoverflow.com/questions/11921100/fatal-error-11segmentation-fault-when-trying-to-enter-gdb-mode-in-emacs-what that means compiling the gentoo ebuild by hand. > i checked for logs, but as far as I see, those crashes get not logged in > any log file. Did you try to start it from a terminal to see if emacs did output something? If you're fine with it, you could also add the -nw switch to emacs for it to start in command-line mode... In any case I think this comes because awesome restricts emacs to start with a given windows size and he just doesn't like specific sizes. You could try emacs' --geometry switch to try and reproduce the problem. In any case, I think this is not an awesome problem. Regards, Camusensei < Why am I helping someone using emacs -_-' > -- To unsubscribe, send mail to [email protected].
