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 75076 - crash on calling of rename folder
crash on calling of rename folder
Status: VERIFIED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Input Methods
unspecified
Other other
: Normal normal
: ---
Assigned To: Hidetoshi Tajima
gtk-bugs
: 75817 95393 98764 99398 102407 108598 108600 108604 109020 109220 111357 146957 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-03-17 10:43 UTC by kz
Modified: 2011-02-04 16:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description kz 2002-03-17 10:43:55 UTC 
Package: nautilus
Severity: normal
Version: 1.1.9
Synopsis: crash on calling of rename folder
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
BugBuddy-GnomeVersion: 2.0 (1.112.1)

Description:
Steps to reproduce the problem:
1. open up an icon view window.
2. call rename for a folder by popup menu

Actual Results:
crash before presence of editable entry.

Expected Results:
appears of entry.

How often does this happen?
this is first time. (3rd using)

Additional Information:
it may crash with xim or something.
before this xim support patch, nothing crash with this task. (thou it
was useless in many case)



Debugging Information:

[New Thread 1024 (LWP 10706)]
[New Thread 2049 (LWP 10707)]
[New Thread 1026 (LWP 10708)]
[New Thread 2051 (LWP 10709)]
[New Thread 3076 (LWP 10710)]
[New Thread 4101 (LWP 10711)]
[New Thread 5126 (LWP 10712)]
0x4094fca9 in __wait4 () from /lib/i686/libc.so.6

+ Trace 19302

Thread 1 (Thread 1024 (LWP 10706))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 593
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/libc.so.6
  • #7 get_im
    at gtkimcontextxim.c line 183
  • #8 gtk_im_context_xim_new
    at gtkimcontextxim.c line 285
  • #9 im_module_create
    at imxim.c line 60
  • #10 _gtk_im_module_create
    at gtkimmodule.c line 471
  • #11 gtk_im_multicontext_get_slave
    at gtkimmulticontext.c line 232
  • #12 gtk_im_multicontext_set_client_window
    at gtkimmulticontext.c line 244
  • #13 gtk_im_context_set_client_window
    at gtkimcontext.c line 256
  • #14 gtk_entry_realize
    at gtkentry.c line 979
  • #15 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 g_type_class_meta_marshal
    at gclosure.c line 514
  • #17 g_closure_invoke
    at gclosure.c line 437
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2270
  • #19 g_signal_emit_valist
    at gsignal.c line 2099
  • #20 gtk_signal_emit
    at gtksignal.c line 355
  • #21 gtk_widget_realize
    at gtkwidget.c line 1896
  • #22 gtk_widget_map
    at gtkwidget.c line 1815
  • #23 gtk_window_map
    at gtkwindow.c line 3120
  • #24 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #25 g_type_class_meta_marshal
    at gclosure.c line 514
  • #26 g_closure_invoke
    at gclosure.c line 437
  • #27 signal_emit_unlocked_R
    at gsignal.c line 2270
  • #28 g_signal_emit_valist
    at gsignal.c line 2099
  • #29 gtk_signal_emit
    at gtksignal.c line 355
  • #30 gtk_widget_map
    at gtkwidget.c line 1817
  • #31 gtk_window_show
    at gtkwindow.c line 3086
  • #32 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #33 g_type_class_meta_marshal
    at gclosure.c line 514
  • #34 g_closure_invoke
    at gclosure.c line 437
  • #35 signal_emit_unlocked_R
    at gsignal.c line 2270
  • #36 g_signal_emit_valist
    at gsignal.c line 2099
  • #37 gtk_signal_emit
    at gtksignal.c line 355
  • #38 gtk_widget_show
    at gtkwidget.c line 1637
  • #39 gtk_container_show_all
    at gtkcontainer.c line 2145
  • #40 gtk_widget_show_all
    at gtkwidget.c line 1775
  • #41 iti_start_editing
    at gnome-icon-item.c line 430
  • #42 nautilus_icon_container_start_renaming_selected_item
    at nautilus-icon-container.c line 4807
  • #43 fm_icon_view_start_renaming_file
    at fm-icon-view.c line 1267
  • #44 rename_file_callback
    at fm-directory-view.c line 4155
  • #45 marshal_VOID__USER_DATA_STRING
    at bonobo-ui-component.c line 217
  • #46 g_closure_invoke
    at gclosure.c line 437
  • #47 bonobo_closure_invoke_va_list
    at bonobo-types.c line 415
  • #48 bonobo_closure_invoke
    at bonobo-types.c line 474
  • #49 impl_Bonobo_UIComponent_execVerb
    at bonobo-ui-component.c line 155
  • #50 Bonobo_UIComponent_execVerb
    at Bonobo-stubs.c line 1733
  • #51 real_exec_verb
    at bonobo-ui-engine.c line 1479
  • #52 impl_emit_verb_on
    at bonobo-ui-engine.c line 1528
  • #53 g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 601
  • #54 g_type_class_meta_marshal
    at gclosure.c line 514
  • #55 g_closure_invoke
    at gclosure.c line 437
  • #56 signal_emit_unlocked_R
    at gsignal.c line 2378
  • #57 g_signal_emit_valist
    at gsignal.c line 2099
  • #58 g_signal_emit
    at gsignal.c line 2143
  • #59 bonobo_ui_engine_emit_verb_on_w
    at bonobo-ui-engine.c line 2945
  • #60 exec_verb_cb
    at bonobo-ui-sync-menu.c line 490
  • #61 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #62 g_closure_invoke
    at gclosure.c line 437
  • #63 signal_emit_unlocked_R
    at gsignal.c line 2340
  • #64 g_signal_emit_valist
    at gsignal.c line 2099
  • #65 gtk_signal_emit
    at gtksignal.c line 355
  • #66 gtk_widget_activate
    at gtkwidget.c line 3108
  • #67 gtk_menu_shell_activate_item
    at gtkmenushell.c line 929
  • #68 gtk_menu_shell_button_release
    at gtkmenushell.c line 550
  • #69 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #70 g_type_class_meta_marshal
    at gclosure.c line 514
  • #71 g_closure_invoke
    at gclosure.c line 437
  • #72 signal_emit_unlocked_R
    at gsignal.c line 2378
  • #73 g_signal_emit_valist
    at gsignal.c line 2109
  • #74 gtk_signal_emit
    at gtksignal.c line 355
  • #75 gtk_widget_event_internal
    at gtkwidget.c line 3076
  • #76 gtk_propagate_event
    at gtkmain.c line 2067
  • #77 gtk_main_do_event
    at gtkmain.c line 1316
  • #78 gdk_event_dispatch
    at gdkevents-x11.c line 1752
  • #79 g_main_dispatch
    at gmain.c line 1617
  • #80 g_main_context_dispatch
    at gmain.c line 2161
  • #81 g_main_context_iterate
    at gmain.c line 2242
  • #82 g_main_loop_run
    at gmain.c line 2462
  • #83 gtk_main
    at gtkmain.c line 915
  • #84 main
    at nautilus-main.c line 265
  • #85 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 593
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/libc.so.6
  • #7 get_im
    at gtkimcontextxim.c line 183 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-17 05:43 -------

Unknown version 1.1.x in product nautilus. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Luis Villa 2002-03-30 19:49:37 UTC 
To my extremely untrained eye this looks like a xim/(gtk?) crash,
maybe? Owen, care to comment?
Comment 2 Owen Taylor 2002-03-30 19:52:55 UTC 
Again, backtrace doesn't tell me much. If it can't
be reproduced in a simpler test case, someone would have
to figure out how to reproduce it,and then track it down
live.
Comment 3 John Fleck 2002-05-05 15:04:16 UTC 
Are you still seeing this?
Comment 4 kz 2002-05-05 15:32:09 UTC 
no, not in these days.. I don't use nautilus heavily nowadays..
Comment 5 John Fleck 2002-05-05 15:48:39 UTC 
Closing, then. Could you please reopen if you can duplicate it again?
Thanks.
Comment 6 Ben FrantzDale 2002-07-16 11:41:48 UTC 
*** Bug 75817 has been marked as a duplicate of this bug. ***
Comment 7 Luis Villa 2002-10-25 19:14:52 UTC 
*** Bug 95393 has been marked as a duplicate of this bug. ***
Comment 8 Luis Villa 2002-10-25 19:15:25 UTC 
Owen: folks are still seeing this with new asian installs. I'm reopening.
Comment 9 John Fleck 2002-11-18 03:53:48 UTC 
*** Bug 98764 has been marked as a duplicate of this bug. ***
Comment 10 Elijah Newren 2002-11-24 02:21:23 UTC 
*** Bug 99398 has been marked as a duplicate of this bug. ***
Comment 11 Aschwin van der Woude 2003-01-03 09:31:46 UTC 
*** Bug 102407 has been marked as a duplicate of this bug. ***
Comment 12 John Fleck 2003-03-17 14:51:14 UTC 
Why is this in Nautilus?
The most recent seeming dup (108598) was in gnome-terminal.
Comment 13 Owen Taylor 2003-03-17 15:08:42 UTC 
No particular ideas here. I doubt we'll be able to debug
it without a reproducible test case, but maybe Toshi
has some ideas.
Comment 14 Owen Taylor 2003-03-17 15:09:30 UTC 
Oh yeah, and information about GTK+ versions is _really important_
for this, since there have been extensive changes 
in GtkIMContextXIM.
Comment 15 Elijah Newren 2003-03-17 18:01:01 UTC 
*** Bug 108604 has been marked as a duplicate of this bug. ***
Comment 16 Elijah Newren 2003-03-17 18:08:01 UTC 
*** Bug 108598 has been marked as a duplicate of this bug. ***
Comment 17 Elijah Newren 2003-03-17 18:11:34 UTC 
*** Bug 108600 has been marked as a duplicate of this bug. ***
Comment 18 Elijah Newren 2003-03-17 18:13:59 UTC 
Note that bugs 108598 and 108600 were filed by the same user--but one
was a gnome-terminal (v. 2.0.1) crash and the other was a nautilus (v.
2.0.6) crash.  Don't know if that helps at all, but I thought I'd
mention it

Marking priority->high (it's a crasher and it appears to be affecting
several different people).
Comment 19 Owen Taylor 2003-03-17 22:58:42 UTC 
To repeat, we need the exact _GTK+_ versions. The nautilus
versions aren't useful if it's a GTK+ bug.
Comment 20 Andrew Sobala 2003-03-23 17:43:02 UTC 
*** Bug 109020 has been marked as a duplicate of this bug. ***
Comment 21 David Kennedy 2003-03-26 03:36:53 UTC 
*** Bug 109220 has been marked as a duplicate of this bug. ***
Comment 22 Hidetoshi Tajima 2003-03-28 22:04:17 UTC 
In reporter's comment:

 before this xim support patch, nothing crash with this task.

What is "this xim support patch" exactly?
Comment 23 Elijah Newren 2003-04-23 16:40:09 UTC 
*** Bug 111357 has been marked as a duplicate of this bug. ***
Comment 24 Hidetoshi Tajima 2003-05-13 22:14:27 UTC 
Seems working for me. Marking needinfo. I'd like 
to know:

 - gtk+ version. (mine gtk+-2.2)
 - system details (mine Solaris9 and RH9)
 - XIM type (mine htt on Solaris9 and kinput2 on RH9).
 - locales (mine ja_JP.eucJP).
Comment 25 Hidetoshi Tajima 2003-06-09 20:11:08 UTC 
Again, I cannot reproduce this with gtk+ of gtk-2-2 or 
the HEAD,

It is possible that this could happen with 2.0.x series
of gtk+, but it is really needed to know exact gtk+
version where this was actually seen.

Have been "NEEDINFO" for that info about a month, I'm 
lowering priority and sevirity. Another month of "NEEDINFO"
may lead to close the bug. Thanks!
Comment 26 Olav Vitters 2004-07-09 19:03:06 UTC 
*** Bug 146957 has been marked as a duplicate of this bug. ***