> The problem is that while changing screen resolutions/setup with xrandr > the xserver crashes often (but not always). It appeared for the first > time after upgrading from awesome 3.3 to 3.4. Before that, switching > screens setups was rock-stable.
This is probably not what you want to hear, but if your X server is working properly it should not be possible to make it crash. Usually the reason behind crashes like this are bugs in the video card driver. Perhaps the latest version of Awesome exercises code in the nVidia/Intel drivers that wasn't used before, leading to the crashes after your upgrade. > 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 did not find any bug reports related to this problem so I wonder > whether I am the only one having this issue. Any ideas? What would be > a good way to debug a crash of awesome? Probably the best idea is to try another version of the nVidia driver. If you try a really old version and the crash goes away that would definitely confirm where the bug lies. In this case you could report the bug directly to nVidia with their scripts. If you're sure it's Awesome crashing, I guess you could SSH in from a different machine and run Awesome under GDB, but this isn't straightforward. Don't forget to check any log files the X server might leave behind, as well as dmesg (where the nVidia kernel driver logs any issues.) Of course you should probably find out for certain whether it is X that is crashing, or whether Awesome crashes and then your X server just exits normally (again the log files will probably tell you this.) I have a while loop in the shell script that launches Awesome so that if it ever does crash, it just gets reloaded and all my programs keep running. Cheers, Adam. -- To unsubscribe, send mail to [email protected].
