https://bugs.kde.org/show_bug.cgi?id=467827
Bug ID: 467827
Summary: Discover crash upon startup, failing to find flathub
Classification: Applications
Product: Discover
Version: 5.27.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Flatpak Backend
Assignee: plasma-b...@kde.org
Reporter: bery...@proton.me
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
Target Milestone: ---
Created attachment 157600
--> https://bugs.kde.org/attachment.cgi?id=157600&action=edit
backtrace
SUMMARY
Sometimes discover "can't find flathub" and doesn't launch.
`Could not find source: 0x7fffa001c240 "flathub"` (0x number probably doesn't
matter)
Very out of ordinary actually, randomly happens after an update is available
from flathub.
Even though I couldn't trigger intentionally(can't give virtual updates by
myself), I highly guess it's related to nvidia flatpak updates as it regularly
happens right after I get an nvidia update on system side.
OBSERVED RESULT
Discover crashes upon startup, before any gui is shown.
EXPECTED RESULT
Discover launched properly (obviously 😅)
Maybe temporarily ignore the broken backend instead of crashing and warn the
user about "unexpected issue with the flatpak backend: couldn't find flathub"
without forcing the user to use command line.
SOFTWARE/OS VERSIONS
Linux: Fedora 37 kernel 6.2
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
Can be worked around by using gnome-software or flatpak cli, then discover no
longer breaks. Can't trigger again until an update though, making it harder to
reproduce. I got the backtrace in 5.27.2 but it's not introduced in that
release nor fixed in .3, it's just that I couldn't get my way to report.
Attached backtrace, my first bug report, hope it's useful (✿^‿^)
--
You are receiving this mail because:
You are watching all bug changes.
