Bug 22118

Summary:	Unsupported encoding iso-8859-2 / windows-1251 on Chromium
Product:	Mageia	Reporter:	Eiden <altsyde>
Component:	RPM Packages	Assignee:	Christiaan Welvaart <cjw>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
See Also:	https://bugzilla.redhat.com/show_bug.cgi?id=1413644
Whiteboard:
Source RPM:	chromium-browser-stable-62.0.3202.94-1.mga6.src	CVE:
Status comment:

Description Eiden 2017-12-03 17:45:15 CET

Unlike Google Chrome and Firefox Chromium doesn't support codepages iso-8859-2 / windows-1251
Latest tested version:
chromium-browser-stable-62.0.3202.94-1.mga6
How reproducible:
1) Create blank file with extension .xml
2) Paste there line
<?xml version="1.0" encoding="windows-1251"?>
3) Open it with Chromium

Fedora has the same bugreport (Bug 1413644), I didn't check if they fixed it
On 'Chromium bugs' it's Issue 28748

Comment 1 Marja Van Waes 2017-12-03 18:38:40 CET

The more recent fedora bug report says it could not be reproduced in v. 60.0.3112.113
Do they have different patches than we have, or is this a regression?

Assigning to our registered chromium-browser-stable maintainer.

CC: (none) => marja11
See Also: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=1413644
Assignee: bugsquad => cjw

Comment 2 Christiaan Welvaart 2017-12-05 01:44:09 CET

I tried to debug this problem so started chromium with --single-process but that solved the problem. NOTE: this option is for debugging, only use it for testing. Same with --no-sandbox, the problem does not show up (again, this is a debugging feature, only use it for testing).

Fedora has chromium built with the bundled libxml so that explains the difference. Chromium builds its bundled libxml with libicu instead of glibc's iconv feature.

So the sandboxing of chromium's rendering processes appears to interfere with libxml's use of iconv to perform character encoding conversions.

Comment 3 Aurelien Oudelet 2020-08-06 16:55:43 CEST

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

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 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien