Description of problem: After those upgrades: Jul 12 12:24:11 Updated: xorg-x11-server-common-1.14.2-3.fc19.x86_64 Jul 12 12:24:13 Updated: xorg-x11-server-Xorg-1.14.2-3.fc19.x86_64 Jul 12 12:24:13 Updated: xorg-x11-drv-qxl-0.1.1-0.11.20130514git77a1594.fc19.x86_64 xorg fails to start. Relevant bits at xorg log: [ 754.868] (++) using VT number 0 [ 754.868] Fatal server error: [ 754.868] xf86OpenConsole: VT_ACTIVATE failed: No such device or address [ 754.868] [ 754.868] (EE) Please consult the Fedora Project support at http://wiki.x.org for help. [ 754.868] (EE) Please also check the log file at "/var/log/Xorg.0.log" for ad ditional information. [ 754.868] (EE) Downgrading to the previous version solved the issue.
Created attachment 772890 [details] Xorg.0.log file
Hi, could you please test : Package xorg-x11-server-1.14.2-4.fc19: * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xorg-x11-server-1.14.2-4.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12886/xorg-x11-server-1.14.2-4.fc19 then log in and leave karma (feedback).
(In reply to Sergio Monteiro Basto from comment #2) > Hi, could you please test : > > Package xorg-x11-server-1.14.2-4.fc19: > * was pushed to the Fedora 19 testing repository, > * should be available at your local mirror within two days. > Update it with: > # su -c 'yum update --enablerepo=updates-testing > xorg-x11-server-1.14.2-4.fc19' > as soon as you are able to. > Please go to the following url: > https://admin.fedoraproject.org/updates/FEDORA-2013-12886/xorg-x11-server-1. > 14.2-4.fc19 > then log in and leave karma (feedback). Worked. Thanks!
Also had a black screen when updating to F19 with fedup, from F18. Although i did not have the same error message, updating xorg-x11-server from updates-testing as described fixed it too. Thanks !
I got this problem a week ago. The workaround I applied was to downgrade xorg-x11-server-Xorg from 1.14.2-3 to 1.14.1-4. Do this is considered as a solution? Best regards!
(In reply to Abdel Gadiel Martínez Lassonde from comment #5) > I got this problem a week ago. The workaround I applied was to downgrade > xorg-x11-server-Xorg from 1.14.2-3 to 1.14.1-4. > > Do this is considered as a solution? no and with xorg-x11-server-Xorg 1.14.2-4 from updates-testing ?
It worked.
Had the same problem. Last update (xorg-x11-server-Xorg-1.14.2-4.fc19.x86_64) fixes the problem. Thank you. :-)
this bug seems fixed with current release , can I close it ?
(In reply to Sergio Monteiro Basto from comment #9) > this bug seems fixed with current release , can I close it ? Sure, it got fixed. I'll close it.