Bug 586952 - [abrt] crash in evince-2.30.1-1.fc13: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evince-2.30.1-1.fc13: Process /usr/bin/evince was killed by s...
Status: CLOSED DUPLICATE of bug 586343
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:7f4efaa4d5a4ca88bf06e6c8c6e...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-28 14:58 UTC by Carl G.
Modified: 2010-04-28 15:31 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-04-28 15:31:45 UTC

Attachments (Terms of Use)
File: backtrace (11.62 KB, text/plain)
2010-04-28 14:58 UTC, Carl G.
no flags Details

Description Carl G. 2010-04-28 14:58:01 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evince /home/carl/Downloads/LearnPythonTheHardWay.pdf
comment: I'm on updates-testing, that might be something else too ? glib?
component: evince
executable: /usr/bin/evince
global_uuid: 7f4efaa4d5a4ca88bf06e6c8c6e4e9e91e1b5ff3
package: evince-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. Tried to open a PDF file
2. Evince failed to start
3. ABRT applet showed up

Comment 1 Carl G. 2010-04-28 14:58:06 UTC
Created attachment 409869 [details]
File: backtrace

Comment 2 Carl G. 2010-04-28 15:04:33 UTC
Turn out Evince doesn't start at all now (used to work with the latest update as far as i can remember).

When i try to start evince from a terminal :

** (evince:16292): WARNING **: Error creating last_settings file: Error opening file '/home/carl/.gnome2/evince/last_settings': No such file or directory

Could it be Bleachbit that deleted that file / folder ?

Comment 3 Marek Kašík 2010-04-28 15:31:45 UTC

*** This bug has been marked as a duplicate of bug 586343 ***

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