Confirmed all working from ppa Xubuntu 22.04

Read More...

No its not working even on Xubuntu. The culprit appears to be indi-eqmod which appears to have bene built against indi 9.4

The following packages have unmet dependencies:
libindi1 : Conflicts: libindi-plugins but 1.9.4+dfsg-1 is to be installed
Conflicts: libindialignmentdriver1 but 1.9.4+dfsg-1 is to be installed
Conflicts: libindidriver1 but 1.9.4+dfsg-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Read More...

James Langston created a new topic ' Ubuntu 22.04 PPA issue' in the forum. 5 months ago

It seems the mutlaqja PPA isn't right for 22.04. I can install Kstars and some indi drivers. But indi-eqmod throwing up warnings for libindi1

Saying that package is conflicting as it seems it's built with indi 1.9.4 instead of 1.9.5 and conflicts with libindi-plugins, libindialignmentdriver and libindidriver1.

This also used to happen on the 20.04 repo too and I only ever had luck with 21.10 repo. Would be great if it can be looked into

Read More...

Getting huge broken package warnings with indi-bin from the PPA using 20.04:

Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) indi-bin:amd64 < none -> 1.9.1-0xneon+20.04+focal+release+build11 @un uN Ib >
Broken indi-bin:amd64 Depends on libindialignmentdriver1:amd64 < none | 1.9.1-0xneon+20.04+focal+release+build11 @un uH > (>= 1.9.1)
  Considering libindialignmentdriver1:amd64 -1 as a solution to indi-bin:amd64 1
  Holding Back indi-bin:amd64 rather than change libindialignmentdriver1:amd64
Investigating (0) libindi1:amd64 < none -> 1.9.1~202107052238~ubuntu20.04.1 @un uN Ib >
Broken libindi1:amd64 Depends on indi-bin:amd64 < none | 1.9.1-0xneon+20.04+focal+release+build11 @un uH > (>= 1.9.1~202107052238~ubuntu20.04.1)
  Considering indi-bin:amd64 1 as a solution to libindi1:amd64 0
  Holding Back libindi1:amd64 rather than change indi-bin:amd64
Investigating (1) kstars-bleeding:amd64 < none -> 6:3.5.4+202107081129~ubuntu20.04.1 @un puN Ib >
Broken kstars-bleeding:amd64 Depends on libindi1:amd64 < none | 1.9.1~202107052238~ubuntu20.04.1 @un uH >
  Considering libindi1:amd64 0 as a solution to kstars-bleeding:amd64 10000
  Re-Instated libindidriver1:amd64
  Re-Instated libindi-plugins:amd64
  Re-Instated libindialignmentdriver1:amd64
  Re-Instated indi-bin:amd64
  Re-Instated libindi1:amd64
Investigating (1) libindi1:amd64 < none -> 1.9.1~202107052238~ubuntu20.04.1 @un uN Ib >
Broken libindi1:amd64 Conflicts on libindi-plugins:amd64 < none -> 1.9.1-0xneon+20.04+focal+release+build11 @un uN >
  Considering libindi-plugins:amd64 -1 as a solution to libindi1:amd64 0
  Added libindi-plugins:amd64 to the remove list
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+release+build9 for libindi-plugins but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+build8 for libindi-plugins but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.2+dfsg-2 for libindi-plugins but that is not InstVer, ignoring
Broken libindi1:amd64 Conflicts on libindialignmentdriver1:amd64 < none -> 1.9.1-0xneon+20.04+focal+release+build11 @un uN >
  Considering libindialignmentdriver1:amd64 -1 as a solution to libindi1:amd64 0
  Added libindialignmentdriver1:amd64 to the remove list
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+release+build9 for libindialignmentdriver1 but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+build8 for libindialignmentdriver1 but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.2+dfsg-2 for libindialignmentdriver1 but that is not InstVer, ignoring
Broken libindi1:amd64 Conflicts on libindidriver1:amd64 < none -> 1.9.1-0xneon+20.04+focal+release+build11 @un uN >
  Considering libindidriver1:amd64 -1 as a solution to libindi1:amd64 0
  Added libindidriver1:amd64 to the remove list
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+release+build9 for libindidriver1 but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.8-0xneon+20.04+focal+build8 for libindidriver1 but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.8.2+dfsg-2 for libindidriver1 but that is not InstVer, ignoring
  Fixing libindi1:amd64 via keep of libindi-plugins:amd64
  Fixing libindi1:amd64 via keep of libindialignmentdriver1:amd64
  Fixing libindi1:amd64 via keep of libindidriver1:amd64
Investigating (2) indi-bin:amd64 < none -> 1.9.1-0xneon+20.04+focal+release+build11 @un uN Ib >
Broken indi-bin:amd64 Depends on libindialignmentdriver1:amd64 < none | 1.9.1-0xneon+20.04+focal+release+build11 @un uH > (>= 1.9.1)
  Considering libindialignmentdriver1:amd64 -1 as a solution to indi-bin:amd64 1
  Holding Back indi-bin:amd64 rather than change libindialignmentdriver1:amd64
Investigating (2) libindi1:amd64 < none -> 1.9.1~202107052238~ubuntu20.04.1 @un uN Ib >
Broken libindi1:amd64 Depends on indi-bin:amd64 < none | 1.9.1-0xneon+20.04+focal+release+build11 @un uH > (>= 1.9.1~202107052238~ubuntu20.04.1)
  Considering indi-bin:amd64 1 as a solution to libindi1:amd64 0
  Holding Back libindi1:amd64 rather than change indi-bin:amd64
Investigating (3) kstars-bleeding:amd64 < none -> 6:3.5.4+202107081129~ubuntu20.04.1 @un puN Ib >
Broken kstars-bleeding:amd64 Depends on libindi1:amd64 < none | 1.9.1~202107052238~ubuntu20.04.1 @un uH >
  Considering libindi1:amd64 0 as a solution to kstars-bleeding:amd64 10000
Broken kstars-bleeding:amd64 Depends on indi-bin:amd64 < none | 1.9.1-0xneon+20.04+focal+release+build11 @un uH >
  Considering indi-bin:amd64 1 as a solution to kstars-bleeding:amd64 10000
  Considering indi-bin:amd64 1 as a solution to kstars-bleeding:amd64 10000
  Considering indi-bin:amd64 1 as a solution to kstars-bleeding:amd64 10000
  Considering indi-bin:amd64 1 as a solution to kstars-bleeding:amd64 10000
  Considering indi-bin:amd64 1 as a solution to kstars-bleeding:amd64 10000
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Read More...

James Langston replied to the topic 'Ubuntu 20.04 failed install' in the forum. 2 years ago

Yep I know what Im doing.... Linux for 25years :)

Read More...

James Langston created a new topic ' Ubuntu 20.04 failed install' in the forum. 2 years ago

Hi,

Tried to install kstars off the PPA in 20.04 but error with:
The following packages have unmet dependencies:
kstars-bleeding : Depends: libwcs6 (>= 4.8.2) but it is not installable

It appears 20.04 has version libwcs7 installed but it wont work with this so maybe you need to update your builds for Focal.

Cheers.

Read More...

Kstars is qt so a kde desktop is best. Plus atm kde has very low memory use and is very quick. Kde neon works great, latest stable kde and uses Ubuntu as its backend

Read More...

Also doing it on Raspberry Pi4 with Raspbian on 3.4 git sources.

Read More...

Hey all. How the hell do I go about setting temp compensation in ekos for Moonlite focuser? I can enable it but what do I put in the calibration tabs? Do I actually need to measure the temperature of something? Also how does EKOS use this info as no tab to say refocus every 1 degree etc?

Read More...

Sorry i know we should supply logs but none were enabled, but needed to bring to your attention. I will enable logging as it will likely happen in the next few nights again. I should note that indi is on a raspberry pi4 using raspbian buster compiled from sources from only 4 days ago and ekos is on a remote computer using ubuntu ppa.

Read More...

Latest Kstars - When mount fails to autofocuss in EKOS it hangs and seems to prevent a scheduled meridian flip from occurring. The result is scope keeps tracking until it hits the mount :( We need something that always prioritises the meridian flip over another module completing something first.

Read More...

I tried the standard methods of resetting home...didn't work. However, I deleted all the .xml files under ~/.indi and it all reset itself and is working fine now. Not sure what went wrong but this is a fix.

Read More...

Would altering the eqmod scope limits XML file (or other XML files) be a solution?

Read More...

Just last night I had an issue that required me to undo clutches. After I went through the usual method to reset home position but had to purge data as couldn't get home set right.
The mount now thinks it's below horizon so won't allow the scope to slew, even though limits are not checked. Furthermore the eqmod config can't be saved or changed. It's like it's just locked everything and although it says unparked it won't even allow me to implement park, or change slew speeds etc.

Funny thing is that if I use different computers the same issue occurs! Yet if I connect hand controller to mount it works fine, and if I connect using synscan driver it appears to work ok (at least can park/unparked and manually move mount).

Read More...