Crash in "Software" app when updating Flatpaks on Zorin OS 17.3

Issue Description:
The GNOME Software application (used in Zorin OS as "Software") freezes and becomes completely unresponsive when attempting to update Flatpak applications. This behavior occurs when the remote repository server (in this case, the Flathub CDN) responds with an HTTP 403 Forbidden error.
Expected Result:
The application should handle this network error gracefully. It should not freeze. Instead, it should display an error message to the user (e.g., "Update failed: Access Denied" or "Update source is unavailable") and remain interactive.
Actual Result:
The application UI hangs indefinitely. A system-level check with ss -tp reveals that the underlying TCP socket is stuck in a persistent CLOSE-WAIT state. This indicates the application is not properly closing the connection after the server has terminated it, likely due to an unhandled exception.
Here is the relevant output from ss -tp showing the stuck connection:

State       Recv-Q  Send-Q  Local Address:Port      Peer Address:Port      Process
CLOSE-WAIT  76      0       192.168.0.100:47008     151.101.1.91:https     users:(("gnome-software",pid=1452,fd=37))

What Linux distribution are you using?
I am using Zorin OS 17.3 The problem occurs specifically with Flatpak packages.
Log File:
I will follow the instructions to generate a verbose log and attach the gnome-software.log file to this report. log

I hope this detailed report helps in making Zorin OS even better. Thank you for your time and for this great operating system.

1 Like

This is a known bug in pre-Gnome 46 versions of Gnome Software Flatpak plugin.
It remains present in the latest versions, though the earlier versions (Zorin OS 17 is using Gnome 43) it seems more prevalent.

The easiest workaround, currently, is to run the flatpak updates from the Terminal:

flatpak update

1 Like

Did You tried it with reinstall of Flatpak, the Plugin for Gnome Software and adding the Flathub Source again?

Thanks, Aravisian. Yes, using the terminal works fine as a workaround. I was hoping to get the GUI fixed, but I understand it's an upstream GNOME issue