Bug 20650

Summary: My bug report with edited title displays an error message (bugs.mageia.org)
Product: Infrastructure Reporter: Stig-Ørjan Smelror <smelror>
Component: BugzillaAssignee: Sysadmin Team <sysadmin-bugs>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: High CC: sysadmin-bugs
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://bugs.mageia.org/show_bug.cgi?id=20638
Whiteboard:
Source RPM: CVE:
Status comment:

Description Stig-Ørjan Smelror 2017-04-10 19:55:48 CEST
Description of problem:

I submitted an bug report and somebody changed the title.
Now when I try to see the bug report, I get an error message.

----------
Software error:

Malformed UTF-8 character (fatal) at Bugzilla/Bug.pm line 567, <DATA> line 751.

For help, please send mail to the webmaster (root@localhost), giving this error message and the time and date of the error.
----------

I've tried with Firefox on Linux and Windows and with Chrome on Linux with the same result. Also tried viewing the report logged in and not being logged in.

I can view all the other reports without errors or problems.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Stig-Ørjan Smelror 2017-04-10 20:01:44 CEST
Wrong place for this bug report.

Resolution: (none) => INVALID
Status: NEW => RESOLVED

Comment 2 Rémi Verschelde 2017-04-11 05:37:33 CEST
It's not the wrong place for such a report, just the wrong component ;)

The issue is that since the upgrade, Bugzilla chokes on non-ascii characters in the database (such as the OE in your name). The sysadmins need to convert the database the UTF-8 to fix it.

Product: Websites => Infrastructure
CC: (none) => sysadmin-bugs
Component: Other => Bugzilla
Assignee: atelier-bugs => sysadmin-bugs
Priority: Normal => High
Resolution: INVALID => (none)
Status: RESOLVED => REOPENED
Severity: normal => major
Version: trunk => unspecified

Comment 3 Rémi Verschelde 2017-04-11 05:39:12 CEST
Ah well, I see you open a new bug report afterwards.

*** This bug has been marked as a duplicate of bug 20652 ***

Resolution: (none) => DUPLICATE
Status: REOPENED => RESOLVED