Bug 448140 – crash in Open Folder: Cancelling copying windo...

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 448140 - crash in Open Folder: Cancelling copying windo...


Summary:	crash in Open Folder: Cancelling copying windo...


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-06-16 08:45 UTC by rok.papez
Modified:	2007-06-23 11:27 UTC

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

Description rok.papez 2007-06-16 08:45:23 UTC

Version: 2.18.1

What were you doing when the application crashed?
Cancelling copying window


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 530477056 vsize: 530477056 resident: 43032576 share: 15032320 rss: 43032576 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181981306 rtime: 6383 utime: 2143 stime: 4240 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912697156272 (LWP 2969)]
[New Thread 1084229968 (LWP 3225)]
(no debugging symbols found)
0x00002aaab111fa20 in strchr () from /lib64/libc.so.6

+ Trace 141401

Thread 2 (Thread 1084229968 (LWP 3225))

#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 /usr/lib64/libgnomevfs-2.so.0
#22 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#23 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#24 start_thread
from /lib64/libpthread.so.0
#25 clone
from /lib64/libc.so.6



----------- .xsession-errors (1898 sec old) ---------------------
localuser:rok being added to access control list
SESSION_MANAGER=local/strader:/tmp/.ICE-unix/2854
Loading "installonlyn" plugin
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1000afd (rok); these messages lack timestamps and therefore suck.
--------------------------------------------------

Comment 1 André Klapper 2007-06-23 11:27:59 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 ***