Bug 325074 – Crashes when double clicking on text box

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 325074 - Crashes when double clicking on text box


Summary:	Crashes when double clicking on text box


Status:	RESOLVED FIXED

Product:	gnome-calculator
Classification:	Core
Component:	general
Version:	5.7.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Rich Burridge
QA Contact:	Rich Burridge

URL:
Whiteboard:

Duplicates:	325332 326146 326317 326591 335202 (view as bug list)
Depends on:
Blocks:

Reported:	2005-12-27 16:49 UTC by Crispin Flowerday (not receiving bugmail)
Modified:	2006-03-20 14:27 UTC

See Also:
GNOME target:	2.14.x
GNOME version:	2.11/2.12

Attachments
Fix for the problem. (363 bytes, text/plain) 2006-01-09 15:55 UTC, Rich Burridge	Details

Description Crispin Flowerday (not receiving bugmail) 2005-12-27 16:49:00 UTC

If I load up gcalctool (5.7.18, ubuntu dapper), and double click the 0 in the text box, it crashes with:

Gtk-ERROR **: file gtktextview.c: line 5685 (gtk_text_view_start_selection_drag): assertion failed: (text_view->selection_drag_handler == 0)
aborting...

+ Trace 64831

#0 IA__g_logv
#1 IA__g_log
at gmessages.c line 517
#2 IA__g_assert_warning
at gmessages.c line 552
#3 gtk_text_view_start_selection_drag
at gtktextview.c line 5685
#4 gtk_text_view_button_press_event
at gtktextview.c line 3993
#5 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#6 g_type_class_meta_marshal
at gclosure.c line 567
#7 IA__g_closure_invoke
at gclosure.c line 490
#8 signal_emit_unlocked_R
at gsignal.c line 2487
#9 IA__g_signal_emit_valist
at gsignal.c line 2218
#10 IA__g_signal_emit
at gsignal.c line 2252
#11 gtk_widget_event_internal
at gtkwidget.c line 3735
#12 IA__gtk_propagate_event
at gtkmain.c line 2175
#13 IA__gtk_main_do_event
at gtkmain.c line 1412
#14 gdk_event_dispatch
at gdkevents-x11.c line 2291
#15 IA__g_main_context_dispatch
at gmain.c line 1913
#16 g_main_context_iterate
at gmain.c line 2544
#17 IA__g_main_loop_run
at gmain.c line 2748
#18 IA__gtk_main
at gtkmain.c line 991

Comment 1 Christian Kirbach 2005-12-27 17:44:37 UTC

Confirming

+ Trace 64832

#2 <signal handler called>
#3 IA__g_logv
at gmessages.c line 503
#4 IA__g_log
at gmessages.c line 517
#5 IA__g_assert_warning
at gmessages.c line 552
#6 gtk_text_view_start_selection_drag
at gtktextview.c line 5685
#7 gtk_text_view_button_press_event
at gtktextview.c line 3993

Comment 2 Rich Burridge 2005-12-28 18:35:30 UTC

Yup, I see it too. Here's my stack trace:

Gtk-CRITICAL **: file gtktextview.c: line 5699: assertion `text_view->selection_ drag_handler == 0' failed
aborting...
t@1 (l@1) signal ABRT (Abort) in _lwp_kill at 0xcfd55805
0xcfd55805: _lwp_kill+0x0015:   jae      _lwp_kill+0x23 [ 0xcfd55813, .+0xe ]
Current function is start_tool
 3383       gtk_main();
(dbx) where
current thread: t@1
  [1] _lwp_kill(0x1, 0x6), at 0xcfd55805
  [2] pthread_kill(0x1, 0x6), at 0xcfd52477
  [3] raise(0x6), at 0xcfd1d3d3
  [4] abort(0x82b0788, 0x81903d0, 0xd0ef03e8, 0x8229338, 0xcf7f2000, 0x8045e7c),  at 0xcfd00e00
  [5] g_log(0xd0ed0bc0, 0x8, 0xd0ed1c90, 0xd0ed1c80, 0x1643, 0xd0ed1148), at 0xc fdf56c9
  [6] gtk_text_view_start_selection_drag(0x81903d0, 0x8046408, 0x82b0788), at 0x d0dd1f34
  [7] gtk_text_view_button_press_event(0x81903d0, 0x82b0788, 0x80d1628), at 0xd0 dcf0e1
  [8] _gtk_marshal_BOOLEAN__BOXED(0x80dce50, 0x8046640, 0x2, 0x80466fc, 0x804665 c, 0xd0dced1c), at 0xd0d2e697
  [9] g_type_class_meta_marshal(0x80dce50, 0x8046640, 0x2, 0x80466fc, 0x804665c,  0xb0), at 0xd0029fd4
  [10] g_closure_invoke(0x80dce50, 0x8046640, 0x2, 0x80466fc, 0x804665c), at 0xd 0029912
  [11] signal_emit_unlocked_R(0x80dc7a0, 0x0, 0x81903d0, 0x804687c, 0x80466fc), at 0xd003f028
  [12] g_signal_emit_valist(0x81903d0, 0x21, 0x0, 0x8046980), at 0xd003e226
  [13] g_signal_emit(0x81903d0, 0x21, 0x0, 0x82b0788, 0x80469a0), at 0xd003e560
  [14] gtk_widget_event(0x81903d0, 0x82b0788), at 0xd0e2fb90
  [15] gtk_propagate_event(0x81903d0, 0x82b0788), at 0xd0d2d2d7
  [16] gtk_main_do_event(0x82b0788, 0x0), at 0xd0d2c2af
  [17] gdk_event_dispatch(0x80d09a8, 0x0, 0x0), at 0xd0ba29a6
  [18] g_main_dispatch(0x80d09f0), at 0xcfdebe09
  [19] g_main_context_dispatch(0x80d09f0), at 0xcfded0ca
  [20] g_main_context_iterate(0x80d09f0, 0x1, 0x1, 0x80b3000), at 0xcfded5c3
  [21] g_main_loop_run(0x836a000), at 0xcfdedbcd
  [22] gtk_main(0x8046ea8, 0x8046d54, 0x80aa138, 0x80aa138, 0x8046d48, 0x8063ee5 ), at 0xd0d2bb54
=>[23] start_tool(), line 3383 in "gtk.c"
  [24] do_calctool(argc = 2, argv = 0x8046d98), line 1215 in "calctool.c"
  [25] main(argc = 2, argv = 0x8046d98), line 493 in "gtk.c"
(dbx)

Looks like I need to work out how to assign a default selection_drag_handler.
I'll investigate further when I return from vacation on 9th January 2006.

Comment 3 Rich Burridge 2005-12-30 00:28:51 UTC

Problem is with the return value in the mouse_button_cb() routine
in gtk.c. It should return FALSE not TRUE.

Comment 4 Olav Vitters 2005-12-30 22:41:18 UTC

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

Comment 5 Rich Burridge 2006-01-08 00:30:43 UTC

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

Comment 6 Rich Burridge 2006-01-09 15:55:12 UTC

Created attachment 57042 [details]
Fix for the problem.

Comment 7 Rich Burridge 2006-01-09 16:02:51 UTC

Change checked into CVS HEAD. Bumped the version number in
configure.in to 5.7.19.

Comment 8 Rich Burridge 2006-01-09 17:15:10 UTC

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

Comment 9 Rich Burridge 2006-01-11 19:41:52 UTC

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

Comment 10 Rich Burridge 2006-03-20 14:27:18 UTC

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