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. Furthermore, HAL (which is also based on DBUS) works fine 3) Network issues: no sugar. As I said, using anything other than gvfs/nautilus for browsing it works fine - gnomevfs, mount.cifs, xsmbrowser... So no network problems 4) Going to the other box: no need to run ssh, I could do it locally. However, that box uses Mythbuntu, so no gvfs to toy with (and I don't feel like installing a nonworking app on a working computer) 5) Local copies et al work correctly, yes. Even big files are copied OK between other gvfs backends (i.e. trash, burn, ftp...)
The strange thing with this is that _sometimes_ it works and sometimes it doesn't. A thing, however, that always fails is copying large files over SMB, even when browsing had previously worked. This might indicate that gvfsd-smb may have a problem with bulk transfers. Concretely, after 5~10 MiB, the transfer stops and can't even be cancelled without killing gvfsd-smb. An analysis with Wireshark reveals that it's my Ubuntu box the one that stopped requesting data, not the Windows box who stopped serving them, and the last messages exchanged don't reveal anything special (no errors, etc). -- 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
