Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 568441

Summary: F13 in VirtualBox Guest is unable to startx
Product: [Fedora] Fedora Reporter: Nathanael Noblet <nathanael>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mcepl, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-06 09:55:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 507681    
Attachments:
Description Flags
Xorg error log none

Description Nathanael Noblet 2010-02-25 18:21:13 UTC
Created attachment 396350 [details]
Xorg error log

Description of problem:
When attempting to startx on F13 within a VirtualBox guest X is unable to start as it can't find the vboxvideo driver. Creating an xorg.conf setting the device to use vesa allows X to start. Either provide the module or allow X to fall back to vesa for this virtual hardware I guess?

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


How reproducible:
Always.

Steps to Reproduce:
1. login on console
2. startx
3.
  
Actual results:
error output to consol

Expected results:
Xwindows startup successful...

Additional info:

Comment 1 Matěj Cepl 2010-03-06 09:55:12 UTC

*** This bug has been marked as a duplicate of bug 569664 ***