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 405345 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 405344
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-07 13:14 UTC by stefano.merlini
Modified: 2007-02-07 21:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description stefano.merlini 2007-02-07 13:14:18 UTC
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 76865536 vsize: 0 resident: 76865536 share: 0 rss: 17002496 rss_rlim: 0
CPU usage: start_time: 1170853830 rtime: 0 utime: 158 stime: 0 cutime:141 cstime: 0 timeout: 17 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 -1208472832 (LWP 22796)]
(no debugging symbols found)
0x00c4f402 in __kernel_vsyscall ()

Thread 1 (Thread -1208472832 (LWP 22796))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 nautilus_directory_async_state_changed
  • #11 nautilus_directory_async_state_changed
  • #12 nautilus_clipboard_monitor_emit_changed
  • #13 nautilus_clipboard_monitor_emit_changed
  • #14 nautilus_clipboard_monitor_emit_changed
  • #15 nautilus_clipboard_monitor_emit_changed
  • #16 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #22 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib/libgnomevfs-2.so.0
  • #23 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #24 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #25 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 POA_Nautilus_MetafileMonitor__init
  • #30 __libc_start_main
    from /lib/libc.so.6
  • #31 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** ERROR **: file nautilus-directory.c: line 594 (add_to_hash_table): assertion failed: (g_hash_table_lookup (directory->details->file_hash, file->details->relative_uri) == NULL)
aborting...
** (bug-buddy:22990): WARNING **: Impossibile caricare l'icona per Apri cartella
--------------------------------------------------
Comment 1 André Klapper 2007-02-07 21:53:27 UTC

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