Created attachment 696273 [details] uname -a, lsmod, lspci, dmesg, rpm -qa and part of /var/log/messages Description of problem: When I use Firefox and tvtime together during my X window session, with or without other programs being open, the X session will freeze. That is the session no longer accepts keyboard or mouse input and the last screen displayed remains. The net may also be down, if so, reboot is needed. If not, sometimes I can recover the system, not the X session, by killing X from a ssh session on another system. Version-Release number of selected component (if applicable): firefox 18.0.2-1 tvtime 1.0.2-22 xorg-x11-drv-nouveau 1.0.6-1 fvwm 2.6.5-3 mate-panel 1.5.4-1 How reproducible: Run tvtime and firefox at the same time on different window panes and wait for the Nouveau PFIFO DMA_PUSHER and PGRAPH DATA_ERROR messages to start piling up in the messages log file. For me on the system, this process does not take very long. If you run tvtime or firefox with the other one NOT running, the problem does not occur. Steps to Reproduce: 1. Run firefox in one fvwm window pane. 2. Run tvtime (or a movie using vlc sometimes works) in another window pane. 3. Wait for the Nouveau PFIFO DMA_PUSHER and PGRAPH DATA_ERROR messages in /var/log/messages. Session and system may take some minutes to actually freeze up. Actual results: X window session will freeze with unresponsive keyboard and mouse. Network may also stop requiring a reboot. If network is still up, a ssh session from another system can be used to kill the X program without requiring the reboot. Expected results: To have firefox and tvtime (or vlc) to operate normally without the freezing and Nouveau error entries in the /var/log/messages file. Additional info: Attachments are included with: uname -a, lsmod, lspci, dmesg, rpm -qa and the last set of nouveau crash entries from /var/log/messages.
I have updated the system to the latest kernel: 3.7.9-205.fc18.x86_64, and several of the xorg packages have been updated as well: 1.13.2-4.fc18.x86_64 This issue appears to no longer be a problem as of this date.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.