Bug 890686 - Unable to select Thunderbird/Lightning as the default calendar app
Summary: Unable to select Thunderbird/Lightning as the default calendar app
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 18
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-28 18:18 UTC by Nicholas Schuetz
Modified: 2014-02-05 14:14 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:14:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Thunderbird / Lightining is not an option under Calendar (32.38 KB, image/png)
2012-12-28 18:18 UTC, Nicholas Schuetz
no flags Details

Description Nicholas Schuetz 2012-12-28 18:18:36 UTC
Created attachment 669944 [details]
Thunderbird / Lightining is not an option under Calendar

Install Thunderbird with Lightning (Calendar).

Goto the 'System Tools' Application grouping
Select 'System Settings'
Select 'Details' under the 'System' header at the bottom
In the column on the left, select 'Default Applications'
Click the 'Mail' dropdown and select 'Thunderbird' (the default is Evolution).
Now click the 'Calendar' dropdown, there is no other option that the default 'Evolution'.

This is inconvenient because i cannot see my appointments for today and tomorrow in the 'systray' like i was able to in F16.

Versions:

[nick@desktop ~]$ rpm -qf /usr/bin/gnome-control-center
control-center-3.6.3-1.fc18.x86_64

[nick@desktop ~]$ rpm -qa |grep thunder
thunderbird-lightning-1.9-1.fc18.x86_64
thunderbird-17.0-1.fc18.x86_64

Comment 1 David Dreggors 2013-01-02 05:04:48 UTC
I can confirm this. I can set default mail app as Thunderbird but under Calendar all I see is Evolution. 

thunderbird-17.0-1.fc18.x86_64
thunderbird-lightning-1.9-1.fc18.x86_64

Comment 2 Fedora End Of Life 2013-12-21 10:06:33 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 3 David Dreggors 2014-01-03 14:58:47 UTC
Well Fedora 18 may be nearing end of life, but I can positively confirm that this is still an issue in Fedora 19 and Fedora 20.

I have several installs of Fedora 20 already and the same problem exists here as well.

Comment 4 Fedora End Of Life 2014-02-05 14:14:22 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.