Bug 395569 – Crash when selecting chinese characters

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 395569 - Crash when selecting chinese characters


Summary:	Crash when selecting chinese characters


Status:	RESOLVED DUPLICATE of bug 364329

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.15.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-11 21:16 UTC by xelnaga
Modified:	2007-01-16 18:05 UTC

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

Description xelnaga 2007-01-11 21:16:30 UTC

Version: 2.15.9

What were you doing when the application crashed?
I am editing  my txt, I just input several chinese characters and  then the problem  appears.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 89616384 vsize: 0 resident: 89616384 share: 0 rss: 20160512 rss_rlim: 0
CPU usage: start_time: 1168545157 rtime: 0 utime: 319 stime: 0 cutime:299 cstime: 0 timeout: 20 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208284416 (LWP 6006)]
(no debugging symbols found)
0x002c0402 in __kernel_vsyscall ()

+ Trace 101384

Thread 1 (Thread -1208284416 (LWP 6006))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/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/i686/nosegneg/libc.so.6
#6 abort
from /lib/i686/nosegneg/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 gtk_text_line_segment_split
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_line_segment_split
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_mark_set_visible
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_view_new_with_buffer
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_source_view_get_show_line_numbers
from /usr/lib/libgtksourceview-1.0.so.0
#19 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#29 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#30 g_main_context_check
from /lib/libglib-2.0.so.0
#31 g_main_loop_run
from /lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 __kernel_vsyscall

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

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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