14 years ago
SOAPUI crash on save project
Running SOAPUI from the command line, create new project, save all projects this is the result:
ian@suse:~> /bin/sh "/home/ian/SmartBear/soapUI-4.5.1/bin/soapUI-4.5.1"
Configuring log4j from [/home/ian/SmartBear/soapUI-4.5.1/bin/soapui-log4j.xml]
10:45:55,450 INFO [DefaultSoapUICore] initialized soapui-settings from [/home/ian/soapui-settings.xml]
10:45:56,169 INFO [WorkspaceImpl] Loading workspace from [/home/ian/default-soapui-workspace.xml]
10:45:56,234 INFO [WsdlProject] Loaded project from [file:/home/ian/hello-soapui-project.xml]
10:45:56,480 INFO [SoapUI] Used java version: 1.7.0_02
10:46:17,162 INFO [WsdlProject] Saved project [hello] to [/home/ian/hello-soapui-project.xml - 4298 bytes
The program 'java' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 3709 error_code 8 request_code 42 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.)
Any ideas ?
ian@suse:~> /bin/sh "/home/ian/SmartBear/soapUI-4.5.1/bin/soapUI-4.5.1"
Configuring log4j from [/home/ian/SmartBear/soapUI-4.5.1/bin/soapui-log4j.xml]
10:45:55,450 INFO [DefaultSoapUICore] initialized soapui-settings from [/home/ian/soapui-settings.xml]
10:45:56,169 INFO [WorkspaceImpl] Loading workspace from [/home/ian/default-soapui-workspace.xml]
10:45:56,234 INFO [WsdlProject] Loaded project from [file:/home/ian/hello-soapui-project.xml]
10:45:56,480 INFO [SoapUI] Used java version: 1.7.0_02
10:46:17,162 INFO [WsdlProject] Saved project [hello] to [/home/ian/hello-soapui-project.xml - 4298 bytes
The program 'java' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 3709 error_code 8 request_code 42 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.)
Any ideas ?