I saved the appimage to my ~/bin directory. Running it either from xterm or through a launcher, saving a newly opened picture (no edits) offers /tmp/.mount_*/usr as the save directory instead of $HOME. /tmp/.mount_whatever/usr doesn't exist, so at least I'm not saving things to /tmp by mistake. Reproducible: Always Steps to Reproduce: 1. Create a new document 2. Save it immediately to the default directory Actual Results: The default directory doesn't exist. It's something like /tmp/.mount_SPDYXZ/usr Expected Results: It should offer to save to $HOME
Yeah, this is true on Ubuntu 16.04 for me.
This is because AppRun inside the AppImage changes the working directory to usr/ inside the AppImage before executing the payload application. The reason is given in https://github.com/probonopd/AppImageKit/issues/172#issuecomment-229993161 Either Krita could specify to show $HOME in the open/save dialog, or a different AppRun without the chdir command could be used for the Krita AppImage.
Perhaps the default location for saving files could be made a preference? $HOME is certainly better than a missing directory, but my $HOME is awfully cluttered - it'd be nice to be able to nominate $HOME/pictures/2016-Q2/ or something.
Hum, actually the pictures directory should be the default.
And there's also code to remember the last used folder. I'll investigate a bit.
Argh, now I remember... Having the current working directory as the default directory for saving was added because people wanted to start krita from a terminal and have the the current directory as default save dir. So I guess we'd best fix the apprun command to not change the working directory.
This is fixed in linuxdeployqt which no longer uses an AppRun file nor changes the current working directory. Alternatively, you can use any shell script as the AppRun file, as long as it is able to launch Krita.
I really need to update our appimage build script... It's still basically what it was end of 2016.
with 3.3.2, the appimage now shows $HOME by default.