Fedora 20 – some post installation issues may bother

Even though Fedora wiki has posted some common issues after the system is upgraded into Fedora 20, interestingly, none of them applies the issues I have encountered:( Anyway, this post is for guys who may have a little bit chance of suffering similar issues of newly upgraded Fedora 20. Cheers~

0. fedup

You could use ‘yum’ to do the upgrading (http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum). I use ‘fedup’ (https://fedoraproject.org/wiki/FedUp)to upgrade from Fedora 18 to 20. It works all right except you have to manually insert the gpg keys for RPM fusion repos if they are in your yum repo. Unless ‘fedup’ runs smoothly, there would be no way to see the ‘System Upgrade’ in the grub after reboot…

Error: https://bugzilla.redhat.com/show_bug.cgi?id=1044086
Downloading failed: GPG key retrieval failed: [Errno 14] curl#37 – “Couldn’t open file /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-x86_64”

a. Bypass the gpg check
fedup-cli –network 20 –nogpgcheck
b. Insert the keys manually
rpmkeys –import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-primary
rpmkeys –import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20

1. common bugs of Fedora 20


2. KVM/SELinux

Starting KVM may report the weird error like. This is related with SELinux. However, it is not SELinux’s fault. The damn root cause is nvidia…Checking out these 2 latest bugs from RedHat…


/usr/bin/qemu-system-x86_64: error while loading shared libraries: libGL.so.1: failed to map segment from shared object: Permission denied

sudo setsebool -P virt_use_execmem 1

3. ddclient

My ddclient continued reporting SSL failure on verifying server certificate and could not get connected with my dynamic DNS server (HE) like below. It turns out that the SSL authentication disabled before by default is enabled in ddclient. To force the connection, ssl=no has to be added into /etc/ddclient.conf for your DDNS entry.

WARNING:  cannot connect to dyn.dns.he.net:443 socket:  IO::Socket::IP configuration failed SSL connect attempt failed with unknown error error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
FAILED:   updating daveti.me: Could not connect to dyn.dns.he.net.

4. nvidia (again)

There was a long story about my previous painful experience with nvidia (https://davejingtian.org/2013/03/02/nvidia-sucks-issues-related-with-the-official-gpu-driver-and-cuda-on-linux-fedora-18/). On my Fedora 18, I installed the nvidia property driver, deleted it (ASAP) and recovered the nouveau driver. However, all the driver configure files generated by nvidia was left there and they did not bother Fedora 18. Then it became the nightmare for Fedora 20 – display resolution was unable to change (640*480). Only rescue mode could have a normal display. Deeper investigation finds nouveau driver was not loaded, which reminds me all the changes happened under /etc/modprobe.d – Remove the nvidia conf file and unblock nouveau mod in the blacklist.conf. God bless us!

5. some daemons

This is weird too. Some daemons were not started automatically once the system is boot as they used to, like ddclient and tcsd. Anyway, fix that:

systemctl status XXX
systemctl enable XXX –system

About daveti

Interested in kernel hacking, compilers, machine learning and guitars.
This entry was posted in Linux Distro and tagged , , , , , , , . Bookmark the permalink.

1 Response to Fedora 20 – some post installation issues may bother

  1. Pingback: Fedora 21 Workstation – some post installation issues after fedup from 20 | davejingtian.org

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.