|Summary:||gnome-software crashes while fedora-third-party enable is run|
|Product:||[Fedora] Fedora||Reporter:||Kamil Páral <kparal>|
|Component:||gnome-software||Assignee:||Milan Crha <mcrha>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||37||CC:||awilliam, gnome-sig, mcrha, rhughes|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2022-09-12 17:47:21 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Kamil Páral 2022-09-07 12:20:01 UTC
Comment 1 Milan Crha 2022-09-07 15:07:02 UTC
Thanks for the backtrace. My semi-wild guess is that this is . Seeing one thread in the flatpak's curl code could be a hint, but not necessarily. I see the  is included in flatpak 1.14.0. It does not seem to be in Fedora yet. It will be good to re-test once it's available.  https://github.com/flatpak/flatpak/issues/3701
Comment 2 Kamil Páral 2022-09-08 13:29:06 UTC
Thanks. I tried it a few times with flatpak 1.14 and no crash occurred, so it might really fix this problem: https://bodhi.fedoraproject.org/updates/FEDORA-2022-786cdbe62c Proposing as a freeze exception, in case we don't sign off Beta today. (Please note that the gnome-software crash might occur not just when running the command manually in the terminal, but also when enabling the flathub selection repo graphically from inside gnome-software itself).
Comment 3 Fedora Update System 2022-09-08 15:30:04 UTC
FEDORA-2022-786cdbe62c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-786cdbe62c
Comment 4 Adam Williamson 2022-09-09 22:40:46 UTC
Beta is signed off, so this can't go into it. Moving to proposed Final FE, though of course it can go in before the Final freeze with no FE status needed.
Comment 5 Fedora Update System 2022-09-12 17:47:21 UTC
FEDORA-2022-786cdbe62c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.