| Summary: | [abrt] evolution-data-server-3.0.3.1-1.fc15: Crash involving libical __tzfile_read and icaltimezone_get_utc_offset_of_utc_time from two threads | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tadej Janež <tadej.j> | ||||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | beejo.niein, chandana, dennisgdaniels, mbarnes, mcrha, pavol.ondercin, Reinhard.Bayer100, ruppertstefan, tepaze, twaugh | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:d6c4999cfc3e5a6ce53fad6d4991ce196293b572 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | --- | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Tadej Janež
2012-01-05 10:06:33 UTC
Created attachment 550870 [details]
File: maps
Created attachment 550871 [details]
File: backtrace
Thanks for a bug report. This is crashing in libical, and I see you've the recent 0.48 version. Could you try to downgrade it to the previous version, to see whether it'll help? Thanks in advance. You can do it by this command: $ yum downgrade libical Another option is that this is related to bug #756231, because I'm also using libical 0.48, on Fedora 16, with the change from bug #756231 applied, and I didn't see any such crash yet. What I forgot to mention, then in the backtrace one thread is reading timezone information in libical, while other thread is reading it, working with NULL value, which probably leads to the crash. Ok, I can downgrade to libical 0.47. I have a problem, however, because I don't know how to quickly and repeatably reproduce the crash? I haven't downgraded libical yet and I got another backtrace. ABRT filed it as a new bug report though: bug #771959 Milan, can you confirm that that is the same bug as this one? *** Bug 771959 has been marked as a duplicate of this bug. *** (In reply to comment #6) > ABRT filed it as a new bug report though: > bug #771959 > > Milan, can you confirm that that is the same bug as this one? Yup, it's a crash in the same function and same circumstances, only slightly later, thus ABRT's hash for the backtrace was different. With the next release of evolution-data-server-3.2.3, I would also give a try to it, as it contains changes in this area too. We would be able to check where is the issue, either eds or libical (testing with both new libical and eds as a final step will be appreciated, as they both should work together without crashing - it's basically a combination I'm using now). (In reply to comment #8) > > Yup, it's a crash in the same function and same circumstances, only slightly > later, thus ABRT's hash for the backtrace was different. Aha, ok. Thanks for clearing this up for me! > With the next release of evolution-data-server-3.2.3, I would also give a try > to it, as it contains changes in this area too. We would be able to check where > is the issue, either eds or libical (testing with both new libical and eds as a > final step will be appreciated, as they both should work together without > crashing - it's basically a combination I'm using now). I think you mixed up F-16 and F-15 here. I've seen this crash on my F-15 machine with evolution-data-server-3.0.3.1 and libical-0.48. Would your words still apply here? (In reply to comment #9) > I think you mixed up F-16 and F-15 here. I've seen this crash on my F-15 > machine with evolution-data-server-3.0.3.1 and libical-0.48. Would your words > still apply here? Ouch, I overlooked this is for Fedora 15, though I believe the same applies to it too, only the change would be slightly modified, to fit 3.0.3 sources of evolution-data-server. The only thing is that there are not planned any further updates of evolution-data-server in Fedora 15, and the 3.2.3 release in Fedora 16 is also final for that version (unless any critical issue arises). *** Bug 772572 has been marked as a duplicate of this bug. *** (In reply to comment #10) > > Ouch, I overlooked this is for Fedora 15, though I believe the same applies to > it too, only the change would be slightly modified, to fit 3.0.3 sources of > evolution-data-server. The only thing is that there are not planned any further > updates of evolution-data-server in Fedora 15, and the 3.2.3 release in Fedora > 16 is also final for that version (unless any critical issue arises). Ok, I understand! Milan, thanks for taking the time to explain this. I've downgraded libical to version 0.46-3 and I'll see what happens. Anyway, I hope I'll upgrade to F-16 soon. new entry in thunderbird google diary add-on rating: 4 Package: evolution-data-server-3.2.2-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) *** Bug 773695 has been marked as a duplicate of this bug. *** 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 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 |