GNOME Bugzilla – Bug 166309
Nautilus Crash On gnome-vfs file copy
Last modified: 2005-03-11 22:55:17 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: Nautilus Crash On gnome-vfs file copy Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: One directory mounted using gnome-vfs via ssh to a machine running Solaris; One directory mounted using gnome-vfs via Window Share to a Windows Share; Draging files from the ssh mounted nautilus window to the windows share mounted nautilus window crash nautilus imediately. Steps to reproduce the crash: 1. gnome-vfs mount to ssh share; gnome-vfs mount to windows share; 2. drag files to copy from ssh share to windows share. Expected Results: Expected files to be copied. How often does this happen? 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1089478976 (LWP 4957)] [New Thread 1124740016 (LWP 7581)] [Thread debugging using libthread_db enabled] [New Thread 1089478976 (LWP 4957)] [New Thread 1124740016 (LWP 7581)] [Thread debugging using libthread_db enabled] [New Thread 1089478976 (LWP 4957)] [New Thread 1124740016 (LWP 7581)] (no debugging symbols found)...[New Thread 1102850992 (LWP 5014)] (no debugging symbols found)...[New Thread 1102584752 (LWP 5013)] (no debugging symbols found)...[New Thread 1102318512 (LWP 5012)] (no debugging symbols found)...[New Thread 1100950448 (LWP 5011)] (no debugging symbols found)...[New Thread 1100684208 (LWP 5010)] (no debugging symbols found)...[New Thread 1100024752 (LWP 5009)] (no debugging symbols found)...[New Thread 1099717552 (LWP 4970)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 55311
Thread 9 (Thread 1099717552 (LWP 4970))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-04 13:11 ------- Unknown version 2.8.1 in product nautilus. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was aaron@slyness.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 141916 ***
Oops, wrong bug.
Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
Dup of Bug 166799? Last thread trace is equal.
*** This bug has been marked as a duplicate of 166799 ***
Christian: The last stack trace isn't very useful and only contains common functions; further since it's not the main thread and not a thread that contains the signal handler, it probably shouldn't be relied upon. However, I'll leave this bug closed as it's been over a month since Martin marked it as needinfo...