Version-Release number of selected component: zeitgeist-1.0-4.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: zeitgeist-datahub crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/zeitgeist-datahub journald_cursor: s=eef0d83a200b46ec92ea0d547b0d751b;i=258237;b=9cb737ee40fd47818e4a9ce768156602;m=1746a6532;t=558c6b7188291;x=f166f2bc9cb0a01b kernel: 4.13.0-1.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4025 #1 g_object_ref at gobject.c:3180 #2 _g_object_ref0 at event.c:335 #3 zeitgeist_event_add_subject at event.c:395 #4 zeitgeist_event_constructv_full at event.c:442 #5 zeitgeist_event_new_full at event.c:452 #6 telepathy_observer_create_text_event at telepathy-observer.c:621 #7 telepathy_observer_observe_text_channel at telepathy-observer.c:840 #8 telepathy_observer_observe_channels at telepathy-observer.c:1951 #9 _telepathy_observer_observe_channels_tp_simple_observer_observe_channels_impl at telepathy-observer.c:2013 Potential duplicate: bug 1470061
Created attachment 1324179 [details] File: backtrace
Created attachment 1324180 [details] File: cgroup
Created attachment 1324181 [details] File: core_backtrace
Created attachment 1324182 [details] File: cpuinfo
Created attachment 1324183 [details] File: dso_list
Created attachment 1324184 [details] File: environ
Created attachment 1324185 [details] File: exploitable
Created attachment 1324186 [details] File: limits
Created attachment 1324187 [details] File: maps
Created attachment 1324188 [details] File: open_fds
Created attachment 1324189 [details] File: proc_pid_status
Created attachment 1324190 [details] File: var_log_messages
Similar problem has been detected: This crash shows up in gnome-abrt every time after the polari IRC client logs me in at freenode. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: zeitgeist-datahub crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/zeitgeist-datahub journald_cursor: s=b9f2e7c93cbf431f9ea5f3d7663a2763;i=eb905;b=98ca83337dbd4635b25fa2119c4972bc;m=41cd2ec;t=5619e54506531;x=e0d1b8b10580b66f kernel: 4.14.8-300.fc27.x86_64 package: zeitgeist-1.0-5.fc27 reason: zeitgeist-datahub killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
*** Bug 1538761 has been marked as a duplicate of this bug. ***
*** Bug 1541797 has been marked as a duplicate of this bug. ***
*** Bug 1553864 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 EOL if it remains open with a Fedora 'version' of '27'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.