hey Daniel,

if I'm reading the first part of your reply right, it sounds like gnome-
shell extensions can hard crash gnome-shell? which means it's not safe
to ever use any extensions? i feel like i must be misunderstanding that,
since ubuntu distributes a set of extensions by default in the desktop
env, and that wouldn't make sense if the shell extensions are so
dangerous.

on to the next steps, there's no crash files in that dir, but there are
files called `_usr_bin_gnome-shell.1000.upload` and `_usr_bin_gnome-
shell.1000.uploaded`. I'm assuming that's what ties into
errors.ubuntu.com.

I see a ton of errors around gnome on that site for my whoopsie-id, lots of 
gnome-shell and gnome-settings-daemon crashes:
https://errors.ubuntu.com/user/3e155148c8cdcde9fe5cd5283283ef9837d7582a978ff3ce587c63aefe0cd3d3bc1bbe4921b8fff669e75ac4de5f3962de964e0df2f56142604e65bb3aa47f5c

it doesn't let me look at those crash reports so I don't really have a
clue what the root cause could be, but hopefully you have access to them
and can investigate further.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1906137

Title:
  gnome-shell on 20.10 crashes all the time

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  this is probably a dupe of a bunch of other gnome-shell crashing bugs.
  just noting that since upgrading to 20.10, both my systems (which use
  the nvidia binary X drivers) have gnome-shell crashing multiple times
  a day. it restarts fine, but while it's crashing it locks up the whole
  system for a minute or two. no idea why the release in 20.10 is so
  much more unstable than 20.04, but here we are.

  as a starting point, how do I track down what it considers the cause
  of the crashes? I can't discern anything particularly useful from
  `journalctl` at first glance. is there a specific error message I can
  search for in all the noise to find where it crashed and see what
  happened right before that? I see a lot of these in the logs, but they
  seem to be non-fatal, and they also don't print out any actual stack
  traces to examine:

  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==
  Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 
0x55995401f220 ==

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14
  Uname: Linux 5.8.0-29-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 28 22:11:09 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-15 (137 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906137/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to