gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.

Bug #530605 reported by DarrenShare on 2010-03-02
616
This bug affects 178 people
Affects Status Importance Assigned to Milestone
Ubuntu One Client
Critical
Rodney Dawes
desktopcouch
Critical
Chad Miller
gvfs
Invalid
High
desktopcouch (Ubuntu)
High
Unassigned
Lucid
High
Unassigned
gvfs (Fedora)
Unknown
Unknown
gwibber (Ubuntu)
High
Unassigned
Lucid
High
Unassigned
libgnome-keyring (Ubuntu)
High
Sebastien Bacher
Lucid
High
Sebastien Bacher
ubuntuone-client (Ubuntu)
Undecided
Unassigned
Lucid
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

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.

Related branches

DarrenShare (darren-moorstreet) wrote :
description: updated
Sebastien Bacher (seb128) wrote :

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)

Changed in gvfs (Ubuntu):
importance: Undecided → Low
Changed in gvfs (Ubuntu):
status: New → Triaged
axoin (axoin) wrote :

i can confirm that on 10.04 alpha 3

DarrenShare (darren-moorstreet) wrote :

Hey axion, can you also add your +1 to the bug on Bugzilla? The more the merrier (and the more attention it will get).

MichaelB (mrbou) wrote :

I have the same problem (Lucid Alpha 3). Work with share folder "without authentication" BUT fail with authentication (gvfsd-smb 100% cpu). I have only shared smb folder (NAS) with authentication.. I really hope this bug will be fixed for Lucid release.

Sebastien Bacher (seb128) wrote :

is that a duplicate of bug #532024?

Changed in gvfs (Ubuntu Lucid):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
DarrenShare (darren-moorstreet) wrote :

@Sebastien. It Seems to the same bug. This one was raised first though so technically it's a duplicate of this one ;)

I am concerned by the lack of official response to any of these bugs by the Gnome team. Given that mounting shares is pretty much gvfs' sole function you'd think they'd be looking at it by now. This is a total showstopper for me with regard to using Lucid.

Sebastien Bacher (seb128) wrote :

Could you try to get a stacktrace of gvfsd-smb while it's using cpu?

Thomas Poulsen (thomas-lha66) wrote :

I'm having the same problem as reported in Bug #536790.

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.

Martin Pitt (pitti) on 2010-03-16
Changed in gvfs (Ubuntu Lucid):
assignee: Canonical Desktop Team (canonical-desktop-team) → Martin Pitt (pitti)
Geoffrey Pursell (geoffp) wrote :

I'm getting this when trying to load up a bookmark of an ssh server, which is a very common use case for me.

Stacktrace of gvfsd-smb:
1923: /usr/lib/gvfs/gvfsd-smb --spawner :1.6 /org/gtk/gvfs/exec_spaw/3
(No symbols found)
0x003d4422: ???? (93f81f0, 7, ffffffff, 587ff4, 93cbec0, 587ff4)
0x0050f32b: ???? (93f81f0, 7, ffffffff, 93f81f0, 7, bfff6794) + 60
0x00501e5c: ???? (1, 93c3978, 1, 0, 1, 804a914) + 30
0x005025c7: ???? (93cc5c8, 0, 8066aab, 5299ee, 93c33b8, 806a57c) + 50
0x080530ba: ???? (4, bfff6944, 1, 8066aab, 0, 8066aab) + 10
0x080533c6: ???? (4, bfff6944, bfff6958, b7798830, bfff6900, ffffffff) + 60
0x0059fbd6: ???? (8053370, 4, bfff6944, 8066570, 8066560, 3880b0) + 400096c8

danbuntu (danattwood) wrote :

I can confirm as well that I am seeing the same problem. 2 out of three of my gvfs share will mount though the 3rd won't. All three cause 100% cpu usage.

apinunt (apinunt) wrote :

I found that Samba was no longer installed, and after installing it everything now seems to work properly, and no high cpu usage.

Sebastien Bacher (seb128) wrote :

could somebody getting the issue get a stracktrace of gvfsd-smb while it's eating cpu

Sebastien Bacher (seb128) wrote :

Changing the settings, quite some users get the issue, could be due to gnome-keyring I emailed upstream about it now

Changed in gvfs (Ubuntu Lucid):
importance: Low → High
Martin Soto (soto255) wrote :

I already posted to Bug #532024 with my symptoms. I'm attaching a backtrace of the running gvfsd-smb process. It seems to hang while trying to contact gnome-keyring-daemon. I tried to make the backtrace as complete as possible symbol-wise, but let me know if I can provide more info. The issue is 100% reproducible here.

Martin Soto (soto255) wrote :

Here is a backtrace of gnome-keyring-daemon taken while the gvfsd-smb process was hanging. I don't see anything strange here, though.

Majestyx (majestyx) wrote :

no smb, no usb, but a (not really existent) fd0 ;)

Sebastien Bacher (seb128) wrote :

The issue is rather a libgnome-keyring one and there is a change to try on bugzilla.gnome.org now which I will upload to lucid today

affects: gvfs (Ubuntu Lucid) → libgnome-keyring (Ubuntu Lucid)
Changed in libgnome-keyring (Ubuntu Lucid):
assignee: Martin Pitt (pitti) → Sebastien Bacher (seb128)
Sebastien Bacher (seb128) wrote :

the lucid version has been updated with the change to try now, could the users having the issue update to this new version, restart their session and comment on the bug to say if that solves the issue or not

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgnome-keyring - 2.29.4git20100322-0ubuntu3

---------------
libgnome-keyring (2.29.4git20100322-0ubuntu3) lucid; urgency=low

  * debian/patches/01_upstream_gvfsd_cpu_use.patch:
    - upstream change which could be solving the gvfsd eating cpu issue
      (lp: #530605)
 -- Sebastien Bacher <email address hidden> Mon, 29 Mar 2010 13:46:46 +0200

Changed in libgnome-keyring (Ubuntu Lucid):
status: Triaged → Fix Released

@Sebastien

I'm still waiting for the update to come through here. I'm still on libgnome-keyring version 2.29.4git20100322-0ubuntu2.

Jean-Philippe Fleury (jpfle) wrote :

Sebastien Bacher wrote:
>the lucid version has been updated with the change to try now,
>could the users having the issue update to this new version,
>restart their session and comment on the bug to say if that
>solves the issue or not

I updated to libgnome-keyring 2.29.4git20100322-0ubuntu3 and it fixed the problem. Thanks!

timosha (timosha) wrote :

The bug is not completely resolved with the latest libgnome-keyring. I can open one (1) password protected samba share and are prompted for username and password. When I select "remember" forever gvfsd-smb hangs with 100% CPU load when I try to open another password protected samba share.

When I delete the key in Seahorse the whole thing starts all over again. In noticed in Seahorse that the password is stored as "use: Saved password or login" in Ubuntu 9.10 the password is store as "Network Credential" with a network icon in front of the password.

Tested this on 3 machines: Thinkpad R51 & R52 and HP dx2400.

Sebastien Bacher (seb128) wrote :

the new comment could be an another issue, could you get a stracktrace from this one, let's see how it works for the issue other users were having before and open a new one about this bug if the update works for some users

Martin Soto (soto255) wrote :

In my case, the problem persists after the update. I'm attaching a backtrace. Unfortunately, the symbols are incomplete because the -dbgsym package for gvfs-backends hasn't been updated to the current version in Lucid (1.6.0). If nobody beats me to it, I'll upload an updated backtrace when the debugging symbols become available.

axoin (axoin) wrote :

 the patch doesn't do anything for the problems with s/ftp. Version libgnome-keyring0:
  Installiert: 2.29.4git20100322-0ubuntu3
  Kandidat: 2.29.4git20100322-0ubuntu3
gvfs
 Installiert: 1.6.0-0ubuntu

However, I cannot get any libgnome-keyring0-dbgsym so I can't make a new stacktrace.
I also took a look in seahorse like timosha and I have the same behaviour. Credentials are only stored as "password" and not as "network credentials".

Sebastien Bacher (seb128) wrote :

did you restart your session before trying?

timosha (timosha) wrote :

@Sebastien

I did not only restart the session on 3 machines, I rebooted them after the updates. The problem persists.

Changed in libgnome-keyring (Ubuntu Lucid):
status: Fix Released → Triaged
Sebastien Bacher (seb128) wrote :

> I did not only restart the session on 3 machines, I rebooted them after the updates. The problem persists.

seems you have some easy way to trigger the issue, could you share the steps and describe your scenario there? it could be useful to get the issue worked. do you use autologin or not? does that make a difference? is your keyring unlocking when using the share? ie did you run an application using it (seahorse, empathy, ...) before triggering the bug? do you get the issue when browsing smb shares too or only when connecting to one? do you need to add the password to the keyring before? is the issue specific to smb shares or to gvfs locations?

timosha (timosha) wrote :

1) Delete all keys for smb and ftp shares in Seahorse;
2) Connect to password protected samba share #1 - You are prompted for a username and password - Enter username and password and click "remember forever" - Password protected share #1 opens now;
3) Connect to password protected samba share #2 - gvfsd-smb sleeps now with 100% CPU load;
4) Unmount password protected share #1 - reconnect to password protected share #1 - another gvfsd-smb hangs with 100% CPU load;
5) Kill the two (2) gvfsd-smb processes - Delete the password in Seahorse;
6) Go to step 1) and the scenario starts again;

Ditto for ftp, in that case gvsfd-ftp hangs/sleeps with 100% CPU load;

I do not use autologin, but will try that;
The keyring is probably not unlocking as I don't see the key icon in the taskbar;
The keyring works fine in providing a WEP key for WLAN at login;
The keyring works fine in providing credentials for aMSN;
The keyring DOES NOT WORK providing credentials for Ubuntuone;

This issue is typical for PASWORD PROTECTED smb shares, non protected shares mount fine. Ditto for ftp.

I entered the password for the keyring the first time I used it after installing Lucid. I was prompted for it;

timosha (timosha) wrote :

Another test:

On exactly the same machine, a Thinkpad R51 - 2887, I inserted an UltrayBay with Ubuntu 9.10 on the hdd. On this installation the problem does not occur. I upgraded this installation to Lucid 10.04. The problem does not occur after the upgrade. The keys in Seahorse are stored as "Network Credentials" with the particular network icon.

axoin (axoin) wrote :

sebastien, I described the same steps to reproduce already in Bug #538764 which you marked as duplicate.
timosha, I confirm the steps to reproduce and I may add that it is the same for sftp shares too.
However, my system is an upgraded 9.10 to 10.04 and it is a Thinkpad T43 and I am still expieriencing this bug.
I have also problems with ubuntuone-login
If there were -dbgsyms I could add another stacktrace, when will they be available?

Jean-Philippe Fleury (jpfle) wrote :

Ok, I still have the bug. Here's how I can reproduce it:

1) Delete all keys for FTP locations in Seahorse.

2) Connect to a FTP location that is protected by password. Enter the username and the password and choose to remember forever. The location opens well.

3) I can open multiple FTP locations as described in the step 2. There's no problem. All FTP locations open well.

4) Unmount all previously open FTP locations.

5) Try to open again a FTP location previously accessed on the steps 2 or 3.

Actual result: gvfsd-smb starts using 100% CPU.

axoin (axoin) wrote :

gvfs Version 1.6.0-0ubuntu1
libgnome-keyring 2.29.4git20100322-0ubuntu3
New gdb backtrace

axoin (axoin) wrote :

sorry, wrong attachment see new with
    *

gvfs Version 1.6.0-0ubuntu1
libgnome-keyring 2.29.4git20100322-0ubuntu3
New gdb backtrace

timosha (timosha) wrote :

I made another observation:

I have an UbuntuOne Token in my keyring. When I open Ubuntuone the process "ubuntuone-login" sleeps with 100% CPU load until I kill the process.

Garazi (garazi111) wrote :

Issue is not repared for me.
Here is a backtrace.
Tell me what to do if it is not enough explicit.

Andrew Fenn (andrewfenn) wrote :

I upgraded just now and confirmed I had the latest packages described further up in the report. I rebooted then tested however I am still getting the same issues. The CPU maxes out the moment I try to connect to a samba share. This happens even if I delete the keys in seahorse.

Changed in desktopcouch (Ubuntu Lucid):
importance: Undecided → High
Changed in gwibber (Ubuntu Lucid):
importance: Undecided → High
status: New → Triaged
Changed in desktopcouch (Ubuntu Lucid):
status: New → Triaged
Rodney Dawes (dobey) on 2010-03-30
tags: added: u1-lucid
Changed in ubuntuone-client:
assignee: nobody → Rodney Dawes (dobey)
importance: Undecided → Critical
status: New → In Progress
Rodney Dawes (dobey) on 2010-03-30
Changed in ubuntuone-client:
status: In Progress → Fix Committed
mikbini (mikbini) wrote :

It still uses 100% cpu for me

apinunt (apinunt) wrote :

Just applied the following updates:
libcryptui0 (2.30.0-0ubuntu1)
python-kde4 (4:4.4.2-0ubuntu1)
seahorse (2.30.0-0ubuntu1)
seahorse-plugins (2.30.0-0ubuntu1)
Rebooted and opened seahorse. No entries found in seahorse.

1. tried to open network to another computer on the network - no problem.
2. tried to open an NAS drive (WD MyBook World II) - 100% CPU, canceled, killed gvfsd-smb -browse process
3. tried to open another NAS drive (WD sharespace) - keyring password requested - and was given access to the NAS drive

opened seahorse and found a number of entries had appeared.

4. Tried to access the 1st NAS drive again - still failed
5. Tried to access the 2nd NAS drive again - this time was able to see the folders on the NAS but couldn't open them & 100% CPU and had to kill gvfsd-smb this time.
6. tried to open network to another computer on the network - 100% CPU, killed gvfsd-smb-browse

mikbini (mikbini) wrote :

I just updated to seahorse 2.30.0-0ubuntu1 and, immediately after reboot and without launching anything else (no evolution, no empathy, although other things such as desktopcouch-service are running as they are started automatically by the session) I mounted an smb share successfully (I have bookmarked it in nautilus and the key is in seahorse in the default keyring, no password is required to access it) and used it a bit with no problems.

I then tried to mount another one, on the same server, and the cpu usage went 100%. I reboot, tried again the share which previously worked but the mount failed and gvsfd-smb started using 100% cpu. Tried some other times with both shares, logging out and in again, rebooting etc. but always with the same result: 100% cpu usage and mount fails.

It just seems that it sometimes randomly works but most times it doesn't.

timosha (timosha) wrote :

Status Quo: After all updates still the same scenario as in my post #32

mikbini (mikbini) wrote :

I'm attaching a backtrace of gwibber-service stuck at 100% cpu

mikbini (mikbini) wrote :

Sorry for the last post, I was going to post to bug #548540

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgnome-keyring - 2.30.0-0ubuntu3

---------------
libgnome-keyring (2.30.0-0ubuntu3) lucid; urgency=low

  * debian/patches/02_workaround_cpu_use.patch:
    - change from https://bugzilla.gnome.org/show_bug.cgi?id=606902
      to try to workaround extra cpu use issues (lp: #530605)
 -- Sebastien Bacher <email address hidden> Thu, 01 Apr 2010 15:58:01 +0200

Changed in libgnome-keyring (Ubuntu Lucid):
status: Triaged → Fix Released
Sebastien Bacher (seb128) wrote :

The new upload could be a workaround for the issue but since I don't get the bug often there I can't really say if it works, those who get the bug could you try how it's working for you and let us know by commenting there?

luca (l-savio) wrote :

still desktopcouch at 100%, sync contacts in Evolution not working, file sync ok (upgrdade 30 min ago)

It seems to be fixing my isses.

William Shotts (bshotts) wrote :

gvfsd-smb seems to be working now, but desktopcouch and gvfsd-sftp are still failing.

timosha (timosha) wrote :

The issue is not completely resolved. I can mount ONE samba share, but as soon as there is a password for this share in Seahorse I cannot mount it again. Then I get the message "Unable to mount location".

Apart from that, gvfsd-smb crashes on one machine. The crash cannot be reported with Apport.

The 100% CPU load is gone.

Scenario:
1) Delete password for the samba shares in Seahorse;
2) Mount samba password protected share #1 - Enter username & password - the samba share will mount;
3) Mount samba password protected share #2 - Message "Unable to mount location" - DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) immediately appears;
4) Unmount samba share #1 - re-mount samba share #1 - Message "Unable to mount location" - DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) appears immediately;
5) Delete all samba passwords in Seahorse;
6) Go to step 1 and the scenario starts over again;

NoOp (glgxg) wrote :

Nautilus Go|Network to a samba folder on other machines on the network is now working for me on the affected 32bit machines. I'll need to wait for the 64bit build to complete before that can be tested.

$ apt-cache policy libgnome-keyring0
libgnome-keyring0:
  Installed: 2.30.0-0ubuntu3
  Candidate: 2.30.0-0ubuntu3
  Version table:
 *** 2.30.0-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
$ uname -a
Linux gg 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux

Chad Miller (cmiller) wrote :

With desktopcouch:

2.29.4git20100224-0ubuntu2, works well. Though, perhaps something was introduced in this version. I got SEGVs ( Bug#524566 ) until I moved all keyring access into the first/main thread. This worked since before karmic release otherwise.

2.29.4git20100322-0ubuntu2, SEGV and ABRT on 80 of calls to keyring funcs.

2.29.4git20100322-0ubuntu3, no more SEGVs or ABRT, but eats all CPU on more than half of keyring calls.

2.30.0-0ubuntu2, same as 322-3.

Chad Miller (cmiller) wrote :

Test: Run /usr/lib/desktopcouch/desktopcouch-service (from package "desktopcouch") in a shell in X. Watch CPU. Hit Ctrl-\ to quit. Re-run. 50% to 80% of the time, it eats all CPU.

timosha (timosha) wrote :

Problem in gvfs-backends

The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.

Sebastien Bacher (seb128) wrote :

the change is supposed to fix the gvfs cpu use issue, if it does that's something. The desktopcouch issue could be a different one,
the gvfs crashes should get a new bug

mikbini (mikbini) wrote :

After the updates I have the same results as in comment #52: mount fails if the password is in seahorse (just for the sake of completeness: my smb group is not WORKGROUP).

desktopcouch-service cpu usage is now normal but gwibber-service still runs at 100% cpu (this is bug #548540, which is marked as a duplicate of this one).

axoin (axoin) wrote :

the patch does not bring any change to the gvfsd-sftp/ftp issue. Still full cpu usage if the password is stored in seahorse.
Additionally same problem as in comment #56.

Sergey Sedov (serg-sedov) wrote :

After latest update it works fine for me

Martin-Éric Racine (q-funk) wrote :

SMB finally works here too. Thanks for merging the upstream patch!

mikbini (mikbini) wrote :

I made some more trying and I found that, even with the password stored in seahorse, I can sometimes mount the smb share immediately after I log in.

Changed in libgnome-keyring (Ubuntu Lucid):
status: Fix Released → Confirmed
mikbini (mikbini) wrote :

After some more trying I found that the "Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)" message is not due to seahorse but to quickly unmounting and remounting shares (I'll report another bug for it) and that the smb mount 100% cpu problem seems solved for me.

NoOp (glgxg) wrote :

Same observation as mikbini (comment #63). Mount, 'Remember password until you log out', unmount, try to mount again and receive the Dbus error. mikbini, can you please post the new bug report number for this when you've filed it?

mikbini (mikbini) wrote :
PM (pm77) wrote :

This bug is not fixed yet: Still cannot reliable attach network shares.

I have had this ever since my first install of lucid (a few das before beta-1 release). Still cannot reliable attach network shares. At least 8 of then ends in "DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)". I have not seen the CPU@100% last couple of days.

Clean test machine with updates as of 5.april applied. WLAN conncention to network share. Network shares workes fine in Ubuntu 9.10.

PM (pm77) wrote :

Oups...Sorry...Didn't notice the #554103 bug, mentioned by mikbini. This seems to be the main problem for network shares connection issues. Not saving the passwords in keyring makes network shares work all right.

Vish (vish) wrote :

I was having a similar bug with evolution using high CPU, and Sebastien Bacher told this bug might be the main cause
Update libgnome-keyring (2.30.0-0ubuntu3) /might/ have fixed my evolution bug > Bug #527569

Garazi (garazi111) wrote :

I had to delete all my passwords in seahorse.
But after that, it is working nice again even with password protected samba shared folders.

Majestyx (majestyx) wrote :

i have the : libgnome-keyring 1.0.0-2 install. if i will start firefox (from a shell) as gksu (or gksudo) - no works. if i will mount a LAN (samba) share - a crash. look fw. to the next msg.

sorry, delete all passwords - is IMHO a bad idea.

Majestyx (majestyx) wrote :

>The problem cannot be reported:
>
>The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these >crashes
;)

says to a gvfs-gnome-smb bug ...

Chad Miller (cmiller) on 2010-04-05
tags: added: desktop+
Chad Miller (cmiller) on 2010-04-05
Changed in desktopcouch:
assignee: nobody → Chad Miller (cmiller)
importance: Undecided → Critical
status: New → Confirmed
Rodney Dawes (dobey) on 2010-04-05
Changed in ubuntuone-client:
status: Fix Committed → Fix Released
Changed in ubuntuone-client (Ubuntu Lucid):
status: New → Fix Released
Changed in libgnome-keyring (Ubuntu Lucid):
status: Confirmed → Fix Released
tags: added: package
Changed in desktopcouch:
milestone: none → lucid-final
tags: added: iso-testing
Changed in desktopcouch (Ubuntu Lucid):
milestone: none → ubuntu-10.04
Martin Pitt (pitti) wrote :

The original issue has been fixed in libgnome-keyring as the root cause. Please open new bugs if you still have problems on a fully upgraded lucid beta-2 system. Thank you!

Changed in desktopcouch (Ubuntu Lucid):
milestone: ubuntu-10.04 → none
status: Triaged → Invalid
Changed in gwibber (Ubuntu Lucid):
status: Triaged → Invalid
Changed in desktopcouch:
status: Confirmed → Invalid
MacRules (macrules) wrote :

I still experience an inlog problem to Samba with a fullu update 10.04.
There still seems to be a bug in the libgnome-keyring:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/544847 might be related.

So when i store the passwd I get an error, when not, I can connect.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package desktopcouch - 0.6.4-0ubuntu1

---------------
desktopcouch (0.6.4-0ubuntu1) lucid; urgency=low

  * Upstream release. Adds all patches that were previously in this packaging.
  * Split desktopcouch-service threads into to discrete processes, since they
    do not depend on each other, and because multithreading breaks with recent
    changes to libraries. (LP: #524566, #530605)
  * Made desktopcouch more robust when dealing with mergeable lists.
    (LP: #555908)
  * If the replication service gives a user_id, then include it in the
    query string, so the service can shard access.
  * Add bookmark records support.
  * Handle cancelled keyring dialogs. (LP: #527036)
  * Retry when starting couchdb fails. (LP: #530541)
  * debian/patches/0-items-should-expose-private-data-for-now.patch
    - Gwibber demands that some items that are private be exposed, namely
      keys _id and _rev. These should properly be accessed as attributes
      .record_id and .record_revision in some future release of gwibber.
 -- Chad MILLER <email address hidden> Mon, 12 Apr 2010 23:02:01 -0400

Changed in desktopcouch (Ubuntu Lucid):
status: Invalid → Fix Released
timosha (timosha) wrote :

It seems that this problem is now solved with the latest update of libgnome-keyring.

timosha (timosha) wrote :

I can now confirm that password protected Samba shares can be mounted with a stored password.

axoin (axoin) wrote :

As with version 1.6.0+git20100414-0ubuntu1 i do not expierence the gvfsd-(sftp/ftp) problems I mentioned before.
I can mount, unmount and remount a share with stored password as often as I want and it is always successful.
Big THANK YOU to all who helped fix this. Great community!

Changed in gvfs:
status: Unknown → Invalid
nilsja (nilsjansen) wrote :

i have the same problem since 3 days with the current 10.10 maverick.

CaseyR (reinkarnal) wrote :

Same as nilsja. Having this problem with 10.10 Maverick.

Vit (r-vitaliy) wrote :

this bug affects me too

Me too
 > this bug affects me too
>
> --
> gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.
> https://bugs.launchpad.net/bugs/530605
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Desktop CouchDB: Invalid
> Status in GVFS: Invalid
> Status in Ubuntu One Client: Fix Released
> Status in “desktopcouch” package in Ubuntu: Fix Released
> Status in “gwibber” package in Ubuntu: Invalid
> Status in “libgnome-keyring” package in Ubuntu: Fix Released
> Status in “ubuntuone-client” package in Ubuntu: Fix Released
> Status in “desktopcouch” source package in Lucid: Fix Released
> Status in “gwibber” source package in Lucid: Invalid
> Status in “libgnome-keyring” source package in Lucid: Fix Released
> Status in “ubuntuone-client” source package in Lucid: Fix Released
> Status in “gvfs” package in Fedora: Unknown
>
> Bug description:
> Binary package hint: gvfs
>
> 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.
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/desktopcouch/+bug/530605/+subscribe

JPM (jpm) wrote :

I'm having the same issue with Ubuntu 10.10 beta 32bit, installed with Alternate install image. It happened directly after a full update, without any customizations.

Changed in gvfs:
importance: Unknown → High
status: Invalid → Unknown
Dimitrios Ntoulas (ntoulasd) wrote :

Having this problem with 10.10 Maverick.

2.6.35-25-generic #43-Ubuntu SMP Thu Jan 6 22:25:16 UTC 2011 i686 GNU/Linux

I have a server and 2 clients.

Server 10.04 Clients 10.10

One client works fine, the other has problem. Both clients updated.
Its must be some setting that cause the problem.

Changed in gvfs:
status: Unknown → Invalid
karl (karl-sebastian-liebich) wrote :

Well for this is a duplicate of Bug #551645 - I still encounter this bug.

Felix (apoapo) wrote :

Yes, same here. desktopcouch-service restarts every few secs and is using 100% cpu immediately.

edvar (edvar-f) wrote :

I had to uninstall Ubuntu One and all associated packages so my CPU Utilization went back to normal.
I reinstalled Ubuntu One and notice the package "desktopcouch-ubuntuone" wasn't installed this time. I suspect it was the one causing the high utilization.

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

Other bug subscribers

Remote bug watches

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