Description of problem: After upgrading the Xorg stack to ABI version 1.18, running X in a virtual machine is essentially impossible because of low responsiveness. Version-Release number of selected component (if applicable): xorg-x11-server-1.18.0-0.2.20150907.fc23 How reproducible: Always. Steps to Reproduce: 1. Launch a GNOME session in a VM. Actual results: Flickering screen, huge latencies of screen refresh and X input actions. Expected results: Normal behaviour. Additional info: - X used to behave as expected for ABI version 1.17 as can be verified by downgrading the Xorg stack. - The QXL driver package which is used by gnome-boxes has only been rebuilt for ABI version 1.18 but not updated itself. - The issue is possibly rather related to the X driver packages handling mouse and keyboard events.
Okay we somehow seem to have lost GLX_MESA_copy_sub_buffer in the server GLX extension string. I'm assigning this to ajax, though I'll keep looking at it
xorg-x11-server-1.18.0-0.3.20150907.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16471
see also bug 1249731 where i did the same "fix" for rhel 7.
In my VirtualBox Rawhide guest, I immediately get the "Oh no!" screen instead of the GDM login screen after today's Rawhide updates (including xorg).
(In reply to Andre Robatino from comment #4) > In my VirtualBox Rawhide guest, I immediately get the "Oh no!" screen > instead of the GDM login screen after today's Rawhide updates (including > xorg). However, the same update on F23 does fix the problem when running GNOME. (BTW, I had been able to use MATE without the issue before the update, as a workaround.)
xorg-x11-server-1.18.0-0.3.20150907.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Andre Robatino from comment #4) > In my VirtualBox Rawhide guest, I immediately get the "Oh no!" screen > instead of the GDM login screen after today's Rawhide updates (including > xorg). Ignore - this was a result of https://bugzilla.redhat.com/show_bug.cgi?id=1265913 (an selinux bug).