Control: tags -1 unreproducible
Control: severity -1 important 

Akarsh Simha <akarshsi...@gmail.com> writes:
> Therefore, a
> default installation of darktable results in an error message upon
> launch:
>
> darktable: error while loading shared libraries: libcolordprivate.so.1: 
> cannot open shared object file: No such file or directory

I cannot duplicate this problem in a clean amd64 jessie chroot. It is
possible that the problem is architecture specific (or maybe multiarch
related, since for me the library in question lives in libcolord1:amd64).

> and then, there is no issue with using darktable. However, this should
> be included as a dependency and done automatically.

But according to apt-cache show darktable, it is a dependency.

> -- System Information:

The information you report looks like perhaps your system is not
completely upgraded to jessie (or at least is not up to date).

> Debian Release: 7.0
>   APT prefers testing
>   APT policy: (990, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)

This kernel is not in jessie.

> ii  libatk1.0-0               2.4.0-2

this version of libatk1.0-0 is the version from wheezy.

> ii  libc6                     2.17-3

this version of libc is not current, and so on...

I'm not sure if the state of your system is directly causing the
problem, but it would be helpful to know if you can duplicate the
problem in an up to date jessie system.

d

Attachment: pgpYSHgjKg8lH.pgp
Description: PGP signature

Reply via email to