Upgrading Fedora 29 to Fedora 30

Fedora 30 is available now. You’ll likely want to upgrade your system to the latest version of Fedora. Fedora Workstation has a graphical upgrade method. Alternatively, Fedora offers a command-line method for upgrading Fedora 29 to Fedora 30.

Upgrading Fedora 29 Workstation to Fedora 30

Soon after release time, a notification appears to tell you an upgrade is available. You can click the notification to launch the GNOME Software app. Or you can choose Software from GNOME Shell.

Choose the Updates tab in GNOME Software and you should see a screen informing you that Fedora 30 is Now Available.

If you don’t see anything on this screen, try using the reload button at the top left. It may take some time after release for all systems to be able to see an upgrade available.

Choose Download to fetch the upgrade packages. You can continue working until you reach a stopping point, and the download is complete. Then use GNOME Software to restart your system and apply the upgrade. Upgrading takes time, so you may want to grab a coffee and come back to the system later.

Using the command line

If you’ve upgraded from past Fedora releases, you are likely familiar with the dnf upgrade plugin. This method is the recommended and supported way to upgrade from Fedora 29 to Fedora 30. Using this plugin will make your upgrade to Fedora 30 simple and easy.

1. Update software and back up your system

Before you do anything, you will want to make sure you have the latest software for Fedora 29 before beginning the upgrade process. To update your software, use GNOME Software or enter the following command in a terminal.

sudo dnf upgrade --refresh

Additionally, make sure you back up your system before proceeding. For help with taking a backup, see the backup series on the Fedora Magazine.

2. Install the DNF plugin

Next, open a terminal and type the following command to install the plugin:

sudo dnf install dnf-plugin-system-upgrade

3. Start the update with DNF

Now that your system is up-to-date, backed up, and you have the DNF plugin installed, you can begin the upgrade by using the following command in a terminal:

sudo dnf system-upgrade download --releasever=30

This command will begin downloading all of the upgrades for your machine locally to prepare for the upgrade. If you have issues when upgrading because of packages without updates, broken dependencies, or retired packages, add the ‐‐allowerasing flag when typing the above command. This will allow DNF to remove packages that may be blocking your system upgrade.

4. Reboot and upgrade

Once the previous command finishes downloading all of the upgrades, your system will be ready for rebooting. To boot your system into the upgrade process, type the following command in a terminal:

sudo dnf system-upgrade reboot

Your system will restart after this. Many releases ago, the fedup tool would create a new option on the kernel selection / boot screen. With the dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 29; this is normal. Shortly after the kernel selection screen, your system begins the upgrade process.

Now might be a good time for a coffee break! Once it finishes, your system will restart and you’ll be able to log in to your newly upgraded Fedora 30 system.

Upgrading Fedora: Upgrade complete!

Resolving upgrade problems

On occasion, there may be unexpected issues when you upgrade your system. If you experience any issues, please visit the DNF system upgrade wiki page for more information on troubleshooting in the event of a problem.

If you are having issues upgrading and have third-party repositories installed on your system, you may need to disable these repositories while you are upgrading. For support with repositories not provided by Fedora, please contact the providers of the repositories.

Fedora Project community

131 Comments

  1. Punch- to

    Better to backup your data and install Fedora 30, reinstall your apps and data. It takes a very long time to update.

    • I have used the update method since Fedora 19 with no issue ever. The dnf upgrade plugin is even better than

      fedup

      was, again upgrades of the released Fedora have never left me with a broken system. I think the update is on par with the length of time to backup your data, and do a bare metal install, overwriting everything. However, I haven’t timed both to get a definitive answer. I can imagine the upgrade would need to do more dependency checking, which of course you would want, to ensure your system started up as you had it when beginning the upgrade.

    • Gary Traverson

      How long is “very” – My upgrade appears to be stuck around step 81 of 5757 (xemacs-filesystem)

    • Michael Williamson

      It took me about 15 minutes to download the updates, then I rebooted for the upgrade before lunch and had F30 when I got back.

    • nathan

      Upgrade to me about 10-15 minutes on my Thinkpad X380 Yoga. No problems at all.

  2. Leslie Satenstein

    Hi Robin,.

    Do you have an idea why the plugin is not integrated automatically into dnf? The plugin is actually dormant until invoked. It being integrated into dnf in the current version or the new version would make upgrades actions easier for users.

    The following is off topic, but I see the upgrade responsibility being assigned to Anaconda. I envision the user launching Anaconda and clicking a checkbox to indicate a new installation or upgrade. It seems to me that it being within Anaconda fits in with Fedora upgrade management.

    By the way, Fedora 30 is GREAT!!

    • Erick

      How do you see it?? its faster??

    • simon

      Because you need to install the command mediawriter and install the version, use media wrighted to pase a custom image on a flash drive. no need to make it bootable, mediawrighter does that for you.

  3. Leslie Satenstein

    Fedora 3o includes a new user interface Deepin”.

    I have been using it since it was made available. It is very good. I like it as much as I like GNOME. It is an up and coming winner interface.

  4. Robert

    Step 1 has a typo that states “Before you do anything, you will want to make sure you have the latest software for Fedora 39 before beginning the upgrade process.” I’m sure the author meant 29.

  5. Markus

    had to recover my grub config as described in the ‘common F30 bugs’ document. It’s a i686 VM running in virtualbox with legacy boot.
    First install was F27. So I guess all i686 fedora installations might not boot after ‘dnf system-upgrade reboot’

  6. Dave Hugh

    Thanks for the post. I upgraded both my personal laptop and a DIY wireless router from 29 to 30 without issue.

    (PS In “1” did you mean 29 as opposed to 39?)

  7. Alan Olsen

    If you have downloaded extensions from extensions.gnome.org, you will want to disable them and then update them after the upgrade. Some of them cause the gnome-shell to crash, which prevents you from logging in.

    The extensions are in the users home directory in .local/share/gnome-shell/extensions

    • John Smith

      That is a useful tip.

      Two points about this:

      1) It would be nice if the most common Gnome extensions would be integrated better. For example, before upgrading to F30, I used a nice-and-easy audio extension which allowed me to quickly change from headphones to monitor speaker. After upgrading, it disappeared, too bad! Changing speakers/headphones is in my opinion too “clumsy” with the default settings (too many clicks, takes too long).

      2) It would be nice if Gnome shell does not hang/crash when an extension misbehaves. Sometimes, switching between Xorg and Wayland (login screen option) fixes such problems. That should be improved: There should be a clear feedback message for the user what the problem is and the crashing extension should be switched off automatically. After all, I assume most Gnome users will use extensions and are so all at risk.

    • Brian Vaughan

      I wish I’d seen this tip before I spent several hours trying to figure out why gnome-shell kept core-dumping.

    • km

      If do not disable Gnome extensions and have problems getting the desktop to appear, consider using another desktop such as KDE, Mate Cinammon. Cfter logging in change to the terminal interface using ctl+alt+F2, then
      sudo dnf group install “KDE Plasma Workspaces”
      then reboot and choose an alternate desktop when logging in.

      More information for older Fedora versions is at:
      https://computingforgeeks.com/install-kde-plasma-environment-on-fedora-29-fedora-28/
      https://fedoramagazine.org/installing-another-desktop/

    • Greg

      I could not login to Gnome Shell after upgrade to F30 too. I logged in via ssh (you can also via vt) and run:
      $ gsettings set org.gnome.shell disable-user-extensions true
      Then I was able to login to Gnome.
      It would be nice if Gnome/Fedora would ignore and auto-disable crashing and misbehaving extensions.

      • Gayland Gump

        Greg, I much appreciate your sharing this. I’d used the remove the .config directory with root to solve what I believe was the same problem. Consequently, considerable loss of my prior configuration was effected. Since I had saved my original .config directory, I was able to restore it in place of the newly created .config directory, apply your fix and recovered my prior setup. I concur with your wish to the developers. Thanks again.

  8. David Nowak

    The GNOME interface hangs upon bootup on my Raspberry Pi 3b/3b+. I am not a programmer, but would it not be better to develop a separate video interface module (container, I think they call them) which when added to the upgraded server code create an image could be a repeatable bootable from release to release?

  9. Boris

    Source code pro regular 10? lol why?

  10. Pawan Kumar

    After upgrading to fedora 30, my broadcom wifi stopped working.
    I have reinstalled the broadcom driver from rpm fusion, still it is not working.

    • You should definitely check out if this has been answered here https://ask.fedoraproject.org/
      Since that is the place to start for issues with using fedora.

    • David

      Ever miss the old days when you needed ndiswrapper to get Broadcom wifi to work? Or alternate kernel drivers? You haven’t lived until you’ve done that.

    • Peter Braet

      Same here, no more wifi BCM43142, and I can’t find it anymore on the old “Ask Fedora” either. Reinstalled everything, doesn’t work. Where is “Howto install BCM 43142” gone?

    • Peter Braet

      OK, got it back by reinstalling akmods akmod-wl and broadcom-wl, but had to do ‘$ sudo systemctl enable NetworkManager’ and ‘sudo systemctl reboot’ The connection is restored, but the WiFi icon is still missing.

    • John Smith

      I have same problem, my Broadcom BCM4360 worked fine in previous Fedoras, but stopped in F30. Hope to find tips in the magazine how to fix this.

      • Peter Braet

        Will Fedora please explain howto build (f30-candidate, wpa_supplicant-2.8-1.fc30.bz1703745rebuild.src.rpm)? That is the solution according to “Ask Fedora”, something from Koji, I don’t even know what that is. Please Fedora, explain howto do this and make broadcom work, because the solutions I tried only worked temporally.

        • Jonathon Poppleton

          You can download the binary rpm and right click to install it in gnome. You don’t need to build the source rpm.

          RPM:
          https://kojipkgs.fedoraproject.org//packages/wpa_supplicant/2.8/1.fc30/x86_64/wpa_supplicant-2.8-1.fc30.x86_64.rpm

          To install using the terminal:

          [jonathon@here ~]$ cd Downloads
          [jonathon@here ~]$ wget https://kojipkgs.fedoraproject.org//packages/wpa_supplicant/2.8/1.fc30/x86_64/wpa_supplicant-2.8-1.fc30.x86_64.rpm
          –2019-05-09 22:09:49– https://kojipkgs.fedoraproject.org//packages/wpa_supplicant/2.8/1.fc30/x86_64/wpa_supplicant-2.8-1.fc30.x86_64.rpm
          Resolving kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)… 209.132.181.15, 209.132.181.16
          Connecting to kojipkgs.fedoraproject.org (kojipkgs.fedoraproject.org)|209.132.181.15|:443… connected.
          HTTP request sent, awaiting response… 200 OK
          Length: 1982324 (1.9M) [application/x-rpm]
          Saving to: ‘wpa_supplicant-2.8-1.fc30.x86_64.rpm’

          wpa_supplicant-2.8- 100%[===================>] 1.89M 1.33MB/s in 1.4s

          2019-05-09 22:09:52 (1.33 MB/s) – ‘wpa_supplicant-2.8-1.fc30.x86_64.rpm’ saved [1982324/1982324]
          [jonathon@here Downloads]$ su -c “dnf install wpa_supplicant-2.8-1.fc30.x86_64.rpm”
          Password:
          Last metadata expiration check: 0:20:47 ago on Thu 09 May 2019 21:50:54 AEST.

          Dependencies resolved.

          Package Architecture Version Repository Size

          Upgrading:
          wpa_supplicant x86_64 1:2.8-1.fc30 @commandline 1.9 M

          Transaction Summary

          Upgrade 1 Package

          Total size: 1.9 M
          Is this ok [y/N]:

          If you want to build the source rpm let me know.

        • Jonathon Poppleton

          This is how i used wpa supplicant in the past (no guarantees it will work since i am using a pc now):

          Obtain the name of your wifi interface:
          ip link

          Take note of wifi interface:
          eg wlo1

          Stop network manager:
          su -c “systemctl stop NetworkManager”
          Set SSID and password:
          su -c “wpa_passphrase MYROUTER > /etc/wpa_supplicant/wpa_supplicant.conf
          mypassphrase”
          Enable wpa_supplicant:
          su -c “wpa_supplicant -B -iwlo1 -c/etc/wpa_supplicant/wpa_supplicant.conf”
          Obtain ip address:
          su -c “dhcpcd wlo1”
          Check ip address:
          ping -c 3 http://www.google.com

      • Erich Küster

        Broadcom BCM4331 doesn’t work, too. Best solution for me was not UPgrading to wpa_supplicant-2.8 but DOWNgrading to the old wpa_supplicant of Fedora 29. In Terminal remove the actual version
        $ sudo rpm -e –nodeps wpa_supplicant-2.7-5.fc30.x86_64
        and install the old one
        $ sudo dnf install wpa_supplicant-2.7-1.fc29.x86_64
        You will have to reboot.

      • Plamen Vasileff

        Same problem here with Broadcom wireless card on Lenovo laptop.
        I fix the problem when use this solution:

        https://www.reddit.com/r/Fedora/comments/bj95zy/wifi_stuck_on_connecting_after_upgrade_to_fedora/

        We waiting for update for wpa_supplicant package for f30.

        • Erich Küster

          In the meantime a new kernel 5.0.16-300.fc30.x86_64 is out with wpa_supplicant-2.8, but do NOT install, if you are using broadcom wifi, especially Broadcom BCM4331 (as in MacBook Retina late 2012). Going back to kernel 5.0.13-300.fc30.x86_64 and wpa_supplicant-2.7-5.fc30.x86_64 will work again. Still waiting for a better fix …

  11. Groovie

    Update and install work without any problems.
    Thanks for your professional work!

  12. Had an issue with normal upgrade command (sudo dnf system-upgrade download –releasever=30) but with
    sudo dnf system-upgrade download –releasever=30 –allowerasing
    Works like a charm.

    • Jason Tingle

      Same here, had issues with python3-hawkeye and the dnf package.

  13. Muu

    Who was able to convert encrypted disks Luks1 to Luks2 including / , /home and swap?
    Could you please assist me to convert my encrypted partitions of Luks1 after upgraded to Fedora 30.
    $ ▶ sudo cryptsetup convert /dev/sda3 –type luks2
    Operation aborted, device NOT converted.

  14. Cornel Panceac

    Generating “/run/initramfs/rdsosreport.txt”
    After upgrade, system is no longer booting, just gets tuck with the above message.
    Hopefully it’ just me 🙂
    will investigate and provide more details.

    • Cornel Panceac

      I’ve found that dnf erased fedora-release package. It probably conflicted with fedora-release-matecompiz or similar. Still not clear why two packages that are not providing files with same name/intent conflict one with the other. Also i ad to use rpm –force –nodeps to be able to install it. Worth a ticket, in my opinion. Also, what is ‘system-release’ ? fedora-release conflicted with it too, according to RPM database.

    • Nathan D

      I found this in an older Fedora forum upgrade when someone hit the same error. I hit this today when going from Fedora 29 to 30

      Hope it helps you as it did me:
      After you get into emergency mode execute:

      mount -o remount,rw /sysroot
      rm -f /sysroot/etc/os-release
      cp /usr/lib/os-release /sysroot/etc/
      exit

      • Cornel Panceac

        For me it helped to install fedora-release RPM, with –force, since dnf was unnable to solve dependencies, again.

        Your solution would not have workd for me since the files just were not there.

  15. pimou

    Just done upgrade on 2 pcs via gnome software manager. All is ok. Good work !

  16. eckart

    It needed a longer time but the dnf update was problemfree.
    To give a statement about fedora 30 I must make a few experiences, but it seems fantastic.

  17. David Levner

    I upgraded from Fedora 28 to 30 with shell commands. I have some more testing to do but so far everything works fine.

  18. Justin

    After upgrading to 30 last night, when I turn on my computer, after the TOSHIBA screen, I get this for about 1 second:

    error: ../../grub-core/kern/misc.c :465:unrecognized number

    How do I fix this error? Thanks

    • Pete

      I had the same issue and have not been able to get find any definite answer.

      From what I pieced together, it’s related to the default entry for the grub2 selection. The error does not appear if I use left-shift during bootup, which unhides the grub2 menu.

      I found info from a closed bug report where the submitter believes the default option got corrupted on upgrade: https://bugzilla.redhat.com/show_bug.cgi?id=1674512

      I issued the command he used (sudo grub2-set-default 0) and the problem went away for me on the next boot.

  19. Cory Hilliard

    Upgrade went smoothly. It took about 1.5 hours. (I have slowish high-speed).

    I had some conflicting packages, so I had to use the “–allowerasing” flag to get it to work. Otherwise, no issues at all.

  20. after the upgrade gnome (none of them) work. After I enter my password I get back to choosing my user screen.. Good thing I had plasma loaded as well ..

  21. It was a smooth upgrade…it just worked!

    $ uname -a
    Linux sathnaga86 5.0.9-301.fc30.x86_64 #1 SMP Tue Apr 23 23:57:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  22. Lois

    Fantastisch wie immer. Die besten Jungs am Werk

  23. Bernd

    Lots of problems with the Eclipse installation. Nothing works. Endless dependency issues.

  24. Marcelo

    Updated in two workstations, no issues.

  25. My F29 system couldn’t find any of the repos to update, (failed to sync repo) I had to manually hardcode them all to repo mirrors to finally be able to update.
    Even though tons of searches on google gave links to ask fedora answers, any I clicked on said oops, page doesn’t exist. I tried searching on askfedora and couldn’t get any hits either. Seemed pretty odd.

    Then after updating 29 I thought I was ready to do the system-upgrade, which downloaded everything, rebooted, said almost instantly that upgrade was complete, but never gave me a login screen or rebooted or anything after waiting about an hour. I ctrl-alt-del rebooted and it hung.

    I got tired of dealing with it and tried the windows disc writer to download and burn the iso to usb drive. Then installed from scratch.

    That worked and finally able to log in. Then followed https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ to install Nvidia drivers

  26. River14

    I’ll wait to upgrade to F30 until Nvidia-Linux-x86_64-430.09 not be beta.
    Two birds with one stone !!!

  27. Johnny B

    I have several external repositories, and my spin is KDE. Should I disable the non Fedora repositories before I start the upgrade? Is there something to watch out for or precautions to be taken since my spin 8s KDE? TIA.

  28. James Brock

    Thanks for Fedora 30!

    dnf system-upgrade download

    prints the message

    To remove cached metadata and transaction use 'dnf system-upgrade clean'

    Maybe this article should mention that too.

  29. Kris

    After update gnome doesn`t load… How to resolve it? (I tried to disable all extensions as written above, but no effect).

  30. Michael

    After upgrading to fedora 30 using dnf gnome session won’t start. I’m getting only black screen with a mouse pointer. XFCE is working fine. Any recommendations on how to fix GNOME?

  31. theodore

    i have installed fedora 30 beta (with no issues, works very well) . Upgrade instructions as 29-30?
    thank you

  32. Jon

    Upgrade from 29 to 30 went smooth as silk. Zero issues. HP Elitebook Thanks!

  33. Ernst

    ERROR: Failed to load zone file ‘/usr/lib/firewalld/zones/libvirt.xml’: PARSE_ERROR: rule: Unexpected attribute priority

    Is that serious?

    Also what do you think of :
    gkr-pam: unable to locate daemon control file

    This looks serious what do you think?
    Failed to start System Security Services Daemon.

    I have another concern:
    chroot.c: open() failed: Permission denied

    I’m a novice user so I thought to ask.

  34. Tulio

    I had some packages that I’d not find in F30, so I tried to use ‐‐allowerasing flag, but the download command of dnf don’t recognize this flag. I’ve unisntalled all packages that don’t have a correspondence in F30 before the command begins successfuly.

  35. Bill Chatfield

    Upgrade from Gnome Software failed. It would not boot. I had to reinstall from scratch. First time since Fedora 20 the upgrade failed.

  36. Earl Ramirez

    Thanks for sharing, and thanks for the Fedora devs for another flawless upgrade.

  37. Massimo

    Hi my upgrade failed with the following error :

    Running transaction test
    The downloaded packages were saved in cache until the next successful transaction.
    You can remove cached packages by executing ‘dnf clean packages’.
    Error: Transaction check error:
    file /usr/bin/pipelight-plugin conflicts between attempted installs of pipelight-0.2.8.2-13.fc30.i686 and pipelight-0.2.8.2-13.fc30.x86_64

    Error Summary

    • Stephen Snow

      Are you running both i686 and x86_64 packages of pipelight? There is very likely conflicts between the two.

  38. Jonathon Poppleton

    Smooth upgrade from Fedora 29 to 30. My nextcloud server started without issue:

    systemctl disable httpd
    sudo dnf upgrade –refresh
    sudo dnf install dnf-plugin-system-upgrade
    sudo systemctl set-default multi-user.target
    sudo reboot
    sudo dnf system-upgrade download –best –allowerasing –refresh –releasever=30
    sudo dnf system-upgrade reboot
    login
    sudo systemctl set-default graphical.target
    systemctl enable httpd
    reboot

  39. River14

    I’ve just upgraded to Fedora 30 -I couldn’t wait any more-.
    Any trouble !! Everything works like a charm !!
    I only had to reinstall the Nvidia-Linux-x86_64-418.56 proprietary driver!!
    Great great job !!
    Congrats !!

  40. Sergey

    For some reason nouveau is broken after the update (spamming in dmesg). Was needed to blacklist the module to run gdm.

  41. Finn

    unrecognized arguments: -releasever = 30???

    • River14

      –releasever=30 –allowerasing (two dashes)

    • Stephen Snow

      unrecognized arguments: -releasever = 30???

      I think the command option needs two dashes, so

      --releasever=30
    • Earl Ramirez

      its –releasever not -releasever, it’s two hyphen

    • Luya Tshimbalanga

      –releasever=30 . Note the missing extra “-“

  42. Sam

    Upgraded and now I get …

    Free magic is broken at 0xad2c9500: ….

    If I let it count down on the grub menu selection it fails. If I select the version from the menu it boots fine. This is an issue as this pc is scheduled to startup by itself…

    • Sam

      Update…

      I ran dnf update which found software updates including a new kernel. After updating and rebooting all seems to be good now.

  43. Peter Braet

    Too buggy to release already. Sorry, Fedora30 needs to upgrade urgently. This is much worse than only WiFi not working. It is full of bugs.

    • Peter Braet

      Will Fedora please explain howto build (f30-candidate, wpa_supplicant-2.8-1.fc30.bz1703745rebuild.src.rpm)? That is the solution according to “Ask Fedora”, something from Koji, I don’t even know what that is. Please Fedora, explain howto do this and make broadcom work.

  44. Amit Samanta

    The fedora upgraded from 29 to 30 has broke my system. After upgrade to fedora 30, the whole graphics has become fuzzy and blurry. It looks like old days TV screen. Do any body has nay idea how can I resolve this issue.

    • Charles

      Hi, try to create a new account and login using the new account. This solution should work but not very good, because you have to reconfigure your account. Delete .config folder maybe also work. Remember to backup your home folder before do this.

    • EIner Petersen

      Hi Amit,

      Which graphics card/chip?

      (This sounds like a kernel command line issue, specifically the nomodeset or nouveau.modeset=0 )
      What happens is that if the high resolution graphics driver has a problem, the kernel uses the default BIOS VGA resolution of 640×480 == looks like an old TV ………..

  45. Flo

    I have successfully upgraded from 29 to 30 via dnf commands. The only thing that did not work properly afterwards was my sound (using a Focusrite Scarlett as my main sound interface). There seemed to be some problem in parsing the config for the interface.
    To resolve the issue all I had to do is clear the configs for pulseaudio (rm -r ~/.config/pulse) and restart it/let it write new configs. I hope this helps people facing the same issue.

  46. Sad

    PSA: Your bookmarks can completely disappear from Epiphany (Gnome Web) after the upgrade. Make backups!

  47. Donald O'Dona

    updated this morning. Started it, gone shopping, watching the final steps on return. No problems. Thanks RH & Fedora people!!!

  48. pete forde

    after upgrading to fedora 30 I get the login screen with my user i attempt to login it acepts passowrd but goes back to login screen.

    • Einer Petersen

      Log in as root and remove the .config directory in your regular home directory (the easy fix that worked for me)

      • Gayland Gump

        After upgrading to FEDORA 30: I am able to login under my normal user name via ssh so I did so and renamed the .config directory to .config-old but I am still unable to get logged into the GUI. I am able to get into the GUI though as root but not as my normal user. The login screen presents with my name, requesting my password, when I click but once the screen has cleared, it returns to the login screen. Any other simple fix suggestions?

        • Erich Küster

          What about using a Fedora 30 Live Cd and renaming .config.old to .config again? Then a reboot will be necessary, of course.

          • Gayland Gump

            Oddly and to my mind inexplicably, I logged in via ssh using my normal user and copied the .config-old directory back to .config, logged out and logged into the GUI as root where I opened a terminal and manually rm -Rf /home/username/.config. I rebooted and this time was able to log into the GUI using my normal user login. I am sure that I’d done a complete reboot with all the prior attempts. I did encounter a problem with the mouse freezing up after my first successful login as my normal user which has not recurred during subsequent logins.

        • Maksym Sanzharov

          I had this issue, but the latest updates fix it for me. Did you try to update packages?

  49. Charles

    Fedora 30 sometimes get frozen about 5 seconds when:
    1) move cursor
    2) drop a video file to a running SMPlayer instance

    I’m using Nvidia by the way. I can see message ‘/usr/lib/gdm-x-session[11388]: nvLock: client timed out, taking the lock. ‘ in ‘journalctl -f’.

    Any advice?

    • Einer Petersen

      I had the same problem and traced it back to the kernel nvidia DRM module ….. (very annoying I might add because it all worked in F29..). I am using the proprietary drivers.

      Modify the grub kernel command line to disable the Nvidia DRM
      nvidia-drm.modeset=0

      My machine also has the Intel 630 (due to i7-8750)
      so my kernel command line looks like this and it is working flawlessly:

      nouveau.modeset=0 rd.driver.blacklist=nouveau i915.modeset=1 nvidia-drm.modeset=0 resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/swap rhgb

      Yes, it is still using the Nvidia card …. just not using the Nvidia Kernel DRM

      Also, I am betting the good folks at the GNOME project just had to screwed things up because in F29 kernel+nvidia DRM worked just fine and I tested the previous kernel/nvidia driver setup after the upgrade to F30 and the only real diff is the upgrade of GNOME to GNOME 3.32 form 3.31. (Linus had to take a “Be Nice Vow” ……… I didn’t :-D)

      • Charles

        Hi, thanks for your reply.

        I’m curious that how did you trace this issue back to the kernel nvidia DRM module?

        I’v changed ‘nvidia-drm.modeset’ to 0 from 1 in the file ‘/etc/default/grub’, and then execute the command ‘grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg’. Then reboot.

        Now the Nvidia DRM is disabled.

        Whether or not this workround works, I’ll reply here later.

        By the way, does disabling the Nvidia DRM have side effect?

        I’v filled a bug report in there: https://bugzilla.redhat.com/show_bug.cgi?id=1706512

        • Einer Petersen

          Hi Charles 🙂

          My first clue was the CPU utilization going to 100% across a 12 threads. My second was seeing that nvLock timeout in /var/log/messages. My third was that it wasn’t happening in KDE. These 3 things usually suggest a bad driver or the driver is being used incorrectly and given that the GNOME project has a very LONG history of screwing things up due to 1) knee-jerk changes and 2) miserable QA …………

          Side effects so far:
          1) no more kernel race —- probably due to a lock (nvLock) no longer being abused by the application (GNOME Shell?) trying to use it :-/
          2) no other issues or degradation on anything I have tried so far since I disabled the Nvidia DRM module 🙂
          3) I am happy about it (the work-around) so far 🙂
          4) Still love/hate GNOME

          • Charles

            Whatever, this workaround does works for me. I’m happy to use Fedora 30.

  50. Murpholinox Peligro

    Same problem with the driver bcm 43142 not working. Used to work fine with Fedora 29. c.c

    • Peter Braet

      Will Fedora please explain howto build (f30-candidate, wpa_supplicant-2.8-1.fc30.bz1703745rebuild.src.rpm)? That is the solution according to “Ask Fedora”, something from Koji, I don’t even know what that is. Please Fedora, explain howto do this and make broadcom work.

  51. Baruch

    Command in section 3 must be

    sudo dnf system-upgrade download –refresh –releasever=30

  52. Maricela

    The wifi driver for BCM4312 is not working!!!!

    • Peter Braet

      Will Fedora please explain howto build (f30-candidate, wpa_supplicant-2.8-1.fc30.bz1703745rebuild.src.rpm)? That is the solution according to “Ask Fedora”, something from Koji, I don’t even know what that is. Please Fedora, explain howto do this and make broadcom work.

  53. Lionel

    Updated my laptop 29 -> 30
    KDE (plasma) freeze averytime I try to use an item in the control panel…

    • Brian

      Do you have nouveau driver installed? I have the same problem.
      Log is full of:
      nouveau 0000:01:00.0: gr: ILLEGAL_CLASS ch 10 [003f774000 plasmashell[7023]] subc 0 class 0000 mthd 35f0 data 0000005f

      • Lionel

        Yes, nouveau.
        I went back to the 29. It was impossible to work.

        • For those of us with thinkpad X1 Extreme, with dual video cards, one of which is the nouveau, we know how to deal with this problem. There are two options:
          1) use the “discrete” video card
          2) use the nouveau (aka “Hybrid” video in the BIOS)
          These may be chosen during boot time, in the bios.
          If you want to have suspend work it is necessary to pick 1, as the nouveau is called
          during the resume cycle. Suspend works, but resume fails when it tries to load the nouveau. The solution is to blacklist the nouveau, and chose option 1. Then suspend/resume works fine.
          With this option you will not be able to use thunderbold (an external monitor). A relatively small price to pay compared to resume.

          One must go with option 2 to boot the system from a USB stick, else it hangs. One may then install Fedora using the nouveau,
          but there is no suspend resume. Once the system is booted it is necessary to black list the nouveau. This is about a 10 step
          proceedure, which works fine for me, once I got it down. The blacklist proceedure may be found at:
          https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/

          Its an ugly set of choices, but it all works for me no, 100% as long as I dont boot the Hybrid/nouveau video and have it blacklisted.
          The proceedure is messy to blacklist. I think there is a better solution during boot, but I have not tried that one, but would like to.

          Here is all I know about that option:

          https://fedoramagazine.org/upgrading-fedora-29-to-fedora-30/
          couldnt boot; nvideo problems
          After you get into emergency mode execute:

          mount -o remount,rw /sysroot
          rm -f /sysroot/etc/os-release
          cp /usr/lib/os-release /sysroot/etc/
          exit

          END

  54. Craig

    Are the instructions identical for the KDE Spin?

  55. Olaf

    Somehow Eclipse ain’t working anymore.

    The needed “ant” repo has the wrong version. Hope that gets fixed soon.

  56. jont allen

    can one simply boot into 29 rather than 30, after installing 30?

  57. Anton

    DEEPIN is a very beautiful but uncomfortable interface. I dream to return to GNOME

  58. FMP

    Successfully upgraded Fedora 29 to Fedora 30 it took the upgrade for a45 minutes.
    I’m not sure what took place but for my case, I have to re do the process before Fedora 30 kicked in. Any input on this is highly appreciated.

  59. Keli

    Upgrade for KDE was easy and no problems arose. Thanks Fedora!!!!

    • Craig

      Glad to hear it!
      Did you do the upgrade described on this article page? Is there anything that needs to be done for the KDE Spin that’s not described here?
      Thanks!

  60. svsv sarma

    FWS 30 on the 30th day is fine. The dnf upgrade allowerasing did the trick smoothly. I congratulate the team for the taming. However, ‘error: ../../grub-core/fs/fat.c:447:not a FAT file system’ alert at boot time is intimidating.

  61. Dirk Gottschalk

    IS there any way to upgrade offline?

    I moved to another location and it takes a while until my internet is switched. I updates my notebook at work and would like to upgrade my home server for various reasons. Is there any workaroung for such situations?

  62. Luis

    After upgrade from 29 to F30, i can’t log on on my desktop just ask for password and don’t enter, help please.

  63. Gabriel

    Anyone any luck with VMWARE with kernel > 4.18? other than dodgy custom kernel patches?

  64. Gabriel

    on fc29 I had to keep off the 5.0 bandwagon due to VMware…

    does anyone have had any exp in running the latest’s of the 4.x mainline with fedora 30. that’s the only thing holding me back to upgrade to 30 right now.

  65. Brian D

    If you have NVidia graphics on your system–maybe that’s my trouble — you might want to stay put at Fedora 28. I had to back up from Fedora 29 after it went berserk last December. Gnome Display manager failed. All kinds of weird dependency problems…. Gnome on Fedora 30 works fine, but KDE-Plasma hangs and freezes immediately when an attempt is made to invoke the Application Menu. I suspect that PKCON may also be part of the problem, as it was in Fedora 29, but I’m not sure yet. I should have stayed put. Fedora 28 worked just fine. My fault for being curious. Fortunately I have Linux Mint Debian and Debian Stretch installed on other partitions. Good Luck. Thanks to Fedora team for all the work, but since last December 16th, Fedora 29 update, something has gone awry. Fedora 29 was initially an excellent desktop.

    • Einer Petersen

      Hi Brian,

      Yup, systems with Nvidia cards can be tricky at times 🙂
      Recently, the part that has been causing most of the problems has been the Nvidia DRM Kernel module (see comments/reply for Charles).
      I have had Fedora on my systems since it came out and the Nvidia drivers have always been challenging (putting it nicely at least :-)). The worst Nvidia driver I have dealt with is the Nouveau driver so, I have completely abandoned it in favor of the proprietary driver from Nvidia. The proprietary driver is a bit of a dance when the kernel or OS are upgraded, it takes planning 🙂
      Steps I use:
      1) dnf update
      2) download the driver from Nvidia
      3) systemctl set-default multi-user.target
      4) reboot
      5) build/install the new Nvidia driver
      6) reboot (because I like double-checking that the kernel is still alive/not hosed :-))
      7) startx (double-check that the GUI desktop comes up and things actually work) — and in the case of the kernel command line setting for nouveau.modeset=0 rd.driver.blacklist=nouveau nvidia-drm.modeset=0
      (also I am lucky that I also have an i7 with the embedded graphics so I also set i915.modeset=1)
      8) IF everything is doing what it is supposed to do, systemctl set-default graphical.target
      9) reboot
      — IF things go kaboom!, reboot single user and fix it
      — IF things go as planned, enjoy the OS and go back to love/hate of GNOME

      This has worked for me for many years now 🙂

    • Brian D

      After the latest update today Saturday, May 11– KDE-Plasma now works beautifully.
      Gnome– not my first choice works better than ever, and I could actually learn to like it.
      Congratulations to Fedora for the improvements. I am running with an older NVidia card and the nouveau driver. I could probably do better with the proprietary driver, but I am satisfied with the system as it stands. THANKYOU.

  66. Gio

    upgrade from 28 to 30 will be “dangerous” ? or better do 28 -> 29 -> 30 ?

  67. Hi there
    Very happy after upgrading my local development server from fedora 29 to 30.
    I just followed the instructions and it’s done without any issue.
    Thanks!
    Regards
    Kamal Mehta
    https://www.smiansh.com

  68. Samuel

    After upgrading my UHD display resolution is reduced to 1024 x 768 and I can’t change it in Gnome display settings, or ~/.config/monitors.xml. The Resolution is already applied when being prompted for the LUKS password of my root partition during boot – so I assume it’s not a userspace problem. Does anyone know which other configs could be interfering?

    • Vaclav

      Hi, I have the same issue. After upgrade I have some unsupported resolution on my second UHD monitor during the boot (from the LUKS prompt). The monitor must be reconnected after the boot to Gnome, then it works.

      • Vaclav

        Update: my issue is only with more screens. So maybe the resolution is set accordingly to primary screen and then applied to the second screen, that can not display it. The bad thing is that the resolution stays the same in Gnome, so I must unplug the connector or turn off the secondary screen. When I boot only with secondary screen, the resolution is setted properly.

  69. JC

    My upgrade failed with “unable to allocate memory” errors about 30% of the way through. I had to revert to a backup as it FUBAR’ed the DNF/YUM subsystem. Tried twice, the second time after doubling the memory, still failed. My estimate, had it run to completion, would have been about 4 hours to complete. Something’s not right, I’ll wait.

  70. hello friends, I have a laptop with wifi broadcom and ith the update in F30 , my wifi not work anymore , is it posible avoid the update for “wpa_supplicant” end leave it in a version of F29?

    • Erich Küster

      Sorry, my fingers were quicker than my brain: It is important to look every time when dnfdragora offers a list of available updates on them: Will update the old wpa_supplicant, of course. Do not select this request !!

  71. Erich Küster

    Please look at the comments of Jonathon Poppleton and myself from above. You must remove the new wpa_suppplicant, then download an old version (in the moment I am using wpa_supplicant-2.7-1.fc30.x86_64.rpm). At first look that does not work as expected. Strange enough I installed in addition wpa_supplicant-gui-2.7-1.fc30.x86_64.rpm and … all worked fine.

Comments are Closed

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. Fedora Magazine aspires to publish all content under a Creative Commons license but may not be able to do so in all cases. You are responsible for ensuring that you have the necessary permission to reuse any work on this site. The Fedora logo is a trademark of Red Hat, Inc. Terms and Conditions

%d bloggers like this: