| Bug #21907 | X Window System error 'BadMatch (invalid parameter attributes)'. | ||
|---|---|---|---|
| Submitted: | 29 Aug 2006 19:28 | Modified: | 21 Dec 2006 21:33 |
| Reporter: | John Yodsnukis (Basic Quality Contributor) | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Workbench Preview | Severity: | S1 (Critical) |
| Version: | 1.1 (5.0-r8) | OS: | Linux (Linux (Gentoo on x86)) |
| Assigned to: | CPU Architecture: | Any | |
[29 Aug 2006 19:28]
John Yodsnukis
[7 Sep 2006 3:41]
Alfredo Kojima
Can you confirm whether you started WB on a remote X display?
[7 Sep 2006 15:48]
John Yodsnukis
No, this error only occurs on a local X display. On a remote X display, I get a corrupted desktop/window manager. I lose ALL title bars. If I mouse over the mysql-workbench window menu bar, it will repaint the menus and they do seem to respond, but the canvas is greyed and unresponsive.
[5 Oct 2006 8:30]
Valeriy Kravchuk
Please, try to repeat with a newer version, 1.1.4 alpha (or 1.1.3, at least), and inform about the results.
[18 Oct 2006 17:45]
John Yodsnukis
Still occurs with v1.1.4 alpha and svn revisions 1794/444. What additional information is needed?
[21 Nov 2006 12:45]
Valeriy Kravchuk
Please, try to repeat with a newer version, from GUI Tools 5.0-r5, and inform about the results.
[21 Nov 2006 13:18]
John Yodsnukis
Still broken with latest release AND in svn versions.
[22 Nov 2006 23:43]
MySQL Verification Team
I am changing to Verified status because i am able to get similar error message on Ubuntu 6.10 and version 1.2.5rc. (mysql-workbench-bin:7701): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
[21 Dec 2006 21:33]
John Yodsnukis
Still a problem with new release 8.
[4 Jan 2007 18:11]
Andre Hinrichs
I have a similar bug here. However, it's slightly different: The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 731 error_code 8 request_code 145 minor_code 5) (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 also run gentoo here with mysql-gui-tools-5.0r8 and the ebuild script from here: http://bugs.gentoo.org/show_bug.cgi?id=159957
[7 Jan 2007 4:01]
Ron Harwood
I get this exact same error under Mandriva 2006.0 using the x86 tar-ball.
[15 Mar 2007 2:04]
Roland Bouman
Mmm, it used to work...suddenly (come to think of it, I installed a proprietary ATI driver as of late, and tweaked X configuration files) if does not work anymore on my Kununtu linux system roland@roland-laptop:/opt/mysql/gui/mysql-gui-tools-5.0$ ./mysql-workbench Error starting ./mysql-workbench. The actual installation path of mysql-workbench is different from the expected one. Please run ./mysql-workbench --update-paths (as the root user, if needed) to have the installation directory updated. roland@roland-laptop:/opt/mysql/gui/mysql-gui-tools-5.0$ ./mysql-workbench --update-paths Updating mysql-workbench installation paths... Done. roland@roland-laptop:/opt/mysql/gui/mysql-gui-tools-5.0$ ./mysql-workbench (mysql-workbench-bin:10869): Gtk-WARNING **: Unable to locate theme engine in module_path: "mist", The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 742 error_code 8 request_code 142 minor_code 5) (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.) roland@roland-laptop:/opt/mysql/gui/mysql-gui-tools-5.0$
[24 Mar 2007 0:24]
John Dangler
Hell, at least you got something... I set this up on Ubuntu (1.1.10), and it won't connect to a database, no matter what I do. All I get is this - Error calling ReverseEngineeringMysql.getSchemata: Can't connect to server. Please check the connection parameters. The list of schema names could not be retrieved And I get the same message for sync, or resync... I've also tried the forums, and had my repeated questions for help just getting this to start properly either completely ignored for a week or more, or just removed from the forum. It's unbelievable to me that I can't even get a simple reply...
[2 Apr 2007 9:44]
Levi Stanley
Having the same issue, here is what I am getting with debug on: [...] ** Message: Initialized module WorkbenchController ** Message: Registration ok ** Message: Initialized module /usr/local/share/mysql-gui/workbench/lua/Workbench.lua ** Message: Initialized module /usr/local/share/mysql-gui/workbench/lua/WorkbenchCorePlugins.lua ** Message: Initialized module /usr/local/share/mysql-gui/workbench/lua/WorkbenchImport.lua ** Message: Registered 3 modules ** Message: Calling lua function Workbench.registerEditors The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 656 error_code 8 request_code 146 minor_code 5) (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.) OS: Gentoo Architecture: x86
[14 Nov 2007 7:29]
[ name withheld ]
I got almost the same error message: The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 778 error_code 8 request_code 143 minor_code 5) (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.) But no 'theme engine' references with debug flags: DEBUG=X GRT_VERBOSE=X mysql-workbench ** Message: MySQL Generic Runtime Environment 2.0.12 ** Message: Type 'help' or '?' for help. Type 'quit' to exit the shell. ** Message: Lua Shell initialized. ** Message: Registered 14 struct definitions ** Message: Initialized module Base ** Message: Initialized module ReverseEngineeringMysql ** Message: Initialized module TransformationMysql ** Message: Loading Lua modules... ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfo.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/DbUtils.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoOracle.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoMysql.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoAccess.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/BaseLua.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsManagement.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoGeneric.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoMaxdb.lua ** Message: Initialized module //usr/local/share/mysql-gui/common//lua/RdbmsInfoMssql.lua ** Message: Registered 10 Lua modules ** Message: Initializing C++ loader... ** Message: Registered 0 struct definitions ** Message: Initialized module WorkbenchController ** Message: Registration ok ** Message: Initialized module //usr/local/share/mysql-gui/workbench/lua/WorkbenchCorePlugins.lua ** Message: Initialized module //usr/local/share/mysql-gui/workbench/lua/Workbench.lua ** Message: Initialized module //usr/local/share/mysql-gui/workbench/lua/WorkbenchImport.lua ** Message: Registered 3 modules ** Message: Calling lua function Workbench.registerEditors The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 778 error_code 8 request_code 143 minor_code 5) (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.) This is a Debian testing system: Linux debian 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 GNU/Linux mysql-gui-tools-bundle-5.0-r10-linux (SVN) mysql-workbench-bundle-5.0-r10-linux (SVN)
[8 Mar 2011 18:49]
Raphaël Gertz
It seems to be related with locale : http://www.dlcube.com/index.php?id=76&tx_ttnews[tt_news]=28&tx_ttnews[backPid]=74&cHash=1c... It seems to be enough to unset : LANG LC_NUMERIC Then mysql workbench stop crashing. Without (crash) : ** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit /usr/lib64/python2.6/site-packages/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken RandomPool_DeprecationWarning) Log levels '0111000' disabling log level 0 enabling log level 1 enabling log level 2 enabling log level 3 disabling log level 4 disabling log level 5 disabling log level 6 Ready. The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 258 error_code 16 request_code 135 minor_code 17) (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.) With : ** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit /usr/lib64/python2.6/site-packages/Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken RandomPool_DeprecationWarning) Log levels '0111000' disabling log level 0 enabling log level 1 enabling log level 2 enabling log level 3 disabling log level 4 disabling log level 5 disabling log level 6 Ready. Plz fix asap. The problem seems to not trigger on x86 version, but only on x86_64 version here on Mandriva Linux 64 2010.1 (compiled from source).
