Closed Bug 459356 Opened 17 years ago Closed 17 years ago

File -> New -> Calendar disabled (in all TB modes)

Categories

(Calendar :: Lightning Only, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: computermacgyver, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3 Build Identifier: 2008091718 (0.9) I have no calendars defined and upgraded from a previous build to the latest one. File -> New -> Calendar is disabled in the menu in all modes. Switching to Calendar mode yields the following error in the error counsel: Error: Components.classes['@mozilla.org/calendar/datetime;1'] has no properties Source File: chrome://calendar/content/calUtils.js Line: 59 Bug 437451 -- Shows that Calendar should be disabled in Mail mode, but without a calendar defined it seems that the menu option to create a new calendar is not enabled by going to Calendar mode Reproducible: Always Steps to Reproduce: 1. Delete all calendars. 2. Switch to Mail Mode 3. Exit Thunderbird 4. Open Thunderbird Actual Results: It is now impossible to create a new calendar. Expected Results: File -> New -> Calendar option should be available in when switching to Calendar mode.
Does your system meet following requirements, especially libstdc++5? http://www.mozilla.org/projects/calendar/lightning/system-requirements.html#linux
I was lacking libstdc++5. Installing that package and removing and then reinstalling lightning fixed the problem. All works correctly now. What is frustrating, however, is that the previous version worked fine on my system. It was not until Thunderbird automatically downloaded the updated version and I elected to install it that the problem appeared. Is there someway that we can warn users if an update will require a new package, etc.? Thank you for your help! I appreciate the excellent work on this project.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.