[SOLVED] Fedora 16 Upgrade Disaster - Page 2

Geval · #16 9th November 2011, 09:15 AM

Same issue here, gdm just won't start, any idea on how to fix this? using nvidia original drivers btw.

kindofautomatic · #17 9th November 2011, 09:24 AM

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.

MrMarcus · #18 9th November 2011, 09:31 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

Geval · #19 9th November 2011, 10:17 AM

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.

leigh123linux · #20 9th November 2011, 10:17 AM

Quote:

Originally Posted by MrMarcus

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

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

grunch · #21 9th November 2011, 05:11 PM

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.

sea · #22 9th November 2011, 05:16 PM

(optional: Rename the logs, then restart.)
After the failure, switch to VC (ctrl+alt+f2) and run for example:

Code:

cat /var/log/Xorg.0.log | grep "(EE)"

to show only errors.

bbehnam · #23 9th November 2011, 05:19 PM

Quote:

Originally Posted by Finalzone

How about resetting gnome session?
From File Manager (Nautilus),
- press Ctrl+H to reveal hidden files and folders.
- Delete folders like .gnome .gnome2 .gconf .gconfd .metacity (or back up if you want to keep custom setting)
- Log out

From terminal as user

Code:

rm -fr .gnome .gnome2 .gconf .gconfd .metacity

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 work

Many heads are a lot better than mine

grunch · #24 9th November 2011, 05:26 PM

Quote:

Originally Posted by leigh123linux

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'm not sure which (if either) of these is the problem. But disabling selinux (in /etc/selinux/config) allowed me to successfully log in. I look forward to being able to re-enable selinux.

Interestingly, 'yum distro-sync' Downgraded several packages.

***DBelton*** · #25 9th November 2011, 05:34 PM

Did you install the updated selinux policy to solve the issues with the nvidia drivers and gnome?

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

look in Leigh123linux's thread on the nvidia drivers...

http://forums.fedoraforum.org/showthread.php?t=204752

bbehnam · #26 9th November 2011, 05:39 PM

Quote:

Originally Posted by harshad1

Reverted to nouveau drivers. This let me boot into and use gnome-shell.

However power management is a disaster. Suspend doesn't work, the power button doesn't work and neither dconf nor gconf seem to have any settings that might affect a thing....

Don't know if reinstalling the nvidia drivers again will break things again or fix them.

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

Salamandra · #27 9th November 2011, 07:33 PM

I've had the same problem and solved it by:

ctrl+alt+f2

login as root

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

And reboot.

u-noneinc-s · #28 9th November 2011, 08:32 PM

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?

Ex_Soft · #29 9th November 2011, 08:50 PM

Quote:

Originally Posted by Salamandra

I've had the same problem and solved it by:

ctrl+alt+f2

login as root

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

And reboot.

Many thanks. This has resolved my same problem.

ogradye · #30 10th November 2011, 03:04 AM

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.