| Summary: | kstars does not start indiserver, the button 'toggle indi control panel' is greued out. | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Dino.Lentura |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | REPORTED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.7.7 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dino.Lentura
2025-08-02 18:37:18 UTC
It seems this happens when I just connect my ASI ZWO 174 camera and configure it as main camera. In that case kstars (Indi?) claims it can not detect a device. When I add a second 174 as guide cam, the INDI server does start, and I can use the camera. So I have to 'configure' two cams although only one is connected. I forgot to mention that the behaviour is identical on macOS and on Ubuntu (raspi) Seems my settings or preferences got corrupted by some upgrade. On the Mac I first deleted ~/Library/Application_Support/kstars and ~/Library/Preferences/kstars, reconfigured everything and re-created some profiles, which worked. On the raspi I deleted all Ekos device profiles, and recreated one without mount (which was not connected), but when starting Ekos I got a message from kstars that it could not find the mount. Using sqlite3 to like at the opticaltrains db I noticed that this had some eqmod entry, which I find odd. I the ntried to create a profile using the device wizard, which also allows to configure the optical train, and this finally worked. So it looks as if creating a profile (via the '+' buttong or editing a profile does not allow to edit all the settings for an optical train, which can result in profiles that block kstars / ekos? |