Bug 500218 – crash in Home Folder: create new file fold

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 500218 - crash in Home Folder: create new file fold


Summary:	crash in Home Folder: create new file fold


Status:	RESOLVED DUPLICATE of bug 479128

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:	2007-11-28 14:49 UTC by hyppuma
Modified:	2007-11-28 22:12 UTC

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

Description hyppuma 2007-11-28 14:49:46 UTC

What were you doing when the application crashed?
create new file fold


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: 115974144 vsize: 115974144 resident: 32735232 share: 19435520 rss: 32735232 rss_rlim: 4294967295
CPU usage: start_time: 1196255495 rtime: 1439 utime: 1235 stime: 204 cutime:8 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 -1208776992 (LWP 3115)]
(no debugging symbols found)
0x00be6402 in __kernel_vsyscall ()

+ Trace 179964

Thread 1 (Thread -1208776992 (LWP 3115))

#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 (2409 sec old) ---------------------
0:  6 d2 74  d  4 fc 84 92 
8:  0  7 3d 2d 3a 3c  f 3c 
16: 1f 40  0 84 11  3  6 d2 
24: 74  d  4 fc 84 92 9c 46 
32: dd 56 d4 92 2a dc 58 c7 
40:  5 fc c6 50 67 cb  0 81 
48: 20 e9 47 4d 76 68  0  0 
56:  0  0  0  1  0  0  0  0 
64:  0  0  0  0  0  0  0  0 
72:  0  0  0  0  0  0  0  0 
80:  0  0  0 6b  0 6b  0  0 
88:  0  0  0  1  0  0 20 e9 
EvaPacketManager::processReceiveIM -- unknown transfer type: 6b
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2007-11-28 22:12:55 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 479128 ***