MySQL Bugs: #52474: Failed to look up character set 'auto'

Bug #52474	Failed to look up character set 'auto'
Submitted:	30 Mar 2010 12:51	Modified:	30 Apr 2010 13:55
Reporter:	Michal Hrusecky	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Charsets	Severity:	S3 (Non-critical)
Version:	5.5.1-m2	OS:	Linux (openSUSE + server:database:UNSTABLE)
Assigned to:		CPU Architecture:	Any

Description:
I tried MySQL 5.5.1-m2 and I tried mysql_upgrade after updating but it can't locate charset auto. I tried deleting all my data and recreating fresh new with mysql_install_db and then I tried to rerun mysql_upgrade and got the same error:

# mysql_upgrade -u root
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysql/mysql.sock' 
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysql/mysql.sock' 
mysqlcheck: Character set 'auto' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file
mysqlcheck: Got error: 2019: Can't initialize character set auto (path: /usr/share/mysql/charsets/) when trying to connect
FATAL ERROR: Upgrade failed

With 5.1.44 everything works fine with same datadir (and same compilation options (both have --with-charset=utf8 --with-collation=utf8_unicode_ci --with-extra-charsets=all). If I specify manually --default-character-set=utf8 with 5.5.1-m2, everything proceed as well.

How to repeat:
Install MySQL 5.5.1-m2, create empty database with mysql_install_db, run mysql_upgrade.

Please, check with a newer version, 5.5.2-m2, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".