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 363515 - crash refreshing nautilus
crash refreshing nautilus
Status: RESOLVED DUPLICATE of bug 348161
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-19 22:00 UTC by depaolis.salvatore
Modified: 2006-10-21 18:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description depaolis.salvatore 2006-10-19 22:00:47 UTC
What were you doing when the application crashed?
running F5


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.1 2006-10-17 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 73596928 vsize: 0 resident: 73596928 share: 0 rss: 23625728 rss_rlim: 0
CPU usage: start_time: 1161295198 rtime: 0 utime: 176 stime: 0 cutime:167 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227323728 (LWP 8713)]
0xb7f2a410 in ?? ()
  • #0 ??
  • #1 ??
  • #2 ??

Comment 1 André Klapper 2006-10-19 22:05:12 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 depaolis.salvatore 2006-10-20 13:10:39 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Unfortunately, that stack trace is missing some elements that will help a lot
> to solve the problem, so it will be hard for the developers to fix that crash.
> Can you get us a stack trace with debugging symbols? Please see
> http://live.gnome.org/GettingTraces for more information on how to do so.
> Thanks in advance!

I hope that can help!

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 -1225759040 (LWP 12451)]
[New Thread -1227359312 (LWP 12454)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225759040 (LWP 12451))

  • #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 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #5 fm_icon_container_get_icon_text
    at fm-icon-container.c line 272
  • #6 nautilus_icon_container_update_icon
    at nautilus-icon-container.c line 5391
  • #7 nautilus_icon_container_request_update_all
    at nautilus-icon-container.c line 5926
  • #8 fm_icon_view_emblems_changed
    at fm-icon-view.c line 2302
  • #9 file_changed_callback
    at fm-directory-view.c line 8555
  • #10 g_cclosure_marshal_VOID__VOID
    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 nautilus_file_emit_changed
    at nautilus-file.c line 5398
  • #16 nautilus_file_changed
    at nautilus-file.c line 5339
  • #17 get_info_callback
    at nautilus-directory-async.c line 2798
  • #18 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #19 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
    at nautilus-main.c line 406
  • #25 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #26 _start
    at ../sysdeps/i386/elf/start.S line 119
  • #0 __kernel_vsyscall

Comment 3 depaolis.salvatore 2006-10-20 13:23:22 UTC
Sorry i made a little mess..but useful one:)
First trace is from a gentoo system running gnome 2.16.0.
But I get the same bug also in ubuntu with nautilus-2.14.3.
Details of crash (comment #2) referring ubuntu / nautilus-2.14.3 and NOT gentoo / nautilus-2.16.1 (i'll try to post a trace as soon as).

Crash is with nautilus and refresh(F5) only in the root / filesystem.
I tried with other location and i don't get a crash.
Comment 4 depaolis.salvatore 2006-10-20 13:40:57 UTC
...and here trace from Gentoo / nautilus-2.16.1

Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.1 2006-10-17 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 74055680 vsize: 0 resident: 74055680 share: 0 rss: 24993792 rss_rlim: 0
CPU usage: start_time: 1161351014 rtime: 0 utime: 238 stime: 0 cutime:230 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xb7f2a000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227323728 (LWP 8529)]
0xb7f2a410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_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_icon_container_get_icon_text
    at fm-icon-container.c line 275
  • #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 8753
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #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 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
    from /usr/lib/libgthread-2.0.so.0
  • #28 ??
  • #29 ??
    from /usr/lib/libglib-2.0.so.0
  • #30 ??
  • #31 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #32 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #33 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 main
    at nautilus-main.c line 371
  • #38 __libc_start_main
    from /lib/libc.so.6
  • #39 _start

Comment 5 André Klapper 2006-10-21 18:21:00 UTC
thanks for your efforts, the stacktrace looks very good!
this is the same stacktrace as the one in bug 363582, which is the same bug as bug 348161. therefore marking as duplicate.

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