Bug 594577 - [abrt] crash in tor-core- fetch_bridge_descriptors: Process /usr/bin/tor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tor-core- fetch_bridge_descriptors: Proces...
Alias: None
Product: Fedora
Classification: Fedora
Component: tor
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Enrico Scholz
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:1a76e50c61bc6fe2f803b9739c8...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-21 04:07 UTC by cyrushmh
Modified: 2011-06-02 14:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-02 14:44:22 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (8.52 KB, text/plain)
2010-05-21 04:07 UTC, cyrushmh
no flags Details

Description cyrushmh 2010-05-21 04:07:23 UTC
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
package: tor-core-
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

Comment 1 cyrushmh 2010-05-21 04:07:26 UTC
Created attachment 415569 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-02 13:45:44 UTC
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: 

Note You need to log in before you can comment on or make changes to this bug.