Bug 378532 – crash in Document Viewer: Mirar un PDF

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 378532 - crash in Document Viewer: Mirar un PDF


Summary:	crash in Document Viewer: Mirar un PDF


Status:	RESOLVED DUPLICATE of bug 316907

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-11-23 16:28 UTC by engripo
Modified:	2006-11-23 16:39 UTC

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

Description engripo 2006-11-23 16:28:03 UTC

Version: 0.6.1

What were you doing when the application crashed?
Mirar un PDF


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

Memory status: size: 65015808 vsize: 0 resident: 65015808 share: 0 rss: 29499392 rss_rlim: 0
CPU usage: start_time: 1164299185 rtime: 0 utime: 105 stime: 0 cutime:98 cstime: 0 timeout: 7 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 -1230158160 (LWP 6094)]
[New Thread -1231758432 (LWP 6098)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88810

Thread 1 (Thread -1230158160 (LWP 6094))

#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 ??
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#0 __kernel_vsyscall

Comment 1 Carlos Garcia Campos 2006-11-23 16:39:10 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 ***