Jan Niehusmann <[email protected]> writes: > On Tue, Mar 16, 2010 at 11:43:12AM +0100, Christoph Groth wrote: >> I verified that indeed X does not crash. It's awesome which crashes >> and then X just exits. Perhaps someone knowledgeable could have a >> look at the attached backtrace? What I did is running > > I can confirm that the same 'crash' does happen here. Some more > observations: > > (...) > > - I tried to circumvent the problem by just restarting awesome before > running xrandr, but then I noticed that restarting awesome shows the > same behaviour: It seems to be safe for a fresh instance of awesome, > but can crash it after awesome has been running for a while.
Same here. Launching awesome from within an infinite loop is a viable workaround for this bug. The only inconvenience is that in order to quit awesome you have to kill the shell which otherwise keeps restarting it... I am still interested in helping to cure this problem but for that the help of someone knowledgeable with the internals of awesome is necessary. Should a bug in the bug tracking system be opened for this issue? Some time ago I sent to this list a backtrace which was suffering from parameters being optimized out. I had compiled the awesome debian package from source using DEB_BUILD_OPTIONS="nostrip noopt" fakeroot apt-get -b source awesome and AFAIK this should disable optimizations for the build. Apparently this does not work. Is this another bug? Christoph -- To unsubscribe, send mail to [email protected].
