Bug 5442 – Ubuntu: Character set "#33" is not a compiled character set.

Bug 5442 - Ubuntu: Character set "#33" is not a compiled character set.

Summary:

Ubuntu: Character set "#33" is not a compiled character set.

Status:	CLOSED PATCHWELCOME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Database
Version:	7.0
Platform:	PC Ubuntu Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-09-11 17:23 UTC by Wallace Lai
Modified:	2008-12-18 11:12 UTC (History)
CC List:	0 users

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 Wallace Lai 2007-09-11 17:23:40 UTC

System Info:  IBM Think Centre, P4, 1.9 GHz,  Ubuntu 6.10

Steps to Reproduce:
1.  svn check out today's code to Ubuntu.
2.  Change dir to trunk/server.
3.  Start SlimServer by typing perl SlimServer.pl.
4.  SlimServer starts with some error messages.  All of them are complaining about:
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

Comment 1 KDF 2007-09-12 09:24:24 UTC

see bug 3845 and bug 5288

Comment 2 Wallace Lai 2007-09-12 09:55:55 UTC

According to the comments on bug #5288, this is a harmless bug.  I tested the SlimServer on Ubuntu this morning.  So far, nothing seems to be broken because of this.  However, when there is a warhning, it is best to track it down and fix it some how.

I am closing this as "LATER" for now.  I feel uncomfortable closing it as "WONTFIX".

Comment 3 Chris Owens 2008-03-07 09:04:54 UTC

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.