Hide Forgot
abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: evince /home/john/Documents/Training/RHCX/setup-instructions-RHEL6.pdf comment: I did get evince to open the pdf w/o crashing by running evince on the command line and passing the pdf in component: evince crash_function: g_atomic_int_exchange_and_add executable: /usr/bin/evince kernel: 2.6.35.10-74.fc14.x86_64 package: evince-2.32.0-3.fc14 rating: 4 reason: Process /usr/bin/evince was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1295535731 uid: 500 How to reproduce ----- 1. opening a PDF from nautilus 2. 3.
Created attachment 474473 [details] File: backtrace
It seems this bug is related to a hanging NFS mount which is a result of an autofs mount I have [root@laptop ~]# ps ax | grep \ D 12579 ? D 0:00 /sbin/mount.nfs 192.168.2.17:/efserv /efserv -s -o rw,intr 12583 pts/2 S+ 0:00 grep --color=auto D [root@laptop ~]# kill 12579 [root@laptop ~]# Often when I download files in firefox it will hang and I will find this same mount hung and killing it fixes the issue. Somtimes when I open PDFs from nautilus autofs will try to mount this directory and it will hang and cause evince to hang. As soon as I kill the state D mount evince pops up.
Package: evince-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Was viewing a PDF doc generated by LyX. After updating in LyX, evince froze and showed blank white pages. I tried closing the window, and a couple of seconds later Evince crashed.
Re. comment 2: I'm not using NFS, but experienced the same crash.
Package: evince-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Opened one PDF doc while printing another one. Comment ----- Not sure if this is reproducible or not.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping