Bug 629362 – crash in Document Viewer: nothing

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 629362 - crash in Document Viewer: nothing


Summary:	crash in Document Viewer: nothing


Status:	RESOLVED DUPLICATE of bug 594408

Product:	evince
Classification:	Core
Component:	BugBuddyBugs
Version:	2.30.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	629434 (view as bug list)
Depends on:
Blocks:

Reported:	2010-09-11 14:33 UTC by tmphyy
Modified:	2010-10-27 12:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description tmphyy 2010-09-11 14:33:08 UTC

Version: 2.30.3

What were you doing when the application crashed?
nothing


Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-07-17 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 113393664 vsize: 113393664 resident: 16814080 share: 11329536 rss: 16814080 rss_rlim: 18446744073709551615
CPU usage: start_time: 1284215529 rtime: 87 utime: 76 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb233ab70 (LWP 18463)]
[New Thread 0xb2b3bb70 (LWP 18462)]
0xb7741424 in __kernel_vsyscall ()

+ Trace 223654

Thread 1 (Thread 0xb67f1750 (LWP 18459))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 IA__g_assertion_message
#10 IA__g_assertion_message_expr
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gtestutils.c line 1329
#11 ev_document_misc_get_thumbnail_frame
at /build/buildd-evince_2.30.3-1-i386-YyrmzQ/evince-2.30.3/./libdocument/ev-document-misc.c line 58
#12 ??
#13 ??
#14 ??
#15 IA__g_cclosure_marshal_VOID__PARAM
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gmarshal.c line 531
#16 IA__g_closure_invoke
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gclosure.c line 767
#17 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 3248
#18 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 2981
#19 IA__g_signal_emit
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 3038
#20 g_object_dispatch_properties_changed
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gobject.c line 801
#21 g_object_notify_dispatcher
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gobject.c line 328
#22 g_object_notify_queue_thaw
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gobjectnotifyqueue.c line 120
#23 IA__g_object_notify
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gobject.c line 888
#24 ev_document_model_set_document
at /build/buildd-evince_2.30.3-1-i386-YyrmzQ/evince-2.30.3/./libview/ev-document-model.c line 306
#25 ??
#26 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gmarshal.c line 77
#27 IA__g_closure_invoke
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gclosure.c line 767
#28 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 3248
#29 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 2981
#30 IA__g_signal_emit
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/gobject/gsignal.c line 3038
#31 emit_finished
at /build/buildd-evince_2.30.3-1-i386-YyrmzQ/evince-2.30.3/./libview/ev-jobs.c line 175
#32 g_idle_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 4065
#33 g_main_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 1960
#34 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2513
#35 g_main_context_iterate
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2591
#36 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2799
#37 IA__gtk_main
at /build/buildd-gtk+2.0_2.20.1-1-i386-Ixfflh/gtk+2.0-2.20.1/gtk/gtkmain.c line 1219
#38 ??
#39 __libc_start_main
from /lib/i686/cmov/libc.so.6
#40 ??

A debugging session is active.

	Inferior 1 [process 18459] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (337541 sec old) ---------------------
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:2267): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2010-09-12 00:29:11 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Felipe Besoaín Pino 2010-09-13 00:07:26 UTC

*** Bug 629434 has been marked as a duplicate of this bug. ***

Comment 3 Akhil Laddha 2010-10-27 12:05:23 UTC


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