Bug 443866

Summary: VirtualBox, xdriver=vesa, Unable to log into KDE
Product: [Fedora] Fedora Reporter: Roland Wolters <roland.wolters>
Component: kdebase-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: fedora, kevin, ltinkl, rdieter, than, tuxbrewr
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: 2008-04-23 19:38:38 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: 427383    
Bug Blocks:    
Attachments:
Description Flags
.xsession-errors content after a failed KDE login attempt none

Description Roland Wolters 2008-04-23 19:25:24 UTC 
Description of problem:
I installed Fedora 9 Pre-Release (Fedora 8.93 Rawhide), afterwards installed 
the KDE packages and now try to log into KDE. This does however fail:
I can see the KDE 4 screen for a second or two, but the graphics is screwed 
up, and then the system falls back to the login screen.

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

How reproducible:
Everytime, just install the current Fedora 9 pre-release in a VirtualBox 
machine, afterwards install KDE and try to log into it.

Additional info:
The output of .xsession-errors of such a failed log-in is attached.
Comment 1 Roland Wolters 2008-04-23 19:25:24 UTC 
Created attachment 303539 [details]
.xsession-errors content after a failed KDE login attempt
Comment 2 Rex Dieter 2008-04-23 19:31:49 UTC 
X's vesa driver, which VirtualBox emulates, is currently hosed. bug #427383
Comment 3 Steven M. Parrish 2008-04-23 19:38:38 UTC 
This is a known issue with the xorg-x11-drv-vesa and virtualization.  Does not
work in VirtualBox or KVM/QEMU.  Bug report already filed under
https://bugzilla.redhat.com/show_bug.cgi?id=427383

Closing this one as dupe.  So you may want to follow the previous report for
updates.

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