ubuntu-translations-coordinators team mailing list archive

[Dominique Leuenberger aka DimStar <406036@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/406036

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

Status in GTK+ GUI Toolkit:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “inkscape” package in Ubuntu:
  Invalid
Status in “inkscape” package in Debian:
  Fix Released
Status in “inkscape” package in Fedora:
  Unknown
Status in “inkscape” package in Mandriva:
  Fix Released
Status in “inkscape” package in Suse:
  Fix Released

Bug description:
  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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/406036/+subscriptions