[SOLVED] Fedora 16 Upgrade Disaster - Page 2
FedoraForum.org - Fedora Support Forums and Community
Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Results 16 to 30 of 59
  1. #16
    Join Date
    Nov 2011
    Posts
    6

    Re: Fedora 16 Upgrade Disaster

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

  2. #17

    Re: Fedora 16 Upgrade Disaster

    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.

  3. #18
    Join Date
    Nov 2009
    Posts
    13

    Re: Fedora 16 Upgrade Disaster

    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

  4. #19
    Join Date
    Nov 2011
    Posts
    6

    Re: Fedora 16 Upgrade Disaster

    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.

  5. #20
    leigh123linux Guest

    Re: Fedora 16 Upgrade Disaster

    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

  6. #21
    Join Date
    Nov 2011
    Posts
    2

    Re: Fedora 16 Upgrade Disaster

    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.

  7. #22
    Join Date
    May 2011
    Location
    Confoederatio Helvetica (Swissh)
    Age
    38
    Posts
    4,276

    Re: Fedora 16 Upgrade Disaster

    (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.
    EFI Cheatsheet :: http://forums.fedoraforum.org/showthread.php?t=298546
    Video Handler Script (VHS) (mass re-encode videos, screenrecorder, console music/webradio player, ...) :: http://forums.fedoraforum.org/showthread.php?t=299182
    Windows 8+ & Fedora 20+ Dualboot :: http://forums.fedoraforum.org/showthread.php?t=298161

  8. #23
    Join Date
    Jan 2007
    Posts
    49

    Re: Fedora 16 Upgrade Disaster

    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

  9. #24
    Join Date
    Nov 2011
    Posts
    2

    Re: Fedora 16 Upgrade Disaster

    Quote Originally Posted by leigh123linux
    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.

  10. #25
    Join Date
    Aug 2009
    Posts
    8,486

    Re: Fedora 16 Upgrade Disaster

    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

  11. #26
    Join Date
    Jan 2007
    Posts
    49

    Re: Fedora 16 Upgrade Disaster, SOLVED the problem, somewhat

    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

  12. #27
    Join Date
    Sep 2004
    Location
    Spain
    Posts
    335

    Re: Fedora 16 Upgrade Disaster

    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.
    Last edited by Salamandra; 9th November 2011 at 08:35 PM.
    Linux User #365705

  13. #28
    Join Date
    Jul 2005
    Location
    Wine Country, California
    Posts
    2,850

    Re: Fedora 16 Upgrade Disaster

    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

  14. #29
    Join Date
    Feb 2007
    Posts
    96

    Re: Fedora 16 Upgrade Disaster

    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.

  15. #30
    Join Date
    Nov 2011
    Posts
    1

    Re: Fedora 16 Upgrade Disaster

    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.

Page 2 of 4 FirstFirst 1 2 3 4 LastLast

Similar Threads

  1. Disaster after trying preupgrade to Fedora 13
    By Wywern in forum Hardware & Laptops
    Replies: 16
    Last Post: 15th June 2010, 02:28 PM
  2. FC9 Disaster
    By GaJim in forum Installation, Upgrades and Live Media
    Replies: 8
    Last Post: 5th July 2008, 04:47 PM
  3. Why is Fedora a multimedia disaster? - Here is why.
    By Valent in forum Using Fedora
    Replies: 15
    Last Post: 18th April 2007, 01:06 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •