Hi there,
I am currently working on some major revisions in stellarsolver, but they shouldn't affect the things you are trying to do here. This message:
org.kde.kstars.indi: Canon DSLR EOS M50 : "[ERROR] Exposure failed to parse raw image. "
Is not an error in stellarsolver. If you look at the beginning, it says it is an indi error and if you search here:
github.com/indilib/indi-3rdparty/search?...d+to+parse+raw+image
you can see that it can only be one of two drivers,
indi-pentax/pktriggercord_ccd.cpp
or
indi-gphoto/gphoto_ccd.cpp
. Perhaps there was a recent change in one of those drivers? Maybe there is an issue in your installation of gphoto?
StellarSolver does not capture any images, it simply takes images and image buffers that have been given to it by KStars and plate solves them. Are you using the internal StellarSolver solver to solve the images, or are you using ASTAP, online astrometry, or local astrometry.net? StellarSolver has the ability to plate solve using different methods and I want to make sure of which method you are using to know what is happening. It also matters which method you are using because the internal solver needs to receive an image buffer from KStars to solve the image which means KStars needs to be able to load the image (the driver error we discussed already could cause issues with that). The other solving methods usually require FITS in order to solve the images, since astrometry.net itself cannot solve a RAW file. If the image is loaded in KStars, StellarSolver can take the loaded image buffer from KStars and export a FITS file for those other solvers to work, so even if you use a Canon camera with KStars and are capturing RAW files, we can still plate solve using any method as long as the image loads in KStars.
Finally the mmap errors you reported at the end, they are related to your index files, not the file you are trying to solve. Looking at what the output says, I am guessing that you have a LOT of index files? That actually can take up quite a bit of memory, especially if it tries to load them all at once. And note that you might have 8 GB of ram, but is your system armhf or arm64? If it is not 64 bit, it can't use all 8 GB of ram, I think it can use 4 GB. Your operating system will already take a little RAM and if you have a few GB of index files, you can quickly hit the limit if you load them together. Now StellarSolver and astrometry.net have a setting called "in parallel" that lets you load index files sequentially or all at once. There is a huge performance gain to turning on that setting, but if you don't have enough ram and you have too many index files, you can't do that. To change that setting in KStars, you can edit your options profile you like to use most and turn off that setting. Then see if it works better. I wrote code that will automatically check to see if you have enough RAM on your system to load your index files and it is supposed to turn it off if you do not, but if you are on a system where you can't actually use all your available RAM, then that might give a false positive.
Also if you are having problems with recent changes I made in stellarsolver, you can go back to version 1.9 until I finish with my changes. That is available for download from the stellarsolver repo. I don't think I broke anything, but there were a lot of changes and it needs more testing.
Thanks,
Rob