Occasional "Unsupported conversion" error in autohandler

Hi all,

I’m getting an occasional error doing various operations through the web
interface. I’ve tried to reproduce it and failed, but it keeps recurring
from time to time, on operations from "Update"ing a ticket to changing
the Watchers on a ticket, then I can do the same operation five minutes
later without a problem.

From reading the autohandler code it looks like it has something to do
with utf8 handling, but I don’t know enough about that area to be sure.
I’m using Perl 5.6.1 on RedHat 7.3.

I’ve pasted the pretty-printed error output below, which seems to be the
same each time; I can send you the raw error output if that’s necessary.

Any suggestions? Thanks for your help.

michael

----- Error Output Follows -----

System error

error: Unsupported conversion: Invalid argument at
/usr/lib/perl5/site_perl/5.6.1/Encode/compat/common.pm line 115.

context: …
111: } map {
112: Encode::Alias->find_alias($) || lc($)
113: } ($[1], $[2]);
114:
115: my $result = ($from eq $to) ? $[0] : (
116: $decoder{$from, $to} ||= Text::Iconv->new( $from, $to )
117: )->convert($
[0]);
118:
119: return $result;

code stack: /usr/lib/perl5/site_perl/5.6.1/Encode/compat/common.pm:115
g /usr/lib/perl5/site_perl/5.6.1/Encode/compat/common.pm:91
g /usr/local/rt-3.0.6/share/html/autohandler:40
g

rt@mas.ml1.net wrote:

error: Unsupported conversion: Invalid argument at
/usr/lib/perl5/site_perl/5.6.1/Encode/compat/common.pm line 115.

You really really do not want to be using perl 5.6.x with
UTF character sets. Really.
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

rt@mas.ml1.net wrote:

error: Unsupported conversion: Invalid argument at
/usr/lib/perl5/site_perl/5.6.1/Encode/compat/common.pm line 115.

You really really do not want to be using perl 5.6.x with
UTF character sets. Really.

Yeah, I know, and I didn’t think I was; or at least, I’m trying not to.
:slight_smile:

I changed @LexiconLanguages to en only, @EmailInputEncodings to
iso-8859-1 and us-ascii, and @EmailOutputEncoding to iso-8859-1. Neither
I nor anyone else will be creating tickets in anything but English, so
I’ve tried to turn off utf8 stuff everywhere I can. Is there anything
else I can to do to make sure that RT isn’t using UTF characters? Because
that’s really what I want.

Aside from that, do you think this is a UTF problem? Sorry, maybe that’s
an obvious question, but it’s not clear to me.

Thanks for your help!

michael

I changed @LexiconLanguages to en only, @EmailInputEncodings to
iso-8859-1 and us-ascii, and @EmailOutputEncoding to iso-8859-1. Neither
I nor anyone else will be creating tickets in anything but English, so
I’ve tried to turn off utf8 stuff everywhere I can. Is there anything
else I can to do to make sure that RT isn’t using UTF characters? Because
that’s really what I want.

Rewrite all of RT. RT uses UTF8 internally as a canonical format for
all data.

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

Rewrite all of RT. RT uses UTF8 internally as a canonical format for
all data.

Does anyone have a step-by-step howto to install a current perl
on RH 7.3 and run RT3 under fastcgi without disturbing the
stock apache/mod_perl?

Les Mikesell
les@futuresource.com

I changed @LexiconLanguages to en only, @EmailInputEncodings to
iso-8859-1 and us-ascii, and @EmailOutputEncoding to iso-8859-1.
Neither I nor anyone else will be creating tickets in anything but
English, so I’ve tried to turn off utf8 stuff everywhere I can. Is
there anything else I can to do to make sure that RT isn’t using UTF
characters? Because that’s really what I want.

Rewrite all of RT. RT uses UTF8 internally as a canonical format for
all data.

Ouch. Looks like I’ll have to look more seriously into upgrading my Perl.

Incidentally, could this be mentioned somewhere in the README? If you
were to include in the section where it says RT is unsupported on Perl
5.6 a few more details about why, such as that Perl 5.6 has bad UTF8
support and RT uses UTF8 for everything, that would be (for me, would
have been) a big help.

Thanks.

michael