Bug 464921 – crash in Document Viewer: Attempting to view a hom...

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 464921 - crash in Document Viewer: Attempting to view a hom...


Summary:	crash in Document Viewer: Attempting to view a hom...


Status:	RESOLVED INCOMPLETE

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-08-09 04:12 UTC by kevin
Modified:	2007-08-09 16:28 UTC

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

Description kevin 2007-08-09 04:12:38 UTC

Version: 0.8.3

What were you doing when the application crashed?
Attempting to view a homebrew catalog, running Pidgin and had a Gnome-terminal open. Running Gnome on a 2.6.21-vserver-amd64 kernel on an Intel Core 2 Duo.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-vserver-amd64 #1 SMP Sun Jul 29 14:31:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 263786496 vsize: 263786496 resident: 43540480 share: 13631488 rss: 43540480 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186632713 rtime: 213 utime: 204 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47642100720976 (LWP 11586)]
[New Thread 1082132816 (LWP 11587)]
0x00002b54879b3be6 in poll () from /lib/libc.so.6

+ Trace 153883

Thread 2 (Thread 1082132816 (LWP 11587))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 __assert_fail
from /lib/libc.so.6
#6 ??
from /usr/lib/libcairo.so.2
#7 ??
from /usr/lib/libcairo.so.2
#8 ??
from /usr/lib/libcairo.so.2
#9 ??
from /usr/lib/libcairo.so.2
#10 ??
from /usr/lib/libcairo.so.2
#11 ??
from /usr/lib/libcairo.so.2
#12 ??
from /usr/lib/libcairo.so.2
#13 ??
from /usr/lib/libcairo.so.2
#14 ??
from /usr/lib/libcairo.so.2
#15 cairo_stroke_preserve
from /usr/lib/libcairo.so.2
#16 cairo_stroke
from /usr/lib/libcairo.so.2
#17 Gfx::opStroke
from /usr/lib/libpoppler.so.1
#18 Gfx::go
from /usr/lib/libpoppler.so.1
#19 Gfx::display
from /usr/lib/libpoppler.so.1
#20 Page::displaySlice
from /usr/lib/libpoppler.so.1
#21 poppler_page_render_to_pixbuf
from /usr/lib/libpoppler-glib.so.1
#22 pdf_document_thumbnails_get_thumbnail
at ev-poppler.cc line 1195
#23 ev_job_thumbnail_run
at ev-jobs.c line 382
#24 handle_job
at ev-job-queue.c line 96
#25 ev_render_thread
at ev-job-queue.c line 187
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 start_thread
from /lib/libpthread.so.0
#28 clone
from /lib/libc.so.6
#29 ??



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
evince: /build/buildd/libcairo-1.4.10/src/cairo-pen.c:324: _cairo_pen_find_active_cw_vertex_index: Assertion `i < pen->num_vertices' failed.
--------------------------------------------------

Comment 1 palfrey 2007-08-09 16:28:50 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!