crash on XSetIMValues() call when using xim and esperanto locale
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTK+ |
Expired
|
Critical
|
|||
gtk+2.0 (Ubuntu) |
Incomplete
|
Medium
|
Unassigned | ||
libx11 (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: gedit
I'm using Feisty Herd 2 for about a week. Using the Esperanto locale makes it impossible to use dead keys in any application. When I try to change the input method, to see if it helps, the application crashes.
I have the following variable defined in my /etc/environment file:
GTK_IM_MODULE = "xim"
And I'm using Brazilian ABNT2 model keyboard, with the "br" layout.
When using other locale, say pt_BR, everything works as it should.
I tried to uncomment the lines referring the Esperanto locale in /usr/share/
ProblemType: Crash
CrashCounter: 1
Date: Sat Feb 3 22:18:01 2007
Disassembly: 0xb7689d5d:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gedit
Package: gedit 2.17.4-0ubuntu1
ProcCmdline: gedit
ProcCwd: /home/arig
ProcEnviron:
LANGUAGE=
PATH=/
LANG=eo_XX.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
Stacktrace:
Using host libthread_db library "/lib/tls/
#0 0xb7689d5d in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
Uname: Linux ari 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
Changed in gtk: | |
status: | Unknown → Unconfirmed |
tags: | added: crash |
Changed in libx11 (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
tags: | added: feisty |
Changed in libx11 (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
tags: | added: patch |
Changed in libx11 (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
Changed in libx11 (Ubuntu): | |
status: | Incomplete → New |
status: | New → Incomplete |
Changed in gtk: | |
importance: | Unknown → Critical |
Changed in gtk: | |
status: | New → Expired |
Thank you for your bug, the backtrace is not useful and the crash file doesn't permit to regenerate one for some reason. Could you try to get one with the dbgsym packages (https:/ /wiki.ubuntu. com/DebuggingPr ogramCrash) installed for gedit and maybe the input method you are using?