https://bugs.kde.org/show_bug.cgi?id=507636
Bug ID: 507636
Summary: Checking for updates triggers Snap to update on its
own, so I always get an "error" that Snap updates are
already in progress or completed
Classification: Applications
Product: Discover
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Snap Backend
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
I have a couple of Snaps installed. When I check for updates in Discover, it
sometimes shows that these Snaps or the "base Snap" need updates. However, it
seems that the backend checking what Snaps need updating actually triggers Snap
to update them itself, thus Discover gives me an error that Snap updates are
already in progress, or that there are no updates for Snap to apply. This is
non-critical, as I can just ignore the error, but it is annoying nonetheless.
STEPS TO REPRODUCE
1. Install a Snap package via any method (although, come to think of it this
one was required to be installed in classic mode).
2. Wait until said Snap is ready to update.
3. Attempt to perform system updates in Discover.
OBSERVED RESULT
Discover prompts you for sudo permissions, but then gives an error that there
are no updates to apply or that they are already in progress.
EXPECTED RESULT
Discover performs the updates without throwing an error.
SOFTWARE/OS VERSIONS
Windows: No
macOS: No
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora 42 KDE Edition x86 64-bit
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
ADDITIONAL INFORMATION
I think I had to make a symlink somewhere to make classic mode for Snaps work,
per instructions from Snap's error message at the time I think.
--
You are receiving this mail because:
You are watching all bug changes.
