GNOME Bugzilla – Bug 611584
gvfs won't mount samba share in Ubuntu 10.04 alpha. gvfsd-smb using 100% CPU.
Last modified: 2010-04-17 11:33:13 UTC
Please see launchpad bug here: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/530605 I've been asked to report this upstream. Trying to mount a samba share using "gvfs-mount smb://server/home". Works fine in Ubuntu 9.10. In the latest 10.04 alpha release this command just hangs about 75% of the time and gvfsd-smb starts using 100% CPU until killed. Once I kill the process I get a dialogue about the server not responding. I have also tried using "gvfs-mount smb://server.local/home" and get the same results. This is also reproducible using the menu Places | Connect to Server, but browsing directly to the share in Nautilus via the Network bookmark seems to work all the time. The share I am connecting to is on a Debian server running samba and I have no problems connecting to this share in Windows or Ubuntu 9.10. Description: Ubuntu lucid (development branch) Release: 10.04 gvfs: Installed: 1.5.4-0ubuntu1 Candidate: 1.5.4-0ubuntu1 Version table: *** 1.5.4-0ubuntu1 0 500 http://gb.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 CheckboxSubmission: d6a9fb5d438b37af50efc2e4853fca15 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Tue Mar 2 11:11:29 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) NonfreeKernelModules: nvidia Package: gvfs 1.5.4-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic-pae SourcePackage: gvfs Uname: Linux 2.6.32-14-generic-pae i686 [EDIT] I forgot to mention, I can't find anything in any log file that would explain why this is happening.
This also occurs for me with gvfs-sftp. The logs do not indicate anything, and the process gvfs-sftp eats 100% CPU until killed.
Ditto here
Affects me too, on two desktop system, it works on my Compaq Mini 110.
Can you please attach a backtrace of the failing process?
(In reply to comment #4) > Can you please attach a backtrace of the failing process? I have the same problem. Also on a Ubuntu 10.04 alpha 3. A stacktrace of gvfsd-smb while it is using 100% CPU looks like the following: $ pstack 5191 5191: /usr/lib/gvfs/gvfsd-smb --spawner :1.8 /org/gtk/gvfs/exec_spaw/8 (No symbols found) 0x0057d422: ???? (938d400, 7, ffffffff, 37dff4, 931add0, 37dff4) 0x0030539b: ???? (938d400, 7, ffffffff, 938d400, 7, bfb6ede4) + 60 0x002f7eff: ???? (1, 93123f0, 1, 0, 1, 804a914) + 30 0x002f861f: ???? (931b4c8, 0, 8066aab, 31fafe, 9311b40, 806a57c) + 50 0x080530ba: ???? (4, bfb6ef94, 1, 8066aab, 0, 8066aab) + 10 0x080533c6: ???? (4, bfb6ef94, bfb6efa8, b773d830, bfb6ef50, ffffffff) + 60 0x00c54bd6: ???? (8053370, 4, bfb6ef94, 8066570, 8066560, 45e0b0) + 40491078 The gvfsd-smb process was started by opening a bookmarked samba-share in Nautilus.
you have no symbol there, could you install gvfs-dbgsym gvfs-backends-dbgsym and get a stacktrace with those?
I'd like to help, but I don't know of an equivalent to pstack on PowerPC or x86_64.
(In reply to comment #7) > I'd like to help, but I don't know of an equivalent to pstack on PowerPC or > x86_64. First install debugging symbols for gvfs and glib2 packages. When the process starts eating 100% CPU, fire up gdb, attach to the process (gdb <executable> <PID>) and grab a backtrace by typing "t a a bt".
Here's a stacktrace. The gvfs-smb process was started from a bash script that runs gvfs-mount.
+ Trace 221007
(In reply to comment #6) > you have no symbol there, could you install gvfs-dbgsym gvfs-backends-dbgsym > and get a stacktrace with those? I don't have those packages in Ubuntu. I have been stuggeling with pkg-create-dbgsym to build them, but unsuccesfull this far. Hints are appreciated.
@Thomas, Follow these instructions: https://wiki.ubuntu.com/DebuggingProgramCrash Then: sudo apt-get install gvfs-dbgsym gvfs-backends-dbgsym Run gvfs gdb <executable> <PID> t a a bt
Thanks for the debugging help, guys! Here's s stack trace from gvfs-sftp:
+ Trace 221013
Sort of looks to me like it's hanging while trying to talk to gnome-keyring to get a password.
Created attachment 156584 [details] Stacktrace Thanks for the instructions Darren. Here's my stacktrace. gvfsd-smb was started by opening a bookmarked samba-share in the "Places" menu in Ubuntu.
Don't know if this helps, but after upgrading to ubuntu 10.04Beta I began experiencing the same or a similar problem. I just cleared it a little while ago when I discovered that the upgrade had removed Samba. After installing Samba all is working fine again.
Unfortunately, that doesn't seem to be quite the problem for me. I too, started seeing this after upgrading to 10.04 beta, but I still have Samba installed, and it happens for me with sftp, too.
I can't see why installing Samba would work as that is the server package rather the client one. Anyway, it doesn't work for me either and it's a Samba share I'm trying to connect to.
In addition to installing samba, I found the following installed on a working system and had to install them also. gvfs-backends gvfs-bin gvfs-fuse nautilus-share I don't know they were relevant to the problem or not as I was just shooting in the dark, but I no longer have a problem or high cpu usage.
No joy, all those packages are already install :(
Thomas, thanks for the stack trace. What would really help is if you install the debug symbols for libdbus, and then again get a stack trace for all threads in that process. Thanks in advance!
Created attachment 157016 [details] Stacktrace Here's a new stack trace with dbus symbols. Hope it helps. Thank you for looking into this issue.
Created attachment 157161 [details] Stacktrace Another stracktrace from https://bugzilla.redhat.com/show_bug.cgi?id=573202#c21 User also reports high CPU usage... going to debug more.
bug #613399 is a similar issue and has a change to try, I've uploaded an update to ubuntu lucid with the change now to give it testing...
the change on this bug seems to not be working
should the bug be reassigned to gnome-keyring?
(In reply to comment #24) > the change on this bug seems to not be working Confirmed. I still have the issue with this version: $ wajig status libgnome-keyring0 Package Installed Previous Now State =======================-===============-===============-===============-===== libgnome-keyring0 2.29.4git20100322-0ubuntu3 2.29.4git20100322-0ubuntu3 2.29.4git20100322-0ubuntu3 install
Also packaged in Fedora, no change.
*** This bug has been marked as a duplicate of bug 606902 ***
I still have no clue how to debug. I have installed debugging stuff, i get problems with those debbs repos. I can run gdb , bu i do not understand which executable name and pid i need to use to debug this. If anyone has a link to where this with more info, please let me know.
Works for me in Ubuntu 10.04beta after today's updates.