FS#29939 - [chromium] Error: the XML response that was returned from the server is invalid.

Attached to Project: Arch Linux
Opened by Zsolt Udvari (uzsolt) - Friday, 18 May 2012, 13:52 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 20 May 2012, 12:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Go to http://www.delmagyar.hu/belfold_hirek/juliustol_jon_a_ketforintos_tavkozlesi_ado_-_percenkent_es_uzenetenkent/2280156/
Near bottom of page, click "következő" (means "Next" in hungarian). You'll receive the error in subject:
Error: the XML response that was returned from the server is invalid.

With luakit, opera, firefox works well.

Since latest upgrade worked well but after upgrading to 19.0.x drops error.

About two years ago I've reported to chromium similar error:
http://code.google.com/p/chromium/issues/detail?id=44531&q=udvzsolt&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Feature%20Status%20Owner%20Summary
but not on ArchLinux.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 20 May 2012, 12:25 GMT
Reason for closing:  Works for me
Comment by Evangelos Foutras (foutrelis) - Saturday, 19 May 2012, 16:04 GMT
Please upgrade to 19.0.1084.46-2; it should then work.
Comment by Zsolt Udvari (uzsolt) - Sunday, 20 May 2012, 07:03 GMT
It's already 19.0.1084.46-2.

$ LC_ALL=C pacman -Qi chromium
Name : chromium
Version : 19.0.1084.46-2

Does it works for you?
Comment by Evangelos Foutras (foutrelis) - Sunday, 20 May 2012, 11:07 GMT
It works for me, yes. If I downgrade to 19.0.1084.46-1, I can then reproduce the error you describe.

Make sure Chromium is not running in the background or something (even reboot your computer maybe.)
Comment by Zsolt Udvari (uzsolt) - Sunday, 20 May 2012, 11:16 GMT
$ LC_ALL=C yaourt -Qi chromium | grep "Install Date"
Install Date : Fri May 18 18:10:53 2012

I make some power-off/power-on since I've installed this version/release of chromium.

What's the difference between release 1 and release 2 which can produce this error? What can cause this problem? Maybe an user-setting?
Comment by Evangelos Foutras (foutrelis) - Sunday, 20 May 2012, 11:31 GMT
19.0.1084.46-1 linked against the system libxml; 19.0.1084.46-2 went back to building its own internal libxml.

It's not a user setting, so it's weird that it doesn't work for you.

If `readelf -d /usr/lib/chromium/chromium | grep libxml' outputs anything, reinstall the chromium package.

You can also test with a new profile: chromium --user-data-dir=$(mktemp -d)
Comment by Zsolt Udvari (uzsolt) - Sunday, 20 May 2012, 11:38 GMT
readelf doesn't print anything.

Maybe I'm stupid but it works again.
I hope it was my mistake :)

Loading...