Hi,

Sorry for the noise but after more investigation on this problem it was related to a broken symlink in the alternatives handled by liblapack3 (probably after the upgrade to 3.8.0-2). And so running 'dpkg-reconfigure liblapack3' solved this. Strange...

But please feel free to close this bug.

Patrice

Reply via email to