If I boot with my old setup (see attached xorg.conf) then Xorg crashes on startup. That setup was still working with 1.7.7-14. Now with 7.6_1.12.3-1.2.3 I get a backtrace like attached. I have removed everything but the dual screen setup from the xorg.conf (see Xorg.1.log, xorg-*-1-.conf) and Xorg is still crashing which indicates that the dual screen setup may be at stake. Fortunately it is not the dual screenery itself that makes Xorg crash. I can boot in single screen mode without xorg.conf and then activate the second screen via xrandr. This is a bit unhandy since I will have to configure KDE for the second screen on every new boot by hand (i.e. plasma panel & icons) but there is a way to get Xorg well up and running! Please have a look!
Created attachment 66095 [details] xorg.conf
Created attachment 66096 [details] Xorg.0.log
Created attachment 66097 [details] xorg-1-.conf
Created attachment 66098 [details] Xorg.1.log
Does this still happen with xf86-video-ati 6.14.6 (the last version that works without KMS)? If so, can you get a full backtrace with gdb?
Sorry can`t reproduce any more. No chance to annotate the backtrace with hindsight (one of my programs does) since I forgot to copy /proc/$!/maps. Believe me, I have tried everything to reproduce (including restoration of old configuration and testing in exactly the same setup with the same monitor). However if your folks is also interested in occassional or irregular crash backtraces you could make sure that the server itself created a /var/log/Xorg.0.maps. This would be the best way since an Xorg & cp /proc/$!/maps does sometimes work, othertimes not because a too early snapshot may be useless. Sorry, many distributors keep cropping Xorg-debuginfo because they appear to think of it as "spacious" not thinking of any Xorg related backtrace being unusable with that.
... and I would have taken a /proc/$!/maps if I thought that it wouldn`t stay reproducible (i.e was reproducible but only during a certain bootup).
old obsolete issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.