Created attachment 357991 [details] X.log from failed anaconda X start Description of problem: Using boot.iso from 19-Aug-2009 in VMware Workstation. Anaconda attempts to start X, but dumps user into text mode. X.log has a backtrace. The same error does not occur if using xdriver=vesa. Version-Release number of selected component (if applicable): xorg-x11-drv-vmware-10.16.7-2.fc12.i686 How reproducible: Always Steps to Reproduce: 1. Boot using boot.iso in VMware 2. Select "Install or upgrade existing system" in Anaconda welcome screen Actual results: X tries, but fails, to start. "mini-wm: Fatal IO Error 11 (Resource temporarily unavailable) on X server :1.0." Expected results: X starts. Additional info: There are a bunch of SELinux AVC denials in syslog, but they're there using the vesa driver, too. The vesa driver works, anyway, so I think the AVCs are a separate issue.
Hmm, this is lovely: Backtrace: 0: Xorg(xorg_backtrace+0x3c) [0x80a42fc] 1: Xorg [0x80a7af6] 2: [0x2ef40c] 3: Xorg [0x81b1064] 4: Xorg [0x81b14e6] 5: Xorg [0x80e7d3f] 6: Xorg [0x80e6d94] 7: Xorg [0x806eb17] 8: Xorg [0x8062de5] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0xe87b56] 10: Xorg [0x80629d1]
/usr/src/debug/xorg-server-20090814/composite/compalloc.c:88 /usr/src/debug/xorg-server-20090814/composite/compalloc.c:330 /usr/src/debug/xorg-server-20090814/composite/compext.c:183 /usr/src/debug/xorg-server-20090814/composite/compext.c:386 /usr/src/debug/xorg-server-20090814/dix/dispatch.c:427 /usr/src/debug/xorg-server-20090814/dix/main.c:287 Which translates to main -> Dispatch -> ProcCompositeDispatch -> ProcCompositeRedirectSubwindows -> compRedirectSubwindows -> compRedirectWindow. Which is a weird place to crash! Clearly this is from mini-wm turning on automatic redirection, but it's not obvious why that would fail with vmware but work with vesa. Besides, perhaps, that vmware would pick 16bpp but vesa would pick 24 or 32? A quick test with mini-wm and Xvfb shows it falling over in pretty much the same way on 16bpp, so I think we can start the blame there.
(In reply to comment #2) > > [snip] > > .... Besides, perhaps, that vmware would pick > 16bpp but vesa would pick 24 or 32? > > [snip] I'm not sure if there's a question for me, there. But in the same test VM which exhibits the bug in drv-vmware, drv-vesa picks "Depth 24 pixmap format is 32 bpp" and then works. HTH
Booting with the 22-Aug-2009 boot.iso, X starts fine with the vmware driver. There is no backtrace. As nearly as I can tell, xorg-X11-drv-vmware and anaconda (hence mini-wm) are the same as 19-Aug-2009. xorg-x11-server-Xorg is different, though. Blame server and close this report?
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
I don't think this has been a problem for a while. Closing...