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 674348 - case insensitive
case insensitive
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: sftp backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2012-04-18 18:30 UTC by jpdborgna
Modified: 2012-11-28 09:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jpdborgna 2012-04-18 18:30:57 UTC 
The sftp can't connect to hosts defined using uppercase symbols in the .ssh/config file.
Comment 1 Felix Möller 2012-07-29 09:57:22 UTC 
I can confirm this bug.

fm@thinkpad:~$ cat .ssh/config 
Host nas
  HostName ms.xxx.de
  Port 222
  User root

Host NASD
  HostName ms.xxx.de
  Port 222
  User root

fm@thinkpad:~$ gvfs-mount sftp://nas/
works perfectly

fm@thinkpad:~$ gvfs-mount sftp://NASD/
uses 100% CPU!
Comment 2 Felix Möller 2012-07-29 09:59:26 UTC 
I am using gvfs version 1.12.1-0ubuntu1
Comment 3 Felix Möller 2012-07-29 10:12:03 UTC 
The backtrace looks like the following at that moment:

(gdb) bt

+ Trace 230605

  • #0 __GI___poll
    at ../sysdeps/unix/sysv/linux/poll.c line 87
  • #1 handle_login
    at gvfsbackendsftp.c line 872
  • #2 do_mount
    at gvfsbackendsftp.c line 1603
  • #3 real_do_mount
    at gvfsbackendsftp.c line 1716
  • #4 g_vfs_job_run
    at gvfsjob.c line 198
  • #5 job_handler_callback
    at gvfsdaemon.c line 144
  • #6 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.32.3/./glib/gthreadpool.c line 309
  • #7 g_thread_proxy
    at /build/buildd/glib2.0-2.32.3/./glib/gthread.c line 801
  • #8 start_thread
    at pthread_create.c line 308
  • #9 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112
  • #10 ?? 






Comment 4


Ritesh Khadgaray ( irc:ritz)





          2012-11-28 09:15:15 UTC
        



This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.


Please re-open, if otherwise.