Bug 381697 – 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 381697 - crash in Document Viewer:


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 362110

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-02 21:09 UTC by peiffereric
Modified:	2006-12-02 21:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description peiffereric 2006-12-02 21:09:34 UTC

Version: 0.6.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 72392704 vsize: 0 resident: 72392704 share: 0 rss: 39890944 rss_rlim: 0
CPU usage: start_time: 1165084421 rtime: 0 utime: 14993 stime: 0 cutime:14548 cstime: 0 timeout: 445 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229850960 (LWP 5666)]
[New Thread -1231500384 (LWP 5668)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 91134

Thread 1 (Thread -1229850960 (LWP 5666))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 poppler_page_render_selection
from /usr/lib/libpoppler-glib.so.1
#5 pdf_selection_render_selection
#6 _egg_marshal_VOID__INT_INT
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
#0 __kernel_vsyscall

Comment 1 Susana 2006-12-02 21:14:16 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 362110 ***