daily reboot needed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
With a clean installation of the os, Jammy, the last few weeks have been unworkable when it comes to snaps.
The symptoms with firefox are, which happened daily:
* During the day, links from mattermost suddenly don't open in firefox
* A few minutes later, tabs crash in firefox, and the restart button doesn't work
* A few minutes after that, firefox crashes and can't be loaded
* Starting firefox on the cli gives vagues messages about libaries not being available
* Reboot solves this
Mattermost desktop, crashed at least twice
* Just suddenly crashed without any signals leading up to the crash
* Starting didn't work
* Only a reboot solved this
On other moments the following happened, at least once in the last 2 weeks:
* Running a launch command for lxd/lxc to start a new conainer
* Perform an exec to execute a command inside the container
* Perform another exec command, and that complains that there is no longer an lxd socket
* Wait a bit trying to ssh into the container, which doesn't work
* Running an `lxc list` complains about a missing socket
* Reboot solves this
During all the struggles an attempt was made to improve the behavior by setting the following flag:
`snap set core experimental.
That didn't seem to make any difference
Attached is also the snapd.log from the journal that kind of describes what happened and the amount of reboots that took place, created with `journalctl --unit=snapd > ~/snapd.log`
Also filed firefox bug https:/ /bugzilla. mozilla. org/show_ bug.cgi? id=1800584 during this time, relevant as it shows some of the error messages I was getting. Which after a reboot were no longer reproducible.