I have managed to successfully install docfetcher on 18.04 with the daemon autostarting, see https://www.wilderssecurity.com/thre...ubuntu.419743/.
Having figured out how to do it on mine I (confidently) proceeded to my wife's PC. Big problem! When right-clcking, Properties, my folders say folder, hers say inode/directory. My file says executable, hers says application/x-executable. I can double-click and the daemon starts. On hers, nothing happens. On my wife's I even tried running the daemon using the console by navigating to the directory and ./docfetcher-daemon-linux, the result is "bash: docfetcher-daemon-linux: No such file or directory". Yet if I "dir" it correctly lists all the files, including docfetcher-daemon-linux.
I don't understand what's happened as to why the difference in how folders and files are labelled strangely on the wife's PC , as I have always been careful to set-up both PCs the same to minimise PC support. I have searched the internet and am none the wiser. I'm hoping this is something obvious to an expert who lives in Linux world.
Having figured out how to do it on mine I (confidently) proceeded to my wife's PC. Big problem! When right-clcking, Properties, my folders say folder, hers say inode/directory. My file says executable, hers says application/x-executable. I can double-click and the daemon starts. On hers, nothing happens. On my wife's I even tried running the daemon using the console by navigating to the directory and ./docfetcher-daemon-linux, the result is "bash: docfetcher-daemon-linux: No such file or directory". Yet if I "dir" it correctly lists all the files, including docfetcher-daemon-linux.
I don't understand what's happened as to why the difference in how folders and files are labelled strangely on the wife's PC , as I have always been careful to set-up both PCs the same to minimise PC support. I have searched the internet and am none the wiser. I'm hoping this is something obvious to an expert who lives in Linux world.
Comment