I've noticed that this problem of gvfsd-smb taking up 50% of my CPU
(100% of 1 of 2 cores) only exists if I am not logged in to a Windows
share first via the terminal. In other words, I have Windows shares I
like to access with my Linux computer running Xubuntu 16.04. If I open
nemo (my main file manager I like) and click on "Network" on the left-
hand side, then click on my Windows computer name ("Gabriel-Toshiba" in
my case), gvfsd-smb locks up my CPU.*However,* if I *first* mount one of my windows shares via the terminal with this command: "sudo mount -t cifs //192.168.0.106/dev /home/gabriel/mnt/test -o username=gabriel,uid=gabriel,gid=gabriel" and *then* navigate through my network via nemo, it works fine (I am able to actually navigate into my network shares, including others I did *not* mount), and it does NOT take up 100% of one of my CPUs! So, that's my work-around for now: use the terminal to mount a share before trying to click around the Network in a file manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1409032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
