Unable to mount OSX Yosemite causing excessive (~25%) CPU usage and moderate desktop sluggishness

[penalvch]

1) lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

2) apt-cache policy gvfs
gvfs:
  Installed: 1.20.1-1ubuntu1
  Candidate: 1.20.1-1ubuntu1
  Version table:
 *** 1.20.1-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen is when one mounts a shared folder from OSX Yosemite, the connection is unmountable, and doesn't cause excessive (~25%) CPU usage.

4) What happens instead is the mount is unmountable, and is consuming (~25%) CPU as per the attached screenshot. This causes moderate desktop sluggishness. Tried restarting OSX, no change.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gvfs 1.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-28.37~14.04.1-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec 16 11:28:39 2014
InstallationDate: Installed on 2014-06-21 (177 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

[Ross Lagerwall (rosslagerwall)]

The Ubuntu gvfs maintainers should cherry-pick e9c320e49cace543450b961af32ea7ffeb8d512f and 2e3eee275a97abf4d6055c06683f04c7d8f3f7ca from upstream.

[Ross Lagerwall (rosslagerwall)]

Oh, btw it's an afp not smb share you're using.

[Sebastien Bacher (seb128)]

Thanks Ross, the corresponding commit are on
https://git.gnome.org/browse/gvfs/commit/?id=e9c320e49cace543450b961af32ea7ffeb8d512f

https://git.gnome.org/browse/gvfs/commit/?id=2e3eee275a97abf4d6055c06683f04c7d8f3f7ca
(or rather https://git.gnome.org/browse/gvfs/commit/?id=a4016460538ea8be22aa0d8289922b389a93ef78 it looks like?)

[Ross Lagerwall (rosslagerwall)]

Oh, yeah somehow I messed up the commit id but you got the right one.

[penalvch (penalvch)]

Spoke too soon regarding Utopic. I walked away from my computer for about 2 hours, and noticed in System Monitor gvfsd-afp at CPU 25%, Memory 3.4 MB. Perhaps the issue affects Utopic more gradually than in Trusty?!

[Ross Lagerwall (rosslagerwall)]

Nah, neither of them have the required patches (which made only made it into 1.20.3). It's an idle timeout issue, so it depends one the activity on the share.

[Sebastien Bacher (seb128)]

sru for that update on https://launchpad.net/ubuntu/+source/gvfs/1.20.3-0ubuntu1

[Sebastien Bacher (seb128)]

could somebody using trusty try the update and comment on bug #1416891 about whether it resolves their issues?

[penalvch (penalvch)]

Sebastien Bacher, I would test Trusty, but my only instance of it is using Kubuntu (due to how Ubuntu doesn't support RDP as per LP#1251281), and Kubuntu doesn't natively support AFP. I'm using Utopic (gnome-session-flashback) on my main laptop, so I'll have to wait for when the fix lands in Utopic Proposed.