Hide Forgot
abrt 1.1.0 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/bin/tor -f /home/CyrusHMH/.vidalia/torrc DataDirectory /home/CyrusHMH/.tor ControlPort 9051 HashedControlPassword 16:B8DCA520CB417EBC60CFE82C5F7EF58F834C2C4D5B7F6BD5ED8CF6673C component: tor crash_function: fetch_bridge_descriptors executable: /usr/bin/tor global_uuid: 1a76e50c61bc6fe2f803b9739c89e1a12a993287 kernel: 2.6.33.4-95.fc13.i686.PAE package: tor-core-0.2.1.25-1300.fc13 rating: 4 reason: Process /usr/bin/tor was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1.service polipo restart 2.click vidalia 3.start tor
Created attachment 415569 [details] File: backtrace
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping