Chromium snap package was out of date

[Richmond]

Tommy Trussell wrote:
> On Thu, Aug 29, 2024 at 1:27 PM Richmond via ubuntu-users
> <ubuntu-users at lists.ubuntu.com <mailto:ubuntu-users at lists.ubuntu.com>>
> wrote:
>
>     Tommy Trussell wrote:
>     >
>     > On Tue, Aug 27, 2024 at 11:32 AM Richmond via ubuntu-users
>     > <ubuntu-users at lists.ubuntu.com
>     <mailto:ubuntu-users at lists.ubuntu.com>
>     <mailto:ubuntu-users at lists.ubuntu.com
>     <mailto:ubuntu-users at lists.ubuntu.com>>>
>     > wrote:
>     >     Although my system had been updated, both apt and the gnome
>     software
>     >     updates reported it up to date, I found that chromium had
>     not been
>     >     updated for 5 days and was out of date:
>
>  ...
>  
>
>     >
>     > There are several reasons a snap might not be updated. The most
>     common
>     > reason is if the application is running, the snap daemon will delay
>     > the update.
>
> ... 
>
>     According to chatgpt, snaps are updated by the snapd process four
>     times
>     a day. I can see snapd is running. I don't think I was using
>     chromium at
>     the time. Is there a log I can check? I tried:
>
>      snap logs snapd
>     error: snap "snapd" has no services
>
>     snap logs chromium
>     error: snap "chromium" has no services
>
>
> [ I have never used chatgpt. I do not trust it. Sorry I had to get
> that off my chest. ]
>
> OK, so I just read the man page for snap, followed the link from the
> man page to the documentation, read some documentation, and then did a
> Google search to find a relevant AskUbuntu Stack Exchange entry.
> Here's my custom ChatTommyT suggestion:
>
> If your chromium snap has not updated, open a terminal and try this:
>
> $ sudo snap refresh chromium
Yes but as I said in my original post, I have updated it.
>
> If there is a running process keeping the snap from updating, the
> results of the above snap command will indicate it. I think it will
> indicate the PID of the blocking process to help you kill it. (But
> before randomly killing off processes, you might look a bit to see if
> there's a good reason things are still running, or maybe they're just
> "stuck.") [Personally, I'd use the ps -ux command before killing
> anything to have a quick look at ALL the things running under my
> login, but that's only because I've been tinkering with stuff since
> the 1980s, and I hope someday I will understand more of it. You can
> get the same listing using the System Monitor app, and you might even
> be able to kill it from that application.]
>
> Finally, you might also check to make certain the snap is on the
> expected "channel" (normally "stable," but for example could be "beta"
> or "edge,") for the Chromium snap. 
>
> $ snap list chromium
> Name      Version        Rev   Tracking       Publisher   Notes
> chromium  128.0.6613.84  2934  latest/stable  canonical✓  -
>
I gave this information in my original post. My question is, why was it
not up to date, and how can I check that packages are being updated
automatically, as the documentation says they are supposed to be?
Updating them manually does not verify that they are being updated
automatically.