- Package:
- iceweasel
- Source:
- firefox-esr
- Submitter:
- Sam Morris
- Date:
- 2021-05-27 23:09:12 UTC
- Severity:
- wishlist
- Tags:
Since upgrading to rc1, Iceweasel will not work. When run, it opens a
window that says:
XML Parsing Error: undefined entity
Location: chrome://browser/content/browser.xul
Line Number 242, Column 5:
<key key="&fullZoomReduceCmd.commandkey2;" command="cmd_fullZoomReduce" modifiers="accel"/>
----^
clone 483123 -1 reassign -1 iceweasel-l10n-en-gb severity 483123 important retitle 483123 Should be able to cope with out of date lanaguage packs thanks Thanks to Mike Hommey who helped track this down to the iceweasel-l10n-en-gb package. Iceweasel should really be able to cope with this, instead of presenting the user with a totally incomprehensible error message that they will have no chance of figuring out without buing a mozilla expert.
I`ve got the same result with iceweasel-l10n-uk-ua. Starting iceweasel with LANG=C resolves problem. Excuse me my bad English.
Same issue with iceweasel-l10n-pl. Regards.
Same with de and es-ar.
Same issue with iceweasel-l10n-ru
package iceweasel found 483123 3.0~rc2-1 thanks Hi, I get the same error under 3.0~rc2-1 and with l10n-fr Regards, Didier
Le mercredi 11 juin 2008 22:32:32 Mike Hommey, vous avez écrit : Hi, I don't think that a completely unuseable package leads to "wishlist", but I respect your point of view and won't play BTS ping-pong (as I'm no DD...). Anyway, I think that the triggered error should at least inform the user about the error (just mention "warning, your language package is out of date, Iceweasel won't work correctly" would be enough) because without that, we are just lost with broken and not working iceweasel. Another solution is to detect the error and restart as "LANG=C iceweasel" which is at least useable. The last (but not least) would be to conflict with too old language packages. This would elegantly solve the bug. Best regards, OdyX
The fact is the problem is with the way the *experimental* packages for language packs implemented dependencies onto iceweasel. It's useless to add conflicts with old *experimental* language packages, when there are so many of them and when they will obviously be fixed when newer versions are uploaded to unstable. People using only unstable won't have any problem, and people upgrading from etch won't have problems either. This is an interim problem, only due to *experimental* packages. I don't want to clutter iceweasel for experimental issues. Now, for the rest of the possible "workarounds" *that* is a wishlist item, since dependencies already should be doing their work to avoid these issues in the first place. Mike
Le jeudi 12 juin 2008 11:03:07 Mike Hommey, vous avez écrit : ACK. Many thanks for the explanation. OdyX
severity 483123 important thanks On 23:13 Thu 05 Jun , Dmitry E. Oboukhov wrote: DEO> Same issue with iceweasel-l10n-ru please, add record 'Conflict: iceweasel-l10n (<3.0)' to debian/control
Greeting to you once again I am writing for the second time as I did not receive any reply from you to my previous message. Kindly reply so we can discuss the subject as soon as possible. Sincerely, Andy Landman