Bug 1752277 - Loss of calendar colors
Summary: Loss of calendar colors
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-15 15:10 UTC by Nicolas Berrehouc
Modified: 2020-05-26 17:57 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1752279 (view as bug list)
Environment:
Last Closed: 2020-05-26 17:57:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nicolas Berrehouc 2019-09-15 15:10:30 UTC
Description of problem:
Loss of calendar colors after update from thunderbird-60.8.0-1.fc30.x86_64 to thunderbird-68.1.0-1.fc30.x86_64

Version-Release number of selected component (if applicable):
thunderbird-68.1.0-1.fc30.x86_64

How reproducible:


Steps to Reproduce:
1. Update thunderbird
2. Start thunderbird
3. Calendars are still present but without color

Actual results:
Calendars are shown without color parameter, only transparency.

Expected results:
Calendars are shown with the color parameter like before update.

Additional info:
I tried to set value from false to true in Preferences/Advanced/General/Config Editor and the calendar.view.useSystemColors parameter but nothing better after restart.
Downgrade to thunderbird-60.8.0-1.fc30.x86_64 and yhe calendars colors are present.

Comment 1 Nicolas Berrehouc 2019-09-16 15:01:29 UTC
If a new Thunderbird profile is created then the calendar works fine and each calendar color is present, no more transparency.
Something goes wrong when updating.

Comment 2 Nicolas Berrehouc 2019-11-30 20:03:01 UTC
I solved that issue by creating a new profile and copying some files and directories so as not to have configure all the profile.

Steps :
1. Create a new Thunderbird profile with ProfileManager option
2. Close Thunderbird
3. Copy Mail directory from old to new profile to restore mails
4. Copy prefs.js from old to new profile to restore mails configuration
5. Copy abook.mab from old to new profile to restore address book
6. Start Thunderbird new profile

Comment 3 Ben Cotton 2020-04-30 20:40:18 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2020-05-26 17:57:32 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.