snap-store can't be updated due to autostart

Need to add option for users to be able to disable snap updates. When this option is turned on no notifications should be displayed.

According to question on askubuntu ( https://askubuntu.com/questions/1412575/pending-update-of-snap-store ) this issue is affecting more then 100K users.

Snap was advertised as a convenience. It has turned out to be a nuisance. The solution is NOT to disable it. The solution is to FIX IT.

I would not want snap to kill most of my snap installed apps however....

 if (it's just snap-store holding up the show) && (I am not really using it) {
    kill_snap-store(asap);
    update_snap-store();
    rejoice_ur_no_longer_a_PITA();
} else {go_work4_MS$}

huh?

How long does it take for Snap maintainers to get off their high horse and fix bugs that hurt their users? The reluctance to purge Snap from Ubuntu (Desktop) is slowly killing it.

Meanwhile Flatpak just runs fine for my desktop needs. Snap on servers is the one component I advise traditional companies against using Ubuntu and stick with RHEL clones or choose Debian (take a look at what Bitnami are doing and accept that Linux on Chromebooks is also a Debian, ... and that Ubuntu on WSL should be considered broken when you expect Systemd to be working). So, the value of Snap and Snapcruft? A misleading middle ground between Kubernetes-based Container Orchestration for high availability services on servers and Flatpak sandboxed desktop apps.

Would the world look different if Ubuntu Phone had gained significant market share? Sure! But it didn't. Today's developers who still have problems figuring out a path from Docker to Kubernetes would suffer less if a company like Canonical told them: We migrated from our proprietary system to Kubernetes-like Podman and you can do too! You don't have to reinvent the wheel. Just put a stop on your losses and commit to the standards everyone else has been working in the industry with for years.

But uh, well, snap store can't update itself. Status: Confirmed; Importance: Undecided; Unassigned. For months.

Says it all. Purge Snap.

For my own mental health, I do not wish to read comments like the preceding one; unsubscribing.

Please do not be rude. Ranting into a bug report form doesn't actually help anything. I am sorry that developers who are trying to help are being treated in this way.

Rudeness aside though I think there is a valid point in this particular bug report. I am not even close to an expert in snap, but it does seem that having a snap that runs continuously in the background (even when the UI is closed) makes for a bad UX when combined with snap's default update / notification policy.

The original poster wrote a much more thorough post than I could, so I won't reiterate that, other than to say that a startup-based solution might not work for my use case. I use Ubuntu on desktop, and routinely have the system (and by extension snap-store) running for days or weeks at a time. I am not super inconvinienced by having to manually kill a snap-store process, I am comfortable in a terminal environment. I am more concerned because of exposing that kind of experience to people who might not be comfortable with that.

Anyway, don't know if this will help the effort or not, but just throwing in my +1 and input.

As an occasional user of Linux/Ubuntu I have to say that issues like this are what is preventing Linux/Ubuntu from becoming mainstream. Your average retail home computer user is going to run a mile when presented with a recurring issue like this. I am reasonably comfortable with using the command line but when was the last time that a Windows, Apple or Android user had to do that?
Surely the update script for Snap Store could be incorporated into the update process so that it shuts itself down to facilitate the update.