gedit crashes on IM change. This has been reported on LHR9 Gnome gedit 2.2.0. But FreeBSD 5.2-CURRENT + gedit 2.6.0 doesn't causes this problem. #0 0x41aedcd0 in ?? () #1 0x41957fbc in uim_quit () at uim.c:593 #2 0x419324ab in im_module_exit () from /hogehoge/lib/gtk-2.0/2.2.0/immodules/im-uim.so #3 0x408b069d in gtk_im_context_simple_add_table () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x40c8a65f in g_type_module_unuse () from /usr/lib/libgobject-2.0.so.0 #5 0x40c8ae06 in g_type_plugin_unuse () from /usr/lib/libgobject-2.0.so.0 #6 0x40c863e1 in g_type_free_instance () from /usr/lib/libgobject-2.0.so.0 #7 0x40c87558 in g_type_class_unref () from /usr/lib/libgobject-2.0.so.0 #8 0x40c855a2 in g_type_free_instance () from /usr/lib/libgobject-2.0.so.0 #9 0x40c70115 in g_object_class_list_properties () from /usr/lib/libgobject-2.0.so.0 #10 0x408b1423 in gtk_im_multicontext_new () from /usr/lib/libgtk-x11-2.0.so.0 #11 0x408b1b8d in gtk_im_multicontext_new () from /usr/lib/libgtk-x11-2.0.so.0 #12 0x40c80d77 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #13 0x40c6ded7 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #14 0x40c80983 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #15 0x40c7f9a8 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #16 0x40c7fbe4 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #17 0x409b48ed in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x408de682 in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #19 0x408dd8ff in _gtk_menu_shell_activate () from /usr/lib/libgtk-x11-2.0.so.0 #20 0x408d6d6b in gtk_menu_reorder_child () from /usr/lib/libgtk-x11-2.0.so.0 #21 0x408cec2f in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 ...
The problem has also been seen on my Linux box. $ uname -sr Linux 2.4.20 $ gedit --version Gnome gedit 2.4.1 $ gdb gedit ... 0x412a6e7c in create_context () at anthy.c:152 152 if (!context_slot[i].ac) { (gdb) back #0 0x412a6e7c in create_context () at anthy.c:152 #1 0x412ac5c8 in leval (x=0x413769a0, env=0x41300f44) at slib.c:2530 #2 0x412ac2db in leval_args (l=0x413769c4, env=0x41300f44) at slib.c:2448 #3 0x412acaa8 in leval (x=0x413769d0, env=0x41300f44) at slib.c:2588 #4 0x412ad88f in leval_progn (pform=0xbfffe6e0, penv=0xbfffe6e4) at slib.c:2830 #5 0x412aca46 in leval (x=0x41301310, env=0x41300f44) at slib.c:2580 #6 0x412ac2db in leval_args (l=0x413761a8, env=0x413013ac) at slib.c:2448 #7 0x412acaa8 in leval (x=0x413761b4, env=0x413013ac) at slib.c:2588 #8 0x412ad88f in leval_progn (pform=0xbfffe810, penv=0xbfffe814) at slib.c:2830 #9 0x412aca46 in leval (x=0x41301454, env=0x413013ac) at slib.c:2580 #10 0x412a7f50 in repl (h=0xbfffe8c0) at slib.c:517 #11 0x412a87ee in repl_driver (want_init=0, h=0xbfffe8c0) at slib.c:752 #12 0x412a93e4 in repl_c_string (str=0x82731a8 "(create-context 0 '() 'anthy)", want_init=0, want_print=1) at slib.c:1123 #13 0x412a24db in uim_eval_string (uc=0x826b458, buf=0x82731a8 "(create-context 0 '() 'anthy)") at uim-func.c:252 #14 0x412a1484 in uim_create_context (ptr=0x82edba0, enc=0x4129bbe9 "UTF-8", lang=0x412b2786 "()", engine=0x821b3fc "anthy", conv=0x412b5688, commit_cb=0x41299700 <im_uim_commit_string>) at uim.c:190 #15 0x4129b38a in im_module_create (context_id=0x821b3fc "anthy") at gtk-im-uim.c:974 #16 0x40c896c8 in _gtk_im_module_create () from /usr/lib/libgtk-x11-2.0.so.0 ...
Oops, additional Comment #1 was not this problem. That was caused by absence of libanthy on my Linux box. Crash has not caused after install anthy-5229. The reporter reported following steps, but I can't see the problem on my Linux environment. 1. GTK_IM_MODULE_FILE=$HOME/etc/immodules GTK_IM_MODULE=uim-tcode gedit 2. type C-q to quit 3. crashed!
r779 | yamaken | 2004-05-02 17:40:16 +0900 (Sun, 02 May 2004) | 6 lines * uim.c (uim_quit): Avoid excessive cleanup on duplicate quit. * canna.c (uim_quit_canna): Fix memory cleanup for cyclic initialization * This commit has resolved bug #586 by patch [Anthy-dev 798] by Seiichi SATO-san. Thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.