Bug 364329 – Crash 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 364329 - Crash selecting text


Summary:	Crash selecting text


Status:	RESOLVED DUPLICATE of bug 355701

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	371909 375346 381962 394186 394414 394856 395569 398350 402135 402778 403888 426452 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-23 02:56 UTC by amachu.techie
Modified:	2007-04-05 16:39 UTC

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

Description amachu.techie 2006-10-23 02:56:35 UTC

Version: 2.16.1

What were you doing when the application crashed?
Typing Text in Tamil. Selected a full line text and pressed "Home" key.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 48377856 vsize: 0 resident: 48377856 share: 0 rss: 22503424 rss_rlim: 0
CPU usage: start_time: 1161571802 rtime: 0 utime: 287 stime: 0 cutime:268 cstime: 0 timeout: 19 it_real_value: 0 frequency: 0

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 -1226897216 (LWP 4555)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 77792

Thread 1 (Thread -1226897216 (LWP 4555))

#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_char_segment_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 _gtk_char_segment_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_text_line_segment_split
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_text_mark_set_visible
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_text_btree_select_range
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_text_buffer_select_range
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_text_buffer_place_cursor
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_text_view_new_with_buffer
from /usr/lib/libgtk-x11-2.0.so.0
#18 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-10-29 11:33:03 UTC

Thanks for taking the time to report this bug.

It seems a crash in GtkTextView.

Are you able to reproduce it using other gtk+ based editors like for example Leafpad or in Tomboy?

Unfortunately, the stack trace you have attached 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. Thanks in advance!

Comment 2 Steve Frécinaux 2006-11-07 16:28:23 UTC

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

Comment 3 André Klapper 2006-11-15 02:28:52 UTC

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

Comment 4 Bruno Boaventura 2006-12-04 03:32:04 UTC

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

Comment 5 Paolo Maggi 2007-01-02 19:04:03 UTC

pbor: could this crash be related to the mem corruption bug you fixed in GtkTextView?

Comment 6 Susana 2007-01-08 14:16:10 UTC

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

Comment 7 Paolo Maggi 2007-01-10 09:55:15 UTC

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

Comment 8 Paolo Maggi 2007-01-10 10:33:35 UTC

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

Comment 9 Paolo Maggi 2007-01-10 10:36:11 UTC

This could be a duplicated of bug #355701.

Which version of gtk+ are you using?
Did you see messages on the terminal when gedit crashed?

Comment 10 Francesco Mari 2007-01-16 18:05:45 UTC

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

Comment 11 Susana 2007-01-19 14:01:17 UTC

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

Comment 12 Benoit Mortgat 2007-01-19 14:08:39 UTC

Hi,

I don't know how to reproduce that bug. If you want to know what I did:

1. Opened gedit
2. Selected SCIM as Input method (not SCIM Bridge but SCIM)
3. Selected Phonetic Tamil
4. Typed "singkapur" exactly (indeed that's no word in Tamil :)
5. Don't remember, maybe validate the last "r" with space, and then mouse or keybord, I don't remember...

Sorry

Comment 13 Bruno Boaventura 2007-01-30 01:07:29 UTC

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

Comment 14 Susana 2007-01-31 14:22:48 UTC

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

Comment 15 palfrey 2007-02-03 14:06:46 UTC

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

Comment 16 Steve Frécinaux 2007-02-10 08:38:27 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 17 palfrey 2007-04-05 16:39:52 UTC

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