** Changed in: snapd
Status: Incomplete => Confirmed
** Changed in: snapd
Importance: Undecided => High
** No longer affects: snapd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
I saw a similar crash on Tuesday, when gnome-3-38-2004 was automatically
refreshed from revision 39 to revision 76 under a running firefox (with
refresh app awareness enabled). The next time I interacted with firefox,
it crashed instantly.
Ian helped me debug the issue further in a private convers
snap list gnome-3-38-2004 --all
Nom VersionRévision Suivi Éditeur Notes
gnome-3-38-2004 0+git.6ba6040 70latest/stable canonical✓ désactivé
gnome-3-38-2004 0+git.6ba6040 76latest/stable canonical✓ -
I do not have nothing left in snap change
@fthx can you show the output of `snap changes` and `snap list
gnome-3-38-2004 --all` ? What I suspect made your firefox crash is that
the last revision of gnome-3-38-2004 that firefox was launched with was
garbage collected out of existence
--
You received this bug notification because you are a
Updating gnome snap will remove the mount points from the firefox snap
mount namespace. It should not be done. I'm afraid r-a-a should be
extended to prevent refreshes of any connected snaps with the content
interface as well.
--
You received this bug notification because you are a member of Ubun
Ok I've done some logs-crawling.
17h22, gnome snap refreshed
Just 1 minute after that, some Firefox logs:
ExceptionHandler::GenerateDump cloned child 40921
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::GenerateDump cloned child 40921
ExceptionHandler:
Hmm, actually though I cannot reproduce the specific crash/error on my
machine, I was running the firefox snap and I tried both refreshing
gnome-3-38-2004 from revision 61 -> 76 and the inverse of 76 -> 61, can
you describe how the crash happened? Did you do some specific thing in
firefox when the
Thanks for that information, for now I think that it is expected that
refreshes to dependency snaps are not blocked by active snaps using
those dependencies, but that is something I think we should explore
doing automatically.
We are actively working on hooks which snaps can implement manually
whi
snap version
snap2.51.4
snapd 2.51.4
series 16
ubuntu 21.10
kernel 5.13.0-16-generic
snap list
NomVersion Révision Suivi
Éditeur Notes
bare 1.0 5 latest/stable
canonical✓base
c
Hi, can you provide the output of
snap version
snap list
Thanks
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Incomplete
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
10 matches
Mail list logo