×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

indi_canon_ccd crash: latest update

  • Posts: 322
  • Thank you received: 31
I am having the same problem, as I posted in another thread.

It is a dependency problem.

When trying to upgrade everything, there is this message:
The following packages have been kept back:
indi-gphoto
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

$ sudo apt install indi-gphoto
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.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-gphoto : Depends: libraw20 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

If I try to force install libraw20, the result is that kstars-bleeding will be removed!
----
The following additional packages will be installed:
indi-gphoto
The following packages will be REMOVED:
kstars-bleeding kstars-bleeding-dbg libraw19
The following NEW packages will be installed:
libraw20
The following packages will be upgraded:
indi-gphoto
1 upgraded, 1 newly installed, 3 to remove and 0 not upgraded.
Need to get 368 kB of archives.
After this operation, 94.7 MB disk space will be freed.
Do you want to continue? [Y/n]

KStars should depend on the same library version as indi-gphoto.

What we need is
a) a KStars update that depends on libraw20, or
b) revert back to libraw19 for indi-gphoto.
3 years 7 months ago #58592

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi

If you want it now, take the upgrade to libraw20 and let it remove kstars stable.

The git is good ATM. Build and install that until there's a fix?

Tested with indi-canon-ccd, indi-eqmod and indi-asi.

Even better, when you're back to stable, keep the git and help test:)

HTH,
Steve
Last edit: 3 years 7 months ago by alacant.
3 years 7 months ago #58596

Please Log in or Create an account to join the conversation.

  • Posts: 322
  • Thank you received: 31
Thanks for the info.

But, I don't want to be running a development version.
I stick with stable releases as much as I can.
Less work and less surprises ...
3 years 7 months ago #58600

Please Log in or Create an account to join the conversation.

  • Posts: 322
  • Thank you received: 31
If I use the nightly build, instead of the regular stable PPA, would it solve the issue?

I would think not, since Jasem has not posted in this thread or pushed a fix.
Right?

launchpad.net/~mutlaqja/+archive/ubuntu/indinightly
3 years 7 months ago #58603

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 4
I had no luck with the nightly build (switched this morning)
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
3 years 7 months ago #58605

Please Log in or Create an account to join the conversation.

From stable it installs fine if you run this:
sudo apt-get update && sudo apt-get -y install libraw20 kstars-bleeding indi-full
3 years 7 months ago #58620

Please Log in or Create an account to join the conversation.

  • Posts: 322
  • Thank you received: 31
Unfortunately, it does not work:
$ sudo apt-get -y install libraw20 kstars-bleeding indi-full
 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
kstars-bleeding is already the newest version (6:3.4.3+202007200529~ubuntu18.04.1).
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.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
 libraw20 : Conflicts: libraw19 but 0.19.6~202002010817~ubuntu18.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.
 
3 years 7 months ago #58621

Please Log in or Create an account to join the conversation.

Sorry I rebuilt KStars for 20.04 only as a test and verified that, now rebuilding for 18.04 as well.
3 years 7 months ago #58622

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 4
Thank you, Jasem!
Everything is back to normal.
I changed the ppa back to the stable branch. Purged kstars and indi, then reinstalled it.
I had to type in the size of the camera sensor and forgot to fill in the pixel pitch.
From then on I had some hickups, because kstars crashed, when ekos tried to connect to the equipment.
There was no clue in the log files, what could cause the problem. So I reinstalled indi-full and filled in the pixel pitch.
I have a working system.
I must admit that I tried to build the programs from source. There might be some remnants because unfortunately there is no sudo make uninstall (or I missed it?).
By the way: on your facebook site there is a really nice picture of the heart and soul nebula.
Powered by

GNU / Linux
Git
KDE neon
KStars | EKOS | INDI

and some cheap hardware
Last edit: 3 years 7 months ago by Heiko.
3 years 7 months ago #58627

Please Log in or Create an account to join the conversation.

  • Posts: 322
  • Thank you received: 31
Cerro,

This is 20.04 or 18.04?

If it is the latter, can you please expand on what you did to get it to work?
3 years 7 months ago #58668

Please Log in or Create an account to join the conversation.

  • Posts: 322
  • Thank you received: 31
Never mind ...

Just got the new packages from the PPAs for 18.04.
They use libraw20 for kstars-bleeding, and remove libraw19, so all is good now.

Will test tonight.
3 years 7 months ago #58669

Please Log in or Create an account to join the conversation.

  • Posts: 1
  • Thank you received: 0
I also have this problem, if someone has a solution, please tell me
3 years 7 months ago #58670

Please Log in or Create an account to join the conversation.

Time to create page: 0.786 seconds