Bug 341676 – nautilus crash

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 341676 - nautilus crash


Summary:	nautilus crash


Status:	RESOLVED DUPLICATE of bug 338970

Product:	nautilus
Classification:	Core
Component:	File and Folder Operations
Version:	2.14.x
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-05-13 19:10 UTC by Alexander Frey
Modified:	2006-05-14 09:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Alexander Frey 2006-05-13 19:10:26 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.1 2.14.x
Gnome-Distributor: Ubuntu
Synopsis: nautilus crashes while copying files from ssh
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

Ubuntu Dapper and gnome 2.14.1
Nautilus just crashed while I was copying a directory from ssh to my
desktop. BUT I am not sure if the copying of the files with nautilus is
really the cause of the crash....

Steps to reproduce the crash:
1.
2.
3.

Expected Results:


How often does this happen?
1

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226057344 (LWP 5094)]
[New Thread -1303385168 (LWP 7243)]
[New Thread -1228039248 (LWP 5116)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68206

Thread 2 (Thread -1303385168 (LWP 7243))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#11 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#12 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#13 ??
#14 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#15 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#16 ??
from /usr/lib/libgnomevfs-2.so.0
#17 ??
#18 _dl_rtld_di_serinfo
from /lib/ld-linux.so.2
#19 gnome_vfs_create_symbolic_link_cancellable
from /usr/lib/libgnomevfs-2.so.0
#20 gnome_vfs_create_symbolic_link
from /usr/lib/libgnomevfs-2.so.0
#21 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#22 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#23 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#24 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#25 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#26 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#27 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#28 gnome_vfs_is_primary_thread
from /usr/lib/libgnomevfs-2.so.0
#29 g_thread_pool_free
from /usr/lib/libglib-2.0.so.0
#30 g_static_private_free
from /usr/lib/libglib-2.0.so.0
#31 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#32 clone
from /lib/tls/i686/cmov/libc.so.6





------- Bug created by bug-buddy at 2006-05-13 19:10 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.

Comment 1 Fabio Bonelli 2006-05-14 09:26:24 UTC

Thanks for the bug report!

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?


*** This bug has been marked as a duplicate of 338970 ***