We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: gvfs (Ubuntu)
does anybody still get the issue in intrepid?
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
could the people having the issue attach their smb.conf to the bug?
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I had the same issue as described here. Bug #259978 (which i'd say is a
duplicate of this bug) contains a workaround.
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Habbit, the timeouts can also be avoided by using the ip-address rather
than the hostname. Strange how this is not working
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Check out: http://mail.gnome.org/archives/gvfs-
list/2008-May/msg5.html
Specifically:
- we have username, domain, server and share parameters available to be
set into mountspec. However username and domain shouldn't be set unless
we really need them. At the moment, non-anonymous mounts have
I think I have pinpointed the problem: after a clean reinstall Ubuntu
Hardy, the gvfs samba client worked flawlessly until I added the wins
option to the hosts line in /etc/nsswitch.conf in order to make
firefox able to resolve netbios names in the workgroup. Then, the
timeouts appeared again. I
Reopening, new data added
** Changed in: gvfs (Ubuntu)
Status: Incomplete = New
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Just a quick note that I'm running into the same problem with large file
transfers laptop is running hardy heron, desktop is running gusty
gibbon. any large file transfer in Nautilus (~200 MB) will time out,
downloading with SMB client works with no problems. Haven't done any
real digging into the
no, the bug has not been forwarded upstream, you are the only to get the
issue and there is not enough detail to make it useful
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
you are welcome to send the bug upstream though, since you are the one
getting the issue you can reply to their questions
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Ludicrous. AFAIK there is at least another person with this problem,
bug #210746, which is _also_ tagged as incomplete even though the
submitter did everything you asked from him/her and nobody has
answered in a week. But it's OK, I don't want to start the typical
this is why Linux/Ubuntu/GNOME
The upstream bug tracker is bugzilla.gnome.org, you can start a
discussion about why a very small team is not able to fix thousand of
issues a week on code they didn't write but that's not going to bring a
lot there. Those bugs are not trivial, we don't have gvfs hackers in the
team and the
Once again, updated everything to the latest version in the
repositories. The problem has been reduced from ~90% of SMB access
trials to about ~50%, but big file copies are still impossible, as they
hang after about 8 MiB (hang as in have-to-kill-gvfsd-smb-to-remove-
stuck-dialog).
I've rerun
could you try to use ssh locations on the box you are using to try gvfs
smb? you should have gvfs and ssh installed there no? could you also try
to attach gdb to gvfsd-smb after the mount and note if it's crashing or
something when the copy breaks?
--
gvfs-smb: strange timeouts
you can run gvfsd-smb server=server_name share=share_name if the share
is an anonymous one
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Big sigh. Updated everything to the latest version (35 updated today,
wow) and results here:
* Yes, SSH connections, or any kind of gvfs backend _other than_ smb works OK:
ftp, ssh, burn, etc.
* I attached gdb to gvfsd-smb and started a big file copy (which miraculously
completed successfully
not really an useful bug, could you attach the log anyway, maybe you
have some dbus, network, etc issue on your box? could you try using ssh
and see if you get the same issues there? are local copies, etc working
correctly?
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You
1) The log: there is just nothing there! in messages, there are a lot of
--MARK-- messages each 20 mins or so, while syslog contains some pulseaudio
errors, the hourly run of cron and more --MARK--s.
2) DBUS issues: any possible issue would have been brought by the Hardy beta
upgrade.
Thank you for your bug report. What smb server do you use? Does it work
every time or can you use it sometimes? Could you run
/usr/lib/gvfs/gvfsd -r on a command line, try yo mount and use the share
and copy to a comment what is displayed there?
** Changed in: gvfs (Ubuntu)
Importance:
Update: the delays and timeouts still happen, even if I kill the running
gvfsd/gvfsd-smb instance and let just my own. The delays are ~20 seconds
compared to the ~1.5 secs gnomevfs-ls (i.e. the old VFS backend) takes
to successfully display contents. No new output in the terminal-borne
gvfsd
In addition to the computer I'm testing from, there are two SMB servers:
salon (Mythbuntu Hardy beta i686, Samba) and my brother's computer
(Windows XP Pro SP2 32 bits). Running gvfsd on a terminal and then
running the command-line gvfs-* apps seems to work most of the time,
sometimes immediately,
Both: depending on (apparently) whether the current microfortnight is
even or odd, gvfs-ls shows the contents of the SMB share after about ~20
secs, or it just times out. If I get really, really lucky (i.e. when the
current ufn is a multiple of 42), it works correctly without delays. All
of this
now the description is confusing, do you get a delay or do you get
timeout? those are different things and a bug should describe only one
issue
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
could you try running gvfsd-smb manually and see if there is any issue
there? could you also attach .xsession-errors, messages and syslog when
getting the issue?
--
gvfs-smb: strange timeouts
https://bugs.launchpad.net/bugs/209271
You received this bug notification because you are a member of
Did so, and the results are basically non. Turns out that gvfsd-smb is
not to be run manually (request some key-value pairs). On the other
hand, .xsession-errors, dmesg, /var/log/messages and /var/log/syslog say
nothing about gvfs*, smb*, cifs* or whatever related to the problem.
--
gvfs-smb:
26 matches
Mail list logo
