Bug 344800 – Crash when selecting text

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 344800 - Crash when selecting text


Summary:	Crash when selecting text


Status:	RESOLVED DUPLICATE of bug 351671

Product:	gtk+
Classification:	Platform
Component:	Widget: GtkTextView
Version:	2.8.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-06-13 18:38 UTC by Kevin Kubasik
Modified:	2007-06-07 03:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Kevin Kubasik 2006-06-13 18:38:23 UTC

I was selecting a method when:

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225639712 (LWP 29713)]
[New Thread -1291965520 (LWP 3676)]
[New Thread -1282122832 (LWP 29716)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 68822

Thread 1 (Thread -1225639712 (LWP 29713))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gtk_text_view_start_selection_drag
at gtktextview.c line 5670
#11 gtk_text_view_button_press_event
at gtktextview.c line 3996
#12 gtk_source_view_get_marker_pixbuf
from /usr/lib/libgtksourceview-1.0.so.0
#13 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#14 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_widget_event_internal
at gtkwidget.c line 3751
#20 IA__gtk_propagate_event
at gtkmain.c line 2218
#21 IA__gtk_main_do_event
at gtkmain.c line 1447
#22 gdk_event_dispatch
at gdkevents-x11.c line 2291
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 IA__gtk_main
at gtkmain.c line 1026
#27 main
at gedit.c line 570
#0 __kernel_vsyscall

Comment 1 Steve Frécinaux 2006-06-13 19:11:05 UTC

well it looks like a gtk bug to me... was there any output in terminal ?

Can you reproduce it within gedit ? and using gtk-demo ?

Comment 2 Kevin Kubasik 2006-06-15 02:09:43 UTC

I have been unable to reliably reproduce it, although it happened once again with the same back trace. I can move this to gtk+ if its more appropriate.

Comment 3 Sitsofe Wheeler 2007-04-13 19:17:33 UTC

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

Comment 4 Yevgen Muntyan 2007-06-07 03:46:00 UTC


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