Bug 716579 - [abrt] evince-2.30.3-3.fc13: _dbus_abort: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
Summary: [abrt] evince-2.30.3-3.fc13: _dbus_abort: Process /usr/bin/evince was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:084d8100990bc94425edcb07a25...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-25 01:54 UTC by Ren-Bo Wang
Modified: 2011-06-27 11:39 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (21.01 KB, text/plain)
2011-06-25 01:55 UTC, Ren-Bo Wang 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ren-Bo Wang 2011-06-25 01:54:57 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evince '/media/Transcend/Books/Classical Fields/classical fields.pdf'
component: evince
crash_function: _dbus_abort
executable: /usr/bin/evince
kernel: 2.6.34.9-69.fc13.x86_64
package: evince-2.30.3-3.fc13
rating: 4
reason: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1308966629
uid: 500

How to reproduce
-----
1. I am reading some pdf file
2.
3.
Comment 1 Ren-Bo Wang 2011-06-25 01:55:01 UTC 
Created attachment 509868 [details]
File: backtrace
Comment 2 Bug Zapper 2011-06-27 11:39:38 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.