Bug 701526 - [abrt] evince-2.32.0-4.fc14: initable_init: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
Summary: [abrt] evince-2.32.0-4.fc14: initable_init: Process /usr/bin/evince was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 657772
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:946f99a5dbf248c6566502513ac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-03 05:26 UTC by Andrew Gaul
Modified: 2011-05-30 10:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-30 10:34:26 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (12.88 KB, text/plain)
2011-05-03 05:26 UTC, Andrew Gaul 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Andrew Gaul 2011-05-03 05:26:03 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 13194 bytes
cmdline: evince Downloads/evolution_of_coda.pdf
component: evince
Attached file: coredump, 19079168 bytes
crash_function: initable_init
executable: /usr/bin/evince
kernel: 2.6.35.11-83.fc14.x86_64
package: evince-2.32.0-4.fc14
rating: 4
reason: Process /usr/bin/evince was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304400266
uid: 500

How to reproduce
-----
1. open screen session
2. log out
3. log in
4. open document in screen session
5. crash
Comment 1 Andrew Gaul 2011-05-03 05:26:05 UTC 
Created attachment 496428 [details]
File: backtrace
Comment 2 Andrew Gaul 2011-05-28 15:33:40 UTC 
Package: evince-3.0.0-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
1. launch screen
2. log out
3. log in
4. reattach screen
5. run evince
Comment 3 Marek Kašík 2011-05-30 10:34:26 UTC 

*** This bug has been marked as a duplicate of bug 657772 ***
Note You need to log in before you can comment on or make changes to this bug.