Launching Firefox freezes inkscape until browser exits
Bug #168226 reported by
Mathrick-users
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
High
|
Unassigned |
Bug Description
Launching the browser (for FAQ, What's New, etc.), if it hasn't been
running previously and can't be requested to just open a new window (at
least that's the case with Firefox) causes Inkscape to freeze until the
browser process exits completely. As I said, it doesn't happen if there's
another browser window already open, since in that case the process spawned
by Inkscape hands the actual work to the original instance and exits.
Tested on Linux, always reproducible. Manually launching one of
/usr/share/
enough, python seems to exit soon enough.
tags: | added: extensions-plugins |
To post a comment you must log in.
Originator: NO
Confirmed. Ubuntu Feisty - Gnome 2.17(dev) - Inkscape SVN
It seems like there is a possibility that it is caused by Gnome. When I
exit the browser an Inkscape dialog pops up that tells me the following:
"Inkscape has received additional data from the script executed. The
script did not return an error, but this may indicate the results will not
be as expected." and then it's followed by "GTK Accessibility Module
initialized"
I have had issues with the GTK Accessibility Module messing with scripts
in the past which is what leads me to believe it is the problem. Can anyone
else comment on this?