[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-12-18 Thread Charlie Kravetz
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-11-19 Thread Charlie Kravetz
Any further results on the test? I don't really want these bugs to expire, we get some good workaround information from them even if I can't seem to get them fixed yet. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-09-15 Thread b
I confirm this issue. Will try the debugging steps above and post results. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-09-15 Thread b
** Attachment added: Here is the debugging output from sshfs, before putting machine into suspend. https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/345226/+attachment/1590645/+files/sshfs.log -- after resume, sshfs mounted dir can't be remounted immediately

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-09-15 Thread b
This time I had no problems after resume. Either the time was too short for the network to timeout, or the extra options for debugging resolved the issue. I'll try leaving the machine in suspend for a longer period this time. ** Attachment added: Full log after suspend and resume.

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-08-23 Thread Charlie Kravetz
Please try running sshfs with the following options: sshfs -odebug,sshfs_debug,loglevel=debug ... this should produce a log that can be used to resolve this issue. -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-07-21 Thread Charlie Kravetz
Thanks for the confirmation in Lucid. Logs with debugging output can be useful for diagnosing the problem. Try running sshfs with the following options: sshfs -odebug,sshfs_debug,loglevel=debug ... this should produce a log that can be used to resolve this issue. -- after resume, sshfs mounted

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-05-14 Thread swmike
I am now at 10.04 and the problem persists. swm...@swm-laptop:~$ apport-collect 345226 The authorization page: (https://edge.launchpad.net/+authorize-token?oauth_token=7279kJBV8SnpTzLLrL0wallow_permission=WRITE_PRIVATE) should be opening in your browser. After you have authorized this program

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-05-12 Thread Charlie Kravetz
We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks! -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-03-18 Thread Charlie Kravetz
** Changed in: sshfs-fuse (Ubuntu) Status: New = Incomplete -- after resume, sshfs mounted dir can't be remounted immediately https://bugs.launchpad.net/bugs/345226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-03-17 Thread Charlie Kravetz
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed