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


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 501673

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-07-02 11:09 UTC by Xabier Rodríguez Calvar
Modified:	2008-07-04 17:41 UTC

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

Description Xabier Rodríguez Calvar 2008-07-02 11:09:22 UTC

Version: 2.22.2

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.7 #1 SMP PREEMPT Tue Jun 17 11:11:32 CEST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: iFog-Sunset
Icon Theme: dlg-etiquette

Memory status: size: 355655680 vsize: 355655680 resident: 85901312 share: 14233600 rss: 85901312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214996459 rtime: 236 utime: 191 stime: 45 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f7bf8e5c780 (LWP 11983)]
[New Thread 0x41be4950 (LWP 11984)]
(no debugging symbols found)
0x00007f7bf28b3edf in waitpid () from /lib/libpthread.so.0

+ Trace 201898

Thread 1 (Thread 0x7f7bf8e5c780 (LWP 11983))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 TextLine::visitSelection
from /usr/lib/libpoppler.so.3
#6 TextBlock::visitSelection
from /usr/lib/libpoppler.so.3
#7 TextPage::visitSelection
from /usr/lib/libpoppler.so.3
#8 TextPage::getSelectionRegion
from /usr/lib/libpoppler.so.3
#9 poppler_page_get_selection_region
from /usr/lib/libpoppler-glib.so.3
#10 ??
from /usr/lib/evince/backends/libpdfdocument.so
#11 ??
#12 ??
#13 ??
#14 ??
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
#20 __libc_start_main
from /lib/libc.so.6
#21 ??
#22 ??
#23 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (2739 sec old) ---------------------
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
/dev/dsp: Device or resource busy
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2008-07-04 17:41:11 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 501673 ***