Bug 398946 – Crash when selecting text in a PDF file

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 398946 - Crash when selecting text in a PDF file


Summary:	Crash when selecting text in a PDF file


Status:	RESOLVED DUPLICATE of bug 350108

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:	2007-01-21 06:28 UTC by shenyibin
Modified:	2007-01-21 11:19 UTC

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

Description shenyibin 2007-01-21 06:28:44 UTC

Version: 0.6.1

What were you doing when the application crashed?
open a PDF file


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

Memory status: size: 95408128 vsize: 0 resident: 95408128 share: 0 rss: 33710080 rss_rlim: 0
CPU usage: start_time: 1169360876 rtime: 0 utime: 178 stime: 0 cutime:173 cstime: 0 timeout: 5 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 -1230022992 (LWP 6937)]
[New Thread -1231467616 (LWP 6939)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103952

Thread 1 (Thread -1230022992 (LWP 6937))

#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 Francesco Mari 2007-01-21 11:19:41 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 350108 ***