Public bug reported:
Every day for the past few days I've been getting notification 'pending
update of chromium snap (n) days left'. I noticed earlier that chromium
seems to crash my system when it updates(at least it warns now so i can
know it's doing it) - as in when i come back to log in after the update,
to xorg/gnome, the caps lock doesn't turn on when pressed, and there's
nothing but a black screen - ie the system is completely unresponsive.
tried hitting magic Sysrq+i to no avail. Had to hard reboot the system
with the power button.
system was working just fine last night at 1030pm, so whatever happened
had to be after then is what did it:
I just got another one saying 13 days left.
from kern.log
Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change
from 0 to 303936
Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400
audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575
comm="apparmor_parser"
Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400
audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
pid=1586575 comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400
audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.hook.configure" pid=1586580
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400
audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap-update-ns.chromium" pid=1586577
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400
audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.chromium" pid=1586579
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400
audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.chromedriver" pid=1586578
comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400
audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400
audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400
audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.cancel" pid=1586584 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400
audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.accept" pid=1586583 comm="apparmor_parser"
nothing in syslog from 2:38am
ubuntu 20.04
linux: custom kernel 6.0.7 with squashfs bug hotfix
( but it's been crashing during snap updates since at least the 5.x )
root@eva1:/var/log# apt-cache policy chromium-browser
chromium-browser:
Installed: 80.0.3987.163-0ubuntu1
Candidate: 80.0.3987.163-0ubuntu1
Version table:
*** 80.0.3987.163-0ubuntu1 500
500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
actual version post update:
Version 109.0.5414.74 (Official Build) snap (64-bit)
which is different than the last time I saw it ( 103.0.5060.134 ) so
it's clearly updating itself, which supports the idea that the snap is
updating during the crash
but it would be nice to not hard lock my whole desktop system every 2
weeks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 26 09:44:00 2023
InstallationDate: Installed on 2017-04-18 (2108 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 109.0.5414.74 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2020-04-25 (1005 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2003962
Title:
chromium snap update makes system unresponsive, black screen
Status in chromium-browser package in Ubuntu:
New
Bug description:
Every day for the past few days I've been getting notification
'pending update of chromium snap (n) days left'. I noticed earlier
that chromium seems to crash my system when it updates(at least it
warns now so i can know it's doing it) - as in when i come back to log
in after the update, to xorg/gnome, the caps lock doesn't turn on when
pressed, and there's nothing but a black screen - ie the system is
completely unresponsive. tried hitting magic Sysrq+i to no avail.
Had to hard reboot the system with the power button.
system was working just fine last night at 1030pm, so whatever
happened had to be after then is what did it:
I just got another one saying 13 days left.
from kern.log
Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change
from 0 to 303936
Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400
audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575
comm="apparmor_parser"
Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400
audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
pid=1586575 comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400
audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.hook.configure" pid=1586580
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400
audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap-update-ns.chromium" pid=1586577
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400
audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.chromium" pid=1586579
comm="apparmor_parser"
Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400
audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="snap.chromium.chromedriver" pid=1586578
comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400
audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400
audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400
audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.cancel" pid=1586584 comm="apparmor_parser"
Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400
audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace"
info="same as current profile, skipping" profile="unconfined"
name="snap.cups.accept" pid=1586583 comm="apparmor_parser"
nothing in syslog from 2:38am
ubuntu 20.04
linux: custom kernel 6.0.7 with squashfs bug hotfix
( but it's been crashing during snap updates since at least the 5.x )
root@eva1:/var/log# apt-cache policy chromium-browser
chromium-browser:
Installed: 80.0.3987.163-0ubuntu1
Candidate: 80.0.3987.163-0ubuntu1
Version table:
*** 80.0.3987.163-0ubuntu1 500
500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
actual version post update:
Version 109.0.5414.74 (Official Build) snap (64-bit)
which is different than the last time I saw it ( 103.0.5060.134 ) so
it's clearly updating itself, which supports the idea that the snap is
updating during the crash
but it would be nice to not hard lock my whole desktop system every 2
weeks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 26 09:44:00 2023
InstallationDate: Installed on 2017-04-18 (2108 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 109.0.5414.74 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2020-04-25 (1005 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2003962/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
