Description of problem: See attached image. If I not mistaken it looks like the perl-script that generates the graph is missing something like -charset=>'utf-8' which you can use to use to control the character set sent to the browser if it's not set it defaults to ISO-8859-1 Note setting this sets the charset() method as well. Version-Release number of selected component (if applicable): rt3-3.8.8-2.el6.noarch rt3-mailgate-3.8.8-2.el6.noarch How reproducible: Always Steps to Reproduce: 1. Generate a graph 2. 3. Actual results: Expected results: Additional info:
Woops assigned to the wrong component please reassign to RT3
Created attachment 468629 [details] Graph generated in RT with wrong charset
Does the updated version in epel-testing help ? rt3-3.8.10-2.el6.1
Th updated version fails to start with.. [error] Modification of a read-only value attempted at /usr/share/perl5/Net/LDAP/Constant.pm line 13.\nCompilation failed in require at /usr/share/perl5/Net/LDAP/Message.pm line 7.\nBEGIN failed--compilation aborted at /usr/share/perl5/Net/LDAP/Message.pm line 7.\nCompilation failed in require at /usr/share/perl5/Net/LDAP.pm line 13.\nBEGIN failed--compilation aborted at /usr/share/perl5/Net/LDAP.pm line 13.\nCompilation failed in require at /usr/share/perl5/RT/User_Local.pm line 62.\nBEGIN failed--compilation aborted at /usr/share/perl5/RT/User_Local.pm line 62.\nCompilation failed in require at /usr/share/perl5/vendor_perl/RT/Base.pm line 173.\nCompilation failed in require at (eval 131) line 3.\n\t...propagated at /usr/share/perl5/base.pm line 94.\nBEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/RT/CurrentUser.pm line 96.\nCompilation failed in require at /usr/share/perl5/vendor_perl/RT.pm line 515.\nCompilation failed in require at (eval 2) line 1.\n [Tue Jul 26 11:35:58 2011] [error] Can't load Perl file: /usr/sbin/webmux.pl for server x.x.x.x:0, exiting...
(In reply to comment #6) > Th updated version fails to start with.. > > [error] Modification of a read-only value attempted at > /usr/share/perl5/Net/LDAP/Constant.pm line 13.\nCompilation failed in require > at /usr/share/perl5/Net/LDAP/Message.pm line 7.\nBEGIN failed--compilation > aborted at /usr/share/perl5/Net/LDAP/Message.pm line 7.\nCompilation failed in > require at /usr/share/perl5/Net/LDAP.pm line 13.\nBEGIN failed--compilation > aborted at /usr/share/perl5/Net/LDAP.pm line 13.\nCompilation failed in require > at /usr/share/perl5/RT/User_Local.pm line 62.\nBEGIN failed--compilation > aborted at /usr/share/perl5/RT/User_Local.pm line 62.\nCompilation failed in > require at /usr/share/perl5/vendor_perl/RT/Base.pm line 173.\nCompilation > failed in require at (eval 131) line 3.\n\t...propagated at > /usr/share/perl5/base.pm line 94.\nBEGIN failed--compilation aborted at > /usr/share/perl5/vendor_perl/RT/CurrentUser.pm line 96.\nCompilation failed in > require at /usr/share/perl5/vendor_perl/RT.pm line 515.\nCompilation failed in > require at (eval 2) line 1.\n > [Tue Jul 26 11:35:58 2011] [error] Can't load Perl file: /usr/sbin/webmux.pl > for server x.x.x.x:0, exiting... I cannot reproduce this on a fresh fully updated centos 6 install. Can you please make sure everything is uptodate and/or provide the perl modules list as shown in the rt3/Admin/Tools/Configuration.html page ?
Johann, did you had a chance to look at this again ?
Just manage to find the time to update our instance to rt3-3.8.10-2.el6.1.noarch and this is still an issue note that it looks like that release has some perl bug which might be related to unlocalized [1] lurking around atleast our ldap module stopped working since webmux would not start and was complaining about "Modification of a read-only value attempted at...." Adding local $_; above the "while" statement in line 13 /usr/share/perl5/Net/LDAP/Constant.pm allowed webmux to start but still our ldap module would not authenticate our users after the upgrade thus I was forced to switch to using RT-Authen-ExternalAuth instead. 1.http://www.perlmonks.org/?node_id=570712#default_unlocalized
Note that this report is initially about the wrong charset in the graph I should mentioned that it's mentioned in the README for the authentication plugin we switched to using.... "If you are upgrading from an earlier version of this extension, you must remove the following files manually: $RTHOME/local/plugins/RT-Authen-ExternalAuth/lib/RT/User_Vendor.pm $RTHOME/local/lib/RT/User_Vendor.pm $RTHOME/local/lib/RT/Authen/External_Auth.pm Otherwise you will most likely encounter an error about modifying a read only value and be unable to start RT." As you can see others plugins seems to be affected by some change between 3.8.8 <--> 3.8.10 And just for the record you need to use 0.08_02+ version of the RT-Authen-ExternalAuth plugin with 3.8.10 otherwize you will hit the mentioned read only error
(In reply to comment #10) > Note that this report is initially about the wrong charset in the graph Which is still present
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.