| Summary: | Panorama tool doesn't find autooptimiser from Hugin 2017.0 | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | m*sh <hy> |
| Component: | Plugin-Generic-Panorama | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 5.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/digikam/4252b56dd206a04843a3d6f9d8ec5f3573436d16 | Version Fixed In: | 5.7.0 |
| Sentry Crash Report: | |||
| Attachments: | screenshot of the wizard window | ||
Here i use Hugin 2016.2 without problem under Mageia 6. All is detected as expected. I assembled more than 50 mosaic of 10-20 JPEGs (100-200 Mpx), and all work fine. Which Hugin version do you use exactly ? Gilles Caulier Hi Gilles, I am using hugin 2017.0 [hugin is already the newest version (2017.0.0~rc2+dfsg-2).] autooptimiser is in /usr/bin but nothing happens when I select it manually Greetings Can you check if the problem is reproducible with digiKam 5.7.0 pre-release AppImage bundle ? https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier Hi Gilles, I downloaded and started digikam-5.7.0-01-x86-64.appimage the problem persists. autooptimizer is in /usr/bin but after selecting it manually nothing happens. Git commit 4252b56dd206a04843a3d6f9d8ec5f3573436d16 by Gilles Caulier. Committed on 12/08/2017 at 22:27. Pushed by cgilles into branch 'master'. Panorama tool : fix autooptimiser detection with hugin 2017.0 FIXED-IN: 5.7.0 M +6 -5 NEWS M +2 -1 utilities/assistants/panorama/manager/autooptimiserbinary.h https://commits.kde.org/digikam/4252b56dd206a04843a3d6f9d8ec5f3573436d16 |
Created attachment 107154 [details] screenshot of the wizard window The panorama tool doesn't find autooptimiser Hugin is installed completely (Tried uninstall and reinstalled as well...) the wizard can't continue (see screenshot attached) It worked before but I don't use it very often - so I can not exactly describe What was changed. Actually I did one dist-upgrade between last usage in june and now.