hugin-devs team mailing list archive

[tmodes <1666030@xxxxxxxxxxxxxxxxxx>]

Fixed in repository.

PS: For diagnosing there is the option "Copy log messages to clipboard"
in the preferences. Then you can paste the full log of the failed step.

** Summary changed:

- cpfind fails to run if custom temporary directory is set
+ assistant fails to run if custom temporary directory is set

** Changed in: hugin
       Status: New => Fix Committed

** Changed in: hugin
    Milestone: None => 2017.0beta1

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1666030

Title:
  assistant fails to run if custom temporary directory is set

Status in Hugin:
  Fix Committed

Bug description:
  If preferences->file name->Temporary dir is set to an non-empty value,
  running from cpfind from the Assistant ([2. Align]-button]) fails. The
  cpfind window pops up and closes immediately, an error message about
  unconnected images is shown.

  Running cpfind from the main window ([Photos]->[Create control
  points]) still works.

  Googling finds a thread on hugin-ptx but no solution:
  https://www.mail-archive.com/hugin-ptx@xxxxxxxxxxxxxxxx/msg24909.html
  https://groups.google.com/forum/#!msg/hugin-ptx/w_oeNy9rqDE/8qRP5UJzAgAJ
  | Greg 'groggy' Lehey Fri, 16 Sep 2016 18:00:47 -0700
  | [...]
  | For the record: setting that variable (which ends up in ~/.hugin as
  | tmpDir=/var/tmp, for example) appears to cause hugin pass an empty
  | PATH environment variable to icpfind, which then fails.  It's not the
  | problem of icpfind, which works fine if started directly.  But I
  | haven't had time to track it down yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1666030/+subscriptions