Bug 415969

Summary: Center and Track goes to wrong position if empty sky
Product: [Applications] kstars Reporter: Pit <P.Suetterlin>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: REPORTED ---    
Severity: normal CC: giovanniceribella
Priority: NOR    
Version First Reported In: git   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Pit 2020-01-07 16:19:22 UTC 
SUMMARY

If the cursor coordinates do not refer to a listed object, a 'Center and Track' will go to wrong coordinates (not where the cursor was)

STEPS TO REPRODUCE
1. place mouse cursor on some part of the sky without an object
2. RMB, Select 'Center and Track'
3. Check the position of the center

OBSERVED RESULT
The tracked position is not where I clicked

EXPECTED RESULT
The exact position where I clicked should be centered (and tracked)

E.g., I go to Cederblad51,
JNow:	05h 31m 26s	 12° 10' 03"
J2000:	05h 32m 34s	 12° 10' 52"
AzAlt:	 68° 45' 57"	-11° 58' 24"

This is no listed object, RMB menue says 'empty sky'
I select 'Center and Track', and check the center coordinates
JNow:	05h 32m 33s	 12° 11' 05"
J2000:	05h 33m 40s	 12° 11' 52"
AzAlt:	 68° 59' 07"	-11° 36' 51"

So it seems it goes to the J2000 coordinates in the Jnow system....

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.65.0
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION
KStars from git, 3.4.0-978_gc035e1135
Comment 1 Giovanni Ceribella 2020-04-11 08:33:16 UTC 
I confirm the problem on the 2020-02-23T18:06:10Z build of Kstars 3.4.1, installed through the ppa:mutlaqja/ppa repository on Kubuntu 19.10. I have been observing this strange behaviour for a few months: was it fixed in the git version?

Plasma: 5.16.5
KDE Framework: 5.62.0
Qt: 5.12.4
Comment 2 Giovanni Ceribella 2021-12-25 17:53:12 UTC 
The bug is still there in 3.5.6 (PPA repository on Ubuntu 21.10).
Comment 3 Jasem Mutlaq 2021-12-26 07:37:22 UTC 
Interesting, it could be that, or the de-precessing an empty point failed. I see this as a low-hanging fruit, anyone wants to take a stab at fixing it from the code?