Bug 549847 – crash in Document Viewer: opening it

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 549847 - crash in Document Viewer: opening it


Summary:	crash in Document Viewer: opening it


Status:	RESOLVED DUPLICATE of bug 415714

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-08-29 17:42 UTC by evert
Modified:	2008-09-20 17:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description evert 2008-08-29 17:42:41 UTC

Version: 2.22.2

What were you doing when the application crashed?
opening it


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Wed May 14 16:42:03 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 58322944 vsize: 58322944 resident: 36208640 share: 12357632 rss: 36208640 rss_rlim: 4294967295
CPU usage: start_time: 1220031510 rtime: 72 utime: 64 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b66700 (LWP 4088)]
[New Thread 0xb69e4b90 (LWP 4089)]
(no debugging symbols found)
0xb7f61424 in __kernel_vsyscall ()

+ Trace 205860

Thread 1 (Thread 0xb6b66700 (LWP 4088))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 Catalog::embeddedFile
from /usr/lib/libpoppler.so.3
#7 poppler_document_get_attachments
from /usr/lib/libpoppler-glib.so.3
#8 ??
from /usr/lib/evince/backends/libpdfdocument.so
#9 ev_document_get_attachments
from /usr/lib/libevbackend.so.0
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Error (69659195): Illegal character <2f> in hex string
Error (69659196): Illegal character <54> in hex string
Error (69659197): Illegal character <79> in hex string
Error (69659198): Illegal character <70> in hex string
Error (69659200): Illegal character <2f> in hex string
Error (69659202): Illegal character <6e> in hex string
Error (69659204): Illegal character <6f> in hex string
Error (69659206): Illegal character <69> in hex string
Error (69659207): Illegal character <6e> in hex string
Error (69659208): Illegal character <67> in hex string
Error (69659211): Illegal character '>'
Error: End of file inside array
Error: End of file inside array
Error: End of file inside array
Error: End of file inside dictionary
--------------------------------------------------

Comment 1 Sergio Infante Montero 2008-09-01 07:03:26 UTC

Probably the bug is in libpoppler

+ Trace 205972

Thread 2 (Thread 0xb69e4b90 (LWP 4089))

#0 GfxImageColorMap::getRGBLine
from /usr/lib/libpoppler.so.3
#1 CairoOutputDev::drawImage
from /usr/lib/libpoppler-glib.so.3
#2 Gfx::doImage
from /usr/lib/libpoppler.so.3
#3 Gfx::opXObject
from /usr/lib/libpoppler.so.3
#4 Gfx::execOp
from /usr/lib/libpoppler.so.3
#5 Gfx::go
from /usr/lib/libpoppler.so.3
#6 Gfx::display
from /usr/lib/libpoppler.so.3
#7 Page::displaySlice
from /usr/lib/libpoppler.so.3
#8 ??
from /usr/lib/libpoppler-glib.so.3
#9 poppler_page_render
from /usr/lib/libpoppler-glib.so.3

Comment 2 Cosimo Cecchi 2008-09-20 17:43: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 ***