#98 indi_scopedome_dome driver crash, after KStars last update to version 3.7.1

[Carlos Vera Hernández]

Describe the bug:
After last update of KStars to version 3.7.1 and INDI Library to v. 2.0.8, indi_scopedome_dome driver crash (the other indi device drivers in my Ekos profile works properly)

The ScopeDome is a 3m Arduino version and after the crash, I have tested it in Windows 11, with Ascom driver, and works properly.

To Reproduce

Start Kstars

Start Ekos (INDI client)

Execute any Ekos profile including indi_scopedome_dome driver.

OBSERVED RESULT:
All INDI services start properly, but indi_scopedome_dome driver crashes inmediately. Then it try to restart and crashes again and again ... (when on a very rare occasion, it has started normally, its operation remains normal and without interruptions.)

As we can see in the attached file (a commented clipping of the file generated by KStars), in the indi_scopedome_dome driver, there are two failures:

The first and least important one, exists from the first release of 2.0 version of the driver that I’ve used before, and occurs almost always on the first connection attempt as a "handshake" failure, which usually resolves on the second try, as on this occasion.

The second bug is the most important one, that appeared in the latest Kstars-INDI update, and occurs after the connection is successfully established, always in the same step of the initialization sequence.

Expected behavior:
That indi_scopedome_dome driver works properly, like before last update.

Desktop:

OS: Linux Mint:

Version: 21.2

Desktop: Cinnamon 5.8.4

INDI driver: indi_scopedome_dome

version 2.0

interface 32

INDI Library: 2.0.8

KStars Version 3.7.1 Stable 2024-06-18T09:22:30Z

Log Files

INDI driver log (indi_scopedome_dome)
indi_scopedome_dome_10:59:40.log

KStars-Ekos log, including several attempts to execute indi_scopedome_dome driver
log_21-28-59.txt

Commented snip of the same KStars log:
Snip_of_KStars-Ekos_log_21-28-59.txt

2 Attachments

[Carlos Vera Hernández]

After a rebuild and reinstall of indi core and drivers, made by Jasem Mutlaq, I've tested the driver, connecting and disconnecting it a few times, and it has always started well. So I think that now the bug is fixed.

(Only remains the mentioned failure of connection in the first attempt, which is solved on the second attempt without any crash of the driver; but this is another less important issue).

Thank you very much.

Best regards

Carlos Vera Hernández.