Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13637 - [thunar] XFCE will not display sshfs mounts
Attached to Project:
Arch Linux
Opened by Scott (scottuss) - Monday, 02 March 2009, 22:45 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 04 October 2009, 21:21 GMT
Opened by Scott (scottuss) - Monday, 02 March 2009, 22:45 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 04 October 2009, 21:21 GMT
|
DetailsDescription: When mounting SSHFS locations via the termial, XFCE will show the mount location but when trying to open it to view files, it flickers back to the previous directory, almost as if the location does not exist.
However, I have successfully mounted several SSHFS locations and can view them without problems using PCMANFM. Additional info: * sshfs 2.2-1 thunar 1.0.0-1 Steps to reproduce: |
This task depends upon
http://bbs.archlinux.org/viewtopic.php?id=51185
The solution, as many have said before, is to use gamin instead of fam.
To avoid users encounter this problem again in the future, maybe we should advise user to use gamin instead of fam?
In fact, now that we have gamin, do we have any need for fam anymore? If not, then why don't we makes gamin our default file alteration monitor software to avoid confusion?
We already have gamin in the optdepends array. Should we add there a note about fam issues with sshfs or a separate install message? Tobias?
Other than that we should close this here as "upstream" bug.
For now we can't do much here. People will have issues whether we use fam or gamin at buildtime. So this is a won't fix for me and more likely an upstream issue.