Bug 606437 - Xorg restart indefinitely under vmware [Fedora 14 Rawhide i686]
Summary: Xorg restart indefinitely under vmware [Fedora 14 Rawhide i686]
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vmware
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-21 15:42 UTC by Othman Madjoudj
Modified: 2018-04-11 13:15 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-19 14:32:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Guest (F14 rawhide) Xorg log (33.03 KB, text/plain)
2010-07-02 15:41 UTC, Othman Madjoudj 		no flags Details
View All

Description Othman Madjoudj 2010-06-21 15:42:48 UTC 
Description of problem:

I was running fedora rawhide without problem in VMware Player in Fedora 13 Host -sorry my machines doesn't support KVM- after a upgrade to the latest rawhide X won't run and i try to restart itself indefinitely

Version-Release number of selected component (if applicable):

Guest:

xorg-x11-drv-vmware-10.16.7-3.f13

Host: (f13)
VMware Player 3.1



How reproducible:
Always

Steps to Reproduce:
1. Update fedora
2. Restart machine
  
Actual results:
X doesn't run

Expected results:
X run

Additional info:

I have workarounded this by generating x.org and switching to vesa driver.
Comment 1 Othman Madjoudj 2010-07-02 15:39:36 UTC 
the same problem on other VMware Server 2 and VMware ESXi 4.
Comment 2 Othman Madjoudj 2010-07-02 15:41:55 UTC 
Created attachment 429104 [details]
Guest (F14 rawhide) Xorg log
Comment 3 Othman Madjoudj 2010-07-18 18:08:39 UTC 
It fixed in the latest rawhide but i got another bug: RHBZ ID: 606029

https://bugzilla.redhat.com/show_bug.cgi?id=606029

I'm now in RHBZ ID: 606029
Comment 4 Matěj Cepl 2010-07-19 14:32:37 UTC 
OK, so let's close this one. Thank you for letting us know.
Note You need to log in before you can comment on or make changes to this bug.