Bug 749647

Summary: [GD5446_KVM] KDE fails to start in side a VM using the cirrus driver and 'raster' Qt renderer
Product: [Fedora] Fedora Reporter: Martin Kho <lists.kho>
Component: qtAssignee: Ngo Than <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: airlied, ajax, awilliam, dennis, itamar, jarsmith, jreznik, jsmith.fedora, kevin, kparal, ltinkl, mike.hinz, oliver.henshaw, rbergero, rdieter, rnovacek, robatino, smparrish, tflink, than, xgl-maint
Target Milestone: ---Keywords: Patch, Triaged, Upstream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: [cat:others] AcceptedBlocker
Fixed In Version: qt-4.8.0-0.23.rc1.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-29 02:30:30 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 713568    
Description Flags
dmesg from final TC3 guest
kdm.log from final TC3 guest
messages from final TC3 guest
Xorg.0.log from final TC3 guest
xsession-errors from final TC3 guest none

Description Martin Kho 2011-10-27 15:12:58 EDT
Description of problem:
Booting the F16 Beta, Final TC2 KDE x86_64 live image inside a virt-manager VM - host
F15, F16, using the cirrus video adapter - results in KDE crashing right at
the end of startup (after it displays the KDE logo in the bootsplash sequence) giving a black screen.

Booting in 'basic graphics mode' - i.e. using vesa instead of the cirrus
driver - works.

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

How reproducible:

Steps to Reproduce:
1. Boot the live CD
2. Log in
3. After the initialisation plasma crashes
Actual results:
Black screen

Expected results:
Running plasma-desktop

Additional info:
This bug is possible related to bug #731245. The cirrus-driver is the default when installing a new VM.
Comment 1 Martin Kho 2011-10-27 15:15:21 EDT
Created attachment 530548 [details]
Comment 2 Martin Kho 2011-10-27 15:16:11 EDT
Created attachment 530549 [details]
Comment 3 Martin Kho 2011-10-27 15:16:48 EDT
Created attachment 530550 [details]
Comment 4 Martin Kho 2011-10-27 15:17:57 EDT
Created attachment 530551 [details]
Comment 5 Adam Williamson 2011-10-27 16:57:56 EDT
er, kdm.log shows a backtrace in qxl, not cirrus. are you sure this is using cirrus? are you sure you have the right logs?

Fedora Bugzappers volunteer triage team
Comment 6 Oliver Henshaw 2011-10-27 17:10:05 EDT
As with the qxl bug, this only happens with the (new) default of "QT_GRAPHICSSYSTEM=raster" - see bug #731245 comment #32.
Comment 7 Martin Kho 2011-10-27 17:13:25 EDT

Arch, I'll create a new kdm.log from TC3 final. Sorry :-(

Martin Kho
Comment 8 Adam Williamson 2011-10-27 18:45:28 EDT
updating the summary, nominating as a blocker, because F15 defaults to cirrus/vnc not qxl/spice, unfortunately :( as we 'support' both F-N and F-N-1 as virt hosts in the criteria, we need both cirrus and qxl drivers to work with raster, so KDE will run on both F15 and F16 KVM host default configs.

Fedora Bugzappers volunteer triage team
Comment 9 Adam Williamson 2011-10-27 18:47:22 EDT
to reproduce this, btw, just create a VM in Fedora 15 virt-manager with all default settings and try to boot an F16 live KDE image. that should be all that's needed.
Comment 10 Adam Williamson 2011-10-27 18:49:21 EDT
To expand on Oliver's comment #6: Qt's default rendering engine changed from 'native' (which uses Xrender) to 'raster' (software rasterization) in Qt 4.8, and that's what 'broke', here (why this works in F15 and not F16). Switching back to 'native' by default would be sub-optimal for reasons discussed in https://bugzilla.redhat.com/show_bug.cgi?id=731245#c85 , so we really want the cirrus driver to be fixed with respect to Qt's 'raster' rendering, that would be the best solution. thanks!
Comment 11 Andre Robatino 2011-10-27 22:45:42 EDT
I can reproduce this using either the 32- or 64-bit TC3 Live KDE image booted in either a 32- or 64-bit F16 KVM guest (both default installs from the respective TC3 DVDs). My host is F15 x86_64. As long as the guest video driver is set to cirrus, it happens, with the display being set to either VNC or Spice. Booting the 64-bit Live always results in a black screen, while booting the 32-bit Live usually results in a crosshatch pattern (though I did see a black screen the first time booting it).
Comment 12 Andre Robatino 2011-10-27 23:01:48 EDT
Attached below are logs associated with the 64-bit TC3 Live KDE image booted in the 64-bit F16 KVM guest, using VNC+cirrus. I got a black screen.
Comment 13 Andre Robatino 2011-10-27 23:02:52 EDT
Created attachment 530603 [details]
Comment 14 Andre Robatino 2011-10-27 23:03:38 EDT
Created attachment 530604 [details]
Comment 15 Andre Robatino 2011-10-27 23:05:07 EDT
Created attachment 530605 [details]
Comment 16 Adam Williamson 2011-10-28 01:52:46 EDT
Adding CCs for blocker votes. I'm +1 on this, given that cirrus seems to be the default for at least 32-bit VMs in both F15 and F16, and possibly 64-bit in F15.
Comment 17 Martin Kho 2011-10-28 06:45:55 EDT
Created attachment 530639 [details]
dmesg from final TC3 guest
Comment 18 Martin Kho 2011-10-28 06:46:32 EDT
Created attachment 530640 [details]
kdm.log from final TC3 guest
Comment 19 Martin Kho 2011-10-28 06:47:20 EDT
Created attachment 530641 [details]
messages from final TC3 guest
Comment 20 Martin Kho 2011-10-28 06:47:56 EDT
Created attachment 530642 [details]
Xorg.0.log from final TC3 guest
Comment 21 Martin Kho 2011-10-28 06:49:35 EDT
Created attachment 530643 [details]
xsession-errors from final TC3 guest
Comment 22 Martin Kho 2011-10-28 07:00:41 EDT

abrt created a core-dump. Is this info interesting? What files?

Martin Kho
Comment 23 Kamil Páral 2011-10-28 08:01:11 EDT
Reproduced. +1 blocker.
Comment 24 Jared Smith 2011-10-28 11:30:47 EDT
+1 blocker
Comment 25 Robyn Bergeron 2011-10-28 12:51:50 EDT
+1 blocker
Comment 26 Adam Williamson 2011-10-28 14:49:44 EDT
Discussed at 2011-10-28 blocker review meeting. Accepted as a blocker per criterion "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase" as applied to the KDE desktop + cirrus driver combination.
Comment 27 Adam Williamson 2011-10-28 16:19:56 EDT
We have significant progress here. We're pretty sure it's:


rdieter is working on a Qt build with that patch to test.
Comment 29 Rex Dieter 2011-10-28 18:01:51 EDT
snarf over to qt
Comment 30 Fedora Update System 2011-10-28 18:02:50 EDT
qt-4.8.0-0.23.rc1.fc16 has been submitted as an update for Fedora 16.
Comment 31 Adam Williamson 2011-10-28 18:15:05 EDT
I tested the fix, it looks good. I'm uploading a new live image with the fix included.
Comment 32 Adam Williamson 2011-10-28 18:58:10 EDT
If you want to test the fix for this, grab http://adamwill.fedorapeople.org/adamwkde-20111028-x86_64.iso (sha256sum 97a4d9429ec4e06cbb9d3ebeb010fd044ae66d49abeb58915714bb8f4cb49594 ). It has the fix for this and the fix for the qxl bug, so both qxl and cirrus VMs should work with it. Works for me.
Comment 33 Fedora Update System 2011-10-29 02:30:30 EDT
qt-4.8.0-0.23.rc1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 34 Red Hat Bugzilla 2013-10-03 20:21:29 EDT
Removing external tracker bug with the id '21754' as it is not valid for this tracker