Bug 462091 – 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 462091 - crash in Open Folder:


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 446868

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:	2007-07-31 11:25 UTC by guest
Modified:	2007-08-06 14:45 UTC

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

Description guest 2007-07-31 11:25:33 UTC

Version: 2.18.3

What were you doing when the application crashed?



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

System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 528429056 vsize: 528429056 resident: 82726912 share: 22114304 rss: 82726912 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185878529 rtime: 9850 utime: 6917 stime: 2933 cutime:12 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496454704 (LWP 9305)]
[New Thread 1084229968 (LWP 9540)]
(no debugging symbols found)
0x0000003b19ac82e6 in poll () from /lib64/libc.so.6

+ Trace 151785

Thread 2 (Thread 1084229968 (LWP 9540))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#4 gnome_vfs_get_file_info_from_handle_cancellable
from /usr/lib64/libgnomevfs-2.so.0
#5 gnome_vfs_get_file_info_from_handle
from /usr/lib64/libgnomevfs-2.so.0
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#7 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#8 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#9 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#14 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#20 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomevfs-2.so.0
#21 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#22 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#23 start_thread
from /lib64/libpthread.so.0
#24 clone
from /lib64/libc.so.6



----------- .xsession-errors (1664 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/9178
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** Message: Hit unexpected error "Invalid parameters" while doing a file operation.
** Message: Hit unexpected error "Invalid parameters" while doing a file operation.
error: The metadata does not have a thumbnail property
error: The metadata does not have a thumbnail property
--------------------------------------------------

Comment 1 Susana 2007-08-06 14:45:21 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 446868 ***