GNOME 40.1
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2021-b35c663112
Please login to add feedback.
0 | 1 | Test Case Gnome Files |
0 | 1 | Test Case Gnome Maps |
0 | 0 | Test Case base initial setup |
0 | 1 | Test Case calc |
0 | 0 | Test Case desktop update graphical |
0 | 0 | Test Case desktop update graphical/it |
0 | 0 | Test Case desktop update notification |
0 | 0 | Test Case desktop update notification/it |
0 | 1 | Test Case disk management basic |
0 | 0 | Test Case disk management lvm |
0 | 0 | Test Case disk management modify |
0 | 0 | Test Case disk management multipath |
0 | 0 | Test Case disk management remote |
0 | 0 | Test Case gnome initial setup domain join |
0 | 1 | Test Case maps |
0 | 0 | Test Case package install remove |
0 | 0 | Test Case upgrade gnome-software current workstation |
0 | 0 | Test Case upgrade gnome-software previous workstation |
This update has been submitted for testing by kalev.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
kalev edited this update.
This update's test gating status has been changed to 'ignored'.
kalev edited this update.
This update has been pushed to testing.
seems ok. I did not find something special. There are two wiki-pages (and mentioned test cases) for gnome-maps for testing this application. One should be obsolete.
This update can be pushed to stable now if the maintainer wishes
@ibims Thanks! I have never edited the test cases wiki pages, but I think you could just try to remove one of them yourself.
Works for me. No regressions noted compared to previous version.
Works
This update has been submitted for stable by bodhi.
Everything seems fine, except for GNOME Software - now It crashes, while open, when installing flatpak applications using flatpak's CLI. It crashed a few times just running in background too, but I can't tell if this is strictly related to this same condition.
This update has been pushed to stable.
fmarcos, could you file a bug, please? Ideally with the backtrace of the crashes. It might be caught by ABRT, thus make it easier to be filled. Thanks in advance.
@mcrha, I think the most appropriate name for the issue I am facing is 'deadlock', sorry for wording it badly. The app window closes most of the time when the deadlock happens, but it appears that the process itself isn't crashing (is that possible?). I can't seem to find any stack-trace or error in the journal, just a bunch of 'refreshing metadata' debug info. Sometimes gnome-shell will prompt me to choose between 'force-quit or wait' right before it happens. Hope that helps, I still can file a bug with the info I have, in case you can't reproduce it.
File it, please, thus we can investigate further.
As started, install debuginfo packages for glib2, gtk3, evolution-data-server and evolution, then, when it freezes the GUI, instead of letting GNOME Shell to kill the application switch to a terminal and grab a backtrace. You can get the backtrace with a command like this:
$ gdb --batch --ex "t a a bt" --pid=
pidof evolution
&>bt.txtPlease check the bt.txt for any private information, like passwords, email addresses, server addresses,... I usually search for "pass" at least (quotes for clarity only).