Bug 376918 – Gedit crashes when marking end of file by mouse

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 376918 - Gedit crashes when marking end of file by mouse


Summary:	Gedit crashes when marking end of file by mouse


Status:	RESOLVED DUPLICATE of bug 355701

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.14.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

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

Reported:	2006-11-19 09:32 UTC by bugzilla.gnome.org
Modified:	2007-04-07 21:44 UTC

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

Description bugzilla.gnome.org 2006-11-19 09:31:23 UTC

Distribution: Debian testing/unstable
Package: gedit
Severity: Normal
Version: GNOME2.14.3 2.14.x
Gnome-Distributor: Debian
Synopsis: Gedit crashes when marking end of file by mouse
Bugzilla-Product: gedit
Bugzilla-Component: general
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Gedit crashes on certain mouse actions.

Steps to reproduce the crash:
Close to the bottom of a file (in this case UTF-8 formatted plain text,
code coloring for log files activated), left click on text, hold down,
move mouse pointer out of window, unclasp mouse button, move mouse
pointer back over text. Marked text will now extend and decrease based
on the mouse position. Move mouse to and below the very end of the file
- gedit crashes.
Gtk-ERROR **: file gtktextview.c: line 5668
(gtk_text_view_start_selection_drag): assertion failed:
(text_view->selection_drag_handler == 0)
aborting...

Expected Results:
No crash. :)

How often does this happen?
Reproducible.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1494042944 (LWP 11366)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87644

Thread 1 (Thread -1494042944 (LWP 11366))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_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_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#13 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_chain_from_overridden
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_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#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 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-11-19 09:32 -------

Comment 1 André Klapper 2006-11-19 14:59:08 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 355701 ***

Comment 2 palfrey 2007-04-07 21:44:15 UTC

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