Bug 1318879

Summary: Can't support UTF8 string to create bug(summary/comment)
Product: [Community] Bugzilla Reporter: Hui Wang <huiwang>
Component: Creating/Changing BugsAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED NEXTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.0CC: huiwang, jmcdonal, mtahir, qgong
Target Milestone: 5.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rh-bugzilla-5.0.3-rh2.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-06 07:49:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Hui Wang 2016-03-18 03:03:11 UTC 
Description of problem:
bz-5.0 server will show 500 error if edit  summary or comment with UTF8 string.
See bug https://bugzilla.redhat.com/show_bug.cgi?id=1272137

Version-Release number of selected component (if applicable):
5.0.2.rh2

How reproducible:
100%


Steps to Reproduce:
1. Go to enter bug page
2. Edit the summary or description with urf8 string and save bug
3.

Actual results:
It will show 500 error message

Expected results:
The bug should be saved without error

Additional info:
Comment 1 Jeff Fearn 🐞 2016-04-07 06:56:30 UTC 
[Thu Apr 07 02:51:01.491648 2016] [:error] [pid 5415] Wide character in subroutine entry at /var/www/html/bugzilla/Bugzilla/Object.pm line 531.\n
Comment 2 Jeff Fearn 🐞 2016-04-20 06:36:29 UTC 
*** Bug 1320004 has been marked as a duplicate of this bug. ***
Comment 3 Muhammad Tahir 2016-05-18 03:12:18 UTC 
*** Bug 1328678 has been marked as a duplicate of this bug. ***
Comment 4 Matt Tyson 🤬 2016-05-19 00:27:30 UTC 
After far to much debugging inside of DBD::Pg, it turns out this is a database server misconfiguration

edit the postgresql.conf file, look for a setting called 'client_encoding'

It's probably set to something like 'sql_ascii'.  It should be set to UTF8.

EG:

client_encoding            = 'UTF8'

Restart the database server and it should work.
Comment 5 Rony Gong 🔥 2016-05-19 01:18:32 UTC 
QE also changed this setting against QE server, and it could save UTF8 string now.