parcellite crashes when using an action

[PGScooter]

Binary package hint: parcellite

Ubuntu Jaunty 64-bit
Parcellite: Installed: 0.9-1ubuntu1

I made an action and have used it successfully before. Here is the action:
echo "%s" >> /home/frederico/languages/Spanish/sup.txt

However, this time it crashed, no matter what the input was. I ran parcellite from the terminal and reproduced the crash. The terminal gave me several outputs and errors. All of these are from doing the same thing: ctrl-alt-a and then clicked on the action name.

frederico@system76-pc:~/languages/Spanish$ parcellite
parcellite: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
frederico@system76-pc:~/languages/Spanish$

frederico@system76-pc:~/languages/Spanish$ parcellite
The program 'parcellite' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 851 error_code 9 request_code 152 minor_code 4)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

frederico@system76-pc:~/languages/Spanish$ parcellite
parcellite: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Aborted
frederico@system76-pc:~/languages/Spanish$ apt-cache search parcellite

frederico@system76-pc:~/languages/Spanish$ parcellite
Segmentation fault
frederico@system76-pc:~/languages/Spanish$

frederico@system76-pc:~/languages/Spanish$ sudo parcellite
^C
frederico@system76-pc:~/languages/Spanish$ parcellite
parcellite: ../../src/xcb_io.c:176: process_responses: Assertion `!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.
Aborted
frederico@system76-pc:~/languages/Spanish$

I then installed pacellite-dbgsym and used gdb to get a backtrace. Here is what I got:
~
~

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/parcellite
[Thread debugging using libthread_db enabled]
[New Thread 0x7f53f02f76f0 (LWP 9166)]
The program 'parcellite' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC'.
  (Details: serial 1090 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'parcellite' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow'.
  (Details: serial 1089 error_code 3 request_code 4 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[New Thread 0x7f53e7d0b950 (LWP 9169)]

Program exited with code 01.
(gdb)

I hope this helps. Thanks!!!

[Oliver Sauder (sao)]

It seems that this bug has been partially fixed in version 0.9.2-1. When passing a normal string without any special characters to an action, the command is successfully executed. However, when the string contains a curly brace (e.g. ${test.id}) parcellite still crashes with a segmentation fault error.