/./path2/file2 to get a stable symlink.Īnd when the two files are not on the same file system (e.g. I try getting the V4.1.0 AppImage to write its report elsewhere but its /tmp/.mount_linux_?/ read-only-path :įirst I will make a search in a much smaller folder to just test if it writes its report accurately) and report back here how that went.Īnd I also not tested if it will create stable symlinks (as described above), but I doubt it will since you must have a routine of using. I have rebooted since the above issues, so the results from back then are lost anyway. If you want to use the V4.1.0 AppImage and really want / need to save its report the quoted post on states in one reply by giving it a starting work directory it will save such reports in that directory intead of its read-only /tmp/.mount_linux_?/ path.

If that bug would be squashed in an upcoming update, it would be possible to create a patched version of V4.1.0, but most likely no one would create such a version since most people want the newest available version (regardless it it brings them any real advantages - but will most likely strain your system with much larger dependency load ) The AppImage is coded to 'think' its current folder is /tmp/.mount_linux_L1DP7y/usr/ (as seen this is its default search path) but unlike V6.1.0 the V4.1.0 not displays the 'Failed to save results to file Read-only file system' error message.

Downloading LosslessCut 3.58