将 Fedora 30 升级到 Fedora 31
Fedora
![](/data/attachment/album/201911/05/122015z1efmatm6mff667o.jpg)


Fedora 31 [日前发布了](/article-11522-1.html)。你也许想要升级系统来获得 Fedora 中的最新功能。Fedora 工作站有图形化的升级方式。另外，Fedora 提供了一种命令行方式来将 Fedora 30 升级到 Fedora 31。


### 将 Fedora 30 工作站升级到 Fedora 31


在该发布不久之后，就会有通知告诉你有可用升级。你可以点击通知打开 GNOME “软件”。或者在 GNOME Shell 选择“软件”。


在 GNOME 软件中选择*更新*，你应该会看到告诉你有 Fedora 31 更新的提示。


如果你在屏幕上看不到任何内容，请尝试使用左上方的重新加载按钮。在发布后，所有系统可能需要一段时间才能看到可用的升级。


选择*下载*以获取升级包。你可以继续工作，直到下载完成。然后使用 GNOME “软件”重启系统并应用升级。升级需要时间，因此你可能需要喝杯咖啡，稍后再返回系统。


### 使用命令行


如果你是从 Fedora 以前的版本升级的，那么你可能对 `dnf upgrade` 插件很熟悉。这是推荐且支持的从 Fedora 30 升级到 Fedora 31 的方法。使用此插件能让你轻松地升级到 Fedora 31。


#### 1、更新软件并备份系统


在开始升级之前，请确保你安装了 Fedora 30 的最新软件。如果你安装了模块化软件，这点尤为重要。`dnf` 和 GNOME “软件”的最新版本对某些模块化流的升级过程进行了改进。要更新软件，请使用 GNOME “软件” 或在终端中输入以下命令：



```
sudo dnf upgrade --refresh
```

此外，在继续操作之前，请确保备份系统。有关备份的帮助，请参阅 Fedora Magazine 上的[备份系列](https://fedoramagazine.org/taking-smart-backups-duplicity/)。


#### 2、安装 DNF 插件


接下来，打开终端并输入以下命令安装插件：



```
sudo dnf install dnf-plugin-system-upgrade
```

#### 3、使用 DNF 开始更新


现在，你的系统是最新的，已经备份并且安装了 DNF 插件，你可以通过在终端中使用以下命令来开始升级：



```
sudo dnf system-upgrade download --releasever=31
```

该命令将开始在本地下载计算机的所有升级。如果由于缺乏更新包、损坏的依赖项或已淘汰的软件包而在升级时遇到问题，请在输入上面的命令时添加 `‐-allowerasing` 标志。这将使 DNF 删除可能阻止系统升级的软件包。


#### 4、重启并升级


上面的命令下载更新完成后，你的系统就可以重启了。要将系统引导至升级过程，请在终端中输入以下命令：



```
sudo dnf system-upgrade reboot
```

此后，你的系统将重启。在许多版本之前，`fedup` 工具会在内核选择/引导页面上创建一个新选项。使用 `dnf-plugin-system-upgrade` 软件包，你的系统将重新引导到当前 Fedora 30 使用的内核。这很正常。在内核选择页面之后不久，你的系统会开始升级过程。


现在也许可以喝杯咖啡休息下！升级完成后，系统将重启，你将能够登录到新升级的 Fedora 31 系统。


![](/data/attachment/album/201911/05/122018pvc1hogw2awvoovo.png)


### 解决升级问题


有时，升级系统时可能会出现意外问题。如果遇到任何问题，请访问 [DNF 系统升级文档](https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#Resolving_post-upgrade_issues)，以获取有关故障排除的更多信息。


如果升级时遇到问题，并且系统上安装了第三方仓库，那么在升级时可能需要禁用这些仓库。对于 Fedora 不提供的仓库的支持，请联系仓库的提供者。




---


via: <https://fedoramagazine.org/upgrading-fedora-30-to-fedora-31/>


作者：[Ben Cotton](https://fedoramagazine.org/author/bcotton/) 选题：[lujun9972](https://github.com/lujun9972) 译者：[geekpi](https://github.com/geekpi) 校对：[wxy](https://github.com/wxy)


本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出


OK
Fedora 31 [is available now](https://fedoramagazine.org/announcing-fedora-31/). You’ll likely want to upgrade your system to get the latest features available in Fedora. Fedora Workstation has a graphical upgrade method. Alternatively, Fedora offers a command-line method for upgrading Fedora 30 to Fedora 31.

Before upgrading, visit the [wiki page of common Fedora 31 bugs](https://fedoraproject.org/wiki/Common_F31_bugs) to see if there’s an issue that might affect your upgrade. Although the Fedora community tries to ensure upgrades work well, there’s no way to guarantee this for every combination of hardware and software that users might have.

## Upgrading Fedora 30 Workstation to Fedora 31

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 31 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 30 to Fedora 31. Using this plugin will make your upgrade to Fedora 31 simple and easy.

### 1. Update software and back up your system

Before you do start the upgrade process, make sure you have the latest software for Fedora 30. This is particularly important if you have modular software installed; the latest versions of dnf and GNOME Software include improvements to the upgrade process for some modular streams. 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](https://fedoramagazine.org/taking-smart-backups-duplicity/) 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=31

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 30; 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 31 system.

## 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 quick docs](https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/#Resolving_post-upgrade_issues) for more information on troubleshooting.

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.

## Zlopez

I think we should also inform how to upgrade on Fedora Silverblue.

## hammerhead corvette

Absolutely !

## Otsilva

So, how do we do it? (Fedora Silverblue)

## Zlopez

There should be upgrade option in GNOME Software, but I got GPG key not trusted, when I tried it. I recommend to use this guide https://fedoramagazine.org/how-to-rebase-to-fedora-30-beta-on-silverblue, just change F30 to F31 and everything should work.

## Zlopez

I also noticed, that the refs name changed from fedora-workstation to fedora. It looks like I need to write a new article.

## Otsilva

Ok! I will wait!

## Ricky

Hit a road block. I double check eclipse-jgit is from Fedora upstream repo:

sudo dnf system-upgrade download –releasever=31

Before you continue ensure that your system is fully upgraded by running “dnf –refresh upgrade”. Do you want to continue [y/N]: y

Copr repo for bazel owned by vbatts 11 kB/s | 3.3 kB 00:00

Fedora Modular 31 – x86_64 23 kB/s | 12 kB 00:00

Fedora Modular 31 – x86_64 – Updates 32 kB/s | 9.8 kB 00:00

Fedora 31 – x86_64 – Updates 36 kB/s | 11 kB 00:00

Fedora 31 – x86_64 39 kB/s | 12 kB 00:00

Jenkins-stable 45 kB/s | 2.9 kB 00:00

Metasploit 28 kB/s | 3.0 kB 00:00

RPM Fusion for Fedora 31 – Free – Updates 9.3 kB/s | 4.2 kB 00:00

RPM Fusion for Fedora 31 – Free 7.2 kB/s | 3.2 kB 00:00

RPM Fusion for Fedora 31 – Nonfree – Updates 9.4 kB/s | 4.3 kB 00:00

RPM Fusion for Fedora 31 – Nonfree 7.1 kB/s | 3.2 kB 00:00

Error:

Problem: problem with installed package eclipse-jgit-5.4.0-4.fc30.noarch

– eclipse-jgit-5.4.0-4.fc30.noarch does not belong to a distupgrade repository

– package eclipse-jgit-5.4.0-4.module_f31+6165+9b01e00c.noarch is excluded

– package eclipse-jgit-5.5.0-1.module_f31+6519+12cd0b27.noarch is excluded

– nothing provides jgit = 5.3.0-5.fc31 needed by eclipse-jgit-5.3.0-5.fc31.noarch

(try to add ‘–skip-broken’ to skip uninstallable packages)

## Charles

Same issue here. How to resolve this problem?

## Jose

You could just add –allowerasing flag. It will remove the dependend eclipse packages and allow the upgrade to take place. Re-install eclipse after upgrade finishes.

## Zlopez

I’m usually uninstall the package and install it after upgrade. Or you could wait for few days, till this package will be ready for F31.

## jsast21

Easiest way around this is to uninstall eclipse* (dnf erase -y eclipse*) and then run the upgrade. Then you can reinstall eclipse when the upgrade is complete.

I had a similar issue with TeamViewer by the way.

Good luck.

## anony mouse

Eclipse seems broken in F31, it may be best to stay on F30.

## andrej

you can always use eclipse from https://www.eclipse.org/downloads/packages/

## Arthur

Worked a treat. Thanks.

## Yazan Al Monshed

How to do that in SB ??

## Zlopez

There should be upgrade option in GNOME Software, but I got GPG key not trusted, when I tried it. I recommend to use this guide https://fedoramagazine.org/how-to-rebase-to-fedora-30-beta-on-silverblue, just change F30 to F31 and everything should work.

## Bob

Hi,

There is kind of a shortcut here…

You are saying “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 30 to Fedora 31. ”

Yet the official guide says: use the gui:

This is the recommended upgrade method for the Fedora Workstation.

https://docs.fedoraproject.org/en-US/quick-docs/upgrading/

## Brandon

No key installed and system not ready for upgrade.

Fedora 31 – x86_64 1.6 MB/s | 1.6 kB 00:00

Importing GPG key 0x3C3359C4:

Userid : “Fedora (31) fedora-31-primary@fedoraproject.org”

Fingerprint: 7D22 D586 7F2A 4236 474B F7B8 50CB 390B 3C33 59C4

From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64

[…]

Public key for abrt-addon-ccpp-2.12.2-1.fc31.x86_64.rpm is not installed. Failing package is: abrt-addon-ccpp-2.12.2-1.fc31.x86_64

GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64

Public key for abrt-addon-kerneloops-2.12.2-1.fc31.x86_64.rpm is not installed. Failing package is: abrt-addon-kerneloops-2.12.2-1.fc31.x86_64

GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64

Public key for abrt-addon-pstoreoops-2.12.2-1.fc31.x86_64.rpm is not installed. Failing package is: abrt-addon-pstoreoops-2.12.2-1.fc31.x86_64

GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-31-x86_64

[…]

Didn’t install any keys

The downloaded packages were saved in cache until the next successful transaction.

You can remove cached packages by executing ‘dnf clean packages’.

Error: GPG check FAILED

## lruzicka

You are experiencing the problem with modularity. For a little background, you have enabled and installed a modular stream (on purpose or accidentally) and because that stream does not have an upgrade path, it cannot be upgraded and your system stays as is. Modularity is a work-in-progress so it still is not perfect. To solve your situation. There were similar problems with

libgit2module, check if you have it. If that is the libgit problem, there should be a fix ready, make sure you have updated your system fully before upgrading. However, it can be other modules, as well:Check if any modules are installed (or enabled):

dnf module list --installedanddnf module list --enabled.For all such listed modules do

dnf module reset <modulename>This should help to get you upgraded.

## Ricky

I disabled all module and disable modular repository:

sudo dnf config-manager –set-disabled updates-modular

Run dnf update again. It replaced RPM from modular with RPM from Fedora 30 repo.

But I still hit a road block — libgit2 when upgrade:

sudo dnf system-upgrade download –releasever=31

Before you continue ensure that your system is fully upgraded by running “dnf –refresh upgrade”. Do you want to continue [y/N]: y

Copr repo for bazel owned by vbatts 11 kB/s | 3.3 kB 00:00

Fedora 31 – x86_64 – Updates 35 kB/s | 14 kB 00:00

Fedora 31 – x86_64 94 kB/s | 14 kB 00:00

Jenkins-stable 46 kB/s | 2.9 kB 00:00

Metasploit 29 kB/s | 3.0 kB 00:00

RPM Fusion for Fedora 31 – Free – Updates 6.7 kB/s | 3.0 kB 00:00

RPM Fusion for Fedora 31 – Free 7.0 kB/s | 3.2 kB 00:00

RPM Fusion for Fedora 31 – Nonfree – Updates 6.7 kB/s | 3.0 kB 00:00

RPM Fusion for Fedora 31 – Nonfree 7.1 kB/s | 3.2 kB 00:00

Unable to resolve argument libgit2

Error:

Problem: problem with installed package eclipse-jgit-5.4.0-4.fc30.noarch

– eclipse-jgit-5.4.0-4.fc30.noarch does not belong to a distupgrade repository

– nothing provides jgit = 5.3.0-5.fc31 needed by eclipse-jgit-5.3.0-5.fc31.noarch

(try to add ‘–skip-broken’ to skip uninstallable packages)

## lruzicka

Have you reset the modules first, before you disabled the modular repos? Also, I believe that libgit2 for Fedora 31 was only provided as a modular package. There has been a discussion about modular default streams and somebody suggested to create a non-modular libgit2 package, but I do not think that has happened.

So, you either remove eclipse and everything that depends on libgit2 and upgrade first, then you can install eclipse again. Or, you enable the modular repos again, you run

and this should be enough to tell your system to forget the libgit2 stream that became obsolete and move to a newer stream.

Let me know how that went, ok?

## Alastair D'Silva

You’ll probably have issues reinstalling eclipse after the upgrade, I worked around it by manually installing the Fedora 30 packages for: jgit, eclipse-jgit & glassfish-el. Download the binaries from here:

https://fedora.pkgs.org/30/fedora-updates-x86_64/jgit-5.4.0-6.fc30.noarch.rpm.html

https://fedora.pkgs.org/30/fedora-updates-x86_64/eclipse-jgit-5.4.0-4.fc30.noarch.rpm.html

https://fedora.pkgs.org/30/fedora-x86_64/glassfish-el-3.0.1-0.10.b08.fc30.noarch.rpm.html

## Al

Thanks, it worked for me perfectly!

## Dragosh

If I have fedora 31 beta, is need tot do another actions (step) or sudo dnf upgrade –refresh is enough??

## Paul W. Frields

@Dragosh. That should be enough. When you install the Beta you’re on the path toward that final release.

## BuKToP

Everything is fine, but TeamViewer is not working after the upgrade. Tried to uninstall it and then install it again. No success. It starts correctly, but then the GUI just freezes.

Any ideas?

## aa

oh,no

i completed upgrade,but i lose my root pasword

🙁

## Paul W. Frields

@aa: See if this article works for you: https://fedoramagazine.org/reset-root-password-fedora/

## VeNiX

Some packages from the old system must be removed in order the test transaction to pass.

## Charles

Hi, guys,

Running ‘dnf system-upgrade reboot’ cannot trigger the upgrade process in my case.

I can see the log ‘Starting system upgrade. This will take a while’, but after that the OS rebooted quickly. I’m able to see some failure.

But I upgraded Fedora 29 to 30 successfully.

Any ideas?

## lruzicka

Please, send the failure you see. 😀

## Charles

Hi,

I’ve resolved this issue.

1.

Run ‘journalctl’ to open the logs, then search ‘system-upgrade’ or ‘Failed to start System Upgrade using DNF’, etc. I can see error logs, like:

Package XXXXXXXX.x86_64 is already installed.

Error:

Problem: cannot install the best candidate for the job

– conflicting requests

(try to add ‘–skip-broken’ to skip uninstallable packages)

2.

My solution is rebooting to Fedora 30 and remove this annoying package.

Then run ‘dnf system-upgrade reboot’ again, but please remember that before do this run ‘dnf upgrade –refresh’ and ‘dnf system-upgrade download –releasever=31’ at first.

## Charles

But I have other issues:

1.The Nvidia video card cannot be detected, but Intel video instead.

I see these error logs:

(II) LoadModule: “nv”

(WW) Warning, couldn’t open module nv

(EE) Failed to load module “nv” (module does not exist, 0)

and:

(**) Option “fd” “51”

(II) event8 – SIGMACHIP USB Keyboard Consumer Control: device removed

(II) AIGLX: Suspending AIGLX clients for VT switch

(EE) modeset(0): failed to set mode: Permission denied

2.

The second monitor cannot detected, but it can be detected in F30. It’s strange.

Now I’m actually using Intel video card, so may be it’s due to the missing configuration?

I’ve created a configuration file at /etc/X11/xorg.conf.d/20-intel.conf, but this is not useful. The second monitor can’t be detected even after reboot.

## Charles

Hi,

The first issue had been resolved.

My solution is:

Please note that I’ve installed Nvidia packages from rpmfution.

See https://rpmfusion.org/Howto/NVIDIA for more details.

1)cp /usr/share/X11/xorg.conf.d/nvidia.conf /etc/X11/xorg.conf.d

2)Add the following lines to /etc/X11/xorg.conf.d/nvidia.conf:

Section “Module”

Load “modesetting”

EndSection

Section “Device”

Identifier “nvidia”

Driver “nvidia”

BusID “PCI:”

Option “AllowEmptyInitialConfiguration”

EndSection

3)Reboot, I can see Fedora 31 is using Nvidia graphics in the Setting/About.

Please see ‘https://wiki.archlinux.org/index.php/NVIDIA_Optimus#Use_NVIDIA_graphics_only’ for more details.

The second issue should be resolved too, since I’ve used the Nvidia graphics. I’ll reply later.

## Charles

I’m sure that enable Nvidia graphics can make the Fedora 30 to detect the second monitor by default.

## Mislav

Is upgrade from F29 -> F31 also supported? I can see upgrade to F31 option in Gnome Software on my F29 laptop but this article only mentions F30.

## Stephen

Yes it should work. There has been occasion for problems doing what you propose, but that was with way earlier versions such as F17/18/19, etc… I have done “jumpgrades” of two version changes bypassing the in between one with no adverse affects to systems.

## bb

Error: Transaction test error: file /usr/lib/python3.7/sute-packages/mypy/typeshed from install of python3-mypy-0.730-2.fc31.noarch conflicts with file from package python3-mypy-0.670-1.fc30.noarch

## andrej

dnf remove python3-mypy-0.670-1.fc30.noarch

watch for dependent packages that was removed with it

upgrade to the f31

install back those dependent packages

in my case it was thonny-3.1.1-1.fc30.noarch – see my post below for more details.

## River14

I have not yet upgraded to fedora 31 and I can’t wait for this.

But, I need to know if there is any issue about nvidia graphics card.

rpmfussion free and non-free doing the best ???

Thanks a lot

## bnjmn

None

## Charles

Unfortunately. Nvidia graphics card can’t be detected in my laptop after upgrade.

## Nanner

Running into an issue with Banshee when trying to upgrade. If I do –allowreasing, dnf will remove Banshee and install the updated gudev-sharp package for Fedora 31.

Error:

Problem: package banshee-2.6.2-34.fc31.x86_64 requires mono(gudev-sharp) = 1.0.0.0, but none of the providers can be installed

– problem with installed package banshee-2.6.2-32.fc30.x86_64

– gudev-sharp-1:0.1-25.fc30.x86_64 does not belong to a distupgrade repository

– banshee-2.6.2-32.fc30.x86_64 does not belong to a distupgrade repository

(try to add ‘–skip-broken’ to skip uninstallable packages)

However if I try to dnf install banshee from a clean install of Fedora 31 I get this:

Error:

Problem: conflicting requests

– nothing provides mono(Mono.Zeroconf) = 4.0.0.90 needed by banshee-2.6.2-34.fc31.x86_64

– nothing provides mono(gudev-sharp) = 1.0.0.0 needed by banshee-2.6.2-34.fc31.x86_64

– nothing provides mono(notify-sharp) = 0.4.0.0 needed by banshee-2.6.2-34.fc31.x86_64

(try to add ‘–skip-broken’ to skip uninstallable packages)

## lruzicka

Thanks for letting us know, I have opened a bug. Hopefully, the situation will be fixed in the future. (https://bugzilla.redhat.com/show_bug.cgi?id=1767436)

## lruzicka

Hello,

in this update (https://bodhi.fedoraproject.org/updates/FEDORA-2019-bf9384ecd1), you will find updated packages needed to install Banshee. I have tested it and it works. You can install it like this:

Create an empty temporary directory.

Install the Bodhi client

Download the packages from Bodhi using the client

.

Install the packages

.

Install Banshee

## Joachim

The upgrade 30 -> 31 worked like a charm on my old workhorse DELL Precision M6400! No issues whatsoever…

Thanks for the great work, guys!

## Stephen

For upgrading Silverblue to F31SB, the link provided in the comments above will work. There was one difference for me in that the remote ref was named simply fedora on my system. So the command I used to rebase to F31 was ‘rpm-ostree rebase fedora:fedora/31/x86_64/silverblue’. I am now going to reboot into my F31SB system.

## Stephen

This comment has been submitted using Fedora 31 Silverblue after a successful upgrade just minutes ago.

## Enio

Error: Transaction test error: file /usr/lib/python3.7/sute-packages/mypy/typeshed from install of python3-mypy-0.730-2.fc31.noarch conflicts with file from package python3-mypy-0.670-1.fc30.noarch

Even with “[…] –allowerasing”

## Murphy

I suggest “dnf remove python3-mypy”, then your upgrade should go smoothly.

## Michael

Perfect, it worked. Thanks.

## andrej

In my case the root problems seems to be within the thonny-3.1.1-1.fc30.noarch (Python IDE for beginners) from f30. It depends on python3-mypy-0.670-1.fc30.noarch.

In fedora 31 there is the same thonny-3.1.1-1.fc30.noarch but it depends on python3-mypy-0.740-2.fc31.noarch.

The thonny package was not upgraded but the new deps were requested (?) and it makes that conflict.

Removing thonny in f30, upgrading and installing thonny back in f31 solves the problem.

There is also bugzilla issue https://bugzilla.redhat.com/show_bug.cgi?id=1774344 opened for this.

## Paun Narcis-Iulian

Take care, if on ssh remotely like I was, create a user and add it to sudoers because you will lose ability to connect root on ssh after the upgrade. Had to run with keyboard and monitor to server room to login and fix my mistake. I am sure there are others running servers only with root.

## RJF

After the F30 to F31 upgrade today Gnome workspaces don’t appear which is very annoying. Yes, I’ve tried toggling the various settings and extensions.

Plus wired networking is broken, which is temporarily fixed by booting into the older (ie still F30) kernel (or using wifi).

Sound didn’t work at first out of the headphone socket but that seems OK now, not sure if it was just a reboot that fixed it.

## bnjmn

Never mind (

Kernel support EXT3 was not enabled…recompiling now!!!

## River14

I’ve just upgraded from f30 to f31.

Everything works like a charm.

Great great job guys.

Congrats !!

## Suryatej Yaramada

docker is not working after upgrading to fedora31

docker run -it –entrypoint /bin/bash amazonlinux:latest

docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:297: applying cgroup configuration for process caused \”open /sys/fs/cgroup/docker/cpuset.cpus.effective: no such file or directory\””: unknown.

## Paul W. Frields

Out of curiosity, have you tried using podman? Same syntax:

podman run -it --entrypoint /bin/bash amazonlinux:latest## Kostya

Long time (since ~24) Fedora user.

dnf system-upgrade download is giving me network errors, on an otherwise perfect (~750 mbit) network connection.

I’ve tired several mirrors, including Yandex, U. Chemnitz and a server in Ukraine. All time out.

Anyone seen this or know of how to fix?

https://bugzilla.redhat.com/show_bug.cgi?id=1767781

## bioshark.dev

Just finished upgrading from F30 to F31 and everything ran smoothly (almost). I use Nvidia drivers from rpmfusion and the system works fine, and the latest driver is installed.

The only thing that is not working is a bunch of gnome extensions (which I believe will be fixed withing the near future):

– application menu

– dash to dock

– removable drive menu

cheers, and thank you for your work.

## Tz00

Fedora 31 leaves out cairo support (libcairo.so in /usr/…/lua/5.3/) for conky like 29 and 30 did at first. So, to use your conky scripts with rings, you need to download the old conky rpm, then dnf downgrade conky*.rpm to get cairo support (i.e. rings, clocks, etc). I tried to file a bug but the software said “not enough of a stacktrace … to file”.

So, if any other users are frustrated by this, use the aforementioned process to get your scripts running. Thanks

## bnjmn

SMB is now broken after upgrade

## Paul W. Frields

Please report bugs in Bugzilla, not here on the Magazine. We just report news and tips here. 🙂

## bnjmn

Yeah! apologies

https://bugzilla.redhat.com/show_bug.cgi?id=1768117

## Naheed Kamal

Upgrade to Fedora 31 is successful, but after selecting the fedora 31 boot from grub, no display, the PC going to sleep, so I forcefully restart and select fedora 30 to use my PC, please suggest me, what shout I do?

## Charles

Check your logs, you may find some useful information related to this issue.

eg:

1)journalctl

Just check all those lines when this issue happens.

2)/var/log/Xorg.X.log.old

X should be 0, 1 or 2, depending on your case. Use ‘ll /var/log/Xorg.* -rt’ to sort your files.

## Mark

It would be nice if when the upgrade instructions are posted for each new release they include a link to the known issues that will occur with the new release, so users can decide whether to upgrade or not.

For example one of the prior comments referred to docker not working on F31, where it was specifically decided as a release decision to let users suffer the pain of docker not working (reference https://bugzilla.redhat.com/show_bug.cgi?id=1746355 where they just decided not enough Fedora users use Docker services to care about it).

Rather than have a post saying F31 is available and here is how to upgrade, such a post really m u s t also contain a link to known issues with upgrading as part of the post. One benefit to the magazine would be a lot less comments about things breaking as users can decide what features they are willing to lose.

I believe having a post implying upgrade is easy without having a link to at a bare minimum the known issues that will occur when upgrading is reckless.

Especially when replies to comments are such as “Please report bugs in Bugzilla, not here on the Magazine” when it was the magazine that drove the upgrade.

I agree bugs should not be reported here, but nor should the magazine encourage users to blindly jump over a cliff by painting a rosy simple upgrade path. At the very least if there is not a published known bug list available to be linked to the title should include ‘how to upgrade at your own risk if you are really stupid’.

## Paul W. Frields

The announcement for the release has a prominent link to the common Fedora 31 bugs page. That page also has information on what to do if you don’t find your issue listed.

## Jery Mander

Fedora Failure – gui users and groups manager removed. Was fine in 30, no replacement installed by default. Very lame Fedora.

## Paul W. Frields

@Jery: This is incorrect. You can manage users through the Settings > Details control panel in Fedora Workstation; this allows you to add regular users as well as administrators (members of ‘wheel’). You may have another tool available if you’re using a different desktop flavor.

## sam

Going to upgrade from f30 to f31 hopefully doesn’t break things

## Jerry Mander

How does one bring up a graphical user and group control window on Fedora 31 with XFCE?

## Michal Ambroz

Hello,

upgrade of one of my machines went wrong (fc30 -> fc31)

[ OK ] Started D-Bus System message bus.

[ OK ] Started Bluetooth service.

[ OK ] Started IIO Sensor Proxy service.

[ OK ] Reached target Bluetooth.

You are in rescue mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” or “exit” to boot into default mode.

Give root password for maintenance

(or press Control-D to continue):

[root@machine]# exit

exit

Reloading system manager configuration

Starting default target

Failed to start default target: Operation refused, unit may not be isolated.

It turned out that for some reason the upgrade didn’t restore the default systemd target before rebooting.

This fixed the problem:

rm -f /etc/systemd/system/default.target

ln -s /lib/systemd/system/graphical.target /etc/systemd/system/default.target

On servers / machines without GUI it might be:

ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target

Good luck upgrading

## Marco

Hello folks,

after upgrade to Fedora 31 my laptop was unable to start into graphical.target runlevel: no errors displayed and laptop freeze after load “Gnome Display Manager”.

I’m able to start into multi-user.target runlevel and then start Gnome with startx.

Any helps on what to check?

Thanks,

Marco

## Michal Ambroz

Hello Marco,

Start with checking the error messages from the current boot and look for the errors:

journalctl -xb

Check that your local systemd configuration points to something reasonable (in my case it was pointing to /var/tmp/something and normal links were not restored with the finish of upgrade). It should be something like:

$ ls -lad /etc/systemd/system/default.target

lrwxrwxrwx. 1 root root 36 2019-11-07_18:50:49 /etc/systemd/system/default.target -> /lib/systemd/system/graphical.target

$ ls -lad /etc/systemd/system/graphical.target

lrwxrwxrwx. 1 root root 36 2019-11-06_16:35:56 /etc/systemd/system/graphical.target -> /lib/systemd/system/graphical.target

If “Gnome Display Manager” is not starting as a service, but you are able to start gnome with startx … the difference might be confined and unconfined mode. Some SElinux context might be wrong on some files, possibly from previous distro upgrades before fc30.

Try to relabel the filesystem with the default SE context by doing:

sudo touch /.autorelabel

sudo reboot

Then trying

systemctl start graphical.target

Check also the audit log for possible SE permission issues:

https://access.redhat.com/articles/2191331

tail -f /var/log/audit/audit.log

Mik

## Marco

Hello Michal,

problem solved, but because I was in a rush I did not investigate better and performed a fresh installation formatting all LV except the home to preserve my data.

Thanks,

Marco

## Jerry Mander

Several things that worked on Fedora 30 are being labeled as “broken” on Fedora 31. This seems to point to a failure in the new version of Fedora rather than all the supposed “broken” status of files that work fine in Fedor 30. Wish I could downgrade back to 30 and have my features back.

## Paul W. Frields

@Jerry: It’s inevitable that any system that allows a high degree of customization and twiddling can never achieve a “perfect” upgrade record. Unfortunately this is a pretty subjective measure. Many people upgrade with no problems. Overall Fedora keeps evolving and getting better every release though. One alternative is to try a fresh installation to see if that solves some issues for you.

## Tim Kissane

Just upgraded from Fedora 30 to 31 using the CLI. All went smoothly until I logged into the system for the first time to put the new kernel in place. Unfortunately, I get logged out less than a minute after logging in. I’ll try booting into single user mode to see if I can find a clue. This is what makes Linux fun! Since it’s not my daily driver, I can be light-hearted. 😉

## mgmg

Can not use 4 fingers Vertical Gestures (Switch Workspace action doesn’t work) after upgrade fedora 31.

## Remzi

I miss again my favorite desktop icons.

It’s ok when you don’t lik it but i like it.

I star my favorit apps verry fast when i see it on my desktop.

## Henrique Tschannerl

Hello, I’m trying to upgrade the Fedora Server 31 on the HP BL460C Gen1, but the system stop with this messages.

[OK] Reached targe Paths

[ TIME ] Timed out waiting for device

[ DEPEND ] Dependency failed for Resume from hibernation using device /dev/mapper