gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_update_pad_state()

Bug #1803321 reported by Shock
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Medium
Unassigned
mutter (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I tried to configure the buttons on a Wacom Tablet. (In Settings->Devices->Wacom Tablet)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 14 12:32:57 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-03-13 (610 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f831a4a7b38: cmp %ebp,0x8(%rax)
 PC (0x7f831a4a7b38) ok
 source "%ebp" ok
 destination "0x8(%rax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing 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: Upgraded to bionic on 2018-08-24 (81 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Shock (mmiron) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 clutter_input_device_xi2_update_pad_state (device=device@entry=0x55dbc2f5c1a0, button=<optimized out>, state=1, group=group@entry=0x55dbcaa2f324, mode=mode@entry=0x55dbcaa2f330) at x11/clutter-input-device-xi2.c:337
 clutter_device_manager_xi2_translate_event (translator=<optimized out>, native=<optimized out>, event=0x55dbcaa2f300) at x11/clutter-device-manager-xi2.c:1402
 clutter_backend_real_translate_event (backend=<optimized out>, native=0x7ffe92149020, event=0x55dbcaa2f300) at clutter-backend.c:597
 clutter_x11_handle_event (xevent=xevent@entry=0x7ffe92149020) at x11/clutter-event-x11.c:200
 handle_host_xevent (event=0x7ffe92149020, backend=0x55dbc2f1a110) 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_update_pad_state()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't find any other reports of this crash. Does it still happen in 20.04?

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Shock (mmiron) wrote :

I don't have the tablet anymore and I'm still on 18.04.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mutter (Ubuntu):
status: Incomplete → Expired
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.