Bug 581619 – crash in Document Viewer:

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 581619 - crash in Document Viewer:


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 542574

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:	2009-05-06 17:18 UTC by reno.a
Modified:	2009-05-06 19:52 UTC

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

Description reno.a 2009-05-06 17:18:33 UTC

Version: 2.22.2

What were you doing when the application crashed?



Distribution: Debian 5.0.1
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 53579776 vsize: 53579776 resident: 31690752 share: 12247040 rss: 31690752 rss_rlim: 4294967295
CPU usage: start_time: 1241630301 rtime: 77 utime: 70 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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ad8700 (LWP 12765)]
[New Thread 0xb690ab90 (LWP 12766)]
(no debugging symbols found)
0xb7f7b424 in __kernel_vsyscall ()

+ Trace 215183

Thread 2 (Thread 0xb690ab90 (LWP 12766))

#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 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 TextPage::beginWord
from /usr/lib/libpoppler.so.3
#8 TextPage::addChar
from /usr/lib/libpoppler.so.3
#9 TextOutputDev::endMarkedContent
from /usr/lib/libpoppler.so.3
#10 Gfx::opEndMarkedContent
from /usr/lib/libpoppler.so.3
#11 Gfx::execOp
from /usr/lib/libpoppler.so.3
#12 Gfx::go
from /usr/lib/libpoppler.so.3
#13 Gfx::display
from /usr/lib/libpoppler.so.3
#14 Page::display
from /usr/lib/libpoppler.so.3
#15 ??
from /usr/lib/libpoppler-glib.so.3
#16 poppler_page_get_selection_region
from /usr/lib/libpoppler-glib.so.3
#17 ??
from /usr/lib/evince/backends/libpdfdocument.so
#18 ev_selection_get_selection_map
from /usr/lib/libevbackend.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 gtk_action_set_sensitive
#24 ??
#25 ??
#26 ??



----------- .xsession-errors ---------------------
#5 /usr/lib/libgdk-x11-2.0.so.0(gdk_flush+0x35) [0xb76468f5]
#6 /usr/lib/gtk-2.0/modules/libgnomebreakpad.so [0xb69504bb]
#7 [0xb7f7b400]
#8 /usr/lib/libpoppler.so.3(_ZN8TextPage7addCharEP8GfxStateddddjiPji+0x78e) [0xb6f37a1e]
#9 /usr/lib/libpoppler.so.3(_ZN13TextOutputDev16endMarkedContentEP8GfxState+0x139) [0xb6f37b89]
#10 /usr/lib/libpoppler.so.3(_ZN3Gfx18opEndMarkedContentEP6Objecti+0x25) [0xb6eb9515]
#11 /usr/lib/libpoppler.so.3(_ZN3Gfx6execOpEP6ObjectS1_i+0x132) [0xb6ebaef2]
#12 /usr/lib/libpoppler.so.3(_ZN3Gfx2goEi+0x19f) [0xb6ebb14f]
#13 /usr/lib/libpoppler.so.3(_ZN3Gfx7displayEP6Objecti+0x9f) [0xb6ebe2af]
#14 /usr/lib/libpoppler.so.3(_ZN4Page7displayEP3Gfx+0x68) [0xb6f06b48]
#15 /usr/lib/libpoppler-glib.so.3 [0xb769c02f]
#16 /usr/lib/libpoppler-glib.so.3(poppler_page_get_selection_region+0x64) [0xb769c0c4]
#17 /usr/lib/evince/backends/libpdfdocument.so [0xb5f19dc7]
#18 /usr/lib/libevbackend.so.0(ev_selection_get_selection_map+0x42) [0xb7f640e2]
#19 evince [0x80616af]
--------------------------------------------------

Comment 1 Nickolay V. Shmyrev 2009-05-06 19:52:25 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 542574 ***