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 332801 - "Nautilus has quit" after clicking on reload
"Nautilus has quit" after clicking on reload
Status: RESOLVED DUPLICATE of bug 158506
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-28 00:42 UTC by r.f.gantzert
Modified: 2006-02-28 03:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description r.f.gantzert 2006-02-28 00:42:38 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Red Hat, Inc
Synopsis: "Nautilus has quit" after clicking on reload
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
File missing in dir-listing, so I clicked Reload.
Instant termination		

Steps to reproduce the crash:
1. Random, I'm sorry to say
2. 
3. 

Expected Results:
Renewed dir-listing, with the missing file

How often does this happen?
Random

Additional Information:
Mostly when Nautilus is focused on dir, where another task is
creating/deleting files.
In this case, the Mozilla download-directory.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208723776 (LWP 3222)]
[New Thread -1213469776 (LWP 3284)]
[New Thread -1213203536 (LWP 3283)]
[New Thread -1211720784 (LWP 3282)]
[New Thread -1211454544 (LWP 3281)]
[New Thread -1211188304 (LWP 3280)]
[New Thread -1210922064 (LWP 3266)]
(no debugging symbols found)
0x00d9b402 in __kernel_vsyscall ()

Thread 1 (Thread -1208723776 (LWP 3222))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/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 fm_tree_model_get_type
  • #11 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_tree_row_reference_get_type
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_tree_row_reference_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_tree_selection_select_range
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_tree_selection_select_range
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_tree_view_scroll_to_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_tree_view_set_cursor_on_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_tree_view_set_cursor
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 fm_tree_view_get_type
  • #22 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main




------- Bug created by bug-buddy at 2006-02-28 00:42 -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".

Comment 1 Karsten Bräckelmann 2006-02-28 03:43:55 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.


Identical stacktrace as bug 322123, which is a duplicate of bug 158506.

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