Same issue here, gdm just won't start, any idea on how to fix this? using nvidia original drivers btw.
Same issue here, gdm just won't start, any idea on how to fix this? using nvidia original drivers btw.
I think this problem is related to selinux and its policies regarding nvidia. You can now either wait for the update to selinux-policy-3.10.0-55 or temporarily set selinux to permissive mode (edit /etc/selinux/config), which has resolved the problem for me.
As soon as the update happens, though, I'd recommend resetting selinux to enforce mode or use setenforce 1 as soon as the system has passed gdm. Better yet: use the NVIDIA installation guide MrMarcus has posted down below to install the selinux updates directly from koji.
Last edited by kindofautomatic; 9th November 2011 at 10:46 AM.
If you are using the NVIDIA propietary drivers, make sure that you have add the selinux policy regarding the GDM.
And don't forget to add nomodeset to the /boot/grub2/grub.cfg
See Leigh's guide for NVIDIA installation on Fedora 16. (escpecialy point nr. 4)
http://www.fedoraforum.org/forum/sho...d.php?t=204752
Ok i didn't notice, new Nvidia drivers were available on nvidia.org for linux 64 bit, downloading and mounting the windows partition on the file system let me download and install this new driver, which fixed gdm for me.
Well personal note, redownload driver before each update. Ty for your help.
Possible solution: get updated drivers.
The updated policy should be in updates soon.
https://bugzilla.redhat.com/show_bug.cgi?id=748069
https://admin.fedoraproject.org/upda...3.10.0-55.fc16
I've deleted .gnome2, .gnome2_private, .config, .gconf, and .gconfd in $HOME. GNOME still presents the "unhappy computer" screen.
There are several errors in /var/log/Xorg.0.log and in $HOME/.xsession_errors, but I haven't made it through all of them to see which one is causing GNOME to crash.
(optional: Rename the logs, then restart.)
After the failure, switch to VC (ctrl+alt+f2) and run for example:
to show only errors.Code:cat /var/log/Xorg.0.log | grep "(EE)"
* Yet Another Simple Script Installer (YASSI): https://forums.fedoraforum.org/showthread.php?323099
* Shell Wrapper and Runtime Modifier (SWARM): <not yet usable>
* EFI Cheatsheet :: http://forums.fedoraforum.org/showthread.php?t=298546
* Windows 8+ & Fedora 20+ Dualboot :: http://forums.fedoraforum.org/showthread.php?t=298161
I never get as far as a user login. I believe these are in the user's home directories. They are not accessed until you are actually authenticated. If you used something like automount (I.E. like a university lab setup would) The filesystem containing "/home/someusername" might not be even mounted or accessible at this point.
So I don't think it's pertinent to the problem. Removing them should not cause any problems that I can think of (they should just be rebuilt on the next successful login); but, not sure it helps in this case.
But, please keep on suggesting. I had not even considered these files and had to think why or why not this suggestion may or may not workMany heads are a lot better than mine
![]()
Did you install the updated selinux policy to solve the issues with the nvidia drivers and gnome?
look in Leigh123linux's thread on the nvidia drivers...Code:su yum --nogpgcheck update libsepol http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.10.0/53.fc16/noarch/selinux-policy-3.10.0-53.fc16.noarch.rpm \ http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.10.0/53.fc16/noarch/selinux-policy-targeted-3.10.0-53.fc16.noarch.rpm --enablerepo=u*g
http://forums.fedoraforum.org/showthread.php?t=204752
Hi there,
I think you may be on to something. I was able to force an X-session by the following method:
1- Login to another virtual console via CTL+ALT+F2 (any Function Key should work unless it's being used)
2- login as root
3- Rm the x-session lock file from the tmp directory ( rm /tmp/X0-lock )
4- try to login as user by su - yourusername
5- startx
At this point the despised Gnome shell started; but, the networking did not work. Also, sometimes it hung completely.
By trial and error I found out that if I started startx as root I get a working xsession; however, that's useless because it's really stupid to do things like browsing as root.
Next I will see what driver is being used when I startx manually![]()
I've had the same problem and solved it by:
ctrl+alt+f2
login as root
And reboot.Code:yum remove selinux-policy selinux-policy-targeted yum update libsepol yum --nogpgcheck install libsepol http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.10.0/55.fc16/noarch/selinux-policy-3.10.0-55.fc16.noarch.rpm --enablerepo=u*g yum --nogpgcheck install http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.10.0/55.fc16/noarch/selinux-policy-targeted-3.10.0-55.fc16.noarch.rpm --enablerepo=u*g
Last edited by Salamandra; 9th November 2011 at 08:35 PM.
Linux User #365705
Same issue here with KDE.
I can login level 3 and startx and I get up and running with a doggy X.
If I just run just xterms and nothing else, CPU usage is normal. If I start any graphical app X takes 98-99% of the CPU.
I'm using the kmod-nvidia (which did get updated) and I have NO nomodset in my grub and there is no rdblacklist=neuveau. Is that line also still required?
Mark N.
Perpetual Newbie
--
I wanted to proclaim myself "The Typo King" but there's way too much competion. :p
411874 Get Counted
An older thread
http://www.fedoraforum.org/forum/sho...d.php?t=266030
Selinux seems to be prohibiting the startup of something on the desktop.
---------- Post added at 03:04 AM ---------- Previous post was at 02:55 AM ----------
I found an old thread that can be fixed by
1. turning off selinux
or
2. touch /.autorelabel as root and then reboot.
autolabel worked for me from Fedora 15 upgrading to Fedora 16.