Bug #3320 MySQLAdministrator crashes when starting backup with it
Submitted: 29 Mar 2004 1:28 Modified: 30 Mar 2004 17:25
Reporter: Matthias Paul Scholz Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.02b-alpha OS:Linux (Suse Linux 8.2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[29 Mar 2004 1:28] Matthias Paul Scholz
When I start MySQLAdministrator as root on my local host, choose a backup profile and start the the backup ("Start backup"), the whole application crashes after closing the backup file chooser (an empty backup file is created yet at the file system position I have chosen). The progress dialog is shown for some seconds saying "preparing".

How to repeat:
1. Start MySQLAdministrator as root on your local host.
2. Connect to the MySQLServer instance running on your local host.
3. Choose a formerly created backup profile. Mine contained one schema with five tables. All settings are the default ones.
4. Press "Start Backup".
5. Choose a backup file location (e.g. "/root/backup/MySQLBackup-29-03-2004.sql").
6. The backup will start showing a progress dialog saying "Preparing". After some seconds the whole application crashes.  An empty backup file is created.

Suggested fix:
Creation of a resonable backup file.
Application mustn't crash.
[29 Mar 2004 1:31] Matthias Paul Scholz
Forget to say: The whole is running on KDE 3.1.1, Linux has an 2.4.20-4GB-Athlon-Kernel.
[29 Mar 2004 1:35] Matthias Paul Scholz
Me again: 
MySQLServer has version MySQL 4.0.18-standard 
(Client has version MySQL Client Version 50000, Protocol 10)
[29 Mar 2004 2:11] Matthias Paul Scholz
Last but not least:

Backup of the tables in matter works when using mysqlhotcopy from a shell.
[30 Mar 2004 17:25] 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