Created attachment 563957 [details] Xorg.0.log from Fc17 Alpha RC2 KDE spin in spice-enabled guest Description of problem: F17 alpha RC2 boots to desktop but then is unresponsive - e.g. click on the Fedoa menu (the mouse cursor does work) and nothing happens; right click on the desktop and the menu flashes and a shrunken part-animated desktop menu shows up. But this trick only seems to work once, after which I can only get screen updates by interacting with the desktop and typing or clicking blind and then switching to another vt (inside the VM) and back. In this way I can launch e.g. konsole and see output from the command-line. It's an interesting concept for a workflow but I don't think it will catch on. This was observed with qxl in the guest, but using video:vesa or display: vnc (or both) doesn't make any difference. Guest packages: kernel-3.3.0-0.rc3.git5.1.fc17.x86_64 xorg-x11-drv-qxl-0.0.21-16.fc16.x86_64 xorg-x11-drv-vesa-2.3.0-15.fc17.x86_64 kde-workspace-4.8.0-7.fc17.x86_64 qt-4.8.0-8.fc17.x86_64 Host packages: spice-server-0.10.1-1.fc16.x86_64 spice-gtk-0.9-1.fc16.x86_64 virt-manager-0.9.1-1.fc16.noarch libvirt-0.9.6-4.fc16.x86_64
Fedora-17-Nightly-20120213.15-i686-Live-kde.iso - last nightly CD that started fine. 20120214 and later are hangs when KDE almost started.
At hackfest today, christoph witnessed the spice/qxl did indeed hang shortly after (auto)login. a bit of screen corruption, I mostly assumed some sort of qxl video driver issue. I'll try to reproduce myself tomorrow, see if we can short this (and the ConsoleKit) thing out, or at least get some more useful debugging.
I tested with xdriver=vesa in vmware (because vmware xorg driver crashes - bug 782995).
(In reply to comment #1) > Fedora-17-Nightly-20120213.15-i686-Live-kde.iso - last nightly CD that started > fine. 20120214 and later are hangs when KDE almost started. Could it be llvmpipe? http://koji.fedoraproject.org/koji/buildinfo?buildID=299348 Indeed kde-workspace-4.8.0-7.fc17 is in Alpha-RC2 and http://koji.fedoraproject.org/koji/buildinfo?buildID=299348 but not in http://koji.fedoraproject.org/koji/taskinfo?taskID=3787932
Whoops. Make that: Indeed kde-workspace-4.8.0-7.fc17 is in Alpha-RC2 and http://koji.fedoraproject.org/koji/taskinfo?taskID=3790203 but not in http://koji.fedoraproject.org/koji/taskinfo?taskID=3787932
Confirmed, it works fine with kde-workspace-4.8.0-6. With -7 whole desktop freezes with qxl and vga drivers.
OK, compositing by default + llvmpipe then is fail so far. May be worth filing bugs against affected drivers.
Alright, looks like llvmpipe simply isn't ready for testing yet, so we'll need to disable compositing by default. details in the #fedora-kde irc chat below. [02/21/12 07:47] <rdieter> .bug 794835 [02/21/12 07:47] <zodbot> rdieter: Bug 794835 kde desktop unresponsive in F17 alpha RC2 with virt-manager - https://bugzilla.redhat.com/show_bug.cgi?id=794835 [02/21/12 07:48] <rdieter> d1saster: ^^ so, seems like compositing+llvmpipe doesn't work too well for qxl and vga drivers at least. [02/21/12 07:48] <d1saster> rdieter: wasn't that clear after ajax said that the tfp enhancements are not in place yet? [02/21/12 07:49] <jreznik> revert it? [02/21/12 07:49] <d1saster> if they are not in place I also hardly doubt that the gnome people will activate compositing [02/21/12 07:49] <rdieter> hmm... ok, no that wasn't clear to me. [02/21/12 07:49] <d1saster> it's just damn slow to copy the window pixmap every time [02/21/12 07:49] <rdieter> if that indeed is a hard requirement, jreznik's suggestion is the best [02/21/12 07:50] <rdieter> d1saster: thanks [02/21/12 07:50] <d1saster> yw :) [02/21/12 07:50] <d1saster> the fedora feature page for this is imho a bit misleading [02/21/12 07:50] <rdieter> d1saster: do you recall if ajax gave any indication when/if it *would* be ready? [02/21/12 07:50] <d1saster> it suggests that things are almost done, but from the conversation with ajax I would say they are not [02/21/12 07:50] <jreznik> :) [02/21/12 07:51] <rdieter> else, I can ask myself later. [02/21/12 07:51] <rdieter> (and we can open a bug to track it) [02/21/12 07:51] <d1saster> he couldn't even say what the opengl render string would be, so I doubt that mesa 8.0 contains the appropriate code [02/21/12 07:51] <rdieter> probably should have a tracking bug regardless I guess
marking as alpha blocker, the DE is essentially non-functional (matches criteria 19, being able to run a browser/terminal app at least). It's an EasyFix, we'll mark [Compositing] Enabled=false in kwinrc again. This will at least allow testing for those folks who choose to try enabling it manually.
That's the wrong fix. It will also disable compositing by default for all the hardware drivers, which are perfectly fine and for which we want testing for the compositing. We should rebuild kde-workspace without the llvmpipe compositing fix instead.
Without the llvmpipe compositing patch, I mean.
Please submit the build as an update when it's done. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
kde-workspace-4.8.0-8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kde-workspace-4.8.0-8.fc17
Package kde-workspace-4.8.0-8.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kde-workspace-4.8.0-8.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2121/kde-workspace-4.8.0-8.fc17 then log in and leave karma (feedback).
+1 blocker on this, it's going to break KDE on VMs and also probably some 'generic' cards. We had a bad experience in F16 with a similar-impact bug which we didn't take as a blocker until Final, so I'd rather just get this in now. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
+1 blocker
okay, that's three votes, accepting as blocker. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
RC4 Fedora-17-Alpha-i686-Live-KDE.iso don't hangs with xdriver=vesa (desktop effects enabled).
This should be fixed in RC4, the update was pulled in. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Confirm that Alpha RC4 looks good, KDE runs okay in a KVM (bar the CK warning). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
kde-workspace-4.8.0-8.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.