MySQL Bugs: #58976: mysql-workbench can be used by root only, it crashes for other users

Bug #58976	mysql-workbench can be used by root only, it crashes for other users
Submitted:	16 Dec 2010 14:38	Modified:	20 Dec 2010 10:43
Reporter:	Markus Mertens	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.31a	OS:	Linux (Mandriva Powerpack 2010.1 (64-bit))
Assigned to:		CPU Architecture:	Any

Description:
I compiled and installed mysql-workbench. Now, if I start 'mysql-workbench' it crashes and I get the following error. But I can run 'mysql-workbench' as root without problems. How can I make this program available for normal users?

> mysql-workbench
** 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)
/bin/sh: ifconfig: Kommando nicht gefunden.
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 294 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.)
>

How to repeat:
Just try to start as root or as normal user to see the difference.

Can you try with some of the pre-compiled RPM packages for other distributions?

I tried a pre-compiled Red Hat RPM package but it did not change something. Later I found another program which had the same problem. So, I decided to try different settings of the nvidia driver. After reinstallation of this driver the problem disappeared.

Thank you for help!

This problem was not related to any bug in MySQL Workbench.