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 365564 - crash in [2xnautilus_clipboard_monitor_emit_changed + nautilus_directory_async_state_changed]
crash in [2xnautilus_clipboard_monitor_emit_changed + nautilus_directory_asyn...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 378381 391313 402879 403012 405840 416872 419918 432683 433378 440792 450033 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-27 03:44 UTC by alexandrpunk
Modified: 2007-10-19 01:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description alexandrpunk 2006-10-27 03:44:55 UTC
What were you doing when the application crashed?
intente accesar a un disko duro en fat32


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

Memory status: size: 88154112 vsize: 0 resident: 88154112 share: 0 rss: 32739328 rss_rlim: 0
CPU usage: start_time: 1161914987 rtime: 0 utime: 3254 stime: 0 cutime:2881 cstime: 0 timeout: 373 it_real_value: 0 frequency: 103

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227270480 (LWP 4516)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227270480 (LWP 4516))

  • #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 nautilus_clipboard_monitor_emit_changed
  • #5 nautilus_clipboard_monitor_emit_changed
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_directory_async_state_changed
  • #8 nautilus_undo_transaction_unregister_object
  • #9 nautilus_directory_async_state_changed
  • #10 fm_directory_view_bump_zoom_level
  • #11 fm_directory_view_bump_zoom_level
  • #12 nautilus_undo_transaction_unregister_object
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 POA_Nautilus_MetafileMonitor__init
  • #15 POA_Nautilus_MetafileMonitor__init
  • #16 nautilus_clipboard_monitor_emit_changed
  • #17 nautilus_directory_async_state_changed
  • #18 nautilus_directory_async_state_changed
  • #19 nautilus_undo_transaction_unregister_object
  • #20 nautilus_file_get_volume
  • #21 nautilus_file_get_volume
  • #22 fm_directory_view_bump_zoom_level
  • #23 nautilus_file_is_directory
  • #24 nautilus_clipboard_monitor_emit_changed
  • #25 nautilus_directory_async_state_changed
  • #26 nautilus_directory_async_state_changed
  • #27 nautilus_clipboard_monitor_emit_changed
  • #28 nautilus_file_get_volume
  • #29 nautilus_file_get_volume
  • #30 fm_directory_view_bump_zoom_level
  • #31 fm_directory_view_bump_zoom_level
  • #32 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #37 nautilus_file_ref
  • #38 nautilus_icon_container_request_update_all
  • #39 eel_marshal_BOOLEAN__BOXED
    from /usr/lib/libeel-2.so.2
  • #40 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #42 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #44 eel_canvas_window_to_world
    from /usr/lib/libeel-2.so.2
  • #45 nautilus_icon_container_request_update_all
  • #46 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #48 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #49 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #52 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #55 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #56 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #57 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #58 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #59 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 POA_Nautilus_MetafileMonitor__init
  • #61 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #62 ??
  • #0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-10-31 18:07:56 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!
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 367701 ***
Comment 2 André Klapper 2006-12-10 20:13:52 UTC
*** Bug 378381 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2006-12-12 18:38:34 UTC
bug 373595 is probably a duplicate
Comment 4 André Klapper 2007-01-03 21:50:50 UTC
*** Bug 391313 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-01-03 21:52:47 UTC
Thanks everybody for taking the time to report this.

Could you please help fixing this by installing some debugging packages [1], start nautilus as normal, and try to reproduce the crash, if possible?
Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for nautilus, glib, gtk, pango, gnome-vfs and 
    libgnome(ui), as far as provided by your distributor.

    Fedora Core 6 or SuSE 10.2: nautilus-debuginfo, glib2-debuginfo, 
    gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo,
    and libgnomeui-debuginfo.

    Ubuntu 6.10: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, 
    libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg.

    More details can be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 6 André Klapper 2007-02-05 22:55:10 UTC
*** Bug 402879 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-02-06 00:25:48 UTC
*** Bug 403012 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2007-02-09 02:11:29 UTC
*** Bug 405840 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2007-03-11 13:41:25 UTC
*** Bug 416872 has been marked as a duplicate of this bug. ***
Comment 10 André Klapper 2007-03-19 01:18:33 UTC
*** Bug 419918 has been marked as a duplicate of this bug. ***
Comment 11 palfrey 2007-04-26 10:21:16 UTC
*** Bug 433378 has been marked as a duplicate of this bug. ***
Comment 12 palfrey 2007-04-27 15:07:54 UTC
*** Bug 432683 has been marked as a duplicate of this bug. ***
Comment 13 Christian Kirbach 2007-05-23 19:49:00 UTC
*** Bug 440792 has been marked as a duplicate of this bug. ***
Comment 14 André Klapper 2007-06-22 22:47:05 UTC
*** Bug 450033 has been marked as a duplicate of this bug. ***
Comment 15 André Klapper 2007-10-19 01:15:34 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!