| Summary: | cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Marcus <wellendorf> |
| Component: | Plugin-Generic-Panorama | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, wellendorf |
| Priority: | NOR | ||
| Version: | 5.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.7.0 | |
| Sentry Crash Report: | |||
| Attachments: | screenshot software hugin | ||
|
Description
Marcus
2017-06-27 23:26:44 UTC
Created attachment 106477 [details]
screenshot software hugin
In this window can click "find" and it opens /usr/bin where is installed autooptimiser. But clicking the program it returns to this screen, still not display the version and showing "find", not "change (Ändern)" Similar problem if I press "find" to find pto2mk. Actually pto2mk is not installed later than Hugin 2014, hugin should instead search for hugin_executor, not for pto2mk actually. Manually adding hugin_executor doesn't work. This is running on Manjaro stable. I installed a stable opensuse, digikam 5.2, where it works. This is on Manjaro stable. I parallel installed opensuse stable, where everything works fine with digikam 5.2. I cannot confirm this dysfunction here. I currently assemble a lots of panorama and mosaic huge image (around 20 JPEG - 200Mpx) from my trip in French Alps, and all work as expected with hugin 2016.2 and digiKam 5.7.0 pre-release. My system : Mageia 6 running on a small laptop DELL Latitude E6430 with 8Gb of RAM. Gilles Caulier I did some further research and found here another bug https://bugs.kde.org/show_bug.cgi?id=280736 which is maybe related to this. Manjaro provides hugin 2017.0.0-1. As far as I understood the panoramagui tests which version auf autooptimizer is installed through a parsing autooptimizer --help. The above mentioned bugs reporter writes about cpfind: > I assume it's executing 'cpfind --help' and trying to parse the first line, however kubuntu's hugin version does not have version number on the first line, but 'ThreadQueue created'. That would explain that even choosing autooptimizer doesn't work for me. But I don't know how to check the parsing process. Starting digikam from the console I get this output when opening the panoramagui: digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... digikam.general: Testing "autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: Testing "cpclean" ... digikam.general: "cpclean" help header line: "cpclean version 2017.0.0.eac5e8cc546e" digikam.general: Found "cpclean" version: "2017.0.0" digikam.general: Testing "cpfind" ... digikam.general: "cpfind" help header line: "Hugin's cpfind 2017.0.0.eac5e8cc546e" digikam.general: Found "cpfind" version: "2017.0.0" digikam.general: Testing "enblend" ... digikam.general: "enblend" help header line: "enblend 4.2" digikam.general: Found "enblend" version: "4.2" digikam.general: Testing "make" ... digikam.general: "make" help header line: "GNU Make 4.2.1" digikam.general: Found "make" version: "4.2.1" digikam.general: Testing "nona" ... digikam.general: "nona" help header line: "nona version 2017.0.0.eac5e8cc546e" digikam.general: Found "nona" version: "2017.0.0" digikam.general: Testing "pano_modify" ... digikam.general: "pano_modify" help header line: "pano_modify version 2017.0.0.eac5e8cc546e" digikam.general: Found "pano_modify" version: "2017.0.0" digikam.general: Testing "pto2mk" ... digikam.general: Testing "hugin_executor" ... digikam.general: Found "hugin_executor" digikam.general: Starting Main Thread digikam.general: Testing "autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... digikam.general: Testing "autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... digikam.general: Testing "autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: All Binaries Found : false digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... digikam.general: All Binaries Found : false digikam.general: Hugin >= 2015.0 : false digikam.general: Testing "pto2mk" ... digikam.general: Testing "autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: All Binaries Found : false digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... digikam.general: All Binaries Found : false If I manually choose autooptimizer I get this output: kf5.kio.widgets: No node found for item that was just removed: QUrl("file:///usr/bin/gdb") digikam.general: Testing "/usr/bin//autooptimiser" ... digikam.general: "autooptimiser" help header line: "" digikam.general: All Binaries Found : false I was writing autooptimizer but it should be autooptimiser! Checking the help file I get this: $ autooptimiser --help autooptimiser: optimize image positions autooptimiser version 2017.0.0.eac5e8cc546e Usage: autooptimiser [options] input.pto To read a project from stdio, specify - as input file. ... Which seems to be ok. ls -l /usr/bin/autooptimiser: -rwxr-xr-x 1 root root 133272 15. Jul 14:57 /usr/bin/autooptimiser Is that maybe a reason, the automatic testing searches here: digikam.general: Testing "/usr/bin/autooptimiser/autooptimiser" ... (autooptimiser inside a folder "autooptimiser") And manually adding the path: digikam.general: Testing "/usr/bin//autooptimiser" ... (two slashes: bin// ) So it's a DOWNSTREAM problem with your Linux box packaging ? Dear Gilles, thank you for your question. As far as I have researched the problem it could be a bug because it doesn't work with hugin 2017 or a packaging problem downstream, because it should be packaged with an earlier version of hugin. In the beginning I just saw, that the panorama stitching doesn't work for me. But my understanding now is, that it depends on your definition. Actually I posted at the Manjaro forum after I found out, that there have been similar problems with earlier versions and it might be a wrong packaging. Please let me know if you would say this is a packaging problem downstream and I will forward that to the Manjaro team. Thank you very much! I fixed the autooptimizer detection for next 5.7.0. See bug #383280. The hugin 2017.0 support work very well here. Gilles Caulier Great! Looking forward to get the new version. Just to confirm: After an update to 5.7.0 on Arch the autooptimizer detection is working. Thank you! Sorry, that was on Manjaro, I don't know about Arch. |