I have TeamViewer access installed already. I'll look at how to submit the ticket and get that done ASAP.
I've been installing the nightly builds daily and re-testing each time. I'm still having the same issue of the program just crashing fully if I try to loop or capture a preview in the Capture Module. Looping & Preview work fine in the Focus module. Could this be an issue with the FITS viewer? It doesn't get invoked in Focus - the image appears in the built-in window. The error logs don't appear to provide any reason for the crash that I can see - but hopefully smarter minds will see the problem. At this point it has me unable to effectively use StellarMate with my Nikon Z6 setup. Any help toward resolution would be appreciated!
I've installed the update. Kstars is now loading again, but I'm right back to Ekos / kstars crashing every time I try to either loop frames or capture a preview in the Capture Module.
The last entry in the log files is either [ org.kde.kstars.ekos.capture] - "Starting framing..." or [ org.kde.kstars.ekos.capture] - Preparing capture job "/home/stellarmate/Pictures/Light" for execution.
I'll attach the log files for review.
Here's the latest: I've run all the updates and now kstars won't launch. I've rebooted a few times, but it's refusing to launch. I get a spinning hourglass for a few seconds and then nothing.
knro wrote: Thanks, I found the issue with libraw. Apparently, v21 is now available and I'll switch the build to it. Beta should be updated later tonight.
Hi all! My first post here and hoping to be able to get this issue resolved. I am having an issue with my Nikon Z6 DSLR and the Capture module. I am able to take preview images without any issue, but as soon as I try to run a capture job, even if only one exposure, KStars crashes when downloading the image file. I tried a few tweaks to the Frame Image Settings and CCD Info width & height - but the results are always the same. The Preview images are around 146 MB each.
According to DigiCamDB.com the Nikon Z6 specs are as follows:
Sensor Resolution = 6062 x 4041
Max Image Size = 6048 x 4024
ekos seems to want to default to 6064 x 4040.
I have tried all 3 variations without any impact to resolving the issue.
Included in the zip are multiple log files & the DSLR test output. I intended to also upload the sample preview images that I saved after they were displayed, but even zipped it exceeds the file size limit for the forum.
Here's an additional log file. Hope it is helpful!
Sorry for the delay with the logs. Because of some of the earlier issues, I decided to reimage my system entirely. Once I had a fresh install in place, I changed to the Beta channel and ran all the updates I could find from Package Updater. I rebuild my Profile and have everything set up fresh. Still getting the driver crash notice I mentioned before when I start my profile in Ekos. Attached is the log. I have tried to run the DSLR test and it just fails.
Ok - so now that kStars is running again - as soon as I launch INDI - I get a driver crash notice for the Nikon DSLR. I click continue to restart the driver and it just is going in a perpetual loop at this point.
I ran these commands that you had provided on another post - that has restored the program - looks like it re-installed kstars
sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding
Control Panel is still acting strange - but moving forward at least.....
OK - I switched to Beta channel and installed updates. kStars won't launch now from the desktop shortcut. kStars, PHD2, and Image Viewer all have "invalid desktop entry file" messages. Also when I go to Control Panel - it says connection lost & fetching and never loads data. I've tried a few reboots. Do I need to re-image and start fresh?
Hi Jasem - please forgive my ignorance. The nightly PPA? I am on the stable release channel on my Stellarmate install right now. I can change any settings that would be helpful. I'm also open to a Remote Desktop if you have availability and if that would aid in troubleshooting. Thanks!