Bug 547072 – crash in Document Viewer: opening a document from ...

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 547072 - crash in Document Viewer: opening a document from ...


Summary:	crash in Document Viewer: opening a document from ...


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-09 14:14 UTC by dgallmeier
Modified:	2008-08-09 20:38 UTC

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

Description dgallmeier 2008-08-09 14:14:45 UTC

Version: 2.22.2

What were you doing when the application crashed?
opening a document from octopart.com


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: 55316480 vsize: 55316480 resident: 33071104 share: 12926976 rss: 33071104 rss_rlim: 4294967295
CPU usage: start_time: 1218291258 rtime: 42 utime: 33 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 0xb6bca720 (LWP 8708)]
[New Thread 0xb6a4eb90 (LWP 8709)]
(no debugging symbols found)
0xb7fad424 in __kernel_vsyscall ()

+ Trace 204904

Thread 2 (Thread 0xb6a4eb90 (LWP 8709))

#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.
evince: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
Multiple segmentation faults occurred; can't display error dialog
** 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 0x3400003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Baptiste Mille-Mathias 2008-08-09 20:38:15 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 ***