desktop-packages team mailing list archive

[Rocko <rockorequin@xxxxxxxxxxx>]

Public bug reported:

To replicate:

1. Connect to a SFTP or Samba share via nautilus.

2. Change networks, eg by suspending and resuming in a different
location or by manually forcing a change to a network. For instance, I
change from a 10.1.1.x network to a 192.168.10.x network and back again.

3. Open nautilus.

The expected result is that nautilus should open immediately.

The actual result is that nautilus does not open for some minutes.

The workaround is to manually kill the gvfsd-smb and/or gvfsd-ssh
processes. So there is some timeout issue in gvfs that is freezing
nautilus. If the gvfsd-* processes cannot see the mounted shared drive,
this should not prevent nautilus from functioning properly.

This is an issue in both Ubuntu 14.04 and 14.10.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gvfs 1.20.2-1ubuntu2
Uname: Linux 3.18.0-031800rc6-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 29 11:11:19 2014
InstallationDate: Installed on 2014-11-26 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gvfs (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1397486

Title:
  gfvs freezes nautilus after switching networks

Status in gvfs package in Ubuntu:
  New

Bug description:
  To replicate:

  1. Connect to a SFTP or Samba share via nautilus.

  2. Change networks, eg by suspending and resuming in a different
  location or by manually forcing a change to a network. For instance, I
  change from a 10.1.1.x network to a 192.168.10.x network and back
  again.

  3. Open nautilus.

  The expected result is that nautilus should open immediately.

  The actual result is that nautilus does not open for some minutes.

  The workaround is to manually kill the gvfsd-smb and/or gvfsd-ssh
  processes. So there is some timeout issue in gvfs that is freezing
  nautilus. If the gvfsd-* processes cannot see the mounted shared
  drive, this should not prevent nautilus from functioning properly.

  This is an issue in both Ubuntu 14.04 and 14.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  Uname: Linux 3.18.0-031800rc6-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 29 11:11:19 2014
  InstallationDate: Installed on 2014-11-26 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1397486/+subscriptions