Hello, You can re-compile Awesome with the -fsanitize=address CFLAGS (export CFLAGS="$CFLAGS -fsanitize=address -ggdb"), Watch out, you have to clean the compilation directory/files first. This will print some useful information if awesome really crash (rather than quit by itself). You can also wrap the awesome command in gdb one, but that's more tricky than it seem (you have to use the python API to catch useful events, too much trouble).
On 24 August 2015 at 03:21, Max Görner <[email protected]> wrote: > Hi, > I tried a bit to solve my problem and I noticed that awesome crashes during > login. This fact explains all problems I had so far like missing control bar, > no input focus anywhere and no changing tags. Obviously this implies, that I > had non of the described problems yet (but I'm feared to encounter them soon). > > Anyway, now I'm puzzled about why awesome crashes and how to prevent this. I > had a look at my .xsession-errors but did not find a clue. I attached two > versions of it. One when using Awesome as a WM and one when using KWin. (1) > > I'd be very glad about any hint on why awesome crashes and how to fix this. I > will file a bug report on GitHub if thats the place to discuss this. > > sincerely > Max Görner > > (1) My main keyboard layout is DE-Neo2 which I set up using KDE tools. > Nonetheless, it was applied system wide which means that I use it to enter my > disk encryption password at startup or to log in at TTY1. This fact should > make it easier to understand some bits of awesome_xsession_errors. > > PGP: https://wwwpub.zih.tu-dresden.de/~maxgoern/2FE6023F.asc -- To unsubscribe, send mail to [email protected].
