Bug 586615
| Summary: | [abrt] crash in evince-2.30.1-1.fc13: Process /usr/bin/evince was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Petr Bohac <bohacpetr> | ||||||
| Component: | evince | Assignee: | Marek Kašík <mkasik> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 13 | CC: | mkasik | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:4436f397b3422d18d824700f789e4bf604ee01cc | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-04-28 15:31:14 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Petr Bohac
2010-04-28 00:52:55 UTC
Created attachment 409635 [details]
File: backtrace
Created attachment 409637 [details]
PDF file causing SEGV
Found where was the problem. Directory "~/.gnome2/evince" was missing. Don't how I previously managed to open some other PDF (maybe from console as another user). Manually creating the directory will fix this issue. Attached PDF has no relevance to this, so can be removed. When i tried to open evince from console I get this warning message: ** (evince:3773): WARNING **: Error creating last_settings file: Chyba při otevírání souboru "/home/bohyn/.gnome2/evince/last_settings": Adresář nebo soubor neexistuje In English something like: Error when opening file "/home/bohyn/.gnome2/evince/last_settings": File or directory does not exists *** This bug has been marked as a duplicate of bug 586343 *** |