SUMMARY kstars does not start indiserver, the button 'toggle indi control panel' is greued out. STEPS TO REPRODUCE 1. Start kstars 2. Try to toggle indi control panel 3. OBSERVED RESULT indiserver is not started EXPECTED RESULT Should be able to start indiserver SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ubuntu 24.04.2 raspberry Pi 5 ADDITIONAL INFORMATION
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?