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 360208 - Crash in Nautilus when refreshing '/'
Crash in Nautilus when refreshing '/'
Status: RESOLVED DUPLICATE of bug 348161
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-06 16:11 UTC by Adam McMaster
Modified: 2006-10-06 16:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Adam McMaster 2006-10-06 16:11:38 UTC
What were you doing when the application crashed?
I had the / directory open in a nautilus window.  I pressed ctrl-r to refresh, and at that point Nautilus crashed.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 100417536 vsize: 0 resident: 100417536 share: 0 rss: 24498176 rss_rlim: 0
CPU usage: start_time: 1160150941 rtime: 0 utime: 283 stime: 0 cutime:253 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226479952 (LWP 8376)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226479952 (LWP 8376))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 fm_icon_container_get_icon_text
    at fm-icon-container.c line 274
  • #11 nautilus_icon_container_update_icon
    at nautilus-icon-container.c line 5427
  • #12 nautilus_icon_container_request_update_all
    at nautilus-icon-container.c line 5959
  • #13 fm_icon_view_emblems_changed
    at fm-icon-view.c line 2285
  • #14 file_changed_callback
    at fm-directory-view.c line 8843
  • #15 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #19 IA__g_signal_emit
    at gsignal.c line 2243
  • #20 nautilus_file_emit_changed
    at nautilus-file.c line 5459
  • #21 nautilus_file_changed
    at nautilus-file.c line 5400
  • #22 get_info_callback
    at nautilus-directory-async.c line 2794
  • #23 dispatch_job_callback
    at gnome-vfs-job.c line 229
  • #24 g_idle_dispatch
    at gmain.c line 3926
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #26 g_main_context_iterate
    at gmain.c line 2677
  • #27 IA__g_main_loop_run
    at gmain.c line 2881
  • #28 IA__gtk_main
    at gtkmain.c line 1024
  • #29 main
    at nautilus-main.c line 372
  • #30 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #31 _start
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-06 16:23:10 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 348161 ***