From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
I'm having a lot of problems with my setup (Radeon 9000, two monitors, RHL9).
In desperation, I added
Option "DDCmode" "false"
to one of the Monitor sections. This caused X to segfault.
I put this option right after
This latter option was processed just before the segfault
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.put the option in XF86Config
Actual Results: (**) Option "dpms"
(**) RADEON(0): DPMS enabled
(II) RADEON(0): Direct rendering disabled
(==) RandR enabled
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
I will attach my XF86Config and /var/log/XFree86.0.log
Created attachment 91324 [details]
XF86Config that provokes server crash
Created attachment 91325 [details]
/var/log/XFree86.0.log recording crash
hmm. Something else is going on: I have been able to use the option without X
crashing. Will report when I figure out more.
Video driver options go in the video driver "Device" section of the config
file, not in the Monitor or ServerFlags sections.
XFree86-Servers doesn't exist in Red Hat Linux 8.0 or 9, reassigning to
Thanks Mike. Moving the option eliminates the crash.
Still, crashing is a bug, I'd say.
An X server crashing due to being misconfigured might be a bug, but it is
an extremely low priority bug which isn't worth engineering time to investigate
and fix, when there are hundreds of bugs open which actually prevent users from
using X, or are much more serious.
Please file this bug report upstream at http://bugs.xfree86.org for the
community of X developers to fix it.
Our official workaround for this problem is to not misconfigure your X server
in a bogus manner, and it will work properly.