RTC 2.0 client crash under Linux
Hi,
One of our users experienced an error: his RTC client crashed. He's running RH Linux. He got an X11 error due apparently to the embedded web browser:
I imagine that this generic error message is not very helpful.
Is there a trace somewhere that could be helpful? Or do you simply not care about these bugs?
One of our users experienced an error: his RTC client crashed. He's running RH Linux. He got an X11 error due apparently to the embedded web browser:
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 12363540 error_code 1 request_code 0 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.)
I imagine that this generic error message is not very helpful.
Is there a trace somewhere that could be helpful? Or do you simply not care about these bugs?
One answer
Hi,
One of our users experienced an error: his RTC client crashed. He's running RH Linux. He got an X11 error due apparently to the embedded web browser:
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
(Details: serial 12363540 error_code 1 request_code 0 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.)
I imagine that this generic error message is not very helpful.
Is there a trace somewhere that could be helpful? Or do you simply not care about these bugs?
Can you access the Error view to see if this error is there? It may have a stack trace that may be useful to developers.