gnome-shell crashed with SIGSEGV in meta_wayland_data_source_cancel() from meta_selection_source_wayland_deactivated() from _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit_by_name() from meta_selection_set_owner()

[Kai Groner]

https://errors.ubuntu.com/problem/bfae33153e95403126b6f11489857bf579e761ee

---

This crash happened as I was changing the batteries for my wireless mouse. Needing to change the batteries in the middle of a session is routine and has not lead to this failure previously.

There is a crash report, with the following oops id:

https://errors.ubuntu.com/oops/8ad61c2c-16e5-11ea-b0eb-fa163e983629

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 4 17:44:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (169 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Unfortunately that oops ID says:

"This problem failed to retrace because there was no crash signature after retracing."

So we are unable to diagnose it.

Next, we recommend reproducing the crash and reporting a new bug. We might have more luck next time.

[Daniel van Vugt (vanvugt)]

Please also try following these instructions next time:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Kai Groner (kai-gronr)]

Sorry, I'm not very familiar with apport or what the ubuntu error collection system does with crash files.

I've been able to get an actual stack trace using apport-retrace here. Is that useful if I resubmit with that?

[Daniel van Vugt (vanvugt)]

Yes if you can submit any stack trace info then that might be useful.

Also you don't need any familiarity to follow the instructions in comment #3. :)

[Kai Groner (kai-gronr)]

I'm unable to resubmit the retraced crash report using the linked instructions. A message in the journal says "Crash already reported." I can try submitting a new report if the problem reoccurs.

Below is the content of StacktraceSource. I'm attaching the more detailed ThreadStacktrace.

#0 __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
  [Error: raise.c was not found in source tree]
#1 0x00005573ecb6a52a in dump_gjs_stack_on_signal_handler ()
#2 <signal handler called>
#3 0x0000000000000000 in ?? ()
#4 0x00007f073d599a37 in meta_selection_source_wayland_deactivated (source=0x5573fc425b50) at ../src/wayland/meta-selection-source-wayland.c:121
  [Error: meta-selection-source-wayland.c was not found in source tree]
#5 0x00007f073e191936 in _g_closure_invoke_va () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#6 0x00007f073e1ae36c in g_signal_emit_valist () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#7 0x00007f073e1aefa9 in g_signal_emit_by_name () from /tmp/apport_sandbox_rkghhzas/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.1
#8 0x00007f073d55fd99 in meta_selection_set_owner (selection=0x5573edfeb8c0, selection_type=META_SELECTION_DND, owner=0x5573f439a290) at ../src/core/meta-selection.c:100
  [Error: meta-selection.c was not found in source tree]
#9 0x00007f073d586437 in source_new_cb (object=<optimized out>, res=<optimized out>, user_data=user_data@entry=0x5573fdafb8a0) at ../src/x11/meta-x11-selection.c:257
  [Error: meta-x11-selection.c was not found in source tree]
#10 0x00007f073e28c029 in g_task_return_now (task=0x7f072c003a50) at ../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#11 0x00007f073e28cbfd in g_task_return (task=0x7f072c003a50, type=<optimized out>) at ../../../gio/gtask.c:1281
  [Error: gtask.c was not found in source tree]
#12 0x00007f073d5819b2 in read_mimetypes_cb (stream=<optimized out>, res=<optimized out>, task=task@entry=0x7f072c003a50) at ../src/x11/meta-selection-source-x11.c:199
  [Error: meta-selection-source-x11.c was not found in source tree]
#13 0x00007f073e28c029 in g_task_return_now (task=0x5573efdee8e0) at ../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#14 0x00007f073e28cbfd in g_task_return (task=0x5573efdee8e0, type=<optimized out>) at ../../../gio/gtask.c:1281
  [Error: gtask.c was not found in source tree]
#15 0x00007f073e256826 in read_bytes_callback (stream=0x5573f3cb0380, result=0x5573fdae4e40, user_data=0x5573efdee8e0) at ../../../gio/ginputstream.c:874
  [Error: ginputstream.c was not found in source tree]
#16 0x00007f073e257d2b in async_ready_callback_wrapper (source_object=0x5573f3cb0380, res=0x5573fdae4e40, user_data=0x5573efdee8e0) at ../../../gio/ginputstream.c:532
  [Error: ginputstream.c was not found in source tree]
#17 0x00007f073e28c029 in g_task_return_now (task=0x5573fdae4e40) at ../../../gio/gtask.c:1212
  [Error: gtask.c was not found in source tree]
#18 0x00007f073e28c06d in complete_in_idle_cb (task=0x5573fdae4e40) at ../../../gio/gtask.c:1226
  [Error: gtask.c was not found in source tree]
#19 0x00007f...

[Kai Groner (kai-gronr)]

Adding StacktraceSource as an attachment since it got folded in my previous comment.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

Thanks. That looks close enough to this crash that I will call them the same:

https://errors.ubuntu.com/problem/bfae33153e95403126b6f11489857bf579e761ee

[Daniel van Vugt (vanvugt)]

Hmm, maybe there are a couple of similar but different crashes here. Upstream also mentions https://gitlab.gnome.org/GNOME/mutter/issues/591 and https://gitlab.gnome.org/GNOME/mutter/issues/842 which are fixed in mutter!943 (in v3.35.2) and mutter!848 (in v3.34.2).

It's unclear if this is the one that is fixed in 3.34.2 already but we will find out soon enough.

[Daniel van Vugt (vanvugt)]

We might end up needing to separate this from bug 1855225 eventually since technically the top of your stack is NULL and not meta_wayland_data_source_cancel. But that might just be stack corruption and the same function. Until proven otherwise we can treat them as the same bug.