Bug 639611 – crash in Document Viewer: scrolling past page 5

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 639611 - crash in Document Viewer: scrolling past page 5


Summary:	crash in Document Viewer: scrolling past page 5


Status:	RESOLVED DUPLICATE of bug 565758

Product:	evince
Classification:	Core
Component:	BugBuddyBugs
Version:	2.30.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-01-15 17:20 UTC by phil
Modified:	2011-01-15 18:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description phil 2011-01-15 17:20:58 UTC

Version: 2.30.3

What were you doing when the application crashed?
scrolling past page 5


Distribution: Debian 6.0
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.37-opteron-dirty #30 SMP Thu Jan 6 17:39:14 GMT 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10900902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Human
Icon Theme: gnome-human
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 1966014464 vsize: 1966014464 resident: 66301952 share: 14401536 rss: 66301952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1295106515 rtime: 266 utime: 172 stime: 94 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xef85cb70 (LWP 17136)]
[New Thread 0xf14e2b70 (LWP 11254)]
0xf771f425 in __kernel_vsyscall ()

+ Trace 225542

Thread 3 (Thread 0xf14e2b70 (LWP 11254))

#0 __kernel_vsyscall
#1 waitpid
at ../sysdeps/unix/syscall-template.S line 82
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 FcConfigSubstituteWithPat
from /usr/lib/libfontconfig.so.1
#7 FcConfigSubstitute
from /usr/lib/libfontconfig.so.1
#8 GlobalParams::getDisplayFont
at GlobalParams.cc line 1135
#9 CairoFreeTypeFont::create
at CairoFontEngine.cc line 421
#10 CairoFontEngine::getFont
at CairoFontEngine.cc line 769
#11 CairoOutputDev::updateFont
at CairoOutputDev.cc line 551
#12 Gfx::opShowText
at Gfx.cc line 3425
#13 Gfx::execOp
at Gfx.cc line 794
#14 Gfx::go
at Gfx.cc line 665
#15 Gfx::display
at Gfx.cc line 634
#16 Page::displaySlice
at Page.cc line 474
#17 _poppler_page_render
at poppler-page.cc line 560
#18 ??
from /usr/lib/evince/2/backends/libpdfdocument.so
#19 ev_document_render
from /usr/lib/libevdocument.so.2
#20 ??
from /usr/lib/libevview.so.2
#21 ev_job_run
from /usr/lib/libevview.so.2
#22 ??
from /usr/lib/libevview.so.2
#23 ??
from /lib/libglib-2.0.so.0
#24 start_thread
at pthread_create.c line 300
#25 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

A debugging session is active.

	Inferior 1 [process 11250] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (1115 sec old) ---------------------
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
(<unknown>:7239): Gdk-WARNING **: XID collision, trouble ahead
--------------------------------------------------

Comment 1 Akhil Laddha 2011-01-15 18:48:54 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 bug 565758 ***