Public bug reported:
When passing arguments to xargs, ExecuteWithArguments doesn't close the
standard input stream after writing the last argument. As a result, when
multiple arguments are passed the command is not executed, and Do hangs
when exiting. Sending SIGTERM to Do does seem to close the streams and
run any pending commands (so you can try a bunch of copy operations with
the Files and Folders plugin, but they won't actually execute until you
run 'killall gnome-do').
The attached patch fixes this problem by closing the standard input
stream after passing arguments to xargs. It also fixes a minor logging
issue (log messages would list the arguments, but not the actual
command).
** Affects: do
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Do.
https://bugs.launchpad.net/bugs/811366
Title:
ExecuteWithArguments doesn't execute immediately
Status in Do:
New
Bug description:
When passing arguments to xargs, ExecuteWithArguments doesn't close
the standard input stream after writing the last argument. As a
result, when multiple arguments are passed the command is not
executed, and Do hangs when exiting. Sending SIGTERM to Do does seem
to close the streams and run any pending commands (so you can try a
bunch of copy operations with the Files and Folders plugin, but they
won't actually execute until you run 'killall gnome-do').
The attached patch fixes this problem by closing the standard input
stream after passing arguments to xargs. It also fixes a minor logging
issue (log messages would list the arguments, but not the actual
command).
To manage notifications about this bug go to:
https://bugs.launchpad.net/do/+bug/811366/+subscriptions
--
Mailing list: https://launchpad.net/~linux-traipu
Post to : linux-traipu@lists.launchpad.net
Unsubscribe : https://launchpad.net/~linux-traipu
More help : https://help.launchpad.net/ListHelp
