Created attachment 509982 [details] xsession for gnome-shell release 4.fc15/rpmfusion kmod-nvidia Description of problem: After creating a brand-new user account and logging in to GNOME, the top bar appears and the desktop looks ready for use. However, it is frozen. The mouse moves just fine, but nothing responds to clicks or keyboard events. Killing X with crtl-alt-backspace is the only way to return to gdm. I can't do VT switches from this state. Switching to nouveau results in a freeze before gnome-shell even appears. The only way to continue using the computer is to use fallback mode, which works with both nouveau and nvidia. Version-Release number of selected component (if applicable): Name : gnome-shell Arch : i686 Version : 3.0.2 Release : 4.fc15 How reproducible: Always. Steps to Reproduce: 1. Be running gnome-shell 4.fc15 and nvidia drivers from rpmfusion 2. Log in 3. Profit! Actual results: gnome-shell appears but is frozen. Expected results: gnome-shell should respond to keyboard/mouse events. Hardware: nVidia Corporation G72M [GeForce Go 7300] Additional info: The behaviour is the same with both my usual user account and a newly created one. The previous release of gnome-shell (3.fc15) hung without showing gnome-shell on nvidia with clutter fbconfig errors (Bug #716572), but worked OK with nouveau. I originally commented on that bug but was asked to open this one after the -4 release.
I'm encountering the same issue when using the nvidia proprietary driver, same sequence, same symptoms, similar but slightly different hardware: nVidia Corporation G72M [GeForce Go 7400] (rev a1) However, using the noveau driver does not cause me any problems. Laptop is Dell D820, 15-inch screen 1920x1200 resolution, 2G RAM. Other hardware below, smolt profile is http://www.smolts.org/client/show/pub_07e1b1fd-056c-4e74-ad66-c02a7e33e066 277 roland> rpm -q gnome-shell gnome-shell-3.0.2-4.fc15.i686 278 roland> uname -a Linux aristarchus.rlent.pnet 2.6.38.8-32.fc15.i686 #1 SMP Mon Jun 13 20:01:50 UTC 2011 i686 i686 i386 GNU/Linux
I just updated F15 via yum followed by retrying the nvidia related packages: Aug 07 13:53:18 Installed: nvidia-xconfig-1.0-9.fc15.i686 Aug 07 13:53:20 Installed: nvidia-settings-1.0-11.fc15.i686 Aug 07 13:53:33 Installed: 1:xorg-x11-drv-nvidia-libs-280.13-1.fc15.i686 Aug 07 13:53:34 Installed: 1:akmod-nvidia-280.13-2.fc15.i686 Aug 07 13:53:37 Installed: 1:xorg-x11-drv-nvidia-280.13-1.fc15.i686 Aug 07 13:53:56 Installed: 1:kmod-nvidia-2.6.40-4.fc15.i686-280.13-2.fc15.i686 Aug 07 13:53:56 Installed: 1:kmod-nvidia-280.13-2.fc15.i686 I also used dracut to build a new initramfs then rebooted. Same symptoms as before, boot is fine, I get the login screen, but after login, gnome-shell appears to freeze; the mouse moves, but I can't do anything except switch to to a virtual terminal to switch back to runlevel 3. I removed all the about packages, rebuilt the initramfs and am back to using nouveau with Compiz mode. I'd really like to get some feedback on what information is needed to track this down. Loss of accelerated graphics on this machine is a big disappointment as this is my primary development host. I've avoided upgrading my other nvidia-based hosts pending some movement in this issue. Someone tell me what info they need and I'll poke around and try to get it.
Shortly after the above post, the nouveau driver crashed/hung. Here's some of what I see in syslog: Aug 7 21:20:55 aristarchus kernel: [25861.538014] [drm] nouveau 0000:01:00.0: PGRAPH - ERROR nsource: ILLEGAL_MTHD nstatus: INVALID_STATE BAD_ARGUMENT PROTECTION_FAULT Aug 7 21:20:55 aristarchus kernel: [25861.538014] [drm] nouveau 0000:01:00.0: PGRAPH - ch 1 (0x000d4000) subc 6 class 0x024a mthd 0x0400 data 0x00000000 Aug 7 21:20:55 aristarchus kernel: [25861.538544] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x0000 Data 0x80000018 Aug 7 21:20:55 aristarchus kernel: [25861.538625] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x0184 Data 0xd8000002 Aug 7 21:20:55 aristarchus kernel: [25861.538986] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x0184 Data 0xd8000002 Aug 7 21:20:55 aristarchus kernel: [25861.540197] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x0184 Data 0xd8000002 Aug 7 21:20:55 aristarchus kernel: [25861.540606] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 1/5 Mthd 0x0184 Data 0xd8000002 [...] Aug 7 21:20:58 aristarchus kernel: [25864.545455] nouveau_ratelimit: 50656 callbacks suppressed Aug 7 21:20:58 aristarchus kernel: [25864.545462] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 0 Aug 7 21:20:58 aristarchus kernel: [25864.545469] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x00010000 - Ch 0 [...] Aug 7 21:20:58 aristarchus kernel: [25864.545731] [drm] nouveau 0000:01:00.0: PFIFO still angry after 101 spins, halt Aug 7 21:20:58 aristarchus kernel: [25864.597096] [drm] nouveau 0000:01:00.0: GPU lockup - switching to software fbcon
Same hardware as Roland and Gabe: - Dell Latitude D820 - nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] With the latest release of akmod-nvidia and the lot, gnome-shell just won't react to any input event, regardless of SELinux (tried with setenforce 0, the same). No problems after switching back to nouveau, just the usually bad performance.
I'm going to take myself off this one. My D820 nvidia chip has died. I don't know if nouveau killed it or if just happened to die about this time. But I can "sort-of" run in reduced resolution with nouveau for a while, but eventually it locks up and has to be rebooted. And with Windows XP, I get a BSOD pointing to the nvidia driver.
My D620's onboard video fried itself last month. I am no longer able to assist with this bug. Interesting that Roland had the same thing happen.
Once is odd, twice is coincidence, three times.... Well, unless someone else reports the same outcome, but it COULD be the driver. See my comment #3 where I have some of the log messages from the misbehaving driver. It's plausible there's a problem exacerbating the known overheating issue. Oh well, I'm holding my other systems at FC14; much as I'd like to help, I'm not quite willing to risk the possibility of it being the driver.
These laptops were known for heat dissipation problems causing the GPU to de-solder itself from the mainboard. Dell had a huge recall a few years back, which I missed out on. Here's hoping this is coincidence.
It unfortunately doesn't change the fact GNOME shell freezes with nVidia driver 280.13-2 and some others. :-) It's definitely the driver, as the shell works fine (but extremely slowly) with Nouveau on the same hardware. Also, even Nouveau does have its shortcomings - during periods of high system activity, especially combined with high I/O (such as hard swapping and CPU load at the same time) it will also occasionally freeze. But that would be a different issue for a different ticket. :-)
I am having a similar problem with a Geoforce FX 5200. The Gnome Shell loads fine and then is so unresponsive as to be inoperable. The same computer worked perfectly with Gnome 2.32.0 with full Compiz effects. Of course, without an xorg.conf loaded it will work well in fallback mode. I have tried the RPMFusion nvidia driver, the proprietary driver from Nvidia and the nouveau driver. This is the tail of my Xorg.0.log [ 70.793] Warning: Xalloc: requesting unpleasantly large amount of memory: 0 bytes. [ 78.342] Warning: Xalloc: requesting unpleasantly large amount of memory: 0 bytes. [ 78.520] Warning: Xalloc: requesting unpleasantly large amount of memory: 0 bytes. [ 287.760] Warning: Xalloc: requesting unpleasantly large amount of memory: 0 bytes. Here is my current xorg.conf (I have tried various configurations with the same result) # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 1.0 (buildmeister@builder75) Wed Jan 27 03:03:53 PST 2010 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" FontPath "/usr/share/fonts/default/Type1" EndSection Section "ServerFlags" Option "Xinerama" "0" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from data in "/etc/sysconfig/keyboard" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "us" Option "XkbModel" "pc105" EndSection Section "Monitor" # HorizSync source: xconfig, VertRefresh source: xconfig Identifier "Monitor0" VendorName "Unknown" ModelName "CRT-0" HorizSync 31.5 - 64.0 VertRefresh 56.0 - 65.0 Option "DPMS" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce FX 5200" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "0" Option "TwinViewXineramaInfoOrder" "CRT-0" Option "metamodes" "1280x1024 +0+0" SubSection "Display" Depth 24 EndSubSection EndSection
Same issue on a Dell D820 laptop. Gnome-shell and rpmfusion nvidia driver with akmod. Gnome shell and GDM are broke. Unable to select user to login. Also if I startx from a console login I am unable to click on anything. Everything presents correctly. I attempted to install the driver from NVIDIA still presents itself. I upgraded to F16 trying to rectify the problem and it still exists.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping