Red Hat Bugzilla – Bug 211215
MySQL Query Browser 1.1.18 crashes if I try and "Create Table"
Last modified: 2007-11-30 17:11:46 EST
Description of problem: When I try and visually create a table using MySQL Query
Browser, it crashes.
Version-Release number of selected component (if applicable): 1.1.18, with MySQL
Steps to Reproduce:
1. launch MySQL Query Browser 1.1.18
2. connect to localhost, using standard port 3306 and standard "root" account
3. right-click any existing database: "information_schema", "mysql" or "test"
4. choose "Create Table"
Actual results: MySQL Query Browser crashes without error message.
Expected results: you should be able and create a new table.
MySQL Query Browser crashes even if I create my own databases using "Create
Schema", and then I try and add a table to them.
There's no "MySQL Query Browser" in the core mysql packages. Perhaps you meant
to file this against some Extras package or other?
MySQL Query Browser is a graphical front-end for MySQL. It's developed by
MySQL AB itself, and I downloaded it using Yum Extender, so I believe is in
packages managed by Fedora Project.
Reassigning to proper component.
do you have mysql-administrator installed? mysql-query-browser calls
mysql-administrator for editing tables
Yes, I've installed the whole Tools suite.
(In reply to comment #5)
> do you have mysql-administrator installed? mysql-query-browser calls
> mysql-administrator for editing tables
I notice that mysql-query-browser has a dependency on mysql-gui-common and not
mysql-administrator itself. And mysql-query-browser has always had a table
editor built in, so you don't need mysql-administrator (query browser is fully
standalone as an application)
I can repeat the crash with mysql-query-browser on an FC-6 box, with an error
such that its:
** (mysql-query-browser:14099): WARNING **: request for bad widget
'myisam_radio' in glade object
/usr/bin/mysql-query-browser: line 20: 14099 Segmentation fault $PRG-bin
Incidentally, this error cannot be repeated with the upstream variant (1.2.9rc
can you please test with the version just pushed. it has fixed all the bugs
i've personally seen.
all the mysql tools are now released as one tarball. so reassigning to the new
please can you test that this bug has been fixed
closing as fixed