Summary: | Impossible to update Firefox flatpak, discover installs the same update repeatedly | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Patrick Silva <bugseforuns> |
Component: | discover | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | jgrulich |
Priority: | NOR | ||
Version First Reported In: | 5.10.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Silva
2017-06-19 21:54:37 UTC
Could you please start discover from a konsole and share the output from the update? here is Failed to install "Firefox Nightly - Wayland build" : While pulling app/org.mozilla.FirefoxNightlyWayland/x86_64/master from remote org.mozilla.FirefoxRepo: Need more input Failed to install "Firefox Nightly - Wayland build" : While pulling app/org.mozilla.FirefoxNightlyWayland/x86_64/master from remote org.mozilla.FirefoxRepo: Need more input Could you try out whether this works when you run "flatpak update org.mozilla.FirefoxNightlyWayland"? Yes, I can update via Konsole. Yesterday flatpak update failed on neon dev again, but Discover showed an error message quikly, placed in a grey box. Afer few seconds, the error message disappeared and the only information visible was "no update available". On Arch Discover 5.10.2 shows no feedback when flatpak update fails. You get the passive popup (grey box) because it was added recently into discover so users know whether there was an error or not. Your issue seems to be this one https://github.com/xhorak/firefox-devedition-flatpak/issues/1 which doesn't seem to be related to Discover. Thank you Jan. Why does the error message (passive pop up) disappear automatically after few seconds? Is this behavior intentional or a bug? It's how passive messages work. It's unrelated to this issue nevertheless. If the passive pop up appears/disappears while another window is focused, it's not possible to know what happened. Maybe I will open a new report about this. Thanks again. It was showing both an issue in flatpak and an issue in kirigami. |