GNOME Bugzilla – Bug 494699
crash in Document Viewer: Opening a PDF file
Last modified: 2007-11-07 18:24:18 UTC
Version: 0.8.2 What were you doing when the application crashed? Opening a PDF file Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 365629440 vsize: 365629440 resident: 95535104 share: 16150528 rss: 95535104 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194458954 rtime: 71 utime: 55 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496366000 (LWP 15957)] [New Thread 1084229968 (LWP 15958)] (no debugging symbols found) 0x00000039c780d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 176115
Thread 1 (Thread 46912496366000 (LWP 15957))
----------- .xsession-errors (7 sec old) --------------------- JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] Error: End of file inside array Error: End of file inside dictionary --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 415714 ***