Bug #22358 Administrator segfaults due to "bad widgets"
Submitted: 14 Sep 2006 16:34 Modified: 20 Sep 2006 12:44
Reporter: David Shrewsbury Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.2.3rc OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[14 Sep 2006 16:34] David Shrewsbury
Description:
Note: This seems to affect MySQL Administrator from the "Generic x86 Linux TAR (bundled dependencies)" download.

I start MySQL Administrator and connect to a local database just fine. When I click on any of these sections:

 - Startup Parameters
 - Health
 - Restore Backup

then Administrator dies with the following error messages (when started from the command line):

- Startup Parameters
(mysql-administrator-bin:17320): libglade-CRITICAL **: glade_xml_build_interface: assertion `wid != NULL' failed

** (mysql-administrator-bin:17320): WARNING **: request for bad widget 'info_button' in glade object
./mysql-administrator: line 103: 17320 Segmentation fault      $PRG-bin $args

- Health
** (mysql-administrator-bin:17335): WARNING **: request for bad widget 'info_button' in glade object

** ERROR **: request for bad widget 'info_button'
aborting...
./mysql-administrator: line 103: 17335 Aborted                 $PRG-bin $args

- Restore Backup
** (mysql-administrator-bin:17350): WARNING **: request for bad widget 'warning_text' in glade object
./mysql-administrator: line 103: 17350 Segmentation fault      $PRG-bin $args

Info on my test system
----------------------
* uname -a
Linux chief 2.6.16-gentoo-r9 #1 SMP Thu Jun 15 09:59:36 EDT 2006 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GNU/Linux

* mysql -e "select version()"
5.1.12-beta-debug-log

How to repeat:
1) Start MySQL Administrator from Generic x86 Linux TAR (bundled dependencies) from the command line.
2) Click on any of the sections named above (Startup Parameters, Restore Backup, Health)
[20 Sep 2006 12:44] David Shrewsbury
This is not a bug. These errors were due to installing the tarball in an invalid location. It was installed under /usr/local. The startup scripts expect the tarball to be installed in certain locations. I reinstalled under /opt and it works now. I suspect that before, it was using my system libraries and not the libraries in the packaged tarball. Perhaps a quick installation guide provided with the tarball would help others with this mistake.