Bug 521772 – crash in Home Folder: delete from /tmp

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 521772 - crash in Home Folder: delete from /tmp


Summary:	crash in Home Folder: delete from /tmp


Status:	RESOLVED DUPLICATE of bug 425157

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-11 14:23 UTC by zhangruixp
Modified:	2008-03-11 18:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description zhangruixp 2008-03-11 14:23:53 UTC

What were you doing when the application crashed?
delete from /tmp


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: 110706688 vsize: 110706688 resident: 33378304 share: 19120128 rss: 33378304 rss_rlim: 4294967295
CPU usage: start_time: 1205331813 rtime: 707 utime: 239 stime: 468 cutime:109 cstime: 135 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 -1208264992 (LWP 2498)]
(no debugging symbols found)
0x00b7c402 in __kernel_vsyscall ()

+ Trace 192076

Thread 1 (Thread -1208264992 (LWP 2498))

#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 ---------------------
(nautilus:2498): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
** (nautilus:2498): CRITICAL **: nautilus_file_unref: assertion `NAUTILUS_IS_FILE (file)' failed
窗口管理器警告：为 0x16031ae () 指定了无效的 WM_TRANSIENT_FOR 窗口 0x3f。
(nautilus:2498): Eel-WARNING **: Error starting command ''/tmp/mapping-ray'': 执行子进程“/tmp/mapping-ray”失败(权限不够)
(nautilus:2498): Eel-WARNING **: Error starting command ''/tmp/mapping-ray'': 执行子进程“/tmp/mapping-ray”失败(权限不够)
** (nautilus:2498): 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 Cosimo Cecchi 2008-03-11 18:18:07 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 425157 ***