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 322672 - List view: nautilus crashed after renaming a folder
List view: nautilus crashed after renaming a folder
Status: RESOLVED DUPLICATE of bug 318232
Product: nautilus
Classification: Core
Component: general
2.12.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-11-28 17:04 UTC by Peter Parkkali
Modified: 2005-11-30 21:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Peter Parkkali 2005-11-28 17:04:53 UTC
Distribution: Ubuntu 5.10 (breezy)
Package: nautilus
Severity: Normal
Version: GNOME2.12.1 2.12.1
Gnome-Distributor: Ubuntu
Synopsis: List view: nautilus crashed after renaming a folder
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.12.1
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:

I had the List list view open, with a hierarchy of maybe 10-20 folders
open in this one window (the whole tree that this window was showing
contains about 120 folders altogether, with 5 folders in the root). I
renamed a folder (something like "Title 2005-06" -> "2005-06 Title").
After pressing enter, nautilus crashed almost immediately.

For a few deciseconds it looked like nautilus was re-sorting the window
contents to match the new naming, before it crashed. Not sure though.

Spatial mode is on ("always open in browser windows" is off). "Sort
folders before files" is off.

Steps to reproduce the crash:

1. Open a folder w/ some subfolders and files in list view
2. Select one folder, press F2 to rename it
3. Type new name (possibly changing the beginning, so nautilus has to
resort the window contents)

Expected Results:

Nautilus crashes.

How often does this happen?

Not every time you rename something, and then nautilus crashes in other
circumstances too. But, renaming (a folder/anything) seems to be one
situation where it's very likely to crash, like with about 1:5 .... 1:10 
probability

Additional Information:
 
 -



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226475296 (LWP 9784)]
[New Thread -1236194384 (LWP 9800)]
[New Thread -1235928144 (LWP 9799)]
[New Thread -1235158096 (LWP 9796)]
[New Thread -1234891856 (LWP 9795)]
[New Thread -1234625616 (LWP 9794)]
[New Thread -1228747856 (LWP 9792)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226475296 (LWP 9784))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_tree_model_get_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 fm_list_view_get_type
  • #7 gtk_tree_view_column_cell_set_cell_data
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 _gtk_tree_view_queue_draw_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gdk_window_clear_area_e
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #20 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@gnome.bugs 2005-11-28 17:04 UTC -------


Unknown version 2.12.1 in product nautilus.  Setting version to "2.12.x".

Comment 1 Teppo Turtiainen 2005-11-30 21:35:43 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 318232 ***