Red Hat Bugzilla – Bug 136605
caught signal 11 crash
Last modified: 2007-11-30 17:10:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041016
Description of problem:
After upgrading to the current development xorg packages and
restarting X I was met with the pleasant message:
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
The previous build worked perfectly (6.8.1-6) with my very old riva
tnt2 64. Now X cannot start. There do not appear to be any errors in
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.start X (at least with nv driver)
Actual Results: X crashed.
Expected Results: X would not crash.
I tried using the nvidia binary driver and got the same results. I
also tried the fbdev driver, but /dev/fb0 did not exist (I also do not
think that that is really a solution).
*** This bug has been marked as a duplicate of 136478 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.