gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress()

Bug #1548006 reported by Anders Kaseorg
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496

---

gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid()

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.3-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Feb 20 23:14:14 2016
DisplayManager:

EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-02-19 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7ffaec3c76b2: cmp %rdi,0xe8(%rdi)
 PC (0x7ffaec3c76b2) ok
 source "%rdi" ok
 destination "0xe8(%rdi)" (0x000000e8) 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/libgdk-3.so.0
 gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/gnome-shell/libgnome-shell.so
Title: gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Anders Kaseorg (andersk) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _gdk_window_has_impl (window=window@entry=0x0) at /build/gtk+3.0-hryEEv/gtk+3.0-3.18.7/./gdk/gdkwindow.c:626
 gdk_x11_window_get_xid (window=0x0) at /build/gtk+3.0-hryEEv/gtk+3.0-3.18.7/./gdk/x11/gdkwindow-x11.c:5527
 gtk_im_context_xim_filter_keypress (context=0x2b38260, event=0x32d4120) at /build/gtk+3.0-hryEEv/gtk+3.0-3.18.7/./modules/input/gtkimcontextxim.c:673
 gtk_im_multicontext_filter_keypress (context=0x7ffacc0b4870, event=0x32d4120) at /build/gtk+3.0-hryEEv/gtk+3.0-3.18.7/./gtk/gtkimmulticontext.c:359
 st_im_text_captured_event () from /tmp/apport_sandbox_IwvrJ3/usr/lib/gnome-shell/libgnome-shell.so

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 gdk_x11_window_get_xid()
+ gnome-shell crashed with SIGSEGV in _gdk_window_has_impl()
tags: removed: need-amd64-retrace
information type: Private → Public
summary: - gnome-shell crashed with SIGSEGV in _gdk_window_has_impl()
+ gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from
+ gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress()
tags: added: xorg
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
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This looks similar, but different, to bug 1743442.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

^^^
That shows this bug stopped happening after 16.04 so if anyone would like to get a fix you will need to install Ubuntu 17.10 (or 18.04).

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
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.