Description of problem: Actually the problem happen with thunderbird-lightning. I do not use sunbird directly. Sometimes when creating new events the time zone info is lost and new events are created with the time zone info "Local Time". And this "Local Time" does not seem to be the same as the time zone which is configured on the local machine. Obviously the time is interpreted in UTC in this case. In my case I use "Europe/Berlin" as time zone. Since time zone is not shown by default in the dialogs the problem is rather mystic because some events are reported as expected others not which is/was rather frustrating. Version-Release number of selected component (if applicable): thunderbird-lightning-1.0-0.16.20090916hg.fc12.i686 Actually the problem exists in F11, too. How reproducible: Always Steps to Reproduce: 1. Configure a time zone in the lightning preferences (e.g. Europe/Berlin) 1. Switch to the "Events & Tasks" view in the right side bar. 2. Click on "New Event" in the right side bar. 3. Enable the time zone display in the option menu of the dialog and verify that it matches the configured time zone. 4. Close the dialog. 5. Create a new task by either double-clicking in the empty space of the task-section in the right side bar or via context(!) menu. 6. Verify that the time zone shown in the dialog is still the configured one. 7. Close the dialog. 8. Now add a new event by either clicking "New Event" in the right side bar or via double clicking in the empty space of the event-section. 9. Now you see "Local time" instead of the configured time zone. When you configure a reminder it will not appear at the right time because time is interpreted in UTC now. To get the right behaviour back one must restart thunderbird. Actual results: New events will be created with wrong time zone info and reminders are fired at the wrong time. Expected results: Always use the configured time zone to create new events and tasks. Additional info: Using "New Event" via "Events and Tasks" in the main menu bar works. BTW, the term "Local Time" is misleading. While in some configurations it may still work correctly it might not always. For instance in most Unix based systems the time stamps reported by the OS are in UTC. Before showing them in an UI they need to be converted to local time which is commonly done by library functions (e.g. localtime() in C). In Windows based systems the time reported by the system is often already in local time and only there the semantic is ok.
Ping! This bug is really annoying because even opening a task via context menu triggers the bug. So I have to restart thunderbird each time I do this.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Well, it's rather disappointing that reported bugs are just ignored. The bug is not fixed yet. Adjusting to F13.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Bug still there in F15. But I guess my writing will end in /dev/null anyway... :-(
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping