Ubuntu
gvfs package

Connecting to smb mount fails - gvfsd-smb just eats CPU

Bug #631960 reported by Zordid
248
This bug affects 42 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Fix Released
High
Unassigned
Maverick
Fix Released
High
Unassigned

Bug Description

Binary package hint: gvfs

With Ubuntu 10.04 I was always able to connect to an SMB mountpoint which is served by a netdrive (FRITZ!Box with USB Device attached) Its location is //fritz.box/fritz.nas/name-of-device.
Now, with 10.10 all I get when trying to connect is CPU load going up with a process called "gvfsd-smb" using almost 100% CPU, but nothing happens. When I kill this process, a dialog informs me that the connection failed...

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gvfs-backends 1.6.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 6 23:11:42 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-smb
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
SourcePackage: gvfs

See original description

Related branches

lp:ubuntu/maverick/gvfs
Revision history for this message
Zordid (zordid-gmx) wrote :
description: updated
Pedro Villavicencio (pedro)
Changed in gvfs (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Kristopher Ives (krisives) wrote :

Same for me, but in 32-bit

Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream says it's due to the recent gconf changes to use gdbus and similar to https://bugzilla.gnome.org/show_bug.cgi?id=628889, it should be fixed this week and for GNOME 2.32 tarballs

Changed in gvfs (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Jonathan Dotson (dotson83) wrote :

Is there a way to downgrade gconf (without taking out half the system) until the fix is released?

Revision history for this message
nilsja (nilsjansen) wrote :

i am also very interested in a way to downgrade

Revision history for this message
Jonathan Dotson (dotson83) wrote :

I learned that if you mount the share via command line first you can browse as normal. This kinda sucks but it's a workaround until they fix it I guess.

Revision history for this message
Greg Ryman (ryman-greg) wrote :

I've been using Dolphin to do my network shares.

Revision history for this message
Peter (pry) wrote :

Confirm here. This problem existed in Karmic and some other Ubuntu distros as well (can't remember which ones). Is it a regression?

Revision history for this message
Sebastien Bacher (seb128) wrote :

If you have issues in karmic that's a different bug

Revision history for this message
BuM (bumaw) wrote :

same problem

dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba

libpam-smbpass 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
libsmbclient 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
libwbclient0 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
samba 2:3.5.4~dfsg-1ubuntu4 install ok installed
samba-common 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
samba-common-bin 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
samba-dbg 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
smbclient 2:3.5.4~dfsg-1ubuntu4 samba install ok installed
winbind 2:3.5.4~dfsg-1ubuntu4 samba install ok installed

Revision history for this message
Sebastien Bacher (seb128) wrote :

gvfs (1.6.3-0ubuntu2) maverick; urgency=low

  * debian/patches/git_gconf_init.patch:
    - backport upstream commit to fix locking issues (lp: #631960)

Changed in gvfs (Ubuntu Maverick):
status: Triaged → Fix Released
Revision history for this message
BuM (bumaw) wrote :

no problem everything works

dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep gvfs

gvfs 1.6.3-0ubuntu2 install ok installed
gvfs-backends 1.6.3-0ubuntu2 gvfs install ok installed
gvfs-bin 1.6.3-0ubuntu2 gvfs install ok installed
gvfs-fuse 1.6.3-0ubuntu2 gvfs install ok installed
libgvfscommon0 1.6.3-0ubuntu2 gvfs install ok installed

Revision history for this message
Kristopher Ives (krisives) wrote :

Fix #11 works for me!

+1 Sebastien

Revision history for this message
Mark Kaehny (kaehny) wrote :

Fix #11 as embodied in patches as of 2010-09-12 also fix it for me. And the lessening of cpu smoke is noticable (that is, the fact that the CPU doesn't go nuts anymore makes everything else a bit better).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.