[digikam] [Bug 381743] New: cpfind doesn.t work: couldn't parse panos tool script: 'pano_base.pto

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

            Bug ID: 381743
           Summary: cpfind doesn.t work: couldn't parse panos tool script:
                    'pano_base.pto
           Product: digikam
           Version: 5.6.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Panorama
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

Running the panorama tool the tool stops after choosing the photographies to be
stitched and pressing CONTINUE (with or without celeste) with the message

cpfind kann nicht ausgeführt werden:
Hugin's cpfind 2016.2.0.be8da0221960
based on Pan-o-matic by Anael Orlinski
WARN: 07:24:32.652100
(/build/hugin/src/hugin-2016.2.0/src/hugin_base/panodata/Panorama.cpp:2054)
readData(): Failed to read from dataInput.
ERROR: couldn't parse panos tool script: 'pano_base.pto'!
Detection took 0 seconds.

This might have been already with earlier version, I haven't used the panorama
tool for quite a time.

Any suggestions? Thank you!

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #1 from Marcus <[hidden email]> ---
Created attachment 106477
  --> https://bugs.kde.org/attachment.cgi?id=106477&action=edit
screenshot software hugin

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #2 from Marcus <[hidden email]> ---
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.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #3 from Marcus <[hidden email]> ---
This is running on Manjaro stable. I installed a stable opensuse, digikam 5.2,
where it works.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #4 from Marcus <[hidden email]> ---
This is on Manjaro stable. I parallel installed opensuse stable, where
everything works fine with digikam 5.2.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #5 from [hidden email] ---
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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #6 from Marcus <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #7 from Marcus <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #8 from Marcus <[hidden email]> ---
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// )

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381743

--- Comment #9 from [hidden email] ---
So it's a DOWNSTREAM problem with your Linux box packaging ?

--
You are receiving this mail because:
You are the assignee for the bug.