gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Addition for bug report 1930128

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat May 29 12:20:21 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1608008084
GsettingsChanges:
 b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
 b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
 b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
 b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Unfortunately automatic crash dump analysis seems to have failed but this looks like the problem:

      g_warning ("%s: Unable to create an Offscreen buffer", G_STRLOC);

      cogl_object_unref (priv->target);
      priv->target = NULL;

Seems like the crash is probably priv->target being used as NULL, somewhere. But we don't know where or why. Seems strange a GeForce RTX 2070 would run out of resources, if that's what you're still using...

Please look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

[Johannes Mages (johnnii360)]

Hi Daniel,

sorry but in this case there is no error tracker for 2021-05-29: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

[Daniel van Vugt (vanvugt)]

You did however experience bug 1886059 on 2020-05-16.

[Johannes Mages (johnnii360)]

Oh, didn't see that. Sorry! But yes I had this issue sometimes in the past but now was the time to report it finally. :) It's a bit annoying to get this freeze sometimes. But I don't know in what connection with what App it was.

[Daniel van Vugt (vanvugt)]

I've tried forcing the error in GNOME 3.36, 3.38 and 41.beta, but none of them result in a crash. Only error messages. So whatever your crash is or was, we will need more information. Please:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then try reproducing the crash again and then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

[Johannes Mages (johnnii360)]

I already did. This is the addition for 1930128. There is no extra crash file for gnome shell. This here is the only one.

[Daniel van Vugt (vanvugt)]

I guess we're waiting for the bug to happen again (and again). Please follow the instructions each time because without that extra info we have no way to move forward.

If no further comments are added for 60 days then the bug will close automatically.

[Johannes Mages (johnnii360)]

Hi Daniel! The issue occurred again today. In this time I was connected via AnyDesk to my PC from my office to fill my database in Tellico. Now it's always black screen. I will add some additional informations this evening when I'm at home.

[Johannes Mages (johnnii360)]

Ah never mind. The Display Port of my RTX 2070 stopped working.

[Johannes Mages (johnnii360)]

Okay today it really happened again after standby mode. I got nothing about a crash in /var/crash and in my https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 isn't something either. Magic SysRq couldn't be used because the system was completely frozen.

This is the only thing I can offer you, but maybe it will not help you:

20:16:17 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:43 gvfsd-dnssd: Error calling org.gtk.vfs.MonitorClient.Changed(): Zeitüberschreitung wurde erreicht (g-io-error-quark, 24)
20:12:43 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:13 Xorg: (II) event1 - Power Button: device is a keyboard
20:12:13 gnome-shell: cr_declaration_parse_list_from_buf: assertion 'parser' failed
20:12:13 Xorg: (II) event8 - Logitech Gaming Mouse G502 Keyboard: device is a keyboard
20:12:13 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:13 Xorg: (II) systemd-logind: got resume for 13:69
20:12:12 psensor: [2021-09-14T18:12:12] [ERR] nvctrl: Failed to retrieve measure of type 20204 for NVIDIA GPU 1
20:12:12 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
19:14:29 Xorg: (II) systemd-logind: got pause for 13:65
19:14:28 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps

[Johannes Mages (johnnii360)]

Ooookay... I've seen a comment in the Ubuntu Software Center at the Firefox that the Firefox cause this weird freezes.

[Daniel van Vugt (vanvugt)]

I still can't find any other reports of this crash. Maybe it's caused by something uncommon like an extension, maybe <email address hidden>? Please try disabling all non-Ubuntu extensions and then log in again.

[Launchpad Janitor (janitor)]

[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]