Bug 501212

Summary:	Astrometry log not created
Product:	[Applications] kstars	Reporter:	Marcin Owsiany <marcin>
Component:	general	Assignee:	Rob <rlancaste>
Status:	REPORTED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	3.6.2
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marcin Owsiany 2025-03-08 05:53:56 UTC

SUMMARY

No log file gets created for plate solver.

STEPS TO REPRODUCE
1. Go to logs settings, change astrometry to LOG_ALL. Make sure the "Separate log file" is checked and the path is at default /tmp/astrometryLog.txt and click OK
2. Go to "Align", press "capture and solve" 
3.  Solver fails 

OBSERVED RESULT

Log files gets created and I can troubleshoot more about why the solver failed.

EXPECTED RESULT

No log file gets created. No solver info in the main kstars logs either :-(


SOFTWARE/OS VERSIONS
org.kde.kstars: Welcome to KStars 3.6.2 Stable
org.kde.kstars: Build: 2022-12-22T16:31:38Z
org.kde.kstars: OS: "debian"
org.kde.kstars: API: "x86_64-little_endian-lp64"
org.kde.kstars: Arch: "x86_64"
org.kde.kstars: Kernel Type: "linux"
org.kde.kstars: Kernel Version: "6.1.0-31-amd64"
org.kde.kstars: Qt Version: 5.15.7

ADDITIONAL INFORMATION

I also tried various other combinations of main log settings, "separate file" and file path, to no avail.

Using astrometry.net 0.93+dfsg-1+b1 although I'm not sure that's the solver being used because under "Solver mode" I see only "Remote" and "StellarSolver" and the latter is selected.

I only later found the solver was failing because focal length was wrong, in turn because I didn't review the optical trains dialog carefully, but this not very relevant to this report.