Bug #3538 Application terminates when in the "Catalogs" section of mysql-administrator
Submitted: 22 Apr 2004 10:50 Modified: 30 Apr 2004 21:30
Reporter: Eric Lussier Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.0.2b-alpha OS:Linux (Red Hat Linux 9)
Assigned to: Alfredo Kojima CPU Architecture:Any

[22 Apr 2004 10:50] Eric Lussier
I have just installed mysql-administrator version 1.0.2b-alpha on my Red Hat Linux 9 system and i beleive it is going to be a great tool.

But for now there is a problem when i get in the "Catalogs" section and i select a database, the application terminates without any message or anything.

If i see anything else i will let you know.


Eric Lussier

How to repeat:
To repeat the problem, i performed the exact same procedure i described and it does it all the time. I can select any of my databases and it does it.

Suggested fix:
I don't have any idea, i am just reporting the bug.
[22 Apr 2004 14:11] Eric Lussier
When i start the application from the command line i get this after going in the "Catalogs" section and selecting a database:

[root@mysystem root]# /opt/mysql-administrator/bin/mysql-administrator
** Message: refetchng catalogs
glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: attempt to create string with null pointer
[root@mysystem root]#

It does the same thing if i start the application GUI way with a double click on "MySQL Administrator" in path "/opt/mysql-administrator/share/applications/" but i don't get any error message.
[30 Apr 2004 21:30] Alfredo Kojima
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

This happens with MySQL servers 3.x, when using newer server there should be no problem. 
Nevertheless the crash has been fixed in the repository and should be gone in the next release.