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 365277 - crash on File Browser
crash on File Browser
Status: RESOLVED DUPLICATE of bug 349551
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-26 14:00 UTC by dario
Modified: 2006-10-26 14:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dario 2006-10-26 14:00:48 UTC 
What were you doing when the app crashed?:
trying to log in.


Distribution: Red Hat Enterprise Linux Client release 4.91 (Tikanga)
Gnome Release: 2.15.4 2006-07-12 (Red Hat, Inc)
BugBuddy Version: 2.15.0

Memmory status: size: 83726336 vsize: 0 resident: 83726336 share: 0 rss: 17084416 rss_rlim: 0
CPU usage: start_time: 1161871207 rtime: 0 utime: 35 stime: 0 cutime:26 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 -1208383792 (LWP 11621)]
(no debugging symbols found)
0xb7fbf402 in __kernel_vsyscall ()

+ Trace 78438

Thread 1 (Thread -1208383792 (LWP 11621))

  • #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 /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 nautilus_directory_async_state_changed
  • #10 nautilus_directory_async_state_changed
  • #11 nautilus_directory_async_state_changed
  • #12 nautilus_directory_async_state_changed
  • #13 nautilus_undo_transaction_unregister_object
  • #14 nautilus_directory_async_state_changed
  • #15 nautilus_undo_transaction_unregister_object
  • #16 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #17 nautilus_undo_transaction_unregister_object
  • #18 g_cclosure_marshal_VOID__POINTER
    from /lib/libgobject-2.0.so.0
  • #19 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 nautilus_undo_transaction_unregister_object
  • #25 nautilus_marshal_BOOLEAN__POINTER
  • #26 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #27 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 POA_Nautilus_MetafileMonitor__init
  • #33 __libc_start_main
    from /lib/libc.so.6
  • #34 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-10-26 14:02:09 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 349551 ***