Bug 529185 – crash in Document Viewer: double clicked a line in...

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 529185 - crash in Document Viewer: double clicked a line in...


Summary:	crash in Document Viewer: double clicked a line in...


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-04-21 10:38 UTC by purvesh
Modified:	2008-04-21 12:02 UTC

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

Description purvesh 2008-04-21 10:38:51 UTC

Version: 2.20.2

What were you doing when the application crashed?
double clicked a line in the pdf document


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 84910080 vsize: 84910080 resident: 60334080 share: 12857344 rss: 60334080 rss_rlim: 4294967295
CPU usage: start_time: 1208770443 rtime: 3014 utime: 2640 stime: 374 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 0xb69a8aa0 (LWP 9268)]
[New Thread 0xb6825b90 (LWP 9269)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195758

Thread 1 (Thread 0xb69a8aa0 (LWP 9268))

#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 ---------------------
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
--------------------------------------------------

Comment 1 Gianluca Borello 2008-04-21 12:02:32 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 ***