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 443314 - crash in Open Folder: I had the folder
crash in Open Folder: I had the folder
Status: RESOLVED DUPLICATE of bug 435026
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-02 20:27 UTC by cgodley
Modified: 2007-06-02 23:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description cgodley 2007-06-02 20:27:39 UTC 
Version: 2.18.1

What were you doing when the application crashed?
I had the folder "linuxdcpp" open in nautilus and ran the following command in a terminal:

sudo rm -r linuxdcpp


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 126996480 vsize: 126996480 resident: 44711936 share: 24469504 rss: 44711936 rss_rlim: 4294967295
CPU usage: start_time: 1180811190 rtime: 3862 utime: 1993 stime: 1869 cutime:4 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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 -1209063712 (LWP 2663)]
[New Thread -1303209072 (LWP 5369)]
(no debugging symbols found)
0x00fd5402 in __kernel_vsyscall ()

+ Trace 137594

Thread 1 (Thread -1209063712 (LWP 2663))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    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_connect_background_to_file_metadata
  • #11 ??
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 ??
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 fm_directory_view_begin_loading
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(nautilus:2663): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(nautilus:2663): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
** (nautilus:2663): CRITICAL **: nautilus_file_monitor_remove: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:2663): CRITICAL **: nautilus_file_cancel_call_when_ready: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:2663): CRITICAL **: nautilus_file_monitor_remove: assertion `NAUTILUS_IS_FILE (file)' failed
** (nautilus:2663): CRITICAL **: nautilus_file_unref: assertion `NAUTILUS_IS_FILE (file)' failed
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 palfrey 2007-06-02 23:44:25 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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