gvfsd-smb-brows uses 100% cpu after selecting Places-->Network

[stop]

Binary package hint: samba

When I select Places-Network and then double click the "Windows Network" directory I get a pop-up saying: "Opening Windows Network You can stop this operation by clicking cancel.
CPU usage goes up to 100% (gvfsd-smb-brows is causing this). It does not matter how long I wait, nothing changes.
When I click cancel on the dialog, the dialog goes away but CPU stays at 100%.
After a really long time (20 minutes) I get the following dialog:
Unable to mount location
DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

If I click on OK on that dialog it goes away but CPU stays at 100%.

So I can't enter the windows network and CPU usage is 100%.

ProblemType: Bug
Architecture: amd64
Date: Thu Mar 4 18:02:42 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Package: samba (not installed)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
RelatedPackageVersions:
 nautilus 1:2.29.91-0ubuntu2
 gvfs 1.5.4-0ubuntu1
SambaClientRegression: Yes
SourcePackage: samba
Uname: Linux 2.6.32-15-generic x86_64

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-client.

[stop (whoopwhoop)]

Did this use to work properly with a previous release ?
This was never tested.

dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba:
libsmbclient 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
libsmbclient-dev 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
libwbclient0 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
samba-common 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
samba-common-bin 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
smbclient 2:3.4.6~dfsg-1ubuntu1 samba install ok installed

How is the remote share accessed from the Ubuntu system?
nautilus

Connecting with smbclient
this works

smbclient -L //:
Domain=[EBOX] OS=[Unix] Server=[Samba 3.4.0]

[Sergey Sedov (serg-sedov)]

I have same problem with Ubuntu 10.04

test@ubuntu:~$ dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
libsmbclient 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
libwbclient0 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
samba-common 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
samba-common-bin 2:3.4.6~dfsg-1ubuntu1 samba install ok installed
smbclient 2:3.4.6~dfsg-1ubuntu1 samba install ok installed

test@ubuntu:~$ smbclient -L //192.168.0.3

Enter test's password:
Domain=[HOME] OS=[Unix] Server=[Samba 3.4.2-1.1.3.1-2229-SUSE-SL11.2]

 Sharename Type Comment
 --------- ---- -------
 IPC$ IPC IPC Service (server)
 Media Disk

N.B. it works well with Ubuntu 9.10

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[stop (whoopwhoop)]

Done:
https://bugzilla.gnome.org/show_bug.cgi?id=612202

[Jean-Louis Dupond (dupondje)]

Having the same issue here on Lucid.

[Sebastien Bacher (seb128)]

could be similar to bug #538764

[axoin (axoin)]

Sebastien, I do have #538764, but I tested and can not confirm this smb bug. Lucid 10.03 alpha3

[NoOp (glgxg)]

Same issue w/lucid fully updated as of today. Nautilus: I either end up having to kill gvsd-smb (if attempting to connect via 'Go To:smb://<ipaddress>/<sharedfolder>, or kill gvfsd-smb-browse (if attempting to brows using 'Go Network|Windows Network').

It's a clean test machine - let me know what further information/tests you'd like to help troubleshoot this. Note: I see this as a blocker/stopper for final lucid release.

[Karl Larsen (klarsen1)]

 I see this bug with my Lucid 64bit which includes all updates from Alpha to today. It is a serious BUG!

[NoOp (glgxg)]

On 03/15/2010 04:15 PM, NoOp wrote:
> Same issue w/lucid fully updated as of today. Nautilus: I either end up
> having to kill gvsd-smb (if attempting to connect via 'Go
> To:smb://<ipaddress>/<sharedfolder>, or kill gvfsd-smb-browse (if
> attempting to brows using 'Go Network|Windows Network').
>
> It's a clean test machine - let me know what further information/tests
> you'd like to help troubleshoot this. Note: I see this as a
> blocker/stopper for final lucid release.
>

Sebastien, I went into Seahorse (Applications|Accessories|Passwords and
Encryption Keys) and deleted the two previously stored session passwords
for the smb access. The smb browse worked using 'Go Network|Windows
Network'. I got the password prompt for the network share & was able to
mount the share. However after unmounting I cannot repeat;
gvfsd-smb-browse takes the cpu to 51%, I get the 'Opening "MSHOME" you
can stop this operation by clicking cancel.' popup & there it hangs.

If I kill gvfsd-smb-browse *and* nautilus (again with no remaining
passwords in seahorse), restart nautilus via Places|Network the Windows
Network et al works, including getting the password popup.

This time I repeat the process only I've selected the remember password
until logout option. Unmount the share, try Go|Network|Windows
Network|MSHOME|<remotename>|<remoteshare> and get 'Opening
"<remoteshare>" You can stop this operation by clicking cancel.'.
Kill gvfsd-smb and close Nautilus. I notice that no password has been
saved in seahorse.
  Reopen Nautilus via Places|Network and the share doesn't open & other
results are the same (not working, high cpu etc).
Note that when I kill gvfsd-smb I get the 'Unable to mount location
DBus error org.freedesktop.DBus.error.NoReply: Message did not receive a
reply (timeout by message bus)' error.

[NoOp (glgxg)]

On 03/15/2010 05:32 PM, NoOp wrote:
> On 03/15/2010 04:15 PM, NoOp wrote:
>> Same issue w/lucid fully updated as of today. Nautilus: I either end up
>> having to kill gvsd-smb (if attempting to connect via 'Go
>> To:smb://<ipaddress>/<sharedfolder>, or kill gvfsd-smb-browse (if
>> attempting to brows using 'Go Network|Windows Network').
>>
>> It's a clean test machine - let me know what further information/tests
>> you'd like to help troubleshoot this. Note: I see this as a
>> blocker/stopper for final lucid release.
>>
>
> Sebastien, I went into Seahorse (Applications|Accessories|Passwords and
> Encryption Keys) and deleted the two previously stored session passwords
> for the smb access. The smb browse worked using 'Go Network|Windows
> Network'. I got the password prompt for the network share & was able to
> mount the share. However after unmounting I cannot repeat;
> gvfsd-smb-browse takes the cpu to 51%, I get the 'Opening "MSHOME" you
> can stop this operation by clicking cancel.' popup & there it hangs.
>
> If I kill gvfsd-smb-browse *and* nautilus (again with no remaining
> passwords in seahorse), restart nautilus via Places|Network the Windows
> Network et al works, including getting the password popup.
>
> This time I repeat the process only I've selected the remember password
> until logout option. Unmount the share, try Go|Network|Windows
> Network|MSHOME|<remotename>|<remoteshare> and get 'Opening
> "<remoteshare>" You can stop this operation by clicking cancel.'.
> Kill gvfsd-smb and close Nautilus. I notice that no password has been
> saved in seahorse.
> Reopen Nautilus via Places|Network and the share doesn't open & other
> results are the same (not working, high cpu etc).
> Note that when I kill gvfsd-smb I get the 'Unable to mount location
> DBus error org.freedesktop.DBus.error.NoReply: Message did not receive a
> reply (timeout by message bus)' error.
>

Added data points:

1. Did a shutdown & cold boot. Opened Applications|Accessories|Passwords
and Encryption Keys
and found that there was a session password saved. Deleted it.

2. Opened Places|Network|Windows Network & got the same
(gvfsd-smb-browse taking 50% - status sleeping) & had to kill the process.

3. Then went to a bookmark with the previously successful connection -
that works (gives password popup, etc). However, unmounting & trying the
bookmark again goes back to the same issue.

4. Close nautilus. Places|Home Folder| try the bookmark again - same
issue. Note: there is no new record of the password entered from #3
above. But... I logout & log backin & *do* find a 'Passwords:session_1'
entry in seahorse. Delete that and the bookmark works.

So no idea how to troubleshoot further. Looks to be an issue with the
keyring/seahorse & samba/gvfsd.

[Sebastien Bacher (seb128)]

bug #530605 seems similar to this one

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[NoOp (glgxg)]

gvfs have no dbg symbols. Should I try using the '-dbgsym' method?

[Sebastien Bacher (seb128)]

> gvfs have no dbg symbols. Should I try using the '-dbgsym' method?

yes

[NoOp (glgxg)]

OK. First of all the attempts to add the keys per http://wiki.ubuntu.com/DebuggingProgramCrash fails. However I did manager to add the key from http://ddebs.ubuntu.com/dbgsym-release-key.asc and load the dbgsym's for all that I could find in gvfs. Unfortunately I do not think that I am doing the backtrace correctly. Attached is my file for the attempt. Note: at the end I tried to Ctrl-C out of gdb, but ended up killing it from another terminal. Advise please.

[NoOp (glgxg)]

Each time I attempt to add the plain text file I get launchpad errors:

Unexpected form data

Launchpad doesn't understand the form data submitted in this request.

[NoOp (glgxg)]

I put it up on pastebin instead:
http://pastebin.com/t7tD0N4a

[Sebastien Bacher (seb128)]

there is not stracktrace in this log, you didnt do the "backtrace" part in gdb

[NoOp (glgxg)]

On 03/16/2010 01:16 PM, Sebastien Bacher wrote:
> there is not stracktrace in this log, you didnt do the "backtrace" part
> in gdb
>

2nd attempt w/backtrace part on:
http://pastebin.com/UFKuTTxu

[Sebastien Bacher (seb128)]

could you install libgnome-keyring0-dbgsym and get a new stacktrace too?

[Sebastien Bacher (seb128)]

having steps on how to trigger the issue on a new installation or livecd would be useful too there

[NoOp (glgxg)]

On 03/16/2010 01:52 PM, Sebastien Bacher wrote:
> could you install libgnome-keyring0-dbgsym and get a new stacktrace too?
>
Will do. Note: I'm actually rebooting - probably not necessary but want
to clear everything before the new trace.

[NoOp (glgxg)]

On 03/16/2010 02:22 PM, NoOp wrote:
> On 03/16/2010 01:52 PM, Sebastien Bacher wrote:
>> could you install libgnome-keyring0-dbgsym and get a new stacktrace too?
>>
> Will do. Note: I'm actually rebooting - probably not necessary but want
> to clear everything before the new trace.
>

Backtrace with libgnome-keyring0-dbgsym:

http://pastebin.com/YMS4sppa

[NoOp (glgxg)]

Added note: when I attempt to use the 'continue' command in gdb, gdb hangs. Even Ctrl-C doesn't change it. Hence the command has been skipped. Also, I note that as soon as I finish the 'attache <pid>' command, the process (gvfs-smb-browser) drops back to only about 2% cpu. If I then add the 'continue' command the process goes back up to approx 99%. Any suggestions?

[NoOp (glgxg)]

Another interesting find: If after booting (I've been rebooting between
tests) I select Places|<bookmarkedsmblocation> I immediately get the
password prompt for <bookmarkedsmblocation> and can connect w/o issue.
The share gets mounted (it's on an 9.10 machine), nautilus comes up
properly, cpu is behaved, gvfsd-smb is taking 0%, etc. I've repeated
this 5 times (shutdown the machine each time before tests).

Now, while in the same nautilus, I use 'Go|Network|Windows
Network|MSHOME (same as the already mounted smb location)| cpu
skyrockets and gvfsd-sm-browse takes 60-94% cpu & I need to kill
gvfsd-sm-browse. Note that the <bookmarkedsmblocation> is still mounted
& nautilus continues working just fine afterwards.

[Michael Lueck (mlueck)]

Subscribe

Seems this bug is actually the root cause of one I turned in:

"Creating a GUI shortcut to a Samba share, password dialog never appears, PID's stuck in process list"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/538250

[NoOp (glgxg)]

On 03/16/2010 05:09 PM, NoOp wrote:
> Another interesting find: If after booting (I've been rebooting between
> tests) I select Places|<bookmarkedsmblocation> I immediately get the
> password prompt for <bookmarkedsmblocation> and can connect w/o issue.
> The share gets mounted (it's on an 9.10 machine), nautilus comes up
> properly, cpu is behaved, gvfsd-smb is taking 0%, etc. I've repeated
> this 5 times (shutdown the machine each time before tests).
>
> Now, while in the same nautilus, I use 'Go|Network|Windows
> Network|MSHOME (same as the already mounted smb location)| cpu
> skyrockets and gvfsd-sm-browse takes 60-94% cpu & I need to kill
> gvfsd-sm-browse. Note that the <bookmarkedsmblocation> is still mounted
> & nautilus continues working just fine afterwards.
>

Another point: If while in nautilus and 'Go|Network|Windows
Network' and I kill gvfsd-smb-browse, and then try again
('Go|Network|Windows Network') I then get 'MSHOME', double-clic on that,
kill gvfsd-smb-browse again, and then double-click on MSHOME again I get
to <remotehost>, double-click on that and I get <remotesharename(s)>,
double-click on that and I _finally_ get the password prompt. Enter the
username/password for the remotehost & the smb share gets mounted. From
there on out all works. Again, I've repeated this several times from
reboot, restart, and from logout/login.

[Mycohl (mycohl)]

This appears to be happening on my machines when any of the gvfsd modules try to access the keyring, not just the samba module. Someone already submitted another bug here about it:

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/538764

Has anyone submitted this more general form of the issue to gvfs' bugzilla? All I can find are the smb-related entries.

[christian (chmathieu)]

hello !

I have exactly the same bug with sftp !
(I think it is not a samba bug)

[Brandon Elliott (brelliott)]

I have this problem upon boot; however, I can kill all instances of gvfs*, browse back to the bookmarked share and all is well.

[Martin Soto (soto255)]

Hi!

The behavior I'm observing here is different for SSH (ssh: and sftp: URIs) and for SMB. In the SSH case, the gvfs-sftp process hangs when the password is already in Seahorse. If I go to Seahorse and delete the password, however, I get a password prompt again and can login. Indeed, if I ask the system to not store the password, I can keep accessing the directory by typing the password again every time.

In the SMB case on the other hand, I can delete the passwords from Seahorse but that doesn't prevent the gvfs-smb process from hanging. I have tried typing the smb: URI directly or using shortcuts but nothing seems to help.

[Sebastien Bacher (seb128)]

could people having the issue get a stacktrace?

[Sebastien Bacher (seb128)]

the bug seems to be bug #530605, let's use this one