Bug 714324 - [abrt] virtuoso-opensource-6.1.2-1.fc13: ssg_prin_id: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
Summary: [abrt] virtuoso-opensource-6.1.2-1.fc13: ssg_prin_id: Process /usr/bin/virtuo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: virtuoso-opensource
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ff47bf8c3d587458c5eaa379913...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-18 03:40 UTC by H0RN3TT3
Modified: 2011-06-27 11:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:40:12 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (66.72 KB, text/plain)
2011-06-18 03:40 UTC, H0RN3TT3 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description H0RN3TT3 2011-06-18 03:40:51 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_h18990.ini +wait
comment: firefox
component: virtuoso-opensource
crash_function: ssg_prin_id
executable: /usr/bin/virtuoso-t
kernel: 2.6.34.7-66.fc13.i686
package: virtuoso-opensource-6.1.2-1.fc13
rating: 4
reason: Process /usr/bin/virtuoso-t was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1308367359
uid: 500

How to reproduce
-----
1.firefox
2.
3.
Comment 1 H0RN3TT3 2011-06-18 03:40:57 UTC 
Created attachment 505367 [details]
File: backtrace
Comment 2 Bug Zapper 2011-06-27 11:40:12 UTC 
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.