On Tue, Mar 16, 2010 at 11:43:12AM +0100, Christoph Groth wrote: > Adam, thanks for your reply, > > Adam Nielsen <[email protected]> writes: > > >> This problem seems to be specific to awesome, as it never occurs with > >> xfce or gnome. > > > > Again, Awesome shouldn't be able to crash X even if it wanted to. (It's not > > *that* awesome...) > > 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: - it never happend when adding a secondary screen, but does happen quite often when disabling it again. So "xrandr --output VGA1 --auto --left-of LVDS1" seems to be safe, while "xrandr --output VGA1 --off" is not. - it doesn't happen with a freshly started awesome. I did even run the two commands in a loop for a while without problems. But when I have worked for a while and then disable the external screen, the X server exits nearly every time. - 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. Please not that this is on a laptop which I suspend/resume quite often. So it may be necessary to have a suspend/resume cycle to trigger this behaviour. However, it's not sufficient to reproduce it. Jan -- To unsubscribe, send mail to [email protected].
