gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool → clutter_device_manager_xi2_translate_event → clutter_backend_real_translate_event → clutter_x11_handle_event → handle_host_xevent

Bug #1783673 reported by Zhenqing Hu
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.17.0-4.5-generic 4.17.3
Uname: Linux 4.17.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Jul 25 21:54:39 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-06-18 (37 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f3325479e50: mov 0x128(%rdi),%rax
 PC (0x7f3325479e50) ok
 source "0x128(%rdi)" (0x00000128) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Zhenqing Hu (huzq85) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clutter_input_device_xi2_get_current_tool (device=device@entry=0x0) at x11/clutter-input-device-xi2.c:292
 clutter_device_manager_xi2_translate_event (translator=<optimized out>, native=<optimized out>, event=0x55f5fd65a970) at x11/clutter-device-manager-xi2.c:1625
 clutter_backend_real_translate_event (backend=<optimized out>, native=0x7ffd82ef0b60, event=0x55f5fd65a970) at clutter-backend.c:597
 clutter_x11_handle_event (xevent=xevent@entry=0x7ffd82ef0b60) at x11/clutter-event-x11.c:200
 handle_host_xevent (event=0x7ffd82ef0b60, backend=0x55f5fb776110) at backends/x11/meta-backend-x11.c:383

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
+ gnome-shell crashed with SIGSEGV in
+ clutter_input_device_xi2_get_current_tool()
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool()

It appears a few people experience the same crash:
https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f

in 17.04, 17.10, 18.04 and 18.10.

tags: added: artful bionic
description: updated
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
tags: removed: artful
summary: gnome-shell crashed with SIGSEGV in
- clutter_input_device_xi2_get_current_tool()
+ clutter_input_device_xi2_get_current_tool →
+ clutter_device_manager_xi2_translate_event →
+ clutter_backend_real_translate_event → clutter_x11_handle_event →
+ handle_host_xevent
tags: removed: cosmic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.