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()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
https:/
---
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:/
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+
ProcVersionSign
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelMo
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-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (42 days ago)
summary: |
- Gnome shell crash, maybe related to wireless mouse battery running out + gnome-shell crashed in <NULL> 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() |
Changed in gnome-shell (Ubuntu): | |
status: | Invalid → New |
summary: |
- gnome-shell crashed in <NULL> from + gnome-shell crashed 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() |
tags: |
added: focal removed: eoan |
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.