Bug 443710 – crash in Document Viewer: i was openning PDF file

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 443710 - crash in Document Viewer: i was openning PDF file


Summary:	crash in Document Viewer: i was openning PDF file


Status:	RESOLVED DUPLICATE of bug 415714

Product:	evince
Classification:	Core
Component:	general
Version:	0.8.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evince Maintainers
QA Contact:	Evince Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-03 21:01 UTC by adam.vasicek
Modified:	2007-06-04 00:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description adam.vasicek 2007-06-03 21:01:35 UTC

Version: 0.8.0

What were you doing when the application crashed?
i was openning PDF file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 91910144 vsize: 91910144 resident: 18481152 share: 12636160 rss: 18481152 rss_rlim: 4294967295
CPU usage: start_time: 1180904332 rtime: 83 utime: 76 stime: 7 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209133344 (LWP 3177)]
[New Thread -1211565168 (LWP 3178)]
(no debugging symbols found)
0x00654402 in __kernel_vsyscall ()

+ Trace 137937

Thread 1 (Thread -1209133344 (LWP 3177))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 Catalog::embeddedFile
from /usr/lib/libpoppler.so.1
#5 poppler_document_get_attachments
from /usr/lib/libpoppler-glib.so.1
#6 ??
#7 ev_document_get_attachments
#8 ??
#9 ev_sidebar_set_document
#10 ??
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ev_job_finished
#17 ??
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_loop_run
from /lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Error (843): Missing or bad Type3 CharProc entry
Error (843): Missing or bad Type3 CharProc entry
Error (843): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error (853): Missing or bad Type3 CharProc entry
Error: Missing or bad Type3 CharProc entry
Error: Missing or bad Type3 CharProc entry
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-06-04 00:00:57 UTC

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 ***