Great work !
it's not available in Ubuntu's PPA at the moment ?

Thanks for this new version!

Strangely enough, I installed it on my Ubuntu 20.04 LTS system and 3.4.3 got installed, but my 18.04 LTS got the 3.4.2 version instead!? Strange.

Unfortunately, Launchpad is not building any packages now due to some issue. I will try to build as soon as it is up.

As a work around, Sonny486 has posted a version of the missing file that works on Windows.

www.indilib.org/forum/development/7334-w...ckage-dll.html#56885

A new Windows executable is uploaded, please download and check again.

Yep that works Jasem. Many thanks for the hard work you and the guys have put in!

Hello,
I have a strange problem with the last PPA version of kstars '3.4.3).
I use Ubuntu 20.04 and the driver indi_lx200_OnStep.
I can move the telescope with kstars (goto...).
But the buttons Park/unpark crash the program (segfault)
If i use the indi panel buttons to park or unpark the telescope, i have the same result -> segfault..

Very nice news!

When will 3.4.3 be released for astroberry?

I tried to update but still have 3.4.2.

Thanks!

Hello,
I think, my segfault problem is on Indi driver.
I updated indi at the same time as Kstars.
I just tested with Kstars 3.4.3 and the old indi_lx200_onstep driver and I no longer have the crash problem.

I have a different problem since I updated from the source on July 19:

Everything works fine and the polar alignment finishes without a problem. But after that, the mount (iOptron SmartEQ Pro+) is literally paralyzed. It will not slew anymore. (Except when commanded by the hand controller, but not with anything Ekos can throw at it.)
Quitting and restarting Kstars, including full shutdown and restart of the Pi4 did not help.
I then purged Kstars and Indi and rebuilt from the source (Kstars, Indi-full was downloaded from the repository).
The same thing repeated: Works fine, polar aligns, mount returns to Park, followed by complete paralysis.

I then again purged Kstars and Indi and reinstalled 3.4.2 (April 25 build) from the stable repository.
Everything worked fine after that.

Did anyone experience the same thing or is this a driver-specific issue?

Jo


PS: The previous time I had compiled from the source and installed the drivers available from the nightly repository on July 15 the problem was not there. So whatever was done between July 15 and 19 seems to have caused it.
What changes were made during these 4 days?

Awesome! So glad to use some of these features!!! great work!

Awesome work guys