Bug 503644 - Satellite Pointing IC 2915
Summary: Satellite Pointing IC 2915
Status: CONFIRMED
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.7.6
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-02 06:31 UTC by Brendan
Modified: 2025-05-04 06:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Focus shifted to IC 2915 but info for NOAA 18 still displayed. (323.68 KB, image/png)
2025-05-02 06:31 UTC, Brendan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brendan 2025-05-02 06:31:46 UTC
Created attachment 180867 [details]
Focus shifted to IC 2915 but info for NOAA 18 still displayed.

SUMMARY
After using the Find Object feature to focus on a satellite, the focus shifts unpredictably to IC 2915. 

STEPS TO REPRODUCE
1. Use the find object feature to focus on a satellite (eg NOAA 18)
2. Zoom in (tracking was automatically enabled) 


OBSERVED RESULT
Focus unexpectedly shifts to IC 2915. This does not happen when I focus on DSOs, planets, or stars, those keep their focus. 

EXPECTED RESULT
Expected the focus to stay on the satellite indefinitely so I can hook up a telescope mount and orcanize control commands.

SOFTWARE/OS VERSIONS
macOS: Sequoia 15.4.1
KDE Frameworks Version: 5.115.0
Qt Version: Version 5.15.13 (built against 5.15.12)
Stable Release 
Build: 2025-04-01T10:32:04Z

ADDITIONAL INFORMATION
I tried restarting the application. Redownloading the .dmg.  I tried deleting the entire DSO catelog and it still focuses to the random spot where IC 2915 was.

In the attached image you can see that I tried to focus on NOAA 18. It's elevation shows it should be above the horizon. Instead the focus shifted to where IC 2915 is, below the horizin and just above the belt of geostationary satellites. The wrong position.
Comment 1 Jasem Mutlaq 2025-05-04 06:35:29 UTC
I can confirm the issue.