Created attachment 558187 [details] Xorg.0.log Description of problem: X Seg Faults when using vmware driver Version-Release number of selected component (if applicable): xorg-x11-drv-vmware-11.0.3-11.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 17 Alpha/rawhide in VMware using the instructions on Fedora Test List using the usrmove repo: http://lists.fedoraproject.org/pipermail/test/2012-January/105215.html or using the Alpha TC boot iso (the DVD does not seem to boot properly): http://dl.fedoraproject.org/pub/alt/stage/20120127/Fedora/x86_64/iso/Fedora-17-Alpha-x86_64-netinst.iso 2. Reboot Actual results: X does not start Expected results: X Starts Additional info: I also tried building an 11.99.901 rpm after seeing https://bugzilla.redhat.com/show_bug.cgi?id=743872, which went fine, but ended with the same problem: From attached Xorg.0.log: [ 393.314] ABI class: X.Org Video Driver, version 12.0 [ 393.314] [ 393.314] Backtrace: [ 393.314] 0: /usr/bin/X (xorg_backtrace+0x36) [0x464466] [ 393.314] 1: /usr/bin/X (0x400000+0x694a9) [0x4694a9] [ 393.314] 2: /lib64/libpthread.so.0 (0x7fce4fbc6000+0xef90) [0x7fce4fbd4f90] [ 393.314] [ 393.314] Segmentation fault at address (nil) [ 393.314] Fatal server error: [ 393.314] Caught signal 11 (Segmentation fault). Server aborting [ 393.314] [ 393.315]
I forgot to add that if I remove xorg-x11-drv-vmware I at least get video though only to a max resolution of 1280x768 and without the resizing and other benefits the vmware driver provides
Looks like this is the same as I reported in bug 782995 but there was also crash in vesa which is fixed and only vmware crash left.
This *probably* is the reason Anaconda does not start in qemu-kvm -vga vmware: F17 Alpha and VMWare Fusion http://lists.fedoraproject.org/pipermail/devel/2012-March/163675.html qemu-kvm -cdrom Fedora-17-Alpha-x86_64-DVD.iso -boot d -m 2048 -vga vmware fails to initialize X and falls back to text. It works with any of -vga cirrus/std/qxl
This appears to be a duplicate of 782995. Feel free to re-open if need-be. *** This bug has been marked as a duplicate of bug 782995 ***