Bug 506805 – crash in Open Folder:

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 506805 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 465786

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-02 05:38 UTC by nicolas.veloz.savino
Modified:	2008-01-02 20:57 UTC

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

Description nicolas.veloz.savino 2008-01-02 05:38:25 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 96468992 vsize: 96468992 resident: 35344384 share: 21704704 rss: 35344384 rss_rlim: 4294967295
CPU usage: start_time: 1199249843 rtime: 5920 utime: 3348 stime: 2572 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 -1208830240 (LWP 3411)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 183771

Thread 1 (Thread -1208830240 (LWP 3411))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_str_hash
from /lib/libglib-2.0.so.0
#5 g_hash_table_lookup
from /lib/libglib-2.0.so.0
#6 ??
#7 nautilus_file_emit_changed
#8 nautilus_directory_emit_change_signals
#9 nautilus_file_changed
#10 ??
#11 ??
from /usr/lib/libgnomevfs-2.so.0
#12 ??
#13 ??
#14 ??
#15 ??
from /usr/lib/libgnomevfs-2.so.0
#16 ??
#17 ??
from /lib/libpthread.so.0
#18 ??
#19 ??
from /usr/lib/libgnomevfs-2.so.0
#20 ??
#21 ??
#22 ??
#23 g_slice_alloc
from /lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (9 sec old) ---------------------
(nautilus:4073): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/nico
(nautilus:4080): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x440001d (cal-fac.pa); these messages lack timestamps and therefore suck.
--- Hash table keys for warning below:
--> file:///home/nico
(nautilus:4300): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** (nautilus:3411): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-02 20:57:10 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 465786 ***