Hide Forgot
Created attachment 490623 [details] dmesg output Description of problem: System crashes with nouveau drivers loaded Version-Release number of selected component (if applicable): How reproducible: This Sony laptop has a switch labeled "stamina" and "speed". In "speed" mode, it turns on an nVidea graphics chip. Starting the system in "speed" mode causes a crash. Steps to Reproduce: 1. Power off 2. Set to speed mode 3. start and login to gnome shell. Wait a few. Actual results: Gnome shell screen looks like static, not coherent graphical layout. Expected results: Additional info:
Created attachment 490624 [details] Xorg log file
lspci output for video card: nVidia Corporation G72M [GeForce Go 7400] (rev a1)
there's no error in the X log. Can we get ~/.xsession-errors ?
Created attachment 490664 [details] .xsession-errors file The system didn't crash this time, but screen was unreadable. I was able to mouse to the right spot to do a clean shutdown.
I see you have a messy config, do you have the same problem with a new user? If so we may need the /var/log/messages with drm.debug=15 (see the debug instructions page I linked to in email for more details).
Created attachment 490688 [details] Clean user logs using only F15 defaults (xsession,
tar file contains /var/log/messages, /var/log/Xorg.0.log, dmesg output, xsession-errors, and smolt profile booting with debug parameters.
Created attachment 490800 [details] dmesg.txt from the archive
Created attachment 490801 [details] messages from the archive
Created attachment 490802 [details] smoltprofile.txt from the archive
Created attachment 490803 [details] Xorg.0.log from the archive
Created attachment 490804 [details] xsession-errors from the archive
Here's what I see when I login via the test user with the nVidia card active: http://www.youtube.com/watch?v=1OahX8mV-2U
Smolt profile updated to show nVidia profile. Problem with the latest Gnome 3 and kernel (as of April 18).
http://www.smolts.org/client/show/pub_2e1dcbc6-c0c7-4634-94ed-e052a0dfb239
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.