Cheers, and thanks to you for your detailed reply and descriptions
again.
Indeed, based on your descriptions, I don't think any part of it is
Firefox-specific, and it may be best to close this and open a new bug
under the snapd package with appropriate descriptions (please feel free
to include a l
Thanks for the help. This installation, where I have tried to debug the
problem, is installed in a virtual machine. Other installations are on
bare metal. I did the Firefox 128.0 update manually. 128.0.2 seemed to
be available for five days before Firefox updated directly to 128.0.3
This is the lon
Thank you for the explanations, and for looking to make a new report
against snapd if the problem persists.
I believe by default snapd won't auto-update any running snaps, for a
period of 15 days. If 15 days have passed but at the time of the auto-
update check the snap is still running, snapd wi
No problem. The reason I reported under Firefox was because the other
snaps have updated automatically. One time even so that Firefox was not
updated and another snap application was updated at that time.
But maybe that's a better place to report anyway. I can't access those
two machines right awa
Hello, and thanks for the report.
I am indeed not aware of any issues with the snaps auto-update process.
Per https://snapcraft.io/docs/managing-updates snaps update
automatically by default, with snapd checking for updates 4 times a day.
If you do notice/experience an issue with the updates, it
An update.
For some reason, Firefox just got updated. Never done it automatically
before in this installation. This affected system was installed on June
11. I'll have to check the other two installations later. There have
been no other new updates to the system after reporting issue.
apparmor
