Bug 358648 – crash in Document Viewer: Typing a / when reading ...

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 358648 - crash in Document Viewer: Typing a / when reading ...


Summary:	crash in Document Viewer: Typing a / when reading ...


Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:

Duplicates:	375529 378088 385041 433790 437107 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-30 23:34 UTC by Wouter Bolsterlee (uws)
Modified:	2007-05-09 10:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Wouter Bolsterlee (uws) 2006-09-30 23:34:41 UTC

Version: 0.6.0

What were you doing when the application crashed?
Typing a / when reading a gunzip'ped copy of http://www.gnu.org/software/auctex/preview-manual/preview-latex.dvi.gz


Distribution: Debian testing/unstable
Gnome Release: 2.16.0 2006-09-07 (JHBuild)
BugBuddy Version: 2.16.0

Memory status: size: 55320576 vsize: 0 resident: 55320576 share: 0 rss: 30449664 rss_rlim: 0
CPU usage: start_time: 1159659200 rtime: 0 utime: 384 stime: 0 cutime:311 cstime: 0 timeout: 73 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome-2-16/bin/evince'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231468864 (LWP 17786)]
[New Thread -1233691728 (LWP 17787)]
0xb720e201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 73823

Thread 1 (Thread -1231468864 (LWP 17786))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 870
#2 <signal handler called>
#3 raise
from /lib/tls/libc.so.6
#4 abort
from /lib/tls/libc.so.6
#5 IA__g_logv
at gmessages.c line 497
#6 IA__g_log
at gmessages.c line 517
#7 ev_window_cmd_edit_find
at ev-window.c line 1889
#8 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#9 IA__g_closure_invoke
at gclosure.c line 490
#10 signal_emit_unlocked_R
at gsignal.c line 2438
#11 IA__g_signal_emit_valist
at gsignal.c line 2197
#12 IA__g_signal_emit
at gsignal.c line 2241
#13 _gtk_action_emit_activate
at gtkaction.c line 835
#14 closure_accel_activate
at gtkaction.c line 1602
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2438
#17 IA__g_signal_emit_valist
at gsignal.c line 2207
#18 IA__g_signal_emit
at gsignal.c line 2241
#19 IA__gtk_accel_group_activate
at gtkaccelgroup.c line 736
#20 IA__gtk_accel_groups_activate
at gtkaccelgroup.c line 774
#21 IA__gtk_window_activate_key
at gtkwindow.c line 7704
#22 gtk_window_key_press_event
at gtkwindow.c line 4697
#23 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#24 g_type_class_meta_marshal
at gclosure.c line 567
#25 IA__g_closure_invoke
at gclosure.c line 490
#26 signal_emit_unlocked_R
at gsignal.c line 2476
#27 IA__g_signal_emit_valist
at gsignal.c line 2207
#28 IA__g_signal_emit
at gsignal.c line 2241
#29 gtk_widget_event_internal
at gtkwidget.c line 3911
#30 IA__gtk_propagate_event
at gtkmain.c line 2162
#31 IA__gtk_main_do_event
at gtkmain.c line 1422
#32 gdk_event_dispatch
at gdkevents-x11.c line 2320
#33 IA__g_main_context_dispatch
at gmain.c line 2045
#34 g_main_context_iterate
at gmain.c line 2677
#35 IA__g_main_loop_run
at gmain.c line 2881
#36 IA__gtk_main
at gtkmain.c line 1001
#37 main
at main.c line 345
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0

Comment 1 Nickolay V. Shmyrev 2006-10-01 09:15:00 UTC

Nice catch, bug is fixed now, thanks.

Comment 2 Nickolay V. Shmyrev 2006-12-13 10:00:36 UTC

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

Comment 3 Nickolay V. Shmyrev 2006-12-13 10:01:22 UTC

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

Comment 4 Nickolay V. Shmyrev 2006-12-24 15:15:19 UTC

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

Comment 5 palfrey 2007-04-27 10:27:20 UTC

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

Comment 6 palfrey 2007-05-09 10:57:05 UTC

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