Hi,

We have have a same problem but in IIS. We are using OTRS in a none-Europe alphabet and can't ignore utf-8.

Afshar

On Mon, Mar 2, 2009 at 4:21 AM, Paul <otrs-users@neenerville.com> wrote:
Hi all,

I upgraded OTRS 2.3.3 to 2.3.4 and found that when $Self->{DefaultCharset}
is set to 'utf-8', the SysConfig area of the Admin interface results in a
500 server error. Apache error logs show the following:

[Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar  1
18:45:56 2009] index.pl: utf8 "\\xF6" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:56 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar  1
18:45:56 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:57 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar  1
18:45:57 2009] index.pl: utf8 "\\xE4" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar  1
18:45:58 2009] index.pl: utf8 "\\xFC" does not map to Unicode at
../..//Kernel/System/Config.pm line 161, <$In> chunk 1., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] [Sun Mar  1
18:45:58 2009] index.pl: Malformed UTF-8 character (unexpected
non-continuation byte 0x67, immediately after start byte 0xfc) in subroutine
entry at /usr/lib/perl/5.8/Data/Dumper.pm line 179., referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] *** glibc
detected *** free(): invalid next size (normal): 0x095c6590 ***, referer:
https://otrs.host/path/index.pl?Action=Admin
[Sun Mar 01 17:45:58 2009] [error] [client xxx.xxx.xxx.xxx] Premature end of
script headers: index.pl, referer:
https://otrs.host/path/index.pl?Action=Admin

Changing the default charset to iso-8859-1 the problem goes away. Any ideas?
We need UTF-8. Reverting to 2.3.3 resolves the issue as well with utf-8.

Best wishes,
Paul

---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/