Bug 576504 - gvfs-smb eating all CPU
Summary: gvfs-smb eating all CPU
Keywords:
Status: CLOSED DUPLICATE of bug 573202
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-24 10:18 UTC by Pablo Iranzo Gómez
Modified: 2015-03-03 22:46 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-24 17:21:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pablo Iranzo Gómez 2010-03-24 10:18:06 UTC
Description of problem:

gvfs-smb process eats all CPU time


Version-Release number of selected component (if applicable):

rpm -qf /usr/libexec/gvfsd-smb

gvfs-smb-1.5.5-2.fc13.i686


It also happens on x86_64



How reproducible:

Try to connect via SAMBA (using gnome 'places') to a SMB server


Steps to Reproduce:
1. Setup a new connection in gnome to conect usign SAMBA
2. Use that bookmark to connect (it will fail even if the other server works)
3. gvfs-smb starts eating CPU
4. killing process gives: "DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)" 
  
Actual results:

CPU being ate by gvfs-smb and no connection


Expected results:
Working connection to smb servers

Comment 1 Tomáš Bžatek 2010-03-24 17:21:05 UTC
This is the same issue as bug 573202. I'm going to close this one now, please take a look at bug 573202 and provide backtrace if possible. I'm not able to reproduce it here according to your repro steps, can you be more specific? E.g. have you saved the password to the keyring? Does it happen always? Is there a difference between manually entering the URI to nautilus and when bookmarked?

*** This bug has been marked as a duplicate of bug 573202 ***


Note You need to log in before you can comment on or make changes to this bug.