[Desktop-packages] [Bug 591435] Re: Cancel button does not halt extensions

2016-05-24 Thread Windell Oskay
Killing the process sounds (to me) like a real and acceptable solution
to the issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/591435

Title:
  Cancel button does not halt extensions

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The "Cancel" button does not properly halt execution of Inkscape
  extensions.

  This is not normally noticeable because extensions execute quickly.
  But for extensions that take a while-- i.e., those that you'd want to
  cancel --it turns out not to work.  It appears to wait (possibly a
  very long time) for the extension to finish executing before stopping
  the operation.

  To replicate, select Extensions>Render>L-system.   Set Order to 4.
  Click Apply, try to cancel the operation.   If your computer is fast
  and that didn't take very long, set Order to 5, 6, or 7 to make the
  extension take longer to run.

  Discovered on Mac OS 10.4/ Inkscape 0.47
  Verified on Windows XP/ Inkscape 0.47
  Verified on Mac OS 10.6/ Inkscape pre-0.48 snapshot from last week

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

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


[Desktop-packages] [Bug 591435] Re: Cancel button does not halt extensions

2015-12-16 Thread Windell Oskay
It has been more than five years since this issue has been reported.
The presence of this non-working button continues to cause user
frustration, occasionally manifested as additional bug reports and/or
requests for technical support.

I would ask that the developers consider simply hiding (or removing) the
button until such a time that a mechanism for halting extensions can be
determined and implemented.

The text that is presently displayed above the button ("EXTENSION_NAME"
working, please wait...) is clear enough. Simply removing the button is
a simple solution that will likely save user confusion and frustration.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/591435

Title:
  Cancel button does not halt extensions

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The "Cancel" button does not properly halt execution of Inkscape
  extensions.

  This is not normally noticeable because extensions execute quickly.
  But for extensions that take a while-- i.e., those that you'd want to
  cancel --it turns out not to work.  It appears to wait (possibly a
  very long time) for the extension to finish executing before stopping
  the operation.

  To replicate, select Extensions>Render>L-system.   Set Order to 4.
  Click Apply, try to cancel the operation.   If your computer is fast
  and that didn't take very long, set Order to 5, 6, or 7 to make the
  extension take longer to run.

  Discovered on Mac OS 10.4/ Inkscape 0.47
  Verified on Windows XP/ Inkscape 0.47
  Verified on Mac OS 10.6/ Inkscape pre-0.48 snapshot from last week

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

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


[Desktop-packages] [Bug 1204732] Re: inkscape crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2013-08-12 Thread Windell Oskay
It seems like the suggested patch fixes the symptom, not the underlying
cause; I would have guessed that the description inx element would be
the correct place to include desired whitespace.


While we have removed the empty parameters in the Eggbot and Hershey Text 
extensions that caused the crash, we were indeed using them to provide 
whitespace, so the off-topic question is relevant for finding a workaround.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732

Title:
  inkscape crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in Inkscape: A Vector Drawing Tool:
  In Progress
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  I am trying to run an eggbot from inkscape. Everytime I want to setup
  the eggbot through the extensions the program reports an internal
  error and needs to close. I have updated and re-installed all software
  according to instructions (I think!) but the problem is always the
  same and persistent.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 24 21:18:34 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2010-03-03 (1239 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130624)
  MarkForUpload: True
  ProcCmdline: inkscape
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: inkscape
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: inkscape crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1204732] Re: inkscape crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

2013-08-11 Thread Windell Oskay
@~suv
Thank you for the notice, and for verifying the cause.  This issue (crashing 
with an empty param) does not seem to affect Inkscape prior to 0.48.4.


@Hans Schepker (hschepker)
Would have appreciated you filing the bug report with the Eggbot project 
directly, so that we could have gotten you up and running a couple of weeks 
sooner.  (And so that we weren't adding to the load over here.) 

Please try the new version and let me know if that fixes it; we do not 
presently have a system that can reproduce this crash.
http://code.google.com/p/eggbotcode/downloads/detail?name=eggbot_2013_08_11_2.3.4.zip

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732

Title:
  inkscape crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in Inkscape: A Vector Drawing Tool:
  Confirmed
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  I am trying to run an eggbot from inkscape. Everytime I want to setup
  the eggbot through the extensions the program reports an internal
  error and needs to close. I have updated and re-installed all software
  according to instructions (I think!) but the problem is always the
  same and persistent.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 24 21:18:34 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2010-03-03 (1239 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130624)
  MarkForUpload: True
  ProcCmdline: inkscape
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: inkscape
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: inkscape crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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