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 569203 - gvfsd-sftp crashed with SIGSEGV in strlen()
gvfsd-sftp crashed with SIGSEGV in strlen()
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: sftp backend
1.0.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-01-26 15:36 UTC by Sebastien Bacher
Modified: 2014-02-20 12:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Sebastien Bacher 2009-01-26 15:36:59 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/286053

"Not sure where or what crashes every now and then.

.

Thread 1 (process 4653)

  • #0 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #1 do_mount
    at gvfsbackendsftp.c line 910
  • #2 run
    at gvfsjobmount.c line 113
  • #3 g_vfs_job_run
    at gvfsjob.c line 198
  • #4 job_handler_callback
    at gvfsdaemon.c line 142
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #8 clone
    from /lib/tls/i686/cmov/libc.so.6"

Comment 1 Alexander Larsson 2009-03-02 10:22:28 UTC
I have no idea why new_password seems to be NULL in:
  if (!g_output_stream_write_all (reply_stream,
                                  new_password, strlen (new_password),

This would mean either gnome-keyring or the password dialog returned success but a NULL password, which doesn't seem possible.

I'm adding a check to avoid the crash which spews a warning in this case. Hopefully this can give us information from people seeing this.

Comment 2 Tomas Bzatek 2010-02-19 16:16:28 UTC
(In reply to comment #1)
> This would mean either gnome-keyring or the password dialog returned success
> but a NULL password, which doesn't seem possible.
See bug 608510, comment 6 in particular.
Comment 3 Ondrej Holy 2014-02-20 12:44:23 UTC
It is an old bug. It looks like it was solved by Bug 608510. If you still see the problem, please reopen.