Version-Release number of selected component: transmission-gtk-2.82-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: transmission-gtk crash_function: event_exit executable: /usr/bin/transmission-gtk kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 event_exit at log.c:79 #3 event_errx at log.c:136 #4 evdns_cancel_request at evdns.c:2798 #5 evdns_getaddrinfo_timeout_cb at evdns.c:4233 #6 event_process_active_single_queue at event.c:1350 #7 event_process_active at event.c:1420 #8 event_base_loop at event.c:1621 #9 event_base_dispatch at event.c:1450 #10 libeventThreadFunc at trevent.c:249 #11 ThreadFunc at platform.c:108 Potential duplicate: bug 872868
Created attachment 841895 [details] File: backtrace
Created attachment 841896 [details] File: cgroup
Created attachment 841897 [details] File: core_backtrace
Created attachment 841898 [details] File: dso_list
Created attachment 841899 [details] File: environ
Created attachment 841900 [details] File: limits
Created attachment 841901 [details] File: maps
Created attachment 841902 [details] File: open_fds
Created attachment 841903 [details] File: proc_pid_status
Created attachment 841904 [details] File: var_log_messages
Another user experienced a similar problem: I use icon-only task manager in KDE and every time when I suddenly click on the QTransmission icon it opens a new instance instead of the current one working and that causes the crash. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/transmission-qt crash_function: event_exit executable: /usr/bin/transmission-qt kernel: 3.15.6-200.fc20.x86_64 package: transmission-qt-2.84-1.fc20 reason: transmission-qt killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I dont know reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: transmission-gtk crash_function: event_exit executable: /usr/bin/transmission-gtk kernel: 3.16.3-200.fc20.x86_64 package: transmission-gtk-2.84-1.fc20 reason: transmission-gtk killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I resumed from suspend and it had crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/transmission-gtk magnet:?xt=urn:btih:EUV7OLK6GIF36PUVWXBW4S7AGA2Z5XRA&dn=South.Park.S18E05.HDTV.x264-KILLERS&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.publicbt.com:80&tr=udp://tracker.istole.it:80&tr=udp://open.demonii.com:80&tr=udp://tracker.coppersurfer.tk:80 crash_function: event_exit executable: /usr/bin/transmission-gtk kernel: 3.16.6-200.fc20.x86_64 package: transmission-gtk-2.84-1.fc20 reason: transmission-gtk killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.