| Summary: | [abrt] evolution-2.32.2-1.fc14: g_type_class_meta_marshal: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Allan Engelhardt <allane> | ||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | fonya, krsdb, lucilanga, matthias.rambausek, mbarnes, mcrha, thomas.defranc | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:6fd11de0f18ceeea62e55161fedc1eacc6c1e644 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 14:16:21 UTC | 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
Allan Engelhardt
2011-03-09 10:05:43 UTC
Created attachment 483146 [details]
File: backtrace
Thanks for a bug report. The backtrace doesn't show many useful details, I see only that this happened in GDBus, when it was trying to invoke a signal one one of its objects. I suppose it depends on previous work with Evolution, as such object (connection, in this case) is probably freed by evolution, but GDBus didn't notice that yet. Or something similar, it's hard to tell for sure without steps to reproduce, which I do not expect it being easy to find in this case. If this is related to EBook, then I recall some fixes being done on a similar front in 2.91.x development versions. Please try to find some steps to reproduce or just wait for 3.0 version and let's see whether it'll be happening there too. Thanks in advance. Thread 1 (Thread 0x7fe688936980 (LWP 18162)): #0 g_type_class_meta_marshal (closure=0x7fe64c0105d0, return_value=0x0, n_param_values=4, param_values=0x7fe67c003400, invocation_hint=0x7fffa3301e60, marshal_data=<value optimized out>) at gclosure.c:875 #1 0x00000036b4c0e03e in g_closure_invoke (closure=0x7fe64c0105d0, return_value=0x0, n_param_values=4, param_values=0x7fe67c003400, invocation_hint=0x7fffa3301e60) at gclosure.c:766 #2 0x00000036b4c1ec98 in signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x7fe63402dbd0, emission_return=0x0, instance_and_params=0x7fe67c003400) at gsignal.c:3290 #3 0x00000036b4c287b5 in g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at gsignal.c:2983 #4 0x00000036b4c28983 in g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at gsignal.c:3040 0x7fffa3302150, reg_save_area = 0x7fffa3302090}} #5 0x00000036b58921c2 in emit_signal_instance_in_idle_cb (data=0x7fe67c003900) at gdbusconnection.c:3373 #6 0x00000036b3441e33 in g_main_dispatch (context=0x1ff1320) at gmain.c:2149 #7 g_main_context_dispatch (context=0x1ff1320) at gmain.c:2702 #8 0x00000036b3442610 in g_main_context_iterate (context=0x1ff1320, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2780 #9 0x00000036b3442c82 in g_main_loop_run (loop=0x24c7ad0) at gmain.c:2988 #10 0x00000036ba94b0b7 in IA__gtk_main () at gtkmain.c:1237 #11 0x00000000004026f9 in main (argc=1, argv=0x7fffa33024c8) at main.c:679 Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.create new calendar 2. 3. Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Move several mails at once from one imap-folder to another folder on the same imap-account with drag 'n' drop. Comment ----- Account is a gmail account, accessed over evolution's imapx function Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Do nothing, just stop working 2. 3. Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Evolution we just running on a recently-rebooted workstation, Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Evolution was just running in the background checking mail periodically as usual. Had been running for at least a day with no problems. Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Just running in the background against an IMAP and a local spool file. Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I looked at the calender which I just added and synchronised from my Google Calendar 2. I scrolled down to see other months Comment ----- I had a lot of appointments, maybe this is the problem... Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Was just running over night Package: evolution-2.32.2-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Didn't do anything. Assume this is the same crash as all the others but I can't see that from ABRT. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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 |