Bug #21891 mysql-administrator fails with nonlocal XServer

• Submitted: 29 Aug 2006 4:49
• Modified: 7 Sep 2006 10:09
• Reporter: Mark Johnson (Basic Quality Contributor)
• Status: Not a Bug
• Category: MySQL Administrator
• Severity: S3 (Non-critical)
• Version: 1.1.20
• OS: Linux (Linux/Slackware)
• CPU Architecture: Any

[29 Aug 2006 4:49] Mark Johnson

Description:
Both linux machines run Slackware 10.2 (patched with security patches).
Local linux machine runs kernel 2.6.15.
Remote linux machine runs kernel 2.6.12.

While logged into the local machine, I run ssh to connect to the remote.  Then, I try to run mysql-administrator.  It fails:
mj@enterprise:~$ mysql-administrator
The program 'mysql-administrator-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 66 error_code 3 request_code 38 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.)
mj@enterprise:~$ xclock &
[1] 10091
mj@enterprise:~$ mysql-administrator --sync
The program 'mysql-administrator-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 66 error_code 3 request_code 38 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.)
[1]+  Done                    xclock
mj@enterprise:~$ mysql-query-browser
The program 'mysql-query-browser' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 66 error_code 3 request_code 38 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.)

NOTE 1: the xclock command succeeds indicating that X programs can operate.
NOTE 2: The Query Browser fails, too.  Perhaps the problem is in gui common.

How to repeat:
See description.

[1 Sep 2006 19:57] Alfredo Kojima

Hi can you try the same with some gnome/gtk application, like gnome-terminal?
I have tried to repeat your problem with suse and ubuntu but was unable to.

[6 Sep 2006 6:21] Mark Johnson

mj@enterprise:~$ gnome-terminal
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 70 error_code 5 request_code 20 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.)

Interesting.  Perhaps, this is actually a gdk problem.