GNOME Bugzilla – Bug 338970
copying an SVN working copy over ssh
Last modified: 2018-08-17 13:46:01 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: Normal Version: GNOME2.14.0 2.12.2 Gnome-Distributor: Debian Synopsis: nautilus crashed while copying an SVN working copy over ssh Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.2 BugBuddy-GnomeVersion: 2.0 (2.14.0) Description: Description of the crash: I copied a working copy of https://mail.incase.de/svn/cyrus22/trunk (svn repository) over ssh from one computer to another. nautilus crashed while copying some file in build-area/.svn. How often does this happen? I was able to reproduce it several times. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226529088 (LWP 7581)] [New Thread -1242567760 (LWP 7601)] [New Thread -1227961424 (LWP 7582)] (no debugging symbols found) 0xb7406809 in poll () from /lib/tls/libc.so.6
+ Trace 67716
Thread 2 (Thread -1242567760 (LWP 7601))
------- Bug created by bug-buddy at 2006-04-19 06:05 ------- Unknown version 2.12.2 in product nautilus. Setting version to "2.12.x".
*** Bug 338969 has been marked as a duplicate of this bug. ***
crash in gnome-vfs, reassigning I cannot access the hidden subdir on the server can you please find out which file caused this and attach it? alternatively: Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 341676 has been marked as a duplicate of this bug. ***
*** Bug 342787 has been marked as a duplicate of this bug. ***
*** Bug 343673 has been marked as a duplicate of this bug. ***
*** Bug 343738 has been marked as a duplicate of this bug. ***
Ok, unfortnetly. nautilus' 'auto-start' feature makes a stacktrace with gdb very difficult to get. Even when attempting to attach to a running process, I can't quite figure out whats going on. I would be more than happy to meet someone on the irc one day and help figure this out.
Ok, its not much, but heres about all I can get: (gdb) Quit (gdb) Couldn't get registers: No such process. (gdb) thread apply all bt Couldn't get registers: No such process. (gdb) bt
+ Trace 68613
Ok, here we go, some home-compilation with debugging symbols has made this bug-buddy trace about 1000 times more useful... Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225438848 (LWP 31258)] [New Thread -1233183824 (LWP 31422)] [New Thread -1278768208 (LWP 31417)] [New Thread -1226880080 (LWP 31259)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68614
Thread 3 (Thread -1278768208 (LWP 31417))
(In reply to comment #7) > Ok, unfortnetly. nautilus' 'auto-start' feature makes a stacktrace with gdb > very difficult to get. Even when attempting to attach to a running process, I > can't quite figure out whats going on. I would be more than happy to meet > someone on the irc one day and help figure this out. > You can run "gnome-session-remove nautilus" from a terminal, this will kill nautilus without respawning it. Afterwards you can rerun it inside gdb. Attaching to the running process is as good though imo ;) Could you recompile gnome-vfs with debugging symbols as well? Did you upgrade from gnome 2.x to gnome 2.14 without restarting your machine? (gnome-vfs-daemon needs to be restarted during upgrades)
thank you. last trace is way better, but please recompile gnome-vfs with debugging symbols. thanks.
Ok, this is about the best I can do, but to me it looks like it might be all you need ;). Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225819776 (LWP 5378)] [New Thread -1285334096 (LWP 9282)] [New Thread -1227273296 (LWP 5405)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68648
Thread 2 (Thread -1285334096 (LWP 9282))
that information is fair enough to accept this report, thanks. could you recompile without optimisations?
I can't get to crash while compiled with no optimizations... I tried the same files, i tried even more of them, but when no optimization flags are passed etc, theres not an issue.
sounds like a compiler bug to me ... what if you use other versions of your compiler?
*** Bug 345441 has been marked as a duplicate of this bug. ***
*** Bug 350135 has been marked as a duplicate of this bug. ***
Unfortunately, a symlink like "foo/" is turned into "file:/foo" by the GnomeVFSURI code, and unfortunately sftp doesn't check for the URI having another scheme. The attached patch prevents gnome_vfs_uri_new from eating scheme-less URIs and converting them to "file:garbage/". It isn't really a fix for the semi-broken do_create_symbolic_link implementation, but it enables me to do some sftp symlink copy transfers without crashes. I think the current symbolic link creation code is a mess. According to file-method.c, it is supposed to be also used for some cross-FS links, which is something entirely different, and if we want it it doesn't make sense to implement it method-specific. Besides, the current code would try to convert symlinks like "ftp://sucks" into GnomeVFSURIs.
Created attachment 70306 [details] [review] proposed gnome_vfs_uri_new patch
Updating bug version, milestoning to 2.16.
The proposed patch doesn't fix the issue for me (tested by copying the Tango icons folder over sftp to local desktop using the Copy and Paste context menu-items) and breaks dragging files into the Trash bin, which crashes Nautilus and produces the following output on the console: (nautilus:92517): libgnomevfs-CRITICAL **: gnome_vfs_uri_ref: assertion `uri != NULL' failed
*** Bug 354186 has been marked as a duplicate of this bug. ***
*** Bug 348443 has been marked as a duplicate of this bug. ***
*** Bug 378607 has been marked as a duplicate of this bug. ***
*** Bug 381282 has been marked as a duplicate of this bug. ***
Some additonal infos, i hope it could be useful. I can reproduce the Crash _only_ on connection with ssh server with very low speed. Example: on 10Mb speed lan network, it is fine and everything works! on 1Mb speed (about) wan network, it crash!
FWIW, I can't reproduce this with nautilus 2.30.1.
gnome-vfs got deprecated in 2008. gnome-vfs is not under active development anymore and had its last code changes in 2011. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-vfs/commits/master gio (in glib) and gvfs are its successors. See https://developer.gnome.org/gio/stable/ch33.html and https://people.gnome.org/~gicmo/gio-migration-guide/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of glib/gio/gvfs. Thanks!