Description of problem: Just hit the "delete files and remove" menuitem. 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 magnet:?xt=urn:btih:4E5727B83A405AD68856032AD72CAE9D1406D52F&dn=workaholics+s02e07+french+ld+bdrip+xvid+mind&tr=udp%3A%2F%2Ffr33domtracker.h33t.com%3A3310%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337 crash_function: tr_isTorrent executable: /usr/bin/transmission-gtk kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 tr_isTorrent at torrent.h:370 #1 tr_torrentInfo at torrent.c:1151 #2 tr_torrentHasMetadata at transmission.h:1832 #3 tr_cpHasAll at completion.h:94 #4 tr_cpGetStatus at completion.c:66 #5 tr_torrentRecheckCompleteness at torrent.c:2143 #6 onVerifyDoneThreadFunc at torrent.c:1781 #7 readFromPipe at trevent.c:193 #8 event_process_active_single_queue at event.c:1350 #9 event_process_active at event.c:1420
Created attachment 843956 [details] File: backtrace
Created attachment 843957 [details] File: cgroup
Created attachment 843958 [details] File: core_backtrace
Created attachment 843959 [details] File: dso_list
Created attachment 843960 [details] File: environ
Created attachment 843961 [details] File: exploitable
Created attachment 843962 [details] File: limits
Created attachment 843963 [details] File: maps
Created attachment 843964 [details] File: open_fds
Created attachment 843965 [details] File: proc_pid_status
Created attachment 843966 [details] File: var_log_messages
Another user experienced a similar problem: Transmission was just running in the "tray", idling, not downloading anything, when it crashed. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: transmission-gtk magnet:?xt=urn:btih:f688006bc724d227f24ef70631904dd6d7e99fea&dn=Cosmos.A.Space.Time.Odyssey.S01E01.720p.HDTV.X264-DIMENSION+%5BPub&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Ftracker.istole.it%3A6969&tr=udp%3A%2F%2Fopen.demonii.com%3A1337 crash_function: tr_isTorrent executable: /usr/bin/transmission-gtk kernel: 3.14.8-200.fc20.x86_64 package: transmission-gtk-2.82-3.fc20 reason: transmission-gtk killed by SIGSEGV 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.