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


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 555375

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:	2009-03-06 18:13 UTC by paulbarbee
Modified:	2009-03-06 18:51 UTC

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

Description paulbarbee 2009-03-06 18:13:19 UTC

Version: 2.22.2

What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 258580480 vsize: 258580480 resident: 26865664 share: 14536704 rss: 26865664 rss_rlim: 18446744073709551615
CPU usage: start_time: 1236363124 rtime: 49 utime: 40 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f978f3f17d0 (LWP 9881)]
[New Thread 0x4221a950 (LWP 9882)]
(no debugging symbols found)
0x00007f9789bf9384 in __lll_lock_wait () from /lib/libpthread.so.0

+ Trace 213227

Thread 2 (Thread 0x4221a950 (LWP 9882))

#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 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 Form::findWidgetByRef
from /usr/lib/libpoppler.so.3
#7 AnnotWidget::initialize
from /usr/lib/libpoppler.so.3
#8 AnnotWidget::AnnotWidget
from /usr/lib/libpoppler.so.3
#9 Annots::createAnnot
from /usr/lib/libpoppler.so.3
#10 Annots::Annots
from /usr/lib/libpoppler.so.3
#11 Page::displaySlice
from /usr/lib/libpoppler.so.3
#12 ??
from /usr/lib/libpoppler-glib.so.3
#13 ??
from /usr/lib/evince/backends/libpdfdocument.so
#14 ??
#15 ??
#16 ??
#17 ??
from /usr/lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6
#20 ??



----------- .xsession-errors (13 sec old) ---------------------
!!! [MLProbe] handleDocument(about:blank): '[JavaScript Error: "node is null" {file: "file:///home/paul/.mozilla/firefox/wndcffs7.default/extensions/%7Bb9db16a4-6edc-47ec-a1f4-b86292ed211d%7D/componen
!!! [MLProbe] handleDocument(about:blank): '[JavaScript Error: "node is null" {file: "file:///home/paul/.mozilla/firefox/wndcffs7.default/extensions/%7Bb9db16a4-6edc-47ec-a1f4-b86292ed211d%7D/componen
!!! [MLProbe] handleDocument(about:blank): '[JavaScript Error: "node is null" {file: "file:///home/paul/.mozilla/firefox/wndcffs7.default/extensions/%7Bb9db16a4-6edc-47ec-a1f4-b86292ed211d%7D/componen
!!! [MLProbe] handleDocument(about:blank): '[JavaScript Error: "node is null" {file: "file:///home/paul/.mozilla/firefox/wndcffs7.default/extensions/%7Bb9db16a4-6edc-47ec-a1f4-b86292ed211d%7D/componen
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
kbuildsycoca running...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-03-06 18:51:48 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.


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