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

Hi Jo,

Not sure if this could be related, but I had a similar full-on mount lockup issue after upgrading to 3.4.3. Is there any chance you're getting bitten by the dome constraint INDI default state? I don't have a dome, but was impacted. See this post for details just in case:
www.indilib.org/forum/domes/7366-dome-lo...-in-3-4-3.html#57053
Cheers, Doug

That is possible, Doug!

I saw that warning the first time this happened, couldn't make anything out of it, though, since I have no dome. I quit Kstars, restarted it and the dome constraint warning went away. Have not seen it since, but still had the same behaviour, i.e. the mount is stuck and would not slew
It must have set a flag somewhere, which was, however, erased when I downgraded to 3.4.2 by purging and then installing from the stable release repository.

Since I have two Kstars incidences on my system, one installed and one that I just run from the build directory and only install once I used it and have not found any bugs, I can remove the dome constraint in that one and see whether that makes a difference.

Thanks so much for that tip!

Jo


That was indeed the case, Doug! It was set to Dome lock, although the button was half greyed out. I don't know what that means. It turned white when I toggled Dome lock then back again.

It has nothing to do with 3.4.3 though, I think it is triggered by Indi, since it also happened in 3.4.2 after I upgraded Indi only.

See the screenshot:

Note that in my case, it wasn't a no-brainer to get the state machine happy. Kstars mount control said one thing, and INDI said another about the park state. It's not quite clear how I got the state machine to sync up again, but it was awkward. Some number of unpark, park, and GOTO requests were made after I changed the INDI GUI before it unstuck. Something's not quite right in there; I hope too many folks don't get tripped up by this (especially those without domes who may not be thinking about it!)....

I hope so, too. I fired up the system and started the upgrade again. Unfortunately, the updated Indi drivers for my ZWO-EFW and the ZWO cameras, as well as QHY CCD crash when called up by the older 3.4.2 Kstars version.
If I can't figure out your sequence of making this unstuck once I have rebuild the latest Kstars, I will have to purge everything again, at least Indi, and restart once more from the stable repo.

However, as I wrote, this must be a new bug that was introduced between July 15 and 19. I had been using 3.4.3 for a few weeks already and did not have that problem as late as July 15, when I installed the last functioning version. The havoc started on July 19, when I installed the newest version because I wanted to test Hy's new guider algorithms.

Thanks again for this great tip! I had dismissed the dome warning and would most likely not have gone back to it.

PS: The logs can be downloaded here: www.dropbox.com/sh/bbwfky2ij9y1ag0/AAA2H...WugxDTSQ10nKEwa?dl=0

The very last one, at >600 MB, is the one after I purged everything and reinstalled 3.4.2. The imaging with that worked without a flaw throughout the night.

I wonder if this is where the problem is rooted in the CEM60 driver:

[2020-07-19T22:57:46.091 CDT DEBG ][ org.kde.kstars.indi] - iOptron CEM60 : "Error: DOME_IGNORED is not a member of Dome parking policy (DOME_POLICY) property. "

That error, which did not prevent the mount from moving, no longer shows with the latest Indi update, it now says:

[2020-07-19T21:17:09.536 CDT INFO ][ org.kde.kstars.indi] - iOptron CEM60 : "[WARNING] Cannot unpark mount when dome is locking. See: Dome Policy in options tab. "

Just to mention (for my own sanity), be sure to save the dome policy after you've changed it. Otherwise it comes and kicks you each time you start!

Cheers and clear skies,
Steve

El Corazon says :

[2020-07-19T21:17:09.536 CDT INFO ][ org.kde.kstars.indi] - iOptron CEM60 : "[WARNING] Cannot unpark mount when dome is locking. See: Dome Policy in options tab. "

Just as the message says, go to the indi panel/your mount/options and simply click "Dome Ignored". Save and reload and you're done.

- Marc

Now, my own problems :

1/ I'm using Kstars with the dark theme "Black Body". When I quit and then restart, the soft comes back with an incomplete white menu and I have to set my theme again.
it is very unpleasant when you're in the dark and have your vision adapted because of the crude white light.



2/ I have 3 problems with indiwebmanager. (The last version including agent)

- I can't change the default 'root' user in the indiwebmanager.service or it refuses my connection.
- If I connect through indiweb, the indiserver and drivers are launched but everything stalls then. I'can't even unpark my mount.
If I start manually the indiserver and the drivers through an ssh cnx, everything works fine.
- In simulation mode, it says there is no GSC available. (It works with the workaround above)

- Marc