Hi there!
Since Kubuntu 9.04, Gimp 2.6 is pretty much unusable for me, after some time, klicking into an image (either painting or selecting) results in something like this:
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
(Details: serial 73870 error_code 164 request_code 148 minor_code 13)
(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.)
(script-fu:6265): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
I am aware of the wacom xconf.org issue, however, there are no such lines in my xorg.conf.
System is 32bit P4 with ATI Radeon 3850 using packaged fglrx drivers
Any ideas? T.I.A.
Edit: After applying repro updates, the problem seems to be fixed!
Since Kubuntu 9.04, Gimp 2.6 is pretty much unusable for me, after some time, klicking into an image (either painting or selecting) results in something like this:
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
(Details: serial 73870 error_code 164 request_code 148 minor_code 13)
(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.)
(script-fu:6265): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
I am aware of the wacom xconf.org issue, however, there are no such lines in my xorg.conf.
System is 32bit P4 with ATI Radeon 3850 using packaged fglrx drivers
Any ideas? T.I.A.
Edit: After applying repro updates, the problem seems to be fixed!