Description of problem: I do not know for sure what caused this problem. The only thing that I know happened right before the crash occurred was the following sequence of events: 1. I opened Amarok and noticed the playlist was grayed out. 2. Then I noticed that the connection to the server (a mounted nfs partition) had not been established. 3. After mounting the nfs partition, Amarok was unresponsive to *any* action, even ending. 4. When I responded to the query "want to terminate" that KDE gives when an application is unresponsive to closing I chose to terminate and that is when the crash occurred. I hope this is useful. If you have any queries, let me know. Version-Release number of selected component: zeitgeist-0.9.14-3.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/zeitgeist-daemon crash_function: _g_log_abort executable: /usr/bin/zeitgeist-daemon kernel: 3.15.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 g_variant_type_info_check at gvarianttypeinfo.c:164 #6 g_variant_type_info_get_type_string at gvarianttypeinfo.c:200 #7 g_variant_get_type at gvariant.c:2073 #8 append_value_to_blob at gdbusmessage.c:2426 #9 append_body_to_blob at gdbusmessage.c:2542 #10 g_dbus_message_to_blob at gdbusmessage.c:2711 #11 g_dbus_connection_send_message_unlocked at gdbusconnection.c:1662 #12 g_dbus_connection_send_message_with_reply_unlocked at gdbusconnection.c:1996 #13 g_dbus_connection_send_message_with_reply at gdbusconnection.c:2099
Created attachment 928201 [details] File: backtrace
Created attachment 928202 [details] File: cgroup
Created attachment 928203 [details] File: core_backtrace
Created attachment 928204 [details] File: dso_list
Created attachment 928205 [details] File: environ
Created attachment 928206 [details] File: limits
Created attachment 928207 [details] File: maps
Created attachment 928208 [details] File: open_fds
Created attachment 928209 [details] File: proc_pid_status
Created attachment 928210 [details] File: var_log_messages
Another user experienced a similar problem: It just popped up. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/zeitgeist-daemon crash_function: _g_log_abort executable: /usr/bin/zeitgeist-daemon kernel: 3.15.10-200.fc20.x86_64 package: zeitgeist-0.9.14-3.fc20 reason: zeitgeist-daemon killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Dear users, a broken build of zeitgeist has been replaced recently and pushed to the stable updates repository without prior testing: https://admin.fedoraproject.org/updates/search/zeitgeist A new one will be available for testing.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.