Bug 474742

Summary:	kstars crashes (closes) immediately after starting ekos on remote computer.
Product:	[Applications] kstars	Reporter:	Troy Mire <troymire>
Component:	general	Assignee:	Jasem Mutlaq <mutlaqja>
Status:	REPORTED ---
Severity:	crash	CC:	jackbak1, justin.leniger
Priority:	NOR
Version First Reported In:	3.6.6
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Troy Mire 2023-09-20 19:22:36 UTC

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Works fine running on the Rpi4. Tries 3 PCs with same result. 2 nights ago, everything worked fine. Issue started when trying to run last night using the same procedure I've been using.

STEPS TO REPRODUCE
1. Start kstars
2. Start ekos.
3. 

OBSERVED RESULT
kstars closes

EXPECTED RESULT
kstars keeps running with ekos.

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
running latest Astroberry build and no packages have been updated since 2 days ago. No updates to packages available as of today.

Comment 1 Justin Leniger 2023-10-11 00:07:03 UTC

I'm seeing the same issue. I'm on Raspbian. I see the following output when I reproduce the issue by running `kstars` in the terminal:

terminate called after throwing an instance of 'std::runtime_error' what(): could not open file

Comment 2 Justin Leniger 2023-10-11 02:41:43 UTC

(In reply to Justin Leniger from comment #1)
> I'm seeing the same issue. I'm on Raspbian. I see the following output when
> I reproduce the issue by running `kstars` in the terminal:
> 
> terminate called after throwing an instance of 'std::runtime_error' what():
> could not open file

Actually, disregard the above. I believe my crash is occurring at a different point in launch.

Comment 3 jackbak1 2023-10-22 14:38:22 UTC

Seeing same start-up crash with nothing to report via kde bug report system (tried).

System and conditions:
- Current as of 2023-10-22 OpenSuse Tumbleweed, KStars 3.6.7 Stable, Build 2023-10-09T00:00:00Z
  KDE Frameworks: Version 5.111.0
  Qt: 5.15.11 (built against 5.15.11)

- Remote to Ubuntu 22.04 through INDIStarter on remote machine (default ports)

- On startup of KStars on OpenSuse machine with a Profile using Ekos Internal guiding crash on start.
  I believe this is a timing race condition, because ...

- With a Profile using Ekos External Guiding (PHD2), same main/remote combination Ekos starts just fine.
  Sometimes (no apparent pattern) I can close that profile and start the Internal guiding profile and it works fine.

Comment 4 jackbak1 2023-11-04 17:06:53 UTC

My problem (comment 3) seems to be resolved by regenerating the dark files used for guiding.

Comment 5 Jasem Mutlaq 2024-01-08 08:18:05 UTC

is this still an issue in KStars 3.6.8? Cannot reproduce.