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 450857 - crash in Home Folder: deleting the folder whic...
crash in Home Folder: deleting the folder whic...
Status: RESOLVED DUPLICATE of bug 435026
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-25 10:42 UTC by xuhuashan
Modified: 2007-06-26 00:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description xuhuashan 2007-06-25 10:42:15 UTC 
What were you doing when the application crashed?
deleting the folder which nautilus is opened


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 113074176 vsize: 113074176 resident: 37326848 share: 21340160 rss: 37326848 rss_rlim: 4294967295
CPU usage: start_time: 1182767739 rtime: 898 utime: 791 stime: 107 cutime:0 cstime: 0 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 -1208346912 (LWP 2651)]
(no debugging symbols found)
0x006dd402 in __kernel_vsyscall ()

+ Trace 143531

Thread 1 (Thread -1208346912 (LWP 2651))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    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 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    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 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 g_cclosure_marshal_VOID__ENUM
    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 (11 sec old) ---------------------
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
无法打开面板启动器的 desktop 文件 /usr/share/applications/openoffice.org-1.9-writer.desktop: 没有那个文件或目录
无法打开面板启动器的 desktop 文件 /usr/share/applications/openoffice.org-1.9-impress.desktop: 没有那个文件或目录
无法打开面板启动器的 desktop 文件 /usr/share/applications/openoffice.org-1.9-calc.desktop: 没有那个文件或目录
** (nautilus:2651): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-26 00:33:26 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 ***