‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland

[Anders Kaseorg]

Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in this crash.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 10 20:50:10 2017
Disassembly: => 0x2: Cannot access memory at address 0x2
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-02-19 (599 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218)
ProcCmdline: gedit
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x2: Cannot access memory at address 0x2
 PC (0x00000002) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ()
 XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 im_uim_init_modifier_keys () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
 im_module_init () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-05-02 (161 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 XGetModifierMapping (dpy=dpy@entry=0x55acf0471f00) at ../../src/ModMap.c:41
 im_uim_init_modifier_keys () at ../../gtk2/immodule/key-util-gtk.c:333
 im_module_init (type_module=0x55acf0855b40) at ../../gtk2/immodule/gtk-im-uim.c:1808
 gtk_im_module_load (module=0x55acf0855b40) at ././gtk/gtkimmodule.c:171

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.