Bug 535790 – crash in Document Viewer: reading a pdf (produced ...

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 535790 - crash in Document Viewer: reading a pdf (produced ...


Summary:	crash in Document Viewer: reading a pdf (produced ...


Status:	RESOLVED DUPLICATE of bug 316907

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-05-30 15:49 UTC by kiyowmasui
Modified:	2008-05-31 00:30 UTC

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

Description kiyowmasui 2008-05-30 15:49:53 UTC

Version: 2.20.2

What were you doing when the application crashed?
reading a pdf (produced in LaTeX) and randomnly highlighting text.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: Mist

Memory status: size: 132141056 vsize: 132141056 resident: 108814336 share: 14352384 rss: 108814336 rss_rlim: 4294967295
CPU usage: start_time: 1212159185 rtime: 5780 utime: 5301 stime: 479 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 "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b0c940 (LWP 27706)]
[New Thread 0xb6960b90 (LWP 27707)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199199

Thread 1 (Thread 0xb6b0c940 (LWP 27706))

#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 TextLine::visitSelection
from /usr/lib/libpoppler.so.2
#7 TextBlock::visitSelection
from /usr/lib/libpoppler.so.2
#8 TextPage::visitSelection
from /usr/lib/libpoppler.so.2
#9 TextPage::getSelectionRegion
from /usr/lib/libpoppler.so.2
#10 TextOutputDev::getSelectionRegion
from /usr/lib/libpoppler.so.2
#11 poppler_page_get_selection_region
from /usr/lib/libpoppler-glib.so.2
#12 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#0 __kernel_vsyscall



----------- .xsession-errors (3335 sec old) ---------------------
Error (5939956): Unknown operator 'D77'
Error (5939956): Unknown operator 'o0c3'
Error (5939956): Unknown operator 'mQo'
Error (5939956): Unknown operator 'DomIc3'
Error (5939958): Unknown operator 'D3'
Error (5939958): Too few (0) args to 'm' operator
Error (5939959): Unknown operator 'Q.mQo'
Error (5939959): Unknown operator 'Qo..Q35..Q3553.'
Error (5939959): Unknown operator 'D77'
Error (5939959): Unknown operator 'o0c3'
Error (5939959): Unknown operator 'mQo'
Error (5939965): Unknown operator 'DomIc3'
Error (5939968): Unknown operator 'Qo..Q3553.'
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-05-31 00:30:02 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 316907 ***