Summary: | can't update snap in discover because they are already installed | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | kevindu52defargoth |
Component: | Snap Backend | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | aleixpol, julien.dlq, kevindu52defargoth, soumyadeepghosh2004 |
Priority: | NOR | ||
Version First Reported In: | 6.0.4 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
error message
the stalled update in the Update page |
Description
kevindu52defargoth
2024-05-16 20:02:17 UTC
The update was auto applied in the background probably. And there is no update available anymore. Can you give us some more input? Created attachment 174114 [details] the stalled update in the Update page (In reply to Soumyadeep Ghosh from comment #1) > The update was auto applied in the background probably. And there is no > update available anymore. Can you give us some more input? Of course. The issue is still present, each time I update I get a notification about snap being incompatible with security sandboxing, then the error. Everything else update normally. Since last time, I noticed Firefox is up to date. The package is still outdated according to snap info: ``` latest/stable: 4.7.0 2023-06-26 (69) 30MB classic latest/candidate: ↑ latest/beta: ↑ latest/edge: 4.7.0 2023-11-02 (80) 30MB classic installed: 2.0.0 (27) 33MB - ``` In the Update tab, Discover simply says "Refresh of version 2.0.0". When I go Installed > Bash Language Server, it says the installed version is 2.0.0. But then in Update the text turned into "Refresh of version 4.7.0". When I apply the update in this state, it hit the error, then the text turns back to "Refresh of version 2.0.0". Try clearing the cache, and see what happens. remove this file `rm -rf $HOME/.cache/discover` Removing `$HOME/.cache/discover` didn't solved the problem. I also deleted `/var/lib/snapd/cache/*` and now the issue is gone. Thanks for the help |