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


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 535143

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-08-06 16:22 UTC by ryanktr
Modified:	2008-09-17 00:31 UTC

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

Description ryanktr 2008-08-06 16:22:01 UTC

Version: 2.22.2

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 48381952 vsize: 48381952 resident: 26198016 share: 12865536 rss: 26198016 rss_rlim: 4294967295
CPU usage: start_time: 1218039682 rtime: 43 utime: 33 stime: 10 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 0xb6bd0700 (LWP 487)]
[New Thread 0xb6a15b90 (LWP 488)]
(no debugging symbols found)
0xb7fb6424 in __kernel_vsyscall ()

+ Trace 204728

Thread 2 (Thread 0xb6a15b90 (LWP 488))

#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 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 poppler_page_render
from /usr/lib/libpoppler-glib.so.3
#14 ??
from /usr/lib/evince/backends/libpdfdocument.so
#15 ev_document_render
from /usr/lib/libevbackend.so.0
#16 ??
#17 ??
#18 ??
#19 ??
#20 g_once_init_leave
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
#23 ??
#24 ??
#25 g_queue_pop_head
from /usr/lib/libglib-2.0.so.0
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
from /usr/lib/libglib-2.0.so.0
#31 ??
#32 ??
from /usr/lib/libglib-2.0.so.0
#33 ??
#34 ??
from /usr/lib/libglib-2.0.so.0
#35 ??



----------- .xsession-errors ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
XtUngrabButton(drawArea,3,0)
Warning: Attempt to remove nonexistent passive grab
** 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)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Sergio Infante Montero 2008-08-10 23:32:47 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Cosimo Cecchi 2008-09-17 00:31:05 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 535143 ***