[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2017-10-26 Thread Bug Watch Updater
Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=546179.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-12-10T10:20:34+00:00 Glen wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/42


On 2009-12-10T10:20:37+00:00 Glen wrote:

Created attachment 377421
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/43


On 2009-12-13T04:55:46+00:00 Máirín wrote:

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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/44


On 2009-12-13T21:07:17+00:00 Glen wrote:

Yep, fixed me right up.  Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/45


On 2009-12-15T16:47:00+00:00 Karel wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/49


On 2009-12-15T18:48:24+00:00 Joel wrote:

The gtk2 update fixed the problem for me, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/50


On 2009-12-22T12:12:52+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/51


On 2009-12-22T12:12:58+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/52


On 2009-12-22T12:13:30+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/53


On 2009-12-22T12:13:41+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/54


On 2009-12-22T12:13:51+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/55


On 2009-12-22T12:15:24+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/56


On 2009-12-22T12:31:55+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/57


On 2009-12-22T12:32:11+00:00 Lubomir wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/406036/comments/58


On 2010-02-08T00:04:46+00:00 Máirín wrote

[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2015-05-05 Thread Gunnar Hjalmarsson
Ok, good.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2015-05-05 Thread Joel Östblom
@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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2015-04-19 Thread Gunnar Hjalmarsson
@Joel: Then please file a new bug report. This report was closed long
ago.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2015-04-19 Thread Joel Östblom
I am also having this issue on Ubuntu 14.10 with unity. Inkscape often
crashers when modifying text boxes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 406036] Re: inkscape crashes using certain input methods: _gdk_input_grab_pointer: assertion failed: (input_window != NULL)

2015-01-22 Thread Vorik
Still an issue on Ubuntu 14.10, workaround

'unset GTK_IM_MODULE && inkscape'

works well, but is an inconvenience.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp