Bug 366871 – 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 366871 - 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-10-29 13:54 UTC by matthieupeyre
Modified:	2006-10-29 16:01 UTC

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

Description matthieupeyre 2006-10-29 13:54:30 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: 72937472 vsize: 0 resident: 72937472 share: 0 rss: 40132608 rss_rlim: 0
CPU usage: start_time: 1162130040 rtime: 0 utime: 939 stime: 0 cutime:913 cstime: 0 timeout: 26 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 -1229572432 (LWP 16682)]
[New Thread -1231246432 (LWP 16684)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79757

Thread 1 (Thread -1229572432 (LWP 16682))

#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 André Klapper 2006-10-29 16:01:55 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 362110 ***