Description: X window errors in various applications caused by upgrade to qtcurve-*.1.7.1-1

After system upgrade yesterday I now have discovered three applications that will not start anymore, error messages below.
checkgmail-svn
The program 'checkgmail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 159 error_code 8 request_code 2 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.)
me-tv
Me TV 1.3.4
16/11/10 00:11:11: Device: 'DiBcom 7000PC' (DVB-T) at "/dev/dvb/adapter0/frontend0"
16/11/10 00:11:13: Frontend::tune_to(505833330)
16/11/10 00:11:13: Waiting for signal lock ...
16/11/10 00:11:13: Got signal lock
me-tv-player (xine): Setting deinterlacer state to true
me-tv-player (xine): Setting audio stream to 0
me-tv-player (xine): Setting subtitle stream to -1
me-tv-player (xine): Setting mute state to false
me-tv-player (xine): Setting volume to 100
** (process:7162): DEBUG: Failed to call Inhibit method
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 132 (XVideo)
Minor opcode of failed request: 19 ()
Serial number of failed request: 134
Current serial number in output stream: 135
amule-upnp
Initialising aMule 2.2.6 using wxGTK2 v2.8.11
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 2842 error_code 8 request_code 2 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.)

see thread https://bbs.archlinux.org/viewtopic.php?id=108496


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce: