Every time i try and update or install a flatpak with discover i get this error.
Every time i try and update or install a flatpak with discover i get this error.
both buttons cancel the download, but "proceed" also makes discover freeze, is this a known issue? Also, here's the system info:
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i3-10105F CPU @ 3.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600`
Edit replacing my original comment:
Looks like that package has been superseded by org.gtk.Gtk3theme.Breeze. That's what I'm using, and it is receiving updates.
$ flatpak remote-info flathub org.gtk.Gtk3theme.Breeze-Dark ID: org.gtk.Gtk3theme.Breeze-Dark Ref: runtime/org.gtk.Gtk3theme.Breeze-Dark/x86_64/3.22 Arch: x86_64 Branch: 3.22 Collection: org.flathub.Stable Download: 156.9 kB Installed: 386.6 kB Commit: 5a19b0c0808f82290d1f64c95d2406a860329817e0f269b4aaf0a1bbba92323a Parent: 390f820d32df2f22e3a3165eb4d65071dcb93a357ae7730f4ca548b5d016b966 End-of-life: This theme has been replaced by org.gtk.Gtk3theme.Breeze, see README for workaround on using system color schemes. https://github.com/flathub/org.gtk.Gtk3theme.Breeze#workarounds Subject: Add EOL (fc4339ff) Date: 2022-02-22 00:21:51 +0000
7 0 Replythank you,
flatpak remove org.gtk.Gtk3theme.Breeze
did the trick4 0 ReplyIn Fedora, I ran into the same issue, but I fixed it by running flatpak update -y in terminal. Hopefully that works on your end as well.
1 1 Reply
Looks like a runtime is outdated and the repo to install a new runtime is missing. Then when Discover tries to update, crashes cause there is nowhere to download from
Try update the package from terminal
3 0 ReplyTo add to the other answers: Yes, it is a known bug and I think it is being fixed in Plasma 6.1.2 or 6.2
2 0 ReplyOh nice, good to know
1 0 Reply
In Fedora, I ran into the same issue, but I fixed it by running flatpak update -y in terminal. Hopefully that works on your end as well.
3 1 ReplyUnfortunately it didnt, i fixed it by uninstalling the no longer updated dependency
2 0 ReplyCould you explain how? i tried uninstalling it, but I still got the problem in discover and it will reinstall on each update somehow.
1 0 Reply