| Summary: | [abrt] evolution-data-server-3.2.2-2.fc16: g_type_check_instance_cast: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter <cyclonizer> | ||||||||
| Component: | glib2 | Assignee: | Matthias Clasen <mclasen> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | mbarnes, mclasen, mcrha | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:cceb51323888dc68f71dc219222fcec5c45766b3 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-02-13 18:23:38 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
Peter
2012-02-09 17:34:55 UTC
Created attachment 560672 [details]
File: dso_list
Created attachment 560673 [details]
File: maps
Created attachment 560674 [details]
File: backtrace
Thanks for a bug report. I do not see anything evolution-related in the backtrace, it's somewhere deep in GDbus code. The only place from evolution would be frame #19, which is missing debug info, but it's simple gtk_main_run() call on evolution's side. The rest is all about GDBus. I'm moving this to GLib for an opinion of their developers. Frame #2 seems suspicious to me, with context being NULL, but I do not know GDBus code at all, thus maybe it's correct. Thread 1 (Thread 0xb772b740 (LWP 1787)): #0 g_type_check_instance_cast (type_instance=0xb5a01368, iface_type=80) at gtype.c:3992 #1 0x411ad575 in ?? () from /usr/lib/libecal-1.2.so.10 #2 0x4c4cd531 in call_destroy_notify (context=0x0, callback=0x411ad550, user_data=0xb5a01368) at gdbusconnection.c:259 #3 0x4c4cd57c in exported_interface_free (ei=0x870aa30) at gdbusconnection.c:3880 #4 0x4c29172c in g_hash_table_remove_all_nodes (hash_table=0x8706300, notify=<optimized out>) at ghash.c:495 #5 0x4c2921ec in g_hash_table_unref (hash_table=0x8706300) at ghash.c:979 #6 0x4c4ce250 in exported_object_free (eo=0x870a1e8) at gdbusconnection.c:3855 #7 0x4c29172c in g_hash_table_remove_all_nodes (hash_table=0x86ffaf0, notify=<optimized out>) at ghash.c:495 #8 0x4c2921ec in g_hash_table_unref (hash_table=0x86ffaf0) at ghash.c:979 #9 0x4c4cfdc4 in g_dbus_connection_finalize (object=0x8700850) at gdbusconnection.c:627 #10 0x4c3d1176 in g_object_unref (_object=0x8700850) at gobject.c:2746 #11 0x4c4cd285 in emit_closed_data_free (data=0xb5a03a00) at gdbusconnection.c:1297 #12 0x4c2a1235 in g_source_callback_unref (cb_data=0xb5a04468) at gmain.c:1324 #13 g_source_callback_unref (cb_data=0xb5a04468) at gmain.c:1316 #14 0x4c2a0c53 in g_source_destroy_internal (source=0xb5a044c0, context=0x86e9f18, have_lock=1) at gmain.c:993 #15 0x4c2a4684 in g_main_dispatch (context=0x86e9f18) at gmain.c:2466 #16 g_main_context_dispatch (context=0x86e9f18) at gmain.c:3011 #17 0x4c2a4d70 in g_main_context_iterate (context=0x86e9f18, block=1277900816, dispatch=1, self=0x86df888) at gmain.c:3089 #18 0x4c2a53a7 in g_main_loop_run (loop=0x86e9fa8) at gmain.c:3297 #19 0x0804a764 in ?? () #20 0x4c02e6b3 in __libc_start_main (main=0x804a570 <g_hash_table_destroy@plt>, argc=1, ubp_av=0xbff88df4, init=0x804cb50, fini=0x804cbc0, rtld_fini=0x4c0002c0 <_dl_fini>, stack_end=0xbff88dec) at libc-start.c:226 #21 0x0804a7ed in ?? () Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information. Bugs which were found to be similar to this bug: evolution-data-server: bug #652195, bug #725289, bug #766066 This comment is automatically generated. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" 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 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |