Version-Release number of selected component: xorg-x11-server-Xorg-1.14.2-3.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-3cGBuj/database -seat seat0 -nolisten tcp vt1 crash_function: AttachOutputGPU executable: /usr/bin/Xorg kernel: 3.9.9-302.fc19.x86_64 runlevel: unknown uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #4 AttachOutputGPU at dispatch.c:3946 #5 xf86AutoConfigOutputDevice at xf86Crtc.c:3358 #6 xf86AutoConfigOutputDevices at xf86Init.c:371 #7 InitOutput at xf86Init.c:943
Created attachment 773496 [details] File: backtrace
Created attachment 773497 [details] File: cgroup
Created attachment 773498 [details] File: core_backtrace
Created attachment 773499 [details] File: dso_list
Created attachment 773500 [details] File: environ
Created attachment 773501 [details] File: limits
Created attachment 773502 [details] File: maps
Created attachment 773506 [details] File: open_fds
Created attachment 773507 [details] File: proc_pid_status
Created attachment 773511 [details] File: var_log_messages
Hi I don't know what caused this event or how to log it, but I will be glad to provide any information needed.
Situation: After booting my Fedora 19, it displayed a black screen with no possibility of TTY changing. All the processes started properly but I still cannot work with my Fedora. Associate Problems: You can't change TTY because the system retry to load this package on the six available ttys with no success, finally crashing them. Solved : I've an nVidia graphic card (geForce 525M). In grub enter (e), add 'nouveau.modeset=0' after 'rhgb quiet'. If you have AMD try radeon.modeset=0.
please test this one : https://admin.fedoraproject.org/updates/FEDORA-2013-12995/xorg-x11-server-1.14.2-5.fc19
Installing the bugfix, I don't have to add 'noueavu.modeset=0' every time booting F19. "yum update --enablerepo=updates-testing xorg-x11-server-Xorg-1.14.2-4.fc19" seems to be the solution :). Thanx Sergio Monteiro Basto.
So I'm closing this bug since xorg-x11-server-Xorg-1.14.2-4.fc19 fix it, you may reopen it .