Version-Release number of selected component: mt-daapd-0.2.4.2-17.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/sbin/mt-daapd crash_function: avahi_client_errno executable: /usr/sbin/mt-daapd kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (2 frames) #4 avahi_client_errno at client.c:791 #5 rend_init at rend-avahi.c:297
Created attachment 848607 [details] File: backtrace
Created attachment 848608 [details] File: cgroup
Created attachment 848609 [details] File: core_backtrace
Created attachment 848610 [details] File: dso_list
Created attachment 848611 [details] File: environ
Created attachment 848612 [details] File: limits
Created attachment 848613 [details] File: maps
Created attachment 848614 [details] File: open_fds
Created attachment 848615 [details] File: proc_pid_status
Created attachment 848616 [details] File: var_log_messages
Another user experienced a similar problem: The problem occured after trying to start the DAAP server by issuing the following command: sudo service mt-daapd start reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/sbin/mt-daapd crash_function: avahi_client_errno executable: /usr/sbin/mt-daapd kernel: 3.16.3-200.fc20.x86_64 package: mt-daapd-0.2.4.2-17.fc20 reason: mt-daapd killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: 1. It happens short time after starting the service. 2. As another test: * I stopped the service. * I removed /var/cache/mt-daapd/songs.gdb * The service crashed again. The file wasn't created (which means it crash before indexing the music). 3. In the past, it had some occasional crashes (not reported, because it wasn't consistent). But now it crash every time it get restarted. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/sbin/mt-daapd crash_function: avahi_client_errno executable: /usr/sbin/mt-daapd kernel: 3.18.5-101.fc20.x86_64 package: mt-daapd-0.2.4.2-17.fc20 reason: mt-daapd killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
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.