Manual check for updates gets stuck, possibly doing nothing
- Installed version:
gnome-software-41.0-6.fc35.x86_64
- Platform: Fedora 35 Beta (Workstation Edition)
Clicking the refresh button on the Updates page caused the Software window to get stuck on "Loading Updates".
Unlike #1509 (closed) (which involved fwupd updates), this scenario looks like Software isn't actually looking for updates at all.
Steps that led to this:
- Ran
sudo flatpak repair
andflatpak --user repair
to fix some potential issues I was having with permissions of Flatpak installation files - Updated all Flatpak apps with
flatpak update -y
- Rebooted computer in airplane mode & without a wired connection
- After a few minutes, plugged in an Ethernet cable
- Disabled some fwupd remotes as recommended by https://github.com/fwupd/fwupd/issues/3906#issuecomment-951905811
- Opened a Software window, viewed the Updates tab, and clicked the refresh button
Software's stdout at around the time of the refresh click is:
15:06:08:0580 Gs Hourly updates check
15:06:08:0580 Gs Chaining cancellation from 0x55a26267c160 to 0x55a2640a98e0
15:06:08:0580 Gs Getting updates
15:06:08:0580 Gs Chaining cancellation from 0x55a26267c160 to 0x7faaa09836e0
15:12:35:0603 Gs setting state from idle to action-refresh (has-update:0, has-upgrade:0)
15:12:35:0603 Gs Chaining cancellation from 0x55a2688cc8e0 to 0x55a264d2a1e0
The refresh button was clicked at 15:12. Nothing was printed to stderr around that time, and nothing more has been printed to stdout even a half hour after clicking the refresh button. And FWIW, tiles on the Explore view remain blank (#1070 (closed)).
From this, my guess is that an update check had been launched automatically in the background and was pre-empted by my click of the refresh button, leading to some kind of deadlock.
(Then again, clicking elsewhere in the Software window doesn't print anything else to stdout, so maybe something broke my logging.)
And here is the output of gdb --batch --ex "t a a bt" -pid=$(pidof gnome-software)
: bt-noop-update.txt (Perhaps connecting to gdb
is what broke my logs, which were being piped into tee
.)
Note that Software was launched with verbose output and the G_DEBUG=fatal-criticals
flag, and it didn't crash. Also note that the gnome-nightly
Flatpak remote is not enabled.
Potentially a dup of #1472. (With that said, I don't expect a quick fix for this; I'm just going to log any hangs I experience in the hopes that they'll be of use to development.)