Bug 486241 – crash in Document Viewer: Tried opening a 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 486241 - crash in Document Viewer: Tried opening a PDF file...


Summary:	crash in Document Viewer: Tried opening a 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-10-13 06:02 UTC by rexlun
Modified:	2007-10-16 17:05 UTC

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

Description rexlun 2007-10-13 06:02:07 UTC

Version: 0.8.2

What were you doing when the application crashed?
Tried 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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Clearlooks

Memory status: size: 325300224 vsize: 325300224 resident: 42831872 share: 24416256 rss: 42831872 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192255201 rtime: 94 utime: 79 stime: 15 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 46912496419248 (LWP 2965)]
[New Thread 1084229968 (LWP 2966)]
(no debugging symbols found)
0x0000003550e0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 169899

Thread 1 (Thread 46912496419248 (LWP 2965))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__VOID
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 Catalog::embeddedFile
from /usr/lib64/libpoppler.so.1
#4 poppler_document_get_attachments
from /usr/lib64/libpoppler-glib.so.1
#5 ??
#6 ??
#7 ev_sidebar_set_document
#8 ??
#9 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#10 g_cclosure_marshal_VOID__VOID
from /lib64/libglib-2.0.so.0
#11 g_main_loop_run
from /lib64/libglib-2.0.so.0
#12 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#13 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (2885 sec old) ---------------------
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Carlos Garcia Campos 2007-10-16 17:05:48 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 ***