inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

[Anders Kaseorg]

Binary package hint: inkscape

Every time I start inkscape (0.47~pre1-0ubuntu1 on karmic amd64), click on the text tool, and click anywhere in the blank document, inkscape crashes with this dialog:

Inkscape encountered an internal error and will close now.

and the following message on the terminal:

**
Gdk:ERROR:/build/buildd/gtk+2.0-2.17.6/gdk/x11/gdkinput-xfree.c:334:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

This happens for me with GTK_IM_MODULE=xim, and for others with other input methods. Unsetting GTK_IM_MODULE is a workaround (but makes input less functional).

[Alex Valavanis (valavanisalex)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Unfortunately, I wasn't able to reproduce this bug, using the same version & architecture.

[Stephane Epardaud (stef-inforealm)]

Same crash here, what information do you need to fix it?

[Alex Valavanis (valavanisalex)]

Hi Stephane,

Please could you follow the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and generate a backtrace, then upload? That should give the developers the information they need. Let me know if you need any help.

Thanks a lot

[Stephane Epardaud (stef-inforealm)]

I'd love to but there doesn't seem to be any dbgsym packages for Inkscape after I added the repos…

[sadao (sadao.br)]

    It seems that incompatibility with scim. If scim is loaded, the access to text tools crash the inkscape as described above.
   When the scim are not loaded, it works normally.

Ubuntu Karmic Koala amd64, last update on October, 15, 2009.
inkscape 0.47 pre4

[Anders Kaseorg (andersk)]

sadao: Good find! I don’t have scim, but I do set GTK_IM_MODULE=xim, and the crash goes away if I unset that.

[Alex Valavanis (valavanisalex)]

Architecture: i386
DistroRelease: Ubuntu 9.10
Package: inkscape 0.47~pre4-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Anders Kaseorg (andersk)]

Stack trace with debugging symbols (inkscape-dbgsym, libc6-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg).

[Alex Valavanis (valavanisalex)]

Oops, thanks for fixing the backtrace!

[Alex Valavanis (valavanisalex)]

Added a backtrace with extra info per https://wiki.ubuntu.com/Backtrace

[Olivier Guéry (nemolivier)]

Same problem here.
I’m using « default-xim » from im-switch (I need compose).
Last svn (22544) don’t change the problem.

[Olivier Guéry (nemolivier)]

I tried an :
export GTK_IM_MODULE=xim && inkscape
But still the same crach.

Do you, people have a workaround to use inkscape ?

[Anders Kaseorg (andersk)]

> export GTK_IM_MODULE=xim && inkscape

No no no, GTK_IM_MODULE=xim is not a workaround, in fact quite the opposite: it _triggers_ the crash.

If you want a workaround, try unsetting the variable:
  unset GTK_IM_MODULE
  inkscape

[mas (mas-mylug)]

Anders is right. Unsetting GTK_IM_MODULE did not make inkscape crash. But, I lost the way to input text in my language. So, I tried setting GTK_IM_MODULE=scim and was surprised to see that it did not trigger the crash. I also could input text in Kannada which is important for me.

[Olivier Guéry (nemolivier)]

Thank’s. It works.
Don’t realy solve the bug indead. I need xim in order to have compose to work !

[lilydjwg (lilydjwg)]

Same problem here and the workaround doesn't work for me.

[Olivier Guéry (nemolivier)]

@missyou11 did you try this in a terminal :
unset GTK_IM_MODULE && inkscape

[tubaxenor (tubaxenor)]

I have the same problem and unset GTK_IM_MODULE && inkscape doesn't work for me either.

[Olivier Guéry (nemolivier)]

Hum… maybe it’s not this who work’s. I’ve also do :
im-switch -c
in a terminal, and choose « none ».

[tubaxenor (tubaxenor)]

@Olivier Guéry Still not working with the same error message...

[lilydjwg (lilydjwg)]

@Olivier Guéry I tried again and nothing has changed.
But I notice that my error output is a little different:
  Gdk:ERROR:/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkinput-xfree.c:336:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)
and the Inkscape's version is pre4 instead of pre1.

[Patrick Nagel (mail-patrick-nagel)]

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4

Upon selecting the Text object tool and clicking into the page in order to insert text into the page, a dialog window appears, saying "Inkscape encountered an internal error and will close now." - Clicking the 'Close' button closes Inkscape.

When started from a console, the following is being printed (from starting Inkscape until the crash):

>inkscape

(inkscape:5319): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

(inkscape:5319): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

[the warning above appears many times]
**
Gdk:ERROR:gdkinput-xfree.c:337:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Aborted

Reproducible: Always

Steps to Reproduce:
1. Open Inkscape
2. Press F8 or click the Text object tool button on the left (the one with the big A)
3. Click into the page
Actual Results:
Inkscape crashes

Expected Results:
Being able to use the text object tool without a crash

[Patrick Nagel (mail-patrick-nagel)]

It seems this is related to using an input method. I am using scim for entering Chinese text.

When trying to get scim to work, I found various tips saying the following environment variables should be set:

export XMODIFIERS=@im=SCIM
export GTK_IM_MODULE=xim
export QT_IM_MODULE=xim

With these set, scim works in all applications I tried. But the GTK_IM_MODULE=xim seems to cause a conflict with Inkscape.

On https://bugs.launchpad.net/inkscape/+bug/406036 I read that unsetting that variable would help, but it doesn't - the crash still happens (although only on attempting to leave the text area, by clicking somewhere else - it's actually possible to type something before the crash).

But when setting

GTK_IM_MODULE=scim

Inkscape doesn't crash.

So, since GTK_IM_MODULE=xim was my own doing, this is probably not a bug that many others will experience.

[Patrick Nagel (mail-patrick-nagel)]

I have the same problem with inkscape on openSUSE 11.2. Mas says in comment #17, that inkscape doesn't crash when setting GTK_IM_MODULE=scim (instead of =xim). This is also true for my system.

I reported this bug on the openSUSE bugtracker: https://bugzilla.novell.com/show_bug.cgi?id=556834

[Olivier Guéry (nemolivier)]

Nooo… inkscape 0.47 is out this morning… I just build it from source, but the bug still remain :(

[lilydjwg (lilydjwg)]

I am using Ubuntu 9.10, and I've just found that, if I (and a friend of mine with the same Ubuntu 9.10) install ibus, and set GTK_IM_MODULE=ibus, inkscape won't crash, no matter whether I am using ibus. Tried =fcitx when I am using it but inkscape still crashed.

[Daniel Knittl-Frank (knittl)]

i can also reproduce the bug and can confirm the workaround (unsetting GTK_IM_MODULE) as well

i need XIM input method so i can use the compose functionality of my keyboard layout (Neo-Layout)

[L_F_B (lars-behrens)]

Confirmed for OpenSUSE 11.2, Inkscape 0,46

Error lines:
----------------------------------------------------------------------------------------------------------------------------------------------------
** (inkscape:24506): WARNING **: Family name Bitstream Vera Sans does not have an entry in the font lister.
**
Gdk:ERROR:gdkinput-xfree.c:337:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)
----------------------------------------------------------------------------------------------------------------------------------------------------

None of the workarounds helps here.

[L_F_B (lars-behrens)]

Confirmed here on 11.2, 64bit.

But changing the variables doesn't help, so Inkscape is unusable.

[Olivier Guéry (nemolivier)]

@L_F_B under ubuntu jaunty, there were no bug with the 0.46 version. Strange that you find it.

[Diederik van Lierop (mail-diedenrezi)]

Confirmed on Fedora 12 too, using today's revision of Inkscape

However, this does not work for me:

unset GTK_IM_MODULE && inkscape

This did the trick though:

GTK_IM_MODULE=gtk-im-context-simple inkscape

[L_F_B (lars-behrens)]

Can confirm that
 GTK_IM_MODULE=gtk-im-context-simple
works here too, on SUSE 11.2

[L_F_B (lars-behrens)]

However, setting
 GTK_IM_MODULE=gtk-im-context-simple
makes Inkscape work (see https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/34)

[martin (chilivodka)]

I uninstalled XIM and it worked

[Jomit Jose (123jomit)]

Confirmed in fedora 12 i686

** (inkscape:24506): WARNING **: Family name Bitstream Vera Sans does not have an entry in the font lister.
**
Gdk:ERROR:gdkinput-xfree.c:336:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)

I have workaround the problem by first select the text tool, then before clicking on drawing area, I change default font Bitstream Vera Sans from some another font. And It works!!!!!

[Jomit Jose (123jomit)]

I am sorry, I am running inkscape by $ export GTK_IM_MODULE=ibus && inkscape

[nico (romano-nicola)]

Same problem here in Fedora 12.

** (inkscape:8821): WARNING **: Family name Bitstream Vera Sans does not have an entry in the font lister.
**
Gdk:ERROR:gdkinput-xfree.c:336:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)
Emergency save activated!
Emergency save completed. Inkscape will close now.

==

GTK_IM_MODULE=gtk-im-context-simple inkscape
does the trick for me

[remusjlupin (remusjlupin)]

Although in my duplicate bug report I said one of the workarounds fixed the problem, it seems that it didn't, at least not anymore. Ubuntu 9.10 with Inkscape 0.47 here.

[Glen (glen-redhat-bugs)]

abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Create a rectangle
2. Click with the text tool on top of the rectangle you've created.

Comment: Clicking with text tool on a rectangle causes crash.
Attached file: backtrace
cmdline: inkscape
component: inkscape
executable: /usr/bin/inkscape
kernel: 2.6.31.6-162.fc12.x86_64
package: inkscape-0.47-0.17.pre4.20091101svn.fc12
rating: 3
reason: Process was terminated by signal 6

[Glen (glen-redhat-bugs)]

Created attachment 377421
File: backtrace

[Máirín (mirn-redhat-bugs)]

Hi Glen!

Thank you very much for your bug report.

This bug looks like a bug we've seen a lot of users experience lately. I believe it is caused by a bug in the gtk2 package, not Inkscape.

We have a fix for the text-tool issue in Inkscape addressed by an update to gtk2 which I believe will resolve your problem (we've had several testers confirm it resolved text tool crashes in Inkscape for them)

To get the fix, run the following command as root:

yum update gtk2 --enablerepo=updates-testing

Let me know how it goes! And thanks again for the bug report.

[Glen (glen-redhat-bugs)]

Yep, fixed me right up. Thanks!

[Renate (yollywau)]

i have the same problem with Fedora - 12 2.6.31.6-166.fc12.i686. The same error message of nico #40.

And when I type: 'GTK_IM_MODULE=gtk-im-context-simple inkscape', it works fine...
It would be nice, if you can fix the bug.

[marinalan (marinalan)]

I have that with Fedora 12
Gdk:ERROR:gdkinput-xfree.c:336:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)

Emergency save activated!
Emergency save completed. Inkscape will close now.

uname -a
Linux marina-home.localdomain 2.6.31.6-166.fc12.i686.PAE #1 SMP Wed Dec 9 11:00:30 EST 2009 i686 i686 i386 GNU/Linux

GTK_IM_MODULE=gtk-im-context-simple inkscape
helped me too

[scaldov (scaldov)]

>And when I type: 'GTK_IM_MODULE=gtk-im-context-simple inkscape', it works fine...
>It would be nice, if you can fix the bug.

that means that it does'nt work.
Simple
GTK_IM_MODULE= inkscape
has the same effect of so called "it works fine", but you can not input arbitrary unicode symbols with these input methods you selected.

The X-system level input method is the only usable to enter Unicode character and it causes crash.

[Karel (karel-redhat-bugs)]

*** Bug 543380 has been marked as a duplicate of this bug. ***

[Joel (joel-redhat-bugs)]

The gtk2 update fixed the problem for me, too.

[Lubomir (lubomir-redhat-bugs)]

*** Bug 545759 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

*** Bug 544822 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

*** Bug 546588 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

*** Bug 548598 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

*** Bug 548661 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

GTK2 was fixed. Big thanks to everyone involved in reporting/triaging.

[Lubomir (lubomir-redhat-bugs)]

*** Bug 544341 has been marked as a duplicate of this bug. ***

[Lubomir (lubomir-redhat-bugs)]

*** Bug 542411 has been marked as a duplicate of this bug. ***

[Mxwu (mxwu)]

Hmm,
Can't reproduce this on my 32 bit 11.2 box.

Which version are you using?

[Sam Vilain (sam-vilain)]

GTK_IM_MODULE=gtk-im-context-simple XMODIFIERS=@im=xim inkscape makes things slightly better, but then I get a segmentation fault.

Using this command, I get much more stable behaviour:

unset GTK_IM_MODULE XMODIFIERS; inkscape

[Pascal Terjan (pterjan42)]

According to Fedora bug report, this was fixed in Gtk

[Diederik van Lierop (mail-diedenrezi)]

Confirmed fixed on Fedora 12, using gtk2-2.18.6-1.fc12.x86_64

This GTK2 version was already installed on my PC as part of a regular update on Jan. 17th, but I hadn't noticed this fix yet because I was still running Inkscape using the workaround.

[mas (mas-mylug)]

Just installed libgtk2 from unstable. Inkscape does not crash. The version info :

libgtk2.0-0 : 2.18.6-1
inkscape : 0.47.0-1

[mas (mas-mylug)]

Oops, the previous comment was for the debian. Sorry for the missing info.

[Máirín (mirn-redhat-bugs)]

*** Bug 562332 has been marked as a duplicate of this bug. ***

[Juan Sebastián Marulanda (juanchito2006)]

Ubuntu ought to update GTK+ to the latest stable version, that is, 2.18.7

Inkscape is unusable for text input.

[Krzysztof Kosinski (tweenk)]

The available information suggests this is a GTK bug, rather than an Inkscape bug.

[Alex Valavanis (valavanisalex)]

Fixed in Ubuntu in gtk+2.0 version 2.19.2-1

[WolphFang (mjoyner-vbservices)]

How does one get this "fix" installed? My 9.10 system is fully up-to-date, and I need to use XIM for Cherokee/ᏣᎳᎩ composed input.

[Alex Valavanis (valavanisalex)]

@WolphFang,

Ubuntu 9.10 still uses the version of gtk+ that causes the crash but it is fixed in Ubuntu 10.04. You can either:

* upgrade your system to the beta version of Ubuntu 10.04 [press ALT+F2 and type "update-manager -d" in the dialog that pops up]

* wait until the final release of Ubuntu 10.04 next month, and upgrade your system then.

* manually get hold of the latest Ubuntu package for gtk+2.0 from https://launchpad.net/ubuntu/lucid/+source/gtk+2.0/2.19.7-0ubuntu1 and install it. I don't recommend this, as it could break a lot of other things for you!!

Thanks,

Alex

[ZombieRamen (zombieramen-deactivatedaccount)]

I have a similar problem. It seems to be a general problem with text for me. I can use the type tool, but as soon as I go into select and click on the text, the background, or try to resize it, I get this output:

**
Gdk:ERROR:/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkinput-xfree.c:336:_gdk_input_grab_pointer: assertion failed: (input_window != NULL)

Emergency save activated!

Emergency save document locations:
  /tmp/inkscape-
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.

[Ben M. (bmhm)]

@WolphFang
You might want to try this if you are on amd64:
$ wget -ci gtk2_urls.txt
$ sudo dpkg -i *.deb

This is the way Alex told you not to use, but since I didn't want to upgrade yet I preferred this method and did a manual search on dependencies myself. Inkscape works again for me, including xim.

Hope this helps. But remember that there might be side effects I didn't encountered yet. If you don't know what these commands do, better don't execute them (as always).

Regards,
Ben

[Dominique Leuenberger aka DimStar (dimstar)]

Sorry, this bug did not get the attention it deserved.

Not likely, you have already upgraded to newer versions of openSUSE, which had
a lot more bug fixes.

We believe that this specific bug has been fixed during one of the release cycles; as such, I close the bug as 'FIXED'.

Should you be able to reproduce this issue on a newer openSUSE version, please
feel to report it again.

[Vorik (launchpad-gerapeldoorn)]

Still an issue on Ubuntu 14.10, workaround

'unset GTK_IM_MODULE && inkscape'

works well, but is an inconvenience.

[Joel Östblom (joel-ostblom)]

I am also having this issue on Ubuntu 14.10 with unity. Inkscape often crashers when modifying text boxes.

[Gunnar Hjalmarsson (gunnarhj)]

@Joel: Then please file a new bug report. This report was closed long ago.

[Joel Östblom (joel-ostblom)]

@Gunnar I was originally pointed here from a forum thread, but after looking around some more it seems like https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1385009 is more similar to what I am experiencing. It also suggests some fixes I am trying out now.

[Gunnar Hjalmarsson (gunnarhj)]

Ok, good.