Bug 20739

Summary:	Thunderbird calendar crashes when creating an event with en_GB language
Product:	Mageia	Reporter:	Mark Dawson Butterworth <mageia>
Component:	RPM Packages	Assignee:	Florian Hubold <doktor5000>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jim, marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	thunderbird-45.8.0-1.mga5.src.rpm	CVE:
Status comment:

Description Mark Dawson Butterworth 2017-04-26 19:34:26 CEST

Description of problem:

Thunderbird calendar crashes when creating an event with en_GB language

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

45.8.0

How reproducible:

Every time

Steps to Reproduce:
1. Set up Mageia for UK English
2. Attempt to create a new Event in the Thunderbird Calendar
3. Result is: 

XML Parsing Error: undefined entity
Location: chrome://calendar/content/calendar-event-dialog.xul
Line Number 1216, Column 23:                      <checkbox id="notify-attendees-checkbox"
----------------------^

4. Problem seems to be very similar to https://bugzilla.redhat.com/show_bug.cgi?id=1330427 but that one was apparently fixed in 45.7. Are we missing a fix in Mageia?

Workaround is as suggested in Red Hat bug entry - use en_US LANG

Comment 1 James Kerr 2017-04-26 21:48:20 CEST

This does not happen here on 64 bit Mageia 5. I don't use the bundled version of lightning - it has never worked for me. I use the downloaded add-on, currently version 4.7.8

thunderbird-45.8.0-1.mga5
thunderbird-en_GB-45.8.0-1.mga5

CC: (none) => jim

Comment 2 Marja Van Waes 2017-04-28 10:26:56 CEST

Assigning to the registered maintainer

CC: (none) => marja11
Assignee: bugsquad => doktor5000

Comment 3 Mark Dawson Butterworth 2017-05-11 21:48:05 CEST

I can confirm that replacing the bundled version with the latest downloaded add-on (now 5.4) fixes the problem, but do not agree with James that the bundled version has never worked. The bundled version worked fine for me until relatively recently (can't say exactly which update broke it as I hadn't needed to create a new event for a while).

I too am on 64-bit.

Comment 4 katnatek 2018-07-06 19:16:38 CEST

One user in blogdrake report the same for mageia 6

Whiteboard: (none) => MGA6TOO

Comment 5 Marja Van Waes 2018-10-07 16:56:34 CEST

(In reply to katnatek from comment #4)
> One user in blogdrake report the same for mageia 6

Thanks, changing "Version:" to "6" then, since Mageia 5 is no longer maintained.

Version: 5 => 6

Marja Van Waes 2018-10-07 16:56:41 CEST

Whiteboard: MGA6TOO => (none)

Comment 6 Aurelien Oudelet 2020-08-16 18:59:33 CEST

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you 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.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

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