You're welcome, I'm glad we eventually figured it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960313
Title:
[snap] chromium crashes regularly
To manage notifications about this bug go to:
I'm embarrassed now as I'd not detected that (and further telegram was
also shutdown & I'd not even noticed..)
Alas I'm somewhat aware of disk space issues.. (but deal with that only
if the box won't let me login) but as I'd not been denied login for
awhile hadn't noticed how serious it'd
Thanks for the additional info and for the logs Chris. So Chromium was
abruptly killed, and the logs don't contain any hint as to why this
might have happened.
I wonder whether this could be an out of memory situation, where the
kernel decided to kill Chromium to free up memory. Could you inspect
Sorry, I missed the prior crash, but hopefully this one contains
something that is useful
https://pastebin.ubuntu.com/p/c5TTS6bXdP/
Not sure if helpful, but I use `chromium` for sites related to google
(or where I use google SSO to login).
- gmail (regularly refresh this; it's set for manual
Thanks for the additional info.
We can rule out a background refresh of chromium or any of its dependencies
(core20, gnome-3-38-2004, gtk-common-themes).
Since the crash reporter isn't enabled in chromium (it's a chrome-
specific thing), may I suggest that you run chromium from a terminal
with
guiverc@d960-ubu2:/de2900/others/railway$ snap info --abs-time gnome-3-38-2004
name: gnome-3-38-2004
summary: Shared GNOME 3.38 Ubuntu stack
publisher: Canonical✓
store-url: https://snapcraft.io/gnome-3-38-2004
license: unset
description: |
This snap includes a GNOME 3.38 stack (the
