Bug 5288 – File .../charsets/?.conf not found; Character set '#33'...

Bug 5288 - File .../charsets/?.conf not found; Character set '#33'...

Summary:

File .../charsets/?.conf not found; Character set '#33'...

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	7.0
Platform:	PC Linux (other)

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-08-19 21:55 UTC by Real name
Modified:	2007-09-04 11:46 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Real name 2007-08-19 21:55:49 UTC

+++ This bug was initially created as a clone of Bug #3845 +++

I installed SlimServer_trunk_v2007-08-19.noarch.rpm on a clean Fedora Core 6 system (i.e. just the minimal headless system, no GUI), and upon starting SlimServer I see the following 2 lines printed to the console several times:

  File '/usr/share/mysql/charsets/?.conf' not found (Errcode: 2)
  Character set '#33' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index' file

The scanning seems to be working fine.. All my tags are in UTF-8.

------------------------------------
SlimServer Version: 7.0a1 - 12607 - RedHat - EN - utf8
Server IP address: 10.0.0.105
Perl Version: 5.8.8 i386-linux-thread-multi
MySQL Version: 5.0.21-standard

Comment 1 KDF 2007-08-19 23:32:52 UTC

did you read the comment on the existing closed report?
It says this is harmless, and is closed because it is only a symptom of the mysql version on your system does not match the one included with slimserver.

Comment 2 Real name 2007-08-19 23:38:23 UTC

Yes, I read it. It makes no sense. Mysql isn't not installed in my system at all. Directory /usr/share/mysql does not even exist. So, why this error?

Comment 3 KDF 2007-08-20 00:02:35 UTC

It may be related to a small component or library on your system related to mysql. Again it is a harmless warning generated from mysql.  There is nothing to indicate that this leads to a bug in slimserver.  As such, it is a closed issue.