[Hugin-bug-hunters] [Bug 684357] [NEW] 2010.4.0 fails to build on kFreeBSD

[Andreas Metzler]

Public bug reported:

hugin 2010.4.0 failed to build from source on Debian kFreeBSD.

https://buildd.debian.org/fetch.cgi?pkg=huginver=2010.4.0%2Bdfsg~beta1-1arch
=kfreebsd-amd64stamp=1290937275file=log

The error is in src/foreign/zthread. One-line patch attached.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  2010.4.0 fails to build on kFreeBSD

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  hugin 2010.4.0 failed to build from source on Debian kFreeBSD.

https://buildd.debian.org/fetch.cgi?pkg=huginver=2010.4.0%2Bdfsg~beta1-1arch=kfreebsd-amd64stamp=1290937275file=log

The error is in src/foreign/zthread. One-line patch attached.



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 684357] Re: 2010.4.0 fails to build on kFreeBSD

[Andreas Metzler]

** Attachment added: bugfix
   
https://bugs.launchpad.net/bugs/684357/+attachment/1753300/+files/52_build_on_kFreeBSD

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

Title:
  2010.4.0 fails to build on kFreeBSD

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  hugin 2010.4.0 failed to build from source on Debian kFreeBSD.

https://buildd.debian.org/fetch.cgi?pkg=huginver=2010.4.0%2Bdfsg~beta1-1arch=kfreebsd-amd64stamp=1290937275file=log

The error is in src/foreign/zthread. One-line patch attached.



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679164] Re: hugin invokation of make failure on MAKEFLAGS=-j2

[Andreas Metzler]

Verified in 2010.4.0. Hugin nowadays invokes make -f ... info test all
clean, but this does not make a difference, clean and all still run
in parallell.

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

Title:
  hugin invokation of make failure on MAKEFLAGS=-j2

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  Hello,

this has originally been reported by Helmut Grohne in 
http://bugs.debian.org/525494.
--
nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 0 /tmp/huginpto_deFg2s
nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 1 /tmp/huginpto_deFg2s
nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 2 /tmp/huginpto_deFg2s
rm blah.tif blah0001.tif blah0002.tif 
enblend --compression LZW -m 1500 -f2277x4564 -o blah.tif blah.tif 
blah0001.tif blah0002.tif 

enblend: error opening input file blah.tif:

Precondition violation!
Unable to open file 'blah.tif'.

make: *** [blah.tif] Fehler 1
--

Hugin stitiching breaks if MAKEFLAGS=-j2 is set. The reason is a rather simple 
one, during stitching hugin invokes make all clean. With parallelisation 
clean is run before all is finished and this happens with three images and -j2 
(xa and xb are run in parallel):
1a nona for image 1
1b nona for image 2
--
2a nona for image 3
2b rm temporary files, including the output the first nona invocations
--
3a run enblend, which fails due to missing files.

The correct fix is to only run clean after all has finished (make all  make 
clean). Removing MAKEFLAGS from the environment might not hurt but should be 
configurable.
See also 
https://sourceforge.net/tracker/?func=detailaid=2781240group_id=77506atid=550441.

This is verified for 0.7.0, but afaict this should also apply to SVN HEAD 
(0.8.0 prerelease r3801), which invokes make test all clean.

thanks, cu andreas



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679367] Re: crashes on startup with tiling window manager

[Andreas Metzler]

*** This bug is a duplicate of bug 679427 ***
https://bugs.launchpad.net/bugs/679427

Marking as duplicate, removing fix-released.

** Changed in: hugin
   Status: Fix Released = Confirmed

** This bug has been marked a duplicate of bug 679427
   hugin seg faults at launch
 * You can subscribe to bug 679427 by following this link: 
https://bugs.launchpad.net/hugin/+bug/679427/+subscribe

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

Title:
  crashes on startup with tiling window manager

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  Hello,

this is http://bugs.debian.org/551006 but has also been reported on ubuntu LP 
https://bugs.launchpad.net/ubuntu/+source/hugin/+bug/450383

For some usere hugin crashes immediately upon startup. Don Armstrong has 
identified usage of a tiling window manager as possible common denominator and 
has provided a backtrace + offered to provide a coredump.



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 685489] [NEW] cpfind - add option to limit number of control points

[Andreas Metzler]

Public bug reported:

cpfind is missing a option to limit the the number of control points per
pair of images (like autopano-sift-c's --maxmatches option).

Having a large number of control points (cpfind adds 30+) increases the
amount of work to get rid of the bad ones.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  cpfind - add option to limit number of control points

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  cpfind is missing a option to limit the the number of control points per pair 
of images (like autopano-sift-c's --maxmatches option).

Having a large number of control points (cpfind adds 30+) increases the amount 
of work to get rid of the bad ones.



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679338] Re: EXIF-data mangles layout of Images Tab

[Andreas Metzler]

Current hugin impossible to make a reasonable  screenshot of or actually
use at screenwidth below 1200.

The Cp-detector list control element takes up lots of horizontal space
(Hugins CPFind + Celeste (slower but more accurate, no cps on clouds))
and the [Create control points] button is placed beside it. Moving
[Create control points] a little bit down (to the right of Points of
Overlap) would improve thing a lot.

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

Title:
  EXIF-data mangles layout of Images Tab

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  see attached image



___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 729607] Re: perldoc errors and warnings

[Andreas Metzler]

** Patch added: fix pod errorrs
   
https://bugs.launchpad.net/bugs/729607/+attachment/1887361/+files/fixpoderrors.diff

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

Title:
  perldoc errors and warnings

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  There are a couple of trivial syntax and formatting errors in the
  *.pod of 2011.0.0beta1. Some of them appear in the generated manpages
  in section POD ERRORS (e.g. deghosting_mask) others are only reported
  by podchecker.

  Find attached a patch to fix all issues found by podchecker except for
  a single one (WARNING: empty section in previous paragraph at line 11
  in file doc/calibrate_lens.pod. - This caused by a empty DESCRIPTION
  section.)

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 703735] Re: Hugin contains a bundled tclap-1.2.0

[Andreas Metzler]

FWIW I have compared src/foreign/tclap with upstream releases. The copy
in src/foreign is 1.1.0 (released  2006-08-19) + two one-line changes
instead of the latest release 1.2.0 (2009-09-28).

** Patch added: upstream 1.1.0 versus included copy
   
https://bugs.launchpad.net/hugin/+bug/703735/+attachment/1889986/+files/to-tclap-1.1.0.comparedtosrcforeign.diff

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

Title:
  Hugin contains a bundled tclap-1.2.0

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  src/foreign/tclap is a bundled version of tclap
  http://tclap.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 703735] Re: Hugin contains a bundled tclap-1.2.0

[Andreas Metzler]

works-for-me patch attached.

** Patch added: search for external tclap with pkg-cponfig
   
https://bugs.launchpad.net/hugin/+bug/703735/+attachment/1890075/+files/searchfortclap.diff

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

Title:
  Hugin contains a bundled tclap-1.2.0

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  src/foreign/tclap is a bundled version of tclap
  http://tclap.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 703735] Re: Hugin contains a bundled tclap-1.2.0

[Andreas Metzler]

On 2011-03-07 Yuv 703...@bugs.launchpad.net wrote:
 FindTclap.cmake is broken on Ubuntu.  The automatic build from the Hugin
 PPA reports:

 -- checking for module 'tclap=1.1'
 --   package 'tclap=1.1' not found
 CMake Error at CMakeLists.txt:274 (MESSAGE):
   Tclap library not found

 for Lucid, Maverick, Natty.

Did you add a build-dependcy on libtclap-dev?
cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  Hugin contains a bundled tclap-1.2.0

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  src/foreign/tclap is a bundled version of tclap
  http://tclap.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 703737] Re: Hugin contains a bundled flann-1.6.6

[Andreas Metzler]

Please note that FLANN is not packaged for Debian.
http://bugs.debian.org/581903

** Bug watch added: Debian Bug tracker #581903
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581903

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

Title:
  Hugin contains a bundled flann-1.6.6

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  src/foreign/flann is a bundled version of flann
  http://www.cs.ubc.ca/~mariusm/index.php/FLANN/FLANN This is a
  problem with some Linux distributions such as Debian and fedora that
  have policies to not ship multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 703736] Re: Hugin contains a bundled zthread-2.3.1

[Andreas Metzler]

Find attached a patch that changes hugin to use an external zthread if
available and fall back to the included copy otherwise. The code does
not do any version testing.

I think this should be a a sufficient solution for this issue. Afaiu the
big problem is not that hugin source contains a copy of the zthread
library, but that it cannot be built against an external version of the
library. OTOH removing exotic libraries like zthread from src/foreign
can make packaging harder.

** Patch added: search for external zthread library
   
https://bugs.launchpad.net/hugin/+bug/703736/+attachment/1898606/+files/zthread.patch

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

Title:
  Hugin contains a bundled zthread-2.3.1

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  src/foreign/zthread is a bundled version of zthread
  http://zthread.sourceforge.net/ This is a problem with some Linux
  distributions such as Debian and fedora that have policies to not ship
  multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 734867] [NEW] sporadic testsuite error

[Andreas Metzler]

Public bug reported:

Hello,

there is a heisenbug hidden somewhere in the testsuite. Occassionally it fails 
to run:
===
perl ../panoAutomateTest.pl simple.txt
Processing 2 images
To perform all tests:  tiff_m tiff_m_cropped tiff_m_uncropped

tiff_m = Output : TIFF_m
Removing old images: 2
output.tif - tests/tiff_m.tif
output0001.tif - tests/tiff_m0001.tif
Creating panorama.. please wait
PTmender Version 2.9.18 , originally written by Helmut Dersch, rewritten by 
Daniel German
Feathering is ignored. Use PTmasker
Feathering is ignored. Use PTmasker
Feathering is ignored. Use PTmasker
TIFFOpen:  #/_PTStitcher_tmp_03: Cannot open.

Converting Image 1 / 2  Filename 051221_6054_750.jpg
---
Unable to create output file [ #/_PTStitcher_tmp_03]
Could not open  #/_PTStitcher_tmp_03 for writing
===

I am getting the bug on the Debian autobuilder (e.g. 2.9.18rc2 failed on
s390 and amd64) but I have also gotten it once on my production system.
I do not know how to reproduce it though.

https://buildd.debian.org/build.php?pkg=libpano13arch=amd64
https://buildd.debian.org/build.php?pkg=libpano13arch=s390

** Affects: panotools
 Importance: Undecided
 Status: New

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

Title:
  sporadic testsuite error

Status in Panorama Tools:
  New

Bug description:
  Hello,

  there is a heisenbug hidden somewhere in the testsuite. Occassionally it 
fails to run:
  ===
  perl ../panoAutomateTest.pl simple.txt
  Processing 2 images
  To perform all tests:  tiff_m tiff_m_cropped tiff_m_uncropped

  tiff_m = Output : TIFF_m
  Removing old images: 2
  output.tif - tests/tiff_m.tif
  output0001.tif - tests/tiff_m0001.tif
  Creating panorama.. please wait
  PTmender Version 2.9.18 , originally written by Helmut Dersch, rewritten by 
Daniel German
  Feathering is ignored. Use PTmasker
  Feathering is ignored. Use PTmasker
  Feathering is ignored. Use PTmasker
  TIFFOpen:  #/_PTStitcher_tmp_03: Cannot open.

  Converting Image 1 / 2  Filename 051221_6054_750.jpg
  ---
  Unable to create output file [ #/_PTStitcher_tmp_03]
  Could not open  #/_PTStitcher_tmp_03 for writing
  ===

  I am getting the bug on the Debian autobuilder (e.g. 2.9.18rc2 failed
  on s390 and amd64) but I have also gotten it once on my production
  system. I do not know how to reproduce it though.

  https://buildd.debian.org/build.php?pkg=libpano13arch=amd64
  https://buildd.debian.org/build.php?pkg=libpano13arch=s390

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679605] Re: Invalid PNGs crash Hugin

[Andreas Metzler]

Still applies to 2011.0.0 beta3.

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

Title:
  Invalid PNGs crash Hugin

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  I came across some PNG images which would always crash hugin as soon
  as they are loaded.

  Digging a little deeper I discovered that the PNG file had been
  truncated (specifically... the last PNG IDAT chunk wasn\'t the number
  of bytes it should have been).

  Most image viewers I tried opened this file without a problem. Hugin
  should either load the image or (better still) give an error saying
  the image is invalid.

  This was only tested on windows. I have attached an example truncated
  PNG file.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679164] Re: hugin invokation of make failure on MAKEFLAGS=-j2

[Andreas Metzler]

Still present in 2011.0.0 beta3. It invokes make -f /tmp/huginmk_pViQ5m
info test all clean

** Changed in: hugin
   Status: Expired = Confirmed

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

Title:
  hugin invokation of make failure on MAKEFLAGS=-j2

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  Hello,

  this has originally been reported by Helmut Grohne in 
http://bugs.debian.org/525494.
  --
  nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 0 /tmp/huginpto_deFg2s
  nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 1 /tmp/huginpto_deFg2s
  nona -z PACKBITS -r ldr -m TIFF_m -o blah -i 2 /tmp/huginpto_deFg2s
  rm blah.tif blah0001.tif blah0002.tif 
  enblend --compression LZW -m 1500 -f2277x4564 -o blah.tif blah.tif 
blah0001.tif blah0002.tif 

  enblend: error opening input file blah.tif:

  Precondition violation!
  Unable to open file 'blah.tif'.

  make: *** [blah.tif] Fehler 1
  --

  Hugin stitiching breaks if MAKEFLAGS=-j2 is set. The reason is a rather 
simple one, during stitching hugin invokes make all clean. With 
parallelisation clean is run before all is finished and this happens with three 
images and -j2 (xa and xb are run in parallel):
  1a nona for image 1
  1b nona for image 2
  --
  2a nona for image 3
  2b rm temporary files, including the output the first nona invocations
  --
  3a run enblend, which fails due to missing files.

  The correct fix is to only run clean after all has finished (make all  make 
clean). Removing MAKEFLAGS from the environment might not hurt but should be 
configurable.
  See also 
https://sourceforge.net/tracker/?func=detailaid=2781240group_id=77506atid=550441.

  This is verified for 0.7.0, but afaict this should also apply to SVN
  HEAD (0.8.0 prerelease r3801), which invokes make test all clean.

  thanks, cu andreas

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 770802] Re: hugin version 2010.4.0+dfsg-1 failed to build on amd64 with GCC-4.6/oneiric

[Andreas Metzler]

I have just uploaded 2010.4.0+dfsg-2 to Debian/unstable which only adds
the one-line patch to fix this issue.

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

Title:
  hugin version 2010.4.0+dfsg-1 failed to build on amd64 with
  GCC-4.6/oneiric

Status in Hugin - Panorama Tools GUI:
  New
Status in “hugin” package in Ubuntu:
  New

Bug description:
  hugin version 2010.4.0+dfsg-1 failed to build on amd64 with GCC-4.6/oneiric
  Link to failed build: 
https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2453217

  Details about the rebuild:
  https://lists.ubuntu.com/archives/ubuntu-devel/2011-April/033042.html

  Direct link to the build log: https://launchpad.net/ubuntu/+archive
  /test-rebuild-20110413/+buildjob/2453217/+files/buildlog_ubuntu-natty-
  amd64.hugin_2010.4.0%2Bdfsg-1_FAILEDTOBUILD.txt.gz

  This log snippet might be of interest, since it triggered the matcher 
'Purging chroot-autobuild'.
  Excerpt 2346 lines into the build log:

  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:882:29:
 error: request for member 'begin' in '((const vigra::MultiArrayViewN, T, 
C*)this)-vigra::MultiArrayViewN, T, C::m_stride', which is of non-class 
type 'const difference_type'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:882:48:
 error: request for member 'begin' in '((const vigra::MultiArrayViewN, T, 
C*)this)-vigra::MultiArrayViewN, T, C::m_stride', which is of non-class 
type 'const difference_type'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:882:69:
 error: request for member 'begin' in 'stride', which is of non-class type 'int'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:883:29:
 error: request for member 'begin' in '((const vigra::MultiArrayViewN, T, 
C*)this)-vigra::MultiArrayViewN, T, C::m_stride', which is of non-class 
type 'const difference_type'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:883:54:
 error: request for member 'end' in '((const vigra::MultiArrayViewN, T, 
C*)this)-vigra::MultiArrayViewN, T, C::m_stride', which is of non-class 
type 'const difference_type'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:884:27:
 error: request for member 'begin' in 'stride', which is of non-class type 'int'
  
/build/buildd/hugin-2010.4.0+dfsg/src/foreign/vigra/vigra/multi_array.hxx:887:47:
 error: invalid types 'const difference_type[int]' for array subscript
  make[3]: *** 
[src/hugin_base/CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o]
 Error 1
  make[3]: Leaving directory `/build/buildd/hugin-2010.4.0+dfsg/build-dir'
  make[2]: *** [src/hugin_base/CMakeFiles/huginbase.dir/all] Error 2
  make[2]: Leaving directory `/build/buildd/hugin-2010.4.0+dfsg/build-dir'
  make[1]: *** [all] Error 2
  make[1]: Leaving directory `/build/buildd/hugin-2010.4.0+dfsg/build-dir'
  make: *** [build-arch-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2
  **
  Build finished at 20110423-1553
  FAILED [dpkg-buildpackage died]
  Purging chroot-autobuild/build/buildd/hugin-2010.4.0+dfsg

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 756245] Re: enblend doesn't compile with boost 1.46.1

[Andreas Metzler]

Find attached a simple one-line-patch, selecting the V2 interface of
boost_filename. This should work up to boost 1.47 and will break with
1.48_:


http://live.boost.org/doc/libs/1_46_1/libs/filesystem/v3/doc/index.htm

Version 3 is a major revision with many new and improved features. It
may, however, break some user code written for Version 2.

To ease the transition, Boost releases 1.44 through 1.47 will supply both V2 
and V3. Version 2 is the default version for Boost release 1.44 and 1.45. 
Version 3 will be the default starting with release 1.46.--
--

Alex, does enblend still build against older boost with your patch?

** Patch added: BOOST_FILESYSTEM_VERSION=2
   
https://bugs.launchpad.net/enblend/+bug/756245/+attachment/2106682/+files/set-boost-version.diff

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

Title:
  enblend doesn't compile with boost 1.46.1

Status in Enblend:
  New

Bug description:
  looks like basic_patch has been deprecated in boost::filesystem so
  compiling src/filenameparse.cc fails with:

  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:53:9: error: 
'basic_path' in namespace 'boost::filesystem' does not name a type
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc: In function 'bool 
enblend::isRelativePath(const std::string)':
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:63:11: error: 
'basic_path' does not name a type
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:64:13: error: 'path' 
was not declared in this scope
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc: In function 
'std::string enblend::extractDirname(const std::string)':
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:83:11: error: 
'basic_path' does not name a type
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:84:33: error: 'path' 
was not declared in this scope
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc: In function 
'std::string enblend::extractBasename(const std::string)':
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:97:11: error: 
'basic_path' does not name a type
  /home/romosan/cvs/panorama/enblend/src/filenameparse.cc:98:12: error: 'path' 
was not declared in this scope

  etc.

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 801869] [NEW] swig test needs to check version

[Andreas Metzler]

Public bug reported:

According to 2011.2.0_beta1 README hsi has specific version requirements
on swig:

SWIG =2.0 - If Python =3.2, SWIG must be =2.0.4

However the CMake setup does not do any version checks.

FindPythonLibs seems to be one of the (imho very broken) cmake modules
that does return any versioning info, making it impossible to completely
express the abovementioned dependency without trickery. However FindSWIG
can do version checks, making part1 (swig = 2.0) easy as pie:

--- CMakeLists.txt.orig 2011-06-25 09:03:31.0 +0200
+++ CMakeLists.txt  2011-06-25 09:03:54.0 +0200
@@ -295,7 +295,7 @@
 OPTION(BUILD_HSI Python Scripting Interface OFF)
 IF(BUILD_HSI)
   find_program(SWIG_EXECUTABLE NAMES swig2.0 swig)
-  FIND_PACKAGE(SWIG REQUIRED)
+  FIND_PACKAGE(SWIG 2.0 REQUIRED)
   INCLUDE(${SWIG_USE_FILE})

   FIND_PACKAGE(PythonLibs REQUIRED)

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  swig test needs to check version

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  According to 2011.2.0_beta1 README hsi has specific version
  requirements on swig:

  SWIG =2.0 - If Python =3.2, SWIG must be =2.0.4

  However the CMake setup does not do any version checks.

  FindPythonLibs seems to be one of the (imho very broken) cmake modules
  that does return any versioning info, making it impossible to
  completely express the abovementioned dependency without trickery.
  However FindSWIG can do version checks, making part1 (swig = 2.0)
  easy as pie:

  --- CMakeLists.txt.orig 2011-06-25 09:03:31.0 +0200
  +++ CMakeLists.txt  2011-06-25 09:03:54.0 +0200
  @@ -295,7 +295,7 @@
   OPTION(BUILD_HSI Python Scripting Interface OFF)
   IF(BUILD_HSI)
 find_program(SWIG_EXECUTABLE NAMES swig2.0 swig)
  -  FIND_PACKAGE(SWIG REQUIRED)
  +  FIND_PACKAGE(SWIG 2.0 REQUIRED)
 INCLUDE(${SWIG_USE_FILE})

 FIND_PACKAGE(PythonLibs REQUIRED)

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 801869] Re: swig test needs to check version

[Andreas Metzler]

On 2011-06-26 Yuv 801...@bugs.launchpad.net wrote:
 can you try with something along the following please?  sorry I do not
 have time right now to do it myself.
[...]

Hello,

seems to work with minor changes.

Comparing build logs against 2.6.7 and 3.2.1 (actually 2.6.7 with an
edited patchlevel.h file yields this:
-
--- Found SWIG: /usr/bin/swig2.0 (found suitable version 2.0.4, required is 
2.0.4)
+-- Found SWIG: /usr/bin/swig2.0 (found suitable version 2.0.4, required is 
2.0)
 -- Using shared internal libraries
--- Python libs version: 3.2.1
+-- Python libs version: 2.6.7
-

In the attached patch I have also dropped the (now duplicated) python
version parsing code in src/hugin_script_interface/CMakeLists.txt

thanks for the quick help,
cu andreas


** Patch added: versionedswigcheck.diff
   
https://bugs.launchpad.net/bugs/801869/+attachment/2181917/+files/versionedswigcheck.diff

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

Title:
  swig test needs to check version

Status in Hugin - Panorama Tools GUI:
  In Progress

Bug description:
  According to 2011.2.0_beta1 README hsi has specific version
  requirements on swig:

  SWIG =2.0 - If Python =3.2, SWIG must be =2.0.4

  However the CMake setup does not do any version checks.

  FindPythonLibs seems to be one of the (imho very broken) cmake modules
  that does return any versioning info, making it impossible to
  completely express the abovementioned dependency without trickery.
  However FindSWIG can do version checks, making part1 (swig = 2.0)
  easy as pie:

  --- CMakeLists.txt.orig 2011-06-25 09:03:31.0 +0200
  +++ CMakeLists.txt  2011-06-25 09:03:54.0 +0200
  @@ -295,7 +295,7 @@
   OPTION(BUILD_HSI Python Scripting Interface OFF)
   IF(BUILD_HSI)
 find_program(SWIG_EXECUTABLE NAMES swig2.0 swig)
  -  FIND_PACKAGE(SWIG REQUIRED)
  +  FIND_PACKAGE(SWIG 2.0 REQUIRED)
 INCLUDE(${SWIG_USE_FILE})

 FIND_PACKAGE(PythonLibs REQUIRED)

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 811864] [NEW] PTBatcherGUI annoying window handling

[Andreas Metzler]

Public bug reported:

With 2011.2.0 the old Stich Now! is gone, I am using PTBatcherGUI
instead.

The window handling is very annoying. The main autobatcher window and
the progress window are automatically if switch to another virtual
desktop and back again.

It would also be very nice if closing the hugin apllication would close
(the not manually started) PTBatcherGUI instance, too.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  PTBatcherGUI annoying window handling

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  With 2011.2.0 the old Stich Now! is gone, I am using PTBatcherGUI
  instead.

  The window handling is very annoying. The main autobatcher window and
  the progress window are automatically if switch to another virtual
  desktop and back again.

  It would also be very nice if closing the hugin apllication would
  close (the not manually started) PTBatcherGUI instance, too.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 811864] Re: PTBatcherGUI annoying window handling

[Andreas Metzler]

On 2011-09-11 tmodes 811...@bugs.launchpad.net wrote:
 The observed behaviour is related to the window manager. First it
 does not support the tray area.

Correct. This is wmaker FWIW.

 Second the virtual desktop seems to
 be implemented by only minimizing the windows, which are not on the
 active desktop. 

Any way for me to check whether wmaker really implements virtual
desktops this way?

cu andreas

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

Title:
  PTBatcherGUI annoying window handling

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  With 2011.2.0 the old Stich Now! is gone, I am using PTBatcherGUI
  instead.

  The window handling is very annoying. The main autobatcher window and
  the progress window are automatically if switch to another virtual
  desktop and back again.

  It would also be very nice if closing the hugin apllication would
  close (the not manually started) PTBatcherGUI instance, too.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 811864] Re: PTBatcherGUI annoying window handling

[Andreas Metzler]

On 2011-09-11 T. Modes thomas.mo...@gmx.de wrote:
 Hi Andreas,

 some questions to your bug report:

 Have you also tried current tip? I did a change in the last week to
 deactivate the tray icon. Does the mainwindow also disappear if no
 stitch was started (because I don't really understand, why the
 PTBatcherGUI main window disappears.) Please test minimizing windows and
 switching desktops.
[...]

In current tip the strange behavior is fixed, neither the PTBatcherGUI
main window nor the verbose-execution window are automatically minimized
when switching desktops. :-)

Is there any point in me trying out the other thing you suggested?
thanks cu andreas

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

Title:
  PTBatcherGUI annoying window handling

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  With 2011.2.0 the old Stich Now! is gone, I am using PTBatcherGUI
  instead.

  The window handling is very annoying. The main autobatcher window and
  the progress window are automatically if switch to another virtual
  desktop and back again.

  It would also be very nice if closing the hugin apllication would
  close (the not manually started) PTBatcherGUI instance, too.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 853171] [NEW] typo in cpfind.pod - prefered

[Andreas Metzler]

Public bug reported:

There is is a typo in cpfind's documentation. Patch against hg tip
attached.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  typo in cpfind.pod - prefered

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  There is is a typo in cpfind's documentation. Patch against hg tip
  attached.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 685877] Re: Push VIGRA changes to the right place

[Andreas Metzler]

VIGRA 1.8.0 was released today. It contains the patches from hugin which
were forwarded upstream
http://comments.gmane.org/gmane.comp.video.vigra/42.

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

Title:
  Push VIGRA changes to the right place

Status in Enblend:
  Confirmed
Status in Hugin - Panorama Tools GUI:
  Confirmed
Status in “enblend-enfuse” package in Debian:
  Confirmed
Status in “hugin” package in Debian:
  Confirmed
Status in “enblend” package in Fedora:
  New

Bug description:
  Enblend embeds a modified version of the VIGRA 1.4 library. Can we
  push the necessary changes to VIGRA's upstream and use the system
  version rather than an embedded copy?

  Details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542258

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 892827] [NEW] calibrate_lens_gui Segmentation fault on amd64

[Andreas Metzler]

Public bug reported:

On 2011.2.0 this bug is reproducible on amd64:
-
Francesco Potortì writes in http://bugs.debian.org/649171
I call calibrate_lens_gui, have it load the image at
http://fly.isti.cnr.it/tmp/hugin-bug.jpeg.  I set Focal lenght to 157
and Focal length multiplier to 1.  When I press the Find lines button
the program dumps core.
-

i386 binaries or  2011.4.0beta1 on amd64 does not crash. I am still
forwarding this since some doublechecking whether the issue is just not
triggered anymore or whether it was really fixed should be done.

gdb backtrace looks like this:
(sid-AMD64)ametzler@argenau:/tmp/HUGIN/hugin-2011.2.0+dfsg$ gdb `which calibrate
_lens_gui `
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/calibrate_lens_gui...done.
(gdb) run
Starting program: /usr/bin/calibrate_lens_gui
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe9029700 (LWP 505)]
[New Thread 0x7fffe8828700 (LWP 507)]
[Thread 0x7fffe9029700 (LWP 505) exited]
[New Thread 0x7fffe9029700 (LWP 508)]
[New Thread 0x7fffe3f9f700 (LWP 509)]
[New Thread 0x7fffe379e700 (LWP 510)]
[New Thread 0x7fffe2f9d700 (LWP 511)]
[New Thread 0x7fffe279c700 (LWP 512)]
[New Thread 0x7fffe1f9b700 (LWP 513)]
[New Thread 0x7fffe179a700 (LWP 514)]
[New Thread 0x7fffe0f99700 (LWP 515)]
[New Thread 0x7fffdbfff700 (LWP 516)]
[Thread 0x7fffe2f9d700 (LWP 511) exited]
[Thread 0x7fffe279c700 (LWP 512) exited]
[Thread 0x7fffe0f99700 (LWP 515) exited]
[Thread 0x7fffe3f9f700 (LWP 509) exited]
[Thread 0x7fffe8828700 (LWP 507) exited]
[Thread 0x7fffdbfff700 (LWP 516) exited]
[Thread 0x7fffe179a700 (LWP 514) exited]
[Thread 0x7fffe1f9b700 (LWP 513) exited]
[Thread 0x7fffe379e700 (LWP 510) exited]
[New Thread 0x7fffe379e700 (LWP 517)]
[New Thread 0x7fffdbfff700 (LWP 518)]
[New Thread 0x7fffe179a700 (LWP 519)]
[New Thread 0x7fffe8828700 (LWP 520)]
[New Thread 0x7fffe3f9f700 (LWP 521)]

(calibrate_lens_gui:491): Gtk-WARNING **: Could not find the icon 'image-jpeg'. 
The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases
[Thread 0x7fffe179a700 (LWP 519) exited]
[Thread 0x7fffe379e700 (LWP 517) exited]
[Thread 0x7fffe9029700 (LWP 508) exited]
[Thread 0x7fffe3f9f700 (LWP 521) exited]
[Thread 0x7fffe8828700 (LWP 520) exited]
Unable to read EXIF data from opened file:/tmp/hugin-bug.jpeg

(calibrate_lens_gui:491): Gtk-WARNING **: Attempting to store changes
into `/home/ametzler/.local/share/recently-used.xbel', but failed:
Failed to create file '/home/ametzler/.local/share/recently-
used.xbel.8LTA5V': No such file or directory

(calibrate_lens_gui:491): Gtk-WARNING **: Attempting to set the
permissions of `/home/ametzler/.local/share/recently-used.xbel', but
failed: No such file or directory

(calibrate_lens_gui:491): Gtk-WARNING **: Attempting to store changes
into `/home/ametzler/.local/share/recently-used.xbel', but failed:
Failed to create file '/home/ametzler/.local/share/recently-
used.xbel.GPTA5V': No such file or directory

(calibrate_lens_gui:491): Gtk-WARNING **: Attempting to set the
permissions of `/home/ametzler/.local/share/recently-used.xbel', but
failed: No such file or directory

Program received signal SIGSEGV, Segmentation fault.
vigra::internalCannyFindEdgelsvigra::BasicImagedouble, std::allocatordouble 
, vigra::BasicImagedouble, std::allocatordouble , 
std::vectorvigra::Edgel, std::allocatorvigra::Edgel   (gx=..., gy=..., 
magnitude=..., edgels=...)
at 
/tmp/HUGIN/hugin-2011.2.0+dfsg/src/foreign/vigra/vigra/edgedetection.hxx:1222
1222PixelType m1 = magnitude(x1, y1);
(gdb) bt
#0  vigra::internalCannyFindEdgelsvigra::BasicImagedouble, 
std::allocatordouble , vigra::BasicImagedouble, std::allocatordouble , 
std::vectorvigra::Edgel, std::allocatorvigra::Edgel   (gx=..., gy=..., 
magnitude=...,
edgels=...)
at 
/tmp/HUGIN/hugin-2011.2.0+dfsg/src/foreign/vigra/vigra/edgedetection.hxx:1222
#1  0x757f4628 in 
vigra::cannyEdgelListvigra::ConstBasicImageIteratorunsigned char, unsigned 
char**, vigra::StandardConstValueAccessorunsigned char, 
std::vectorvigra::Edgel, std::allocatorvigra::Edgel   (ul=..., lr=...,
src=..., edgels=..., scale=2)
at 
/tmp/HUGIN/hugin-2011.2.0+dfsg/src/foreign/vigra/vigra/edgedetection.hxx:1351
#2  0x757f4dc7 in 
vigra::cannyEdgeImagevigra::ConstBasicImageIteratorunsigned char, unsigned 
char**, vigra::StandardConstValueAccessorunsigned char, 

Re: [Hugin-bug-hunters] [Bug 892827] Re: calibrate_lens_gui Segmentation fault on amd64

[Andreas Metzler]

On 2011-11-27 Bruno Postle 892...@bugs.launchpad.net wrote:
 I don't see this crash on 64bit fedora 15, hugin 2011.3.0  2011-10-31
 snapshot

As I tried to note in the original report this does not apply to
2011.4.0beta1. I am still forwarding this since some doublechecking
whether the issue is just not triggered anymore or whether it was
really fixed should be done.

cu andreas

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

Title:
  calibrate_lens_gui Segmentation fault on amd64

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  On 2011.2.0 this bug is reproducible on amd64:
  -
  Francesco Potortì writes in http://bugs.debian.org/649171
  I call calibrate_lens_gui, have it load the image at
  http://fly.isti.cnr.it/tmp/hugin-bug.jpeg.  I set Focal lenght to 157
  and Focal length multiplier to 1.  When I press the Find lines button
  the program dumps core.
  -

  i386 binaries or  2011.4.0beta1 on amd64 does not crash. I am still
  forwarding this since some doublechecking whether the issue is just
  not triggered anymore or whether it was really fixed should be done.

  gdb backtrace looks like this:
  (sid-AMD64)ametzler@argenau:/tmp/HUGIN/hugin-2011.2.0+dfsg$ gdb `which 
calibrate
  _lens_gui `
  GNU gdb (GDB) 7.3-debian
  Copyright (C) 2011 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as x86_64-linux-gnu.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/...
  Reading symbols from /usr/bin/calibrate_lens_gui...done.
  (gdb) run
  Starting program: /usr/bin/calibrate_lens_gui
  [Thread debugging using libthread_db enabled]
  [New Thread 0x7fffe9029700 (LWP 505)]
  [New Thread 0x7fffe8828700 (LWP 507)]
  [Thread 0x7fffe9029700 (LWP 505) exited]
  [New Thread 0x7fffe9029700 (LWP 508)]
  [New Thread 0x7fffe3f9f700 (LWP 509)]
  [New Thread 0x7fffe379e700 (LWP 510)]
  [New Thread 0x7fffe2f9d700 (LWP 511)]
  [New Thread 0x7fffe279c700 (LWP 512)]
  [New Thread 0x7fffe1f9b700 (LWP 513)]
  [New Thread 0x7fffe179a700 (LWP 514)]
  [New Thread 0x7fffe0f99700 (LWP 515)]
  [New Thread 0x7fffdbfff700 (LWP 516)]
  [Thread 0x7fffe2f9d700 (LWP 511) exited]
  [Thread 0x7fffe279c700 (LWP 512) exited]
  [Thread 0x7fffe0f99700 (LWP 515) exited]
  [Thread 0x7fffe3f9f700 (LWP 509) exited]
  [Thread 0x7fffe8828700 (LWP 507) exited]
  [Thread 0x7fffdbfff700 (LWP 516) exited]
  [Thread 0x7fffe179a700 (LWP 514) exited]
  [Thread 0x7fffe1f9b700 (LWP 513) exited]
  [Thread 0x7fffe379e700 (LWP 510) exited]
  [New Thread 0x7fffe379e700 (LWP 517)]
  [New Thread 0x7fffdbfff700 (LWP 518)]
  [New Thread 0x7fffe179a700 (LWP 519)]
  [New Thread 0x7fffe8828700 (LWP 520)]
  [New Thread 0x7fffe3f9f700 (LWP 521)]

  (calibrate_lens_gui:491): Gtk-WARNING **: Could not find the icon 
'image-jpeg'. The 'hicolor' theme
  was not found either, perhaps you need to install it.
  You can get a copy from:
  http://icon-theme.freedesktop.org/releases
  [Thread 0x7fffe179a700 (LWP 519) exited]
  [Thread 0x7fffe379e700 (LWP 517) exited]
  [Thread 0x7fffe9029700 (LWP 508) exited]
  [Thread 0x7fffe3f9f700 (LWP 521) exited]
  [Thread 0x7fffe8828700 (LWP 520) exited]
  Unable to read EXIF data from opened file:/tmp/hugin-bug.jpeg

  (calibrate_lens_gui:491): Gtk-WARNING **: Attempting to store changes
  into `/home/ametzler/.local/share/recently-used.xbel', but failed:
  Failed to create file '/home/ametzler/.local/share/recently-
  used.xbel.8LTA5V': No such file or directory

  (calibrate_lens_gui:491): Gtk-WARNING **: Attempting to set the
  permissions of `/home/ametzler/.local/share/recently-used.xbel', but
  failed: No such file or directory

  (calibrate_lens_gui:491): Gtk-WARNING **: Attempting to store changes
  into `/home/ametzler/.local/share/recently-used.xbel', but failed:
  Failed to create file '/home/ametzler/.local/share/recently-
  used.xbel.GPTA5V': No such file or directory

  (calibrate_lens_gui:491): Gtk-WARNING **: Attempting to set the
  permissions of `/home/ametzler/.local/share/recently-used.xbel', but
  failed: No such file or directory

  Program received signal SIGSEGV, Segmentation fault.
  vigra::internalCannyFindEdgelsvigra::BasicImagedouble, 
std::allocatordouble , vigra::BasicImagedouble, std::allocatordouble , 
std::vectorvigra::Edgel, std::allocatorvigra::Edgel   (gx=..., gy=..., 
magnitude=..., edgels=...)
  at 
/tmp/HUGIN/hugin-2011.2.0+dfsg/src/foreign/vigra/vigra/edgedetection.hxx:1222
  1222PixelType m1 = magnitude(x1, y1);
  (gdb) bt
  #0  

[Hugin-bug-hunters] [Bug 703737] Re: Hugin contains a bundled flann-1.6.6

[Andreas Metzler]

Hello,

find attached a patch against 2011.4.0rc1 to link against external flann
if available.

cu Andreas

** Patch added: link against external flann if available
   
https://bugs.launchpad.net/hugin/+bug/703737/+attachment/2624513/+files/externalflann.diff

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

Title:
  Hugin contains a bundled flann-1.6.6

Status in Hugin - Panorama Tools GUI:
  Confirmed

Bug description:
  src/foreign/flann is a bundled version of flann
  http://www.cs.ubc.ca/~mariusm/index.php/FLANN/FLANN This is a
  problem with some Linux distributions such as Debian and fedora that
  have policies to not ship multiple versions of the same library.

  The solution would be to modify the cmake configuration to allow
  building against a system version of this library, and/or to remove
  the bundled library altogether.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 999833] [NEW] build error with gcc 4.7 on s390

[Andreas Metzler]

Public bug reported:

Hello,

hugin 2011.4.0 does not build with gcc-4.7. There is an easy to fix
error about a missing include (already tracked and patched in
https://bugs.launchpad.net/hugin/+bug/913250) however there is another
issue that I have only seen on s390 yet:

https://buildd.debian.org/status/fetch.php?pkg=huginarch=s390ver=2011.4.0%2Bdfsg-2stamp=1336510492
Building CXX object 
src/hugin_script_interface/CMakeFiles/_hsi.dir/hsiPYTHON_wrap.cxx.o
[...]
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:
 In function 'Sequence* swig::getslice(const Sequence*, Difference, Difference, 
Py_ssize_t) [with Sequence = std::vectorunsigned int, Difference = long int, 
Py_ssize_t = long int]':
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:5248:45:
   instantiated from here
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:4476:5:
 error: invalid initialization of reference of type 'ptrdiff_t {aka int}' 
from expression of type 'long int'

Any ideas?

thanks, cu andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  build error with gcc 4.7 on s390

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2011.4.0 does not build with gcc-4.7. There is an easy to fix
  error about a missing include (already tracked and patched in
  https://bugs.launchpad.net/hugin/+bug/913250) however there is another
  issue that I have only seen on s390 yet:

  
https://buildd.debian.org/status/fetch.php?pkg=huginarch=s390ver=2011.4.0%2Bdfsg-2stamp=1336510492
  Building CXX object 
src/hugin_script_interface/CMakeFiles/_hsi.dir/hsiPYTHON_wrap.cxx.o
  [...]
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:
 In function 'Sequence* swig::getslice(const Sequence*, Difference, Difference, 
Py_ssize_t) [with Sequence = std::vectorunsigned int, Difference = long int, 
Py_ssize_t = long int]':
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:5248:45:
   instantiated from here
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:4476:5:
 error: invalid initialization of reference of type 'ptrdiff_t {aka int}' 
from expression of type 'long int'

  Any ideas?

  thanks, cu andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 999833] Re: build error with gcc 4.7 on s390

[Andreas Metzler]

Thomas' seems to be correct. Updating to swig 2.0.6 fixed the issue.
Thank you!

** Changed in: hugin
   Status: New = Invalid

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

Title:
  build error with gcc 4.7 on s390

Status in Hugin - Panorama Tools GUI:
  Invalid

Bug description:
  Hello,

  hugin 2011.4.0 does not build with gcc-4.7. There is an easy to fix
  error about a missing include (already tracked and patched in
  https://bugs.launchpad.net/hugin/+bug/913250) however there is another
  issue that I have only seen on s390 yet:

  
https://buildd.debian.org/status/fetch.php?pkg=huginarch=s390ver=2011.4.0%2Bdfsg-2stamp=1336510492
  Building CXX object 
src/hugin_script_interface/CMakeFiles/_hsi.dir/hsiPYTHON_wrap.cxx.o
  [...]
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:
 In function 'Sequence* swig::getslice(const Sequence*, Difference, Difference, 
Py_ssize_t) [with Sequence = std::vectorunsigned int, Difference = long int, 
Py_ssize_t = long int]':
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:5248:45:
   instantiated from here
  
/build/buildd-hugin_2011.4.0+dfsg-2-s390-X6zIld/hugin-2011.4.0+dfsg/build-dir/src/hugin_script_interface/hsiPYTHON_wrap.cxx:4476:5:
 error: invalid initialization of reference of type 'ptrdiff_t {aka int}' 
from expression of type 'long int'

  Any ideas?

  thanks, cu andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1020755] Re: pto_gen does not get packaged

[Andreas Metzler]

@Logan: This bug has nothing to do with the Ubuntu packaging. Any
(semi-)official Debian/Ubuntu package of a newly enough hugin version
already ships pto_gen.

Please note that this binary is not present in latest hugin release
2011.4, which is what Ubuntu ships. Only Debian/experimental and hugin-
next ppa  have packages of 2011.0.0~rc2.

** Changed in: hugin (Ubuntu)
   Status: New = Invalid

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

Title:
  pto_gen does not get packaged

Status in Hugin - Panorama Tools GUI:
  Fix Committed
Status in “hugin” package in Ubuntu:
  Invalid

Bug description:
  The version of hugin that is present in 12.04 should include the
  pto_gen binary.  It is reported that if you do make install with
  this version, the pto_gen binary will be installed, but if you do
  make package the pto_gen binary does not get included in the
  package.

  Ref:
  https://groups.google.com/d/msg/hugin-ptx/D9XzqchEoE0/gLZKDCyAG9cJ

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu

[Andreas Metzler]

This is fixed upstream in enblend-enfuse 4.1.

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

Title:
  Completely replace lcms1 by lcms2 in Ubuntu

Status in digiKam - digital photo management:
  Fix Released
Status in Enblend:
  Fix Committed
Status in Inkscape: A Vector Drawing Tool:
  Fix Released
Status in Wine:
  Confirmed
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “dcraw” package in Ubuntu:
  New
Status in “digikam” package in Ubuntu:
  Fix Released
Status in “enblend” package in Ubuntu:
  New
Status in “enblend-enfuse” package in Ubuntu:
  New
Status in “f-spot” package in Ubuntu:
  New
Status in “geeqie” package in Ubuntu:
  New
Status in “gimp” package in Ubuntu:
  New
Status in “imagemagick” package in Ubuntu:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Fix Released
Status in “kdegraphics” package in Ubuntu:
  Invalid
Status in “lcms” package in Ubuntu:
  New
Status in “libkdcraw” package in Ubuntu:
  Fix Released
Status in “libmng” package in Ubuntu:
  New
Status in “libraw” package in Ubuntu:
  Fix Released
Status in “openjdk-6” package in Ubuntu:
  New
Status in “poppler” package in Ubuntu:
  Fix Released
Status in “python-imaging” package in Ubuntu:
  New
Status in “rawstudio” package in Ubuntu:
  New
Status in “scribus” package in Ubuntu:
  New
Status in “shotwell” package in Ubuntu:
  Fix Released
Status in “ufraw” package in Ubuntu:
  New
Status in “wine1.4” package in Ubuntu:
  Triaged
Status in “xsane” package in Ubuntu:
  New

Bug description:
  Many packages in Ubuntu use the liblcms1 library (source package
  lcms). This library is discontinued upstream and replaced by liblcms2.
  Due to this bugs in liblcms1 are not fixed any more upstream and
  important improvements in color reproduction and safety against
  crashes are not done. Therefore we should remove lcms1 and migrate all
  programs using it to lcms2.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1057012] Re: cpfind always fail on photos with long path

[Andreas Metzler]

Forwarded to
http://sourceforge.net/mailarchive/forum.php?thread_name=1b0ts9-269.ln1%40argenau.downhill.at.eu.orgforum_name
=panotools-devel

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

Title:
  cpfind always fail on photos with long path

Status in Panorama Tools:
  New
Status in “libpano13” package in Ubuntu:
  New

Bug description:
  # Summary

  When run with long paths, cpfind always fails.
  Impact : no automatic control points are available in hugin.

  # Symptom

  When hugin is instructed to work on photos that have a long absolute
  filesystem path, hugin never finds any control point using cpfind.
  Instead the default popup says :

   Warning n unconnected image groups found: (list of [imagenumber])
   Please create control points between unconnected images using the Control 
Points tab.
  
   After adding the points, press the Align button again

  I figured out it was a path length problem because when making a
  minimal test case with shorter path, the bug disappears.

  # How to reproduce

  Make a directory with a long path, e.g.

  
MP=~/AiHome/gros/tries/30_perso/image/PhotoNumerique/by_year/2012-01-02_11.46.57_2012-09-25_18.34.24_Annee_2012/panocuisine/2012-09-25_18.29.02_2012-09-25_18.29.07_correction_porte_fermee_NET
  ; mkdir -p $MP ; cd $MP

  * Copy at least two JPEGs from a digital camera there. Names can be e.g. 
2012-09-25_18.29.03__DSC_3466.JPG
  * Open hugin
  * Import two photos from that directory
  * Press Align...

  ## Expected

  * Some control points found, depending on photos.

  ## Observed

  * No control point found.
  * cpfind log (obtained before window disappears, or by running it separately) 
says

  --- Find matches ---
  *** buffer overflow detected ***: cpfind terminated
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x2b29d619cee7]
  /lib/x86_64-linux-gnu/libc.so.6(+0x107de0)[0x2b29d619bde0]
  /lib/x86_64-linux-gnu/libc.so.6(+0x107249)[0x2b29d619b249]
  /lib/x86_64-linux-gnu/libc.so.6(_IO_default_xsputn+0xdd)[0x2b29d610faad]
  /lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x256e)[0x2b29d60ddbae]
  /lib/x86_64-linux-gnu/libc.so.6(__vsprintf_chk+0x94)[0x2b29d619b2e4]
  /lib/x86_64-linux-gnu/libc.so.6(__sprintf_chk+0x7d)[0x2b29d619b22d]
  /usr/lib/libpano13.so.2(ParseScript+0x7f6)[0x2b29d51fe536]
  
/usr/lib/hugin/libhuginbase.so.0.0(_ZN9HuginBase6PTools8optimizeERNS_12PanoramaDataEPKc+0x46)[0x2b29d4cbfcc6]
  
/usr/lib/hugin/libhuginbase.so.0.0(_ZN6Ransac7computeIN9HuginBase14PTOptEstimatorESt6vectorIdSaIdEENS1_12ControlPointEEES3_IPKT1_SaIS9_EERT0_RS3_IiSaIiEERKT_RKS3_IS7_SaIS7_EEdd+0x124a)[0x2b29d477106a]
  
/usr/lib/hugin/libhuginbase.so.0.0(_ZN9HuginBase15RANSACOptimizer11findInliersERNS_12PanoramaDataEiidNS0_4ModeE+0x166)[0x2b29d4769996]
  
cpfind(_ZN12PanoDetector22RansacMatchesInPairCamERNS_9MatchDataERKS_+0x592)[0x44e7c2]
  cpfind(_ZN17MatchDataRunnable3runEv+0x35)[0x443805]
  /usr/lib/libZThread-2.3.so.2(+0x186ce)[0x2b29d3eee6ce]
  /usr/lib/libZThread-2.3.so.2(+0x17062)[0x2b29d3eed062]
  
/usr/lib/libZThread-2.3.so.2(_ZN7ZThread10ThreadImpl8dispatchEPS0_S1_NS_4TaskE+0x2ed)[0x2b29d3efb66d]
  /usr/lib/libZThread-2.3.so.2(+0x25b26)[0x2b29d3efbb26]
  /usr/lib/libZThread-2.3.so.2(_dispatch+0xa)[0x2b29d3efefba]
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2b29d4111e9a]
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b29d618639d]

  
  ## Additional information

  * When shortening path, problem disappears.
  * (Separate issue) perhaps hugin should have spotted failure of cpfind 
instead of just saying no control point was found.
  * I can provide some photos if needed.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System - About Ubuntu

  $ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  $ LC_ALL=C apt-cache policy hugin
  hugin:
Installed: 2011.4.0+dfsg-1
Candidate: 2011.4.0+dfsg-1
Version table:
   *** 2011.4.0+dfsg-1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hugin 2011.4.0+dfsg-1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Wed Sep 26 16:34:42 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120419)
  SourcePackage: hugin
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : 

[Hugin-bug-hunters] [Bug 1181678] [NEW] build-error with texinfo 5.1

[Andreas Metzler]

Public bug reported:

Hello,

documentation generation fails with texinfo 5.1.  texinfo seems to have stopped 
supporting colons in variable names (@set - @value), causing errors like this 
one:
-
doc/enfuse.texi:564: bad syntax for @value
-

According to texinfo 5.1 documentation basically the only thing
guaranteed to work are alpha-numericals:

Subsequent characters, if any, may not be whitespace, ‘@’, braces, angle
brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may work.
However, it is best to use only letters and numerals in a flag name, not
‘-’ or ‘_’ or others—they will work in some contexts, but not all, due
to limitations in TeX.

cu Andreas

See http://bugs.debian.org/708800 or
https://bugzilla.redhat.com/show_bug.cgi?id=919935

** Affects: enblend
 Importance: Undecided
 Status: New

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

Title:
  build-error with texinfo 5.1

Status in Enblend:
  New

Bug description:
  Hello,

  documentation generation fails with texinfo 5.1.  texinfo seems to have 
stopped supporting colons in variable names (@set - @value), causing errors 
like this one:
  -
  doc/enfuse.texi:564: bad syntax for @value
  -

  According to texinfo 5.1 documentation basically the only thing
  guaranteed to work are alpha-numericals:

  Subsequent characters, if any, may not be whitespace, ‘@’, braces,
  angle brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may
  work. However, it is best to use only letters and numerals in a flag
  name, not ‘-’ or ‘_’ or others—they will work in some contexts, but
  not all, due to limitations in TeX.

  cu Andreas

  See http://bugs.debian.org/708800 or
  https://bugzilla.redhat.com/show_bug.cgi?id=919935

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1181678] Re: build-error with texinfo 5.1

[Andreas Metzler]

Hello,

thanks for trying, there is still some stuff texinfo fails on. - See
attached log.

cu Andreas

** Attachment added: errors on generating enblend.info
   
https://bugs.launchpad.net/enblend/+bug/1181678/+attachment/3680880/+files/buildlog-hg

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

Title:
  build-error with texinfo 5.1

Status in Enblend:
  New

Bug description:
  Hello,

  documentation generation fails with texinfo 5.1.  texinfo seems to have 
stopped supporting colons in variable names (@set - @value), causing errors 
like this one:
  -
  doc/enfuse.texi:564: bad syntax for @value
  -

  According to texinfo 5.1 documentation basically the only thing
  guaranteed to work are alpha-numericals:

  Subsequent characters, if any, may not be whitespace, ‘@’, braces,
  angle brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may
  work. However, it is best to use only letters and numerals in a flag
  name, not ‘-’ or ‘_’ or others—they will work in some contexts, but
  not all, due to limitations in TeX.

  cu Andreas

  See http://bugs.debian.org/708800 or
  https://bugzilla.redhat.com/show_bug.cgi?id=919935

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1181678] Re: build-error with texinfo 5.1

[Andreas Metzler]

Hello,

I have /somehow/ succeeded with these steps:
#1 Drop geq and leq macros from auxmac.texi.
#2 Make sure any macro-reference on a macro using a conditional is on a line of 
its own. (@classictimes, @semilog, 
@inline*)
#3 Drop export TEXINPUTS=$(top_builddir):$(srcdir) from doc/Makefile.am

#1 should be safe to do, the macros are marked with Required for older 
versions of makeinfo anyway.
#3 Seems to be correct.

Regarding #2  the texinfo documentation says Macros containing a command which 
must be on a line by itself, such as a conditional, cannot be invoked in the 
middle of a line. This breaks the formatting, though e.g. changing the input 
like this
-
-@math{width}@classictimes{}@math{height}@tie{}pixels cannot be
+@math{width}
+@classictimes{}
+@math{height}@tie{}pixels cannot be

adds unwanted whitespace in the output:
---
-an image of widthxheight pixels cannot be
+an image of width xheight pixels cannot be
---
cu Andreas

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

Title:
  build-error with texinfo 5.1

Status in Enblend:
  New

Bug description:
  Hello,

  documentation generation fails with texinfo 5.1.  texinfo seems to have 
stopped supporting colons in variable names (@set - @value), causing errors 
like this one:
  -
  doc/enfuse.texi:564: bad syntax for @value
  -

  According to texinfo 5.1 documentation basically the only thing
  guaranteed to work are alpha-numericals:

  Subsequent characters, if any, may not be whitespace, ‘@’, braces,
  angle brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may
  work. However, it is best to use only letters and numerals in a flag
  name, not ‘-’ or ‘_’ or others—they will work in some contexts, but
  not all, due to limitations in TeX.

  cu Andreas

  See http://bugs.debian.org/708800 or
  https://bugzilla.redhat.com/show_bug.cgi?id=919935

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 679362] Re: Hugin crashes with Segfault

[Andreas Metzler]

Hello,

please re-open this report. It has appeared again in
http://bugs.debian.org/71199.

The system in question is using intel graphics, probably with a broken 
configuration. However the fact that hugin simply crashes instead of handling 
the error is clearly a bug. More info below:


---### Started program, loaded image, clicked Layout tab, segfault.
$ hugin
/usr/share/hugin/data/plugins/shooting_pattern.py
   CAT:initial distribution
   NAM:6-1-1 Shooting Pattern
/usr/share/hugin/data/plugins/woa.py
   CAT:Control Points
   NAM:Warped Overlap Analysis
/usr/share/hugin/data/plugins/crop_cp.py
   CAT:Control Points
   NAM:Crop Control Points
/usr/share/hugin/data/plugins/top_five.py
   CAT:Control Points
   NAM:keep 5 CPs per image pair
Xlib:  extension GLX missing on display :0.0.
Xlib:  extension GLX missing on display :0.0.
Xlib:  extension GLX missing on display :0.0.
Segmentation fault
-

 [:~]$ glxgears -info
 Xlib:  extension GLX missing on display :0.0.
 Error: couldn't get an RGB, Double-buffered visual
 [:~]$

And at this point it simply exits?


Yes.
 

Do you have libgl1-mesa-dri or libgl1-mesa-swx11 installed?


Looks like libgl1-mesa-dri is installed. libgl1-mesa-swx11 is not installed.

[:~]$ dpkg -l | grep libgl1-mesa
ii  libgl1-mesa-dri:amd64 8.0.5-6
amd64free implementation of the OpenGL API -- DRI modules
ii  libgl1-mesa-glx:amd64 8.0.5-6
amd64free implementation of the OpenGL API -- GLX runtime
[:~]$ 

Could enter bt at this point?


As you wish!

Program received signal SIGSEGV, Segmentation fault.
0x005b9183 in PreviewIdentifyTool::setConstantOn(bool) ()
(gdb) bt
#0  0x005b9183 in PreviewIdentifyTool::setConstantOn(bool) ()
#1  0x0056040f in GLPreviewFrame::SetMode(int) ()
#2  0x753aa3f6 in 
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const, 
wxEvtHandler*, wxEvent) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x753aa564 in wxEventHashTable::HandleEvent(wxEvent, 
wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#4  0x753aa887 in wxEvtHandler::ProcessEvent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x74f963d9 in wxWindowBase::TryParent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#6  0x74f963d9 in wxWindowBase::TryParent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#7  0x74f79f2b in wxNotebookBase::SendPageChangedEvent(int, int) () 
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#8  0x7fffef05c620 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7fffef06dfde in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x7fffef075cd1 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7fffef075f82 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x70779ef0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x70758f19 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#14 0x7fffef05c620 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7fffef06db1b in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x7fffef075972 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x7fffef075f82 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x70870e9e in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#19 0x70757284 in gtk_propagate_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#20 0x707575eb in gtk_main_do_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#21 0x703cd80c in ?? () from 
/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#22 0x7fffeeb96f25 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fffeeb97268 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fffeeb976da in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x707565e7 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#26 0x74ebc268 in wxEventLoop::Run() () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#27 0x74f2e33c in wxAppBase::MainLoop() () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#28 0x7535c4e5 in wxEntry(int, wchar_t**) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#29 0x004c2dc2 in main ()
(gdb) 
-


** Bug watch added: Debian Bug tracker #71199
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71199

-- 
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.

[Hugin-bug-hunters] [Bug 679362] Re: Hugin crashes with Segfault

[Andreas Metzler]

Correct debian report number: http://bugs.debian.org/711997.

** Bug watch added: Debian Bug tracker #711997
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711997

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

Title:
  Hugin crashes with Segfault

Status in Hugin - Panorama Tools GUI:
  Fix Released

Bug description:
  As soon as Hugin is opened, it crashes; in fact just after closing the
  tips popup.

  ---
  sh-4.0$ export LANG=C
  sh-4.0$ hugin
  Xlib:  extension GLX missing on display :0.0.
  Xlib:  extension GLX missing on display :0.0.
  MainFrame::RestoreLayoutOnNextResize()
  Segmentation fault
  sh-4.0$
  ---

  I join the backtrace

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1194578] [NEW] mouse button functions switched on Move/Drag panel

[Andreas Metzler]

Public bug reported:

Hello,

this is http://bugs.debian.org/712997 reported by Yuri D'Elia against 
2013.0.0~beta1+dfsg-3
-
I can't seem to be able to drag any image in the Move/Drag panel in any mode
(normal, mosaic or the individual combinations). This used to work some time
ago, as I used this feature regularly.

Interestingly, dragging with the third mouse button instead works and rotates
the image. Applying the raw/pitch manually also works. This seems to be a
problem with dragging with the first mouse button only.
-

It does not seem to be a local misconfiguration of hugin, since moving
~/.hugin away did not fix issues.


Ok, I tried on another box, and 2011.4 works as expected.
Literally no idea why.

Could that be a GL driver bug?
On this particular box I have an hd4000, whereas on the working machine
I have an nvidia card.


cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  mouse button functions switched on Move/Drag panel

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  this is http://bugs.debian.org/712997 reported by Yuri D'Elia against 
2013.0.0~beta1+dfsg-3
  -
  I can't seem to be able to drag any image in the Move/Drag panel in any mode
  (normal, mosaic or the individual combinations). This used to work some time
  ago, as I used this feature regularly.

  Interestingly, dragging with the third mouse button instead works and rotates
  the image. Applying the raw/pitch manually also works. This seems to be a
  problem with dragging with the first mouse button only.
  -

  It does not seem to be a local misconfiguration of hugin, since moving
  ~/.hugin away did not fix issues.

  
  Ok, I tried on another box, and 2011.4 works as expected.
  Literally no idea why.

  Could that be a GL driver bug?
  On this particular box I have an hd4000, whereas on the working machine
  I have an nvidia card.
  

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1226151] [NEW] Boost.Signals is deprecated

[Andreas Metzler]

Public bug reported:

Hello,

building hugin 2013.0.0 rc2 against boost 1.54 yields this warning
(compared to boost 1.53):

/usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is
no longer being maintained and is now deprecated. Please switch to
Boost.Signals2. To disable this warning message, define
BOOST_SIGNALS_NO_DEPRECATION_WARNING.

Signals2 was introduced in Boost 1.39.0.

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  Boost.Signals is deprecated

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  building hugin 2013.0.0 rc2 against boost 1.54 yields this warning
  (compared to boost 1.53):

  /usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals
  is no longer being maintained and is now deprecated. Please switch to
  Boost.Signals2. To disable this warning message, define
  BOOST_SIGNALS_NO_DEPRECATION_WARNING.

  Signals2 was introduced in Boost 1.39.0.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1227813] [NEW] Fails to stitch in mktemp -d directory with ptbatcher

[Andreas Metzler]

Public bug reported:

Hello,

hugin fails to stitch images in a directory generated with mktemp -d if
PTBatcherGUI is used.

How to reproduce (starting without ~/.hugin):

8X--
surfonly@argenau:~$ mktemp -d
/tmp/tmp.GWy5J6KUny
surfonly@argenau:~$ cp /tmp/*JPG /tmp/tmp.GWy5J6KUny
surfonly@argenau:~$ ls -la /tmp/tmp.GWy5J6KUny
total 5692
drwx--  2 surfonly surfonly4096 Sep 19 19:04 .
drwxrwxrwt 11 root root   20480 Sep 19 19:04 ..
-rw-r--r--  1 surfonly surfonly 2850496 Sep 19 19:04 IMG_2459.JPG
-rw-r--r--  1 surfonly surfonly 2952114 Sep 19 19:04 IMG_2460.JPG
surfonly@argenau:~$ printenv  | grep -i tmp
surfonly@argenau:~$ pwd
/home/surfonly
surfonly@argenau:~$ hugin


hugin starts (with interface simple), I dismiss the tip of the day.
On the assistant-tab I use Load images to add the two images, followed
by 2. Align and 3. Create panorama (keeping all defaults, in this case
exposure fused from stacks). I am asked about saving for PTbatcher and
again the default filename.

The stitch fails with this error:

===
***  Panorama makefile generated by Hugin   ***
===
System information
===
Operating system: GNU/Linux
Release: 3.2.0-4-amd64
Kernel version: #1 SMP Debian 3.2.46-1+deb7u1
Machine: x86_64
Disc usage
Filesystem  Size  Used Avail Use% 
Mounted on
rootfs  296G  214G   67G  77% /
udev 10M 0   10M   0% 
/dev
tmpfs   396M  316K  396M   1% 
/run
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% /
tmpfs   5.0M 0  5.0M   0% 
/run/lock
tmpfs   792M 0  792M   0% 
/run/shm
/dev/sda568G   11G   58G  15% 
/media/win
/dev/sda1   204G   66G  138G  33% 
/media/xpsystem
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/sid/tmp
tmpfs   792M 0  792M   0% 
/chroots/sid/run/shm
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/sid-amd64/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/etch/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/amd64-wheezy/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/amd64-jessie/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/lenny/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/squeeze/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/wheezy/tmp
/dev/disk/by-uuid/4f566dee-9acc-4629-9ea1-97e32a5da5f3  296G  214G   67G  77% 
/chroots/sq-amd/tmp
Memory usage
 total   used   free sharedbuffers cached
Mem:  3956   2156   1799  0458557
-/+ buffers/cache:   1139   2816
Swap: 8191  0   8191
===
Output options
===
Hugin Version: 2013.0.0.76c3df493921
Project file: /tmp/huginpto_wGDDGb
Output prefix: IMG_2459 - IMG_2460
Projection: Rectilinear (0)
Field of view: 63 x 42
Canvas dimensions: 2453 x 1518
Crop area: (57,44) - (2423,1462)
Output exposure value: 13.66
Output stacks minimum overlap: 0.700
Output layers maximum Ev difference: 0.50
Selected outputs
Exposure fusion
* Fused and blended panorama
===
Input images
===
Number of images in project file: 2
Number of active images: 2
Image 0: /tmp/tmp.GWy5J6KUny/tmp.GWy5J6KUny/IMG_2459.JPG
Image 0: Size 2592x1944, Exposure: 13.61
Image 1: /tmp/tmp.GWy5J6KUny/tmp.GWy5J6KUny/IMG_2460.JPG
Image 1: Size 2592x1944, Exposure: 13.71
===
Testing programs
===
Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...[OK]
===
Stitching panorama

[Hugin-bug-hunters] [Bug 718116] Re: Opening Fast Preview Window crashes Hugin

[Andreas Metzler]

Hello,

I just got a similar report on Debian 2014.0 rc1
http://bugs.debian.org/741466

cu Andreas
---
Philipp Marek writes:

With Interface - Simple, clicking on _any_ tab (except the first visible,
Assistant) crashes Hugin with a segfault; please see the backtrace attached.

The Expert Interface works better, but I cannot do any previews.


After comparing with #711997 I can offer further this information:

* glxgears just works:
  # glxgears -info
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  GL_RENDERER   = Mesa DRI Intel(R) Ironlake Mobile
  GL_VERSION= 2.1 Mesa 9.2.2
  GL_VENDOR = Intel Open Source Technology Center


* No Nvidia traces in /var/log/Xorg.0.log; this is a notebook with an Intel
graphics card, and has never seen the Nvidia proprietary driver.

  # grep module -i /var/log/Xorg.0.log looks clean:
  [59.155] (II) LoadModule: glx
  [59.164] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [59.215] (II) Module glx: vendor=X.Org Foundation
  [ 59.215]compiled for 1.15.0, module version = 1.0.0
  [59.215] (II) LoadModule: dbe
  [59.215] (II) Module dbe already built-in
  [59.215] (II) LoadModule: extmod
  [59.215] (II) Module extmod already built-in
  [59.215] (II) LoadModule: intel
  [59.215] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
  [59.274] (II) Module intel: vendor=X.Org Foundation
  [59.274]compiled for 1.15.0, module version = 2.21.15
  [59.274]Module class: X.Org Video Driver
  [59.448] (II) Loading sub module fb
  [59.448] (II) LoadModule: fb
  [59.448] (II) Loading /usr/lib/xorg/modules/libfb.so
  [59.459] (II) Module fb: vendor=X.Org Foundation
  [59.459]compiled for 1.15.0, module version = 1.0.0
  [59.459] (II) Loading sub module dri2
  [59.459] (II) LoadModule: dri2
  [59.459] (II) Module dri2 already built-in


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hugin depends on:
ii  enblend   4.1.2+dfsg-2
ii  enfuse4.1.2+dfsg-2
ii  hugin-tools   2014.0.0~rc1+dfsg-2
ii  libboost-system1.55.0 1.55.0-1
ii  libboost-thread1.55.0 1.55.0-1
ii  libc6 2.18-4
ii  libexiv2-12   0.23-1
ii  libgcc1   1:4.8.2-16
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libimage-exiftool-perl9.53-1
ii  libpano13-3   2.9.19~beta1+dfsg-2
ii  libstdc++64.8.2-16
ii  libtiff5  4.0.3-8
ii  libwxbase2.8-02.8.12.1+dfsg-2
ii  libwxgtk2.8-0 2.8.12.1+dfsg-2
ii  make  3.82-1

hugin recommends no packages.

hugin suggests no packages.


Program received signal SIGSEGV, Segmentation fault.
0x0058b1f3 in PreviewIdentifyTool::setConstantOn(bool) ()
(gdb) bt
#0  0x0058b1f3 in PreviewIdentifyTool::setConstantOn(bool) ()
#1  0x00530bcc in GLPreviewFrame::SetMode(int) ()
#2  0x756e17c6 in 
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const, 
wxEvtHandler*, wxEvent) ()
   from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x756e186b in wxEventHashTable::HandleEvent(wxEvent, 
wxEvtHandler*) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#4  0x756e1bd7 in wxEvtHandler::ProcessEvent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x752c7c79 in wxWindowBase::TryParent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#6  0x752c7c79 in wxWindowBase::TryParent(wxEvent) () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#7  0x752a7d08 in wxNotebookBase::SendPageChangedEvent(int, int) () 
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#8  0x7fffeef62138 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7fffeef73d41 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x7fffeef7b799 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7fffeef7ba52 in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x703e5d74 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x703c6695 in ?? () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#14 0x7fffeef62138 in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7fffeef7386b in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x7fffeef7b469 

[Hugin-bug-hunters] [Bug 1316702] [NEW] segfault loading multiple images in assistant

[Andreas Metzler]

Public bug reported:

Hello,

hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
using the simple interface ([Load Images] button on preview window.

ERROR: 19:30:12.852684 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading: 
Precondition violation!
Unable to open file ''.

This was submitted by Ingo Steine in https://bugs.debian.org/747021.
Ingo has also provided example images (availabe for download in the
Debian bug report) that reproduce the breakage. The important part seems
to be that they have no EXIF data, causing the Enter FOV-dialogue to
appear.

Using the [Add Images] button in the expert interface does not trigger
the crash.

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  segfault loading multiple images in assistant

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
  using the simple interface ([Load Images] button on preview window.

  ERROR: 19:30:12.852684 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading: 
  Precondition violation!
  Unable to open file ''.

  This was submitted by Ingo Steine in https://bugs.debian.org/747021.
  Ingo has also provided example images (availabe for download in the
  Debian bug report) that reproduce the breakage. The important part
  seems to be that they have no EXIF data, causing the Enter
  FOV-dialogue to appear.

  Using the [Add Images] button in the expert interface does not trigger
  the crash.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1316702] Re: segfault loading multiple images in assistant

[Andreas Metzler]

On 2014-05-06 tmodes 1316...@bugs.launchpad.net wrote:
 Tried to fix in changeset 1df056cbbdd8 in default branch.

 If there is a confirmation, that the bug is fixed we need a decision
 how to proceed with 2014.0.
 If the bug is considered as critical, it needs to ported to 2014.0.
 This will need a new release candidate rc3.
 What is your opinion?

Hello,

I think it is quite ugly but not critical.

Typically images are loaded at very beginning of the workflow, that is
especially true for the assistant. If hugin crashes at this point no
work will be lost.  Therefore I would not think it is critical. OTOH a
program which crashes at the very start does not make a good
impression. ;-)

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault loading multiple images in assistant

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hello,

  hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
  using the simple interface ([Load Images] button on preview window.

  ERROR: 19:30:12.852684 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading: 
  Precondition violation!
  Unable to open file ''.

  This was submitted by Ingo Steine in https://bugs.debian.org/747021.
  Ingo has also provided example images (availabe for download in the
  Debian bug report) that reproduce the breakage. The important part
  seems to be that they have no EXIF data, causing the Enter
  FOV-dialogue to appear.

  Using the [Add Images] button in the expert interface does not trigger
  the crash.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1318207] [NEW] segfault on exit if built against wxwidgets3.0

[Andreas Metzler]

Public bug reported:

Hello,

hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
against wxwidgets3.0 (instead of 2.8):


Program received signal SIGSEGV, Segmentation fault.
0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
(gdb) bt
#0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#1  0xf64b9343 in __cxa_finalize ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
#4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#6  0xf649fa6b in __libc_start_main ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#7  0x080f5b10 in _start ()


Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
Program received signal SIGSEGV, Segmentation fault.
0x0031 in ?? ()
(gdb) bt
#0  0x0031 in ?? ()
#1  0x741c121f in ?? ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
at cxa_finalize.c:56
#3  0x74154723 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#4  0x7fffe210 in ?? ()
#5  0x77debf3a in _dl_fini () at dl-fini.c:252
Backtrace stopped: frame did not save the PC

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  segfault on exit if built against wxwidgets3.0

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
  against wxwidgets3.0 (instead of 2.8):

  
  Program received signal SIGSEGV, Segmentation fault.
  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  (gdb) bt
  #0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #1  0xf64b9343 in __cxa_finalize ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
  #4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #6  0xf649fa6b in __libc_start_main ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #7  0x080f5b10 in _start ()
  

  Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
  Program received signal SIGSEGV, Segmentation fault.
  0x0031 in ?? ()
  (gdb) bt
  #0  0x0031 in ?? ()
  #1  0x741c121f in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
  at cxa_finalize.c:56
  #3  0x74154723 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #4  0x7fffe210 in ?? ()
  #5  0x77debf3a in _dl_fini () at dl-fini.c:252
  Backtrace stopped: frame did not save the PC

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1318207] Re: segfault on exit if built against wxwidgets3.0

[Andreas Metzler]

On 2014-05-13 tmodes 1318...@bugs.launchpad.net wrote:
 I know that Hugins works fine with wxWidgets 3.0 on Windows and
 MacOS (the last release was in both cases compiled with wxWidgets
 3.0). So the problem is specific to the wxGTK port. 
 Unfortunately the back trace does not help really further. Some
 ideas: Does this happens only with Hugin or also with other programs
 (check ptbatchergui and calibrate_lens_gui, does the wxWidgets
 samples work without problems?).

Hello,

The other hugin GUI programs do not show the error.

 Maybe linking with the debug libraries could shed light on the issue.

Installing the wx debug packages yields this:

(gdb) bt full
#0  0xf698e517 in ~wxEventTableEntryBase (
this=0x833101c wxTreeListCtrl::sm_eventHashTable+20,
__in_chrg=optimized out) at ../include/wx/event.h:3177
No locals.
#1  ~wxEventTableEntry (this=0x833101c wxTreeListCtrl::sm_eventHashTable+20,
__in_chrg=optimized out) at ../include/wx/event.h:3196
No locals.
#2  __tcf_0 () at ../src/generic/treelist.cpp:987
No locals.
#3  0xf64b9343 in __cxa_finalize ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.
#4  0xf6913983 in __do_global_dtors_aux ()
   from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
No symbol table info available.
#5  0xf7febdcc in ?? () from /lib/ld-linux.so.2
No symbol table info available.
#6  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.
#7  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
No symbol table info available.
#8  0xf649fa6b in __libc_start_main ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
---Type return to continue, or q return to quit---
No symbol table info available.
#9  0x080f5b10 in _start ()
No symbol table info available.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault on exit if built against wxwidgets3.0

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
  against wxwidgets3.0 (instead of 2.8):

  
  Program received signal SIGSEGV, Segmentation fault.
  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  (gdb) bt
  #0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #1  0xf64b9343 in __cxa_finalize ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
  #4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #6  0xf649fa6b in __libc_start_main ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #7  0x080f5b10 in _start ()
  

  Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
  Program received signal SIGSEGV, Segmentation fault.
  0x0031 in ?? ()
  (gdb) bt
  #0  0x0031 in ?? ()
  #1  0x741c121f in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
  at cxa_finalize.c:56
  #3  0x74154723 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #4  0x7fffe210 in ?? ()
  #5  0x77debf3a in _dl_fini () at dl-fini.c:252
  Backtrace stopped: frame did not save the PC

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1318207] Re: segfault on exit if built against wxwidgets3.0

[Andreas Metzler]

On 2014-05-16 tmodes 1318...@bugs.launchpad.net wrote:
 Thanks for update. Could you please try if changeset 5e144ef0d7fb
 fixes the issue?
 (I have currently no Linux version of wxWidgets 3.0 running.)

Hello,

It fixes the crash with wx3.0, thank you. (I have tried tried
2014.0.0rc2 plus this changeset, which applies just with a little bit
of fuzz).

However it breaks building against wx2.8:
[ 54%] Building CXX object 
src/hugin1/hugin/CMakeFiles/hugin.dir/treelistctrl.cpp.o
/tmp/HUGIN/hugin-2014.0.0/src/hugin1/hugin/treelistctrl.cpp: In member function 
'void wxTreeListMainWindow::OnChar(wxKeyEvent)':
/tmp/HUGIN/hugin-2014.0.0/src/hugin1/hugin/treelistctrl.cpp:3998:48: error: 
'WXK_NONE' was not declared in this scope
 int key = event.GetUnicodeKey() != WXK_NONE ? 
event.GetUnicodeKey() : event.GetKeyCode();
^
/tmp/HUGIN/hugin-2014.0.0/src/hugin1/hugin/treelistctrl.cpp:4003:36: error: 
'wxUniChar' was not declared in this scope
 m_findStr.Append ((wxUniChar)key);
^
src/hugin1/hugin/CMakeFiles/hugin.dir/build.make:1365: recipe for target 
'src/hugin1/hugin/CMakeFiles/hugin.dir/treelistctrl.cpp.o' failed

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault on exit if built against wxwidgets3.0

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
  against wxwidgets3.0 (instead of 2.8):

  
  Program received signal SIGSEGV, Segmentation fault.
  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  (gdb) bt
  #0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #1  0xf64b9343 in __cxa_finalize ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
  #4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #6  0xf649fa6b in __libc_start_main ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #7  0x080f5b10 in _start ()
  

  Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
  Program received signal SIGSEGV, Segmentation fault.
  0x0031 in ?? ()
  (gdb) bt
  #0  0x0031 in ?? ()
  #1  0x741c121f in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
  at cxa_finalize.c:56
  #3  0x74154723 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #4  0x7fffe210 in ?? ()
  #5  0x77debf3a in _dl_fini () at dl-fini.c:252
  Backtrace stopped: frame did not save the PC

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1318207] Re: segfault on exit if built against wxwidgets3.0

[Andreas Metzler]

On 2014-05-17 tmodes 1318...@bugs.launchpad.net wrote:
 Default branch should compile with wx 2.8 again.

 After confirmation that all works again, I think this should go also in
 2014.0 branch.

Thanks, 2014.0.0rc2 + 5e144ef0d7fb + 6022165a79d9 builds for me with both
wx 2.8 and 3.0 and fixes the crash with 3.0.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault on exit if built against wxwidgets3.0

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hello,

  hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
  against wxwidgets3.0 (instead of 2.8):

  
  Program received signal SIGSEGV, Segmentation fault.
  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  (gdb) bt
  #0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #1  0xf64b9343 in __cxa_finalize ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
  #4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #6  0xf649fa6b in __libc_start_main ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #7  0x080f5b10 in _start ()
  

  Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
  Program received signal SIGSEGV, Segmentation fault.
  0x0031 in ?? ()
  (gdb) bt
  #0  0x0031 in ?? ()
  #1  0x741c121f in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
  at cxa_finalize.c:56
  #3  0x74154723 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #4  0x7fffe210 in ?? ()
  #5  0x77debf3a in _dl_fini () at dl-fini.c:252
  Backtrace stopped: frame did not save the PC

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1316702] Re: segfault loading multiple images in assistant

[Andreas Metzler]

Hello,

here is what I get with rc3 (hugin built with -O0):

[...]
[Thread 0xe5bfeb40 (LWP 12214) exited]
Error: XMP Toolkit error 203: Duplicate property or field node
Warning: Failed to decode XMP metadata.
[New Thread 0xe5bfeb40 (LWP 12215)]
ContractViolation:
Precondition violation!
Unable to open file ''.

ERROR: 20:07:56.539886 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading:
Precondition violation!
Unable to open file ''.

[Thread 0xe5bfeb40 (LWP 12215) exited]

Program received signal SIGSEGV, Segmentation fault.
HuginBase::ImageCache::postEvent (this=0x83a4338, request=..., entry=...)
at /tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:871
871 entry-lastAccess = m_accessCounter;
(gdb) bt full
#0  HuginBase::ImageCache::postEvent (this=0x83a4338, request=..., entry=...)
at /tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:871
is_small_request = optimized out
filename = optimized out
#1  0x080f6ad1 in huginApp::relayImageLoaded (this=0x8377120, event=...)
at /tmp/HUGIN/hugin-2014.0.0/src/hugin1/hugin/huginApp.cpp:541
No locals.
#2  0xf7134766 in wxAppConsoleBase::HandleEvent (this=0x8377120, handler=
0x8377120, func=
(void (wxEvtHandler::*)(wxEvtHandler * const, wxEvent )) 0x80f6a80 
huginApp::relayImageLoaded(ImageReadyEvent), event=...)
at ../src/common/appbase.cpp:611
No locals.
#3  0xf7134b8b in wxAppConsoleBase::CallEventHandler (this=0x8377120,
handler=0x8377120, functor=..., event=...) at ../src/common/appbase.cpp:623
No locals.
#4  0xf72be1da in wxEvtHandler::ProcessEventIfMatchesId (entry=...,
handler=0x8377120, event=...) at ../src/common/event.cpp:1384
event = @0x9346f48: {wxObject = {
_vptr.wxObject = 0x82790c8 vtable for ImageReadyEvent+8,
static ms_classInfo = {m_className = 0xf72e8068 LwxObject,
  m_objectSize = 8, m_objectConstructor = 0x0, m_baseInfo1 = 0x0,
  m_baseInfo2 = 0x0, static sm_first = 0x0,
  m_next = 0xf73627bc wxMemoryOutputStream::ms_classInfo,
  static sm_classTable = 0x8334918}, m_refData = 0x0},
  m_eventObject = 0x0, m_eventType = 10331, m_timeStamp = 0, m_id = 0,
  m_callbackUserData = 0x0, m_handlerToProcessOnlyIn = 0x0,
  m_propagationLevel = 0, m_propagatedFrom = 0x0, m_skipped = false,
  m_isCommandEvent = false, m_wasProcessed = true,
  m_willBeProcessedAgain = false, static ms_classInfo = {
m_className = 0x0, m_objectSize = 0, m_objectConstructor = 0x0,
m_baseInfo1 = 0x0, m_baseInfo2 = 0x0, static sm_first = 0x0,
m_next = 0x0, static sm_classTable = 0x8334918}}
handler = 0x8377120
entry = @0x832ef80: {m_id = -1, m_lastId = -1, m_fn = 0x836ed38,
  m_callbackUserData = 0x0}
#5  0xf72be29a in wxEventHashTable::HandleEvent (
this=0x832efa8 huginApp::sm_eventHashTable, event=...,
self=self@entry=0x8377120) at ../src/common/event.cpp:990
entry = optimized out
n = 0
eventEntryTable = @0x866419c: {wxBaseArrayPtrVoid = {m_nSize = 1,
m_nCount = 1, m_pItems = 0x85d2c58}, No data fields}
eTTnode = 0x8664198
#6  0xf72be673 in wxEvtHandler::TryHereOnly (this=this@entry=0x8377120,
event=...) at ../src/common/event.cpp:1581
No locals.
#7  0xf72be6f4 in TryBeforeAndHere (event=..., this=0x8377120)
at ../include/wx/event.h:3671
event = @0x9346f48: {wxObject = {
_vptr.wxObject = 0x82790c8 vtable for ImageReadyEvent+8,
static ms_classInfo = {m_className = 0xf72e8068 LwxObject,
  m_objectSize = 8, m_objectConstructor = 0x0, m_baseInfo1 = 0x0,
  m_baseInfo2 = 0x0, static sm_first = 0x0,
  m_next = 0xf73627bc wxMemoryOutputStream::ms_classInfo,
  static sm_classTable = 0x8334918}, m_refData = 0x0},
  m_eventObject = 0x0, m_eventType = 10331, m_timeStamp = 0, m_id = 0,
  m_callbackUserData = 0x0, m_handlerToProcessOnlyIn = 0x0,
  m_propagationLevel = 0, m_propagatedFrom = 0x0, m_skipped = false,
  m_isCommandEvent = false, m_wasProcessed = true,
  m_willBeProcessedAgain = false, static ms_classInfo = {
m_className = 0x0, m_objectSize = 0, m_objectConstructor = 0x0,
m_baseInfo1 = 0x0, m_baseInfo2 = 0x0, static sm_first = 0x0,
m_next = 0x0, static sm_classTable = 0x8334918}}
this = 0x8377120
#8  wxEvtHandler::ProcessEventLocally (this=this@entry=0x8377120, event=...)
at ../src/common/event.cpp:1514
No locals.
#9  0xf72be755 in wxEvtHandler::ProcessEvent (this=0x8377120, event=...)
at ../src/common/event.cpp:1487
__FUNCTION__ = ProcessEvent
#10 0xf72bf786 in wxEvtHandler::ProcessPendingEvents (this=0x8377120)
at ../src/common/event.cpp:1351
__FUNCTION__ = ProcessPendingEvents
node = optimized out
 

Re: [Hugin-bug-hunters] [Bug 1316702] Re: segfault loading multiple images in assistant

[Andreas Metzler]

On 2014-05-23 tmodes 1316...@bugs.launchpad.net wrote:
 Some more question, because I can't currently not reproduce the crash.

 * Which wxWidgets version? (With 2.8.12 it runs fine with the test
images.)

Hello,
3.0.0

 * I used the images from the original ticket. Are there some special
 chars in the folder name by chance?

No, I used the same images and saved them directly to /tmp.

 * Does Hugin ask 3 times for the lens data (because the images have
 different sizes) and crashes then? Or does the crash happen earlier?

It asks at the first image, I enter hvov it then and crashes when I
confirm the data with [OK].

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault loading multiple images in assistant

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hello,

  hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
  using the simple interface ([Load Images] button on preview window.

  ERROR: 19:30:12.852684 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading: 
  Precondition violation!
  Unable to open file ''.

  This was submitted by Ingo Steine in https://bugs.debian.org/747021.
  Ingo has also provided example images (availabe for download in the
  Debian bug report) that reproduce the breakage. The important part
  seems to be that they have no EXIF data, causing the Enter
  FOV-dialogue to appear.

  Using the [Add Images] button in the expert interface does not trigger
  the crash.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1316702] Re: segfault loading multiple images in assistant

[Andreas Metzler]

On 2014-05-25 tmodes 1316...@bugs.launchpad.net wrote:
 Okay. I was now able to reproduce the crash. It happens only if in
 simple mode. In all other modes it worked.  Committed a workaround
 in changeset 10aa8ea89d9e. Please report back if this works. TIA.

Marvellous. Works for me, too.

I have now uploaded rc3 with
10aa8ea89d9eef64ecd7281194507177dc6a82f7 and
b2c6b668f05243df2aff0ae1994db9b93efacb33
to Debian/unstable.

thanks, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  segfault loading multiple images in assistant

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hello,

  hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
  using the simple interface ([Load Images] button on preview window.

  ERROR: 19:30:12.852684 
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697) 
loadImageSafely(): Error during image reading: 
  Precondition violation!
  Unable to open file ''.

  This was submitted by Ingo Steine in https://bugs.debian.org/747021.
  Ingo has also provided example images (availabe for download in the
  Debian bug report) that reproduce the breakage. The important part
  seems to be that they have no EXIF data, causing the Enter
  FOV-dialogue to appear.

  Using the [Add Images] button in the expert interface does not trigger
  the crash.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1385707] [NEW] 2014.0.0 assert errors in hugin and PTBatcherGUI

[Andreas Metzler]

Public bug reported:

Hello,

on Debian some of our users still see assertion errors with hugin
2014.0.0 (plus 52_044b08eb6adf_Several_fixes_to_treelistctrl.diff and
53_f88dc95914ae_Use_correct_class_wxStaticBitmap_for_bitmap_controls.diff)
either in hugin itself or in PTBatcherGUI:

in https://bugs.debian.org/764759 boris writes:
I'm starting with:

$ hugin IMG_4749.png

open: View - Panorama Editor

in Panorama Editor:

Select tab: Stitcher
switching to format png (but shouldn't matter) 

and click the Stitch! botton which triggers (sorry forgot to add this
too):


ASSERT INFO:
/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype 
/(wxFormatStringSpecifierT::value)) == argtype failed in
/wxArgNormalizer(): format specifier doesn't match argument type

BACKTRACE:
[1] FillPlaceholders(std::mapwxString, wxString, std::lesswxString,
std::allocatorstd::pairwxString const, wxString  , HuginBase::Panorama
const)
[2] getDefaultProjectName(HuginBase::Panorama const, wxString)
[3] MainFrame::OnSaveProjectAs(wxCommandEvent)
[4] MainFrame::OnSaveProject(wxCommandEvent)
[5] PanoPanel::DoSendToBatch()
[6] PanoPanel::OnDoStitch(wxCommandEvent)
[7] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor,
wxEvent) const
[8] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const,
wxEvtHandler*, wxEvent)
[9] wxEventHashTable::HandleEvent(wxEvent, wxEvtHandler*)
[10] wxEvtHandler::TryHereOnly(wxEvent)
[11] wxEvtHandler::ProcessEventLocally(wxEvent)
[12] wxEvtHandler::ProcessEvent(wxEvent)
[13] wxWindowBase::TryAfter(wxEvent)
[14] wxWindowBase::TryAfter(wxEvent)
[15] wxEvtHandler::SafelyProcessEvent(wxEvent)
[16] g_signal_emit_valist
[17] g_signal_emit
[18] g_signal_emit_valist
[19] g_signal_emit
[20] g_closure_invoke
[21] g_signal_emit_valist
[22] g_signal_emit
[23] gtk_propagate_event
[24] gtk_main_do_event
[25] g_main_context_dispatch
[26] g_main_loop_run
[27] gtk_main
[28] wxGUIEventLoop::DoRun()
[29] wxEventLoopBase::Run()
[30] wxAppConsoleBase::MainLoop()
[31] wxEntry(int, wchar_t**)
[32] main
[33] __libc_start_main
[34] _start

Click: Continue

In the Save project file Window
(default filename)

Click: Save

Which triggers:

ASSERT INFO:
/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype 
/(wxFormatStringSpecifierT::value)) == argtype failed in
/wxArgNormalizer(): format specifier doesn't match argument type

BACKTRACE:
[1] ProjectListBox::GetAttributeString(int, Project*)
[2] ProjectListBox::AppendProject(Project*)
[3] ProjectListBox::Fill(Batch*)
[4] BatchFrame::BatchFrame(wxLocale*, wxString)
[5] PTBatcherGUI::OnInit()
[6] wxEntry(int, wchar_t**)
[7] main
[8] __libc_start_main
[9] _start
---

And in 
https://bugs.debian.org/766093 Yuri D'Elia says 
---
Something seems to be broken in either hugin or wxgtk3 right now.

Starting hugin with no existing configuration gives me the following startup
assertion failures:

$ hugin
10:22:20 PM: Debug: Failed to connect to session manager: SESSION_MANAGER 
environment variable not defined
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion 'width  0' 
failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion 'width  0' 
failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed
(hugin:28839): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 
'height = -1' failed

When trying to stich a panorama, the following assertions are emitted:

/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype  
(wxFormatStringSpecifierT::value)) == argtype failed in wxArgNormalizer(): 
format specifier doesn't match argument type
/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype  
(wxFormatStringSpecifierT::value)) == argtype failed in wxArgNormalizer(): 
format specifier doesn't match argument type
10:24:39 PM: Debug: Failed to connect to session manager: SESSION_MANAGER 
environment variable not defined
/usr/include/wx-3.0/wx/strvararg.h(456): assert (argtype  

[Hugin-bug-hunters] [Bug 679988] Re: fulla implicitely cropping output

[Andreas Metzler]

Hello,

this has been re-submitted recently against 2014.0.0 in
http://bugs.debian.org/779003, fulla ignores the -s option.

-
ametzler@argenau:/tmp$ fulla -s -g -0.004318:0.039896:-0.096925:1 -o a.jpeg 
P1040118.JPG
correcting image::   |

ametzler@argenau:/tmp$ fulla -g -0.004318:0.039896:-0.096925:1 -o b.jpeg 
P1040118.JPG
correcting image::   |

ametzler@argenau:/tmp$ md5sum a.jpeg b.jpeg
2e3b30e1ec1359181ffdef09c8a9477b  a.jpeg
2e3b30e1ec1359181ffdef09c8a9477b  b.jpeg
-

FWIW, imho ignoring a documented option is not wishlist.

cu Andreas

** Bug watch added: Debian Bug tracker #779003
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779003

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

Title:
  fulla implicitely cropping output

Status in Hugin - Panorama Tools GUI:
  Triaged

Bug description:
  Run fulla to fix some radial barrel distortion with cropping disabled.
  $ fulla -s -g 0:-0.2:0:1 -o output.jpg input.jpg

  Expected: A corrected image on an enlarged canvas.
  Actual result: A corrected image cropped to the original canvas size.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1451168] [NEW] [patch] broken whatis entry in manpages

[Andreas Metzler]

Public bug reported:

Hello,

two of the newly added manpages in 2015.0.0 have slightly broken formatting, 
the whatis entry cannot be parsed and will theefore not be included into the 
apropos database. Trivial patch attached. (See also 
https://lintian.debian.org/tags/manpage-has-bad-whatis-entry.html and 
https://sourceforge.net/p/hugin/hugin/ci/2c20acd9145787e2b24de603c9a3aded8450ad95/)

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Patch added: bugfix
   
https://bugs.launchpad.net/bugs/1451168/+attachment/4389977/+files/50_fixwhatis.diff

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

Title:
  [patch] broken whatis entry in manpages

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  two of the newly added manpages in 2015.0.0 have slightly broken formatting, 
the whatis entry cannot be parsed and will theefore not be included into the 
apropos database. Trivial patch attached. (See also 
https://lintian.debian.org/tags/manpage-has-bad-whatis-entry.html and 
  
https://sourceforge.net/p/hugin/hugin/ci/2c20acd9145787e2b24de603c9a3aded8450ad95/)

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1453385] [NEW] old FSF address used in copyright header

[Andreas Metzler]

Public bug reported:

Hello,

Multiple files in hugin source (2015.0.0 beta2) point two one of the
older FSF postal addresses (not 51 Franklin Street).

Find attached a patch which either use the current FSF address or
switches to the copyright header currently suggested
http://www.gnu.org/licenses/gpl-howto.html by the FSF, namely:

You should have received a copy of the GNU General Public License
along with this program.  If not, see http://www.gnu.org/licenses/.

thanks, cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Patch added: Update headers
   
https://bugs.launchpad.net/bugs/1453385/+attachment/4394361/+files/0001-Update-GPL-location.patch

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

Title:
  old FSF address used in copyright header

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  Multiple files in hugin source (2015.0.0 beta2) point two one of the
  older FSF postal addresses (not 51 Franklin Street).

  Find attached a patch which either use the current FSF address or
  switches to the copyright header currently suggested
  http://www.gnu.org/licenses/gpl-howto.html by the FSF, namely:

  You should have received a copy of the GNU General Public License
  along with this program.  If not, see http://www.gnu.org/licenses/.

  thanks, cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1457165] [NEW] incorrect documentation for hugin_executor(1)

[Andreas Metzler]

Public bug reported:

Hello,

hugin_executor(1) says:
   -p, --prefix=str
   Prefix used for stitching. If not provided the stitched image will
   have the name of the input project file.
 
However if ~/.hugin does not exist then '%firstimage - %lastimage' will be used 
and otherwise the behavior is controlled by the value of OutputFilename in 
~/.hugin.

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  incorrect documentation for hugin_executor(1)

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin_executor(1) says:
 -p, --prefix=str
 Prefix used for stitching. If not provided the stitched image will
 have the name of the input project file.
   
  However if ~/.hugin does not exist then '%firstimage - %lastimage' will be 
used and otherwise the behavior is controlled by the value of OutputFilename in 
~/.hugin.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1459364] Re: progress window is not locale aware, fails at UTF-8 filenames

[Andreas Metzler]

Hello,

I wrote: FWIW I have also tried it the other way round [...].

This side-issue seems to be already tracked in
https://bugs.launchpad.net/hugin/+bug/678808

cu Andreas

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

Title:
  progress window is not locale aware, fails at UTF-8 filenames

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  This is http://bugs.debian.org/786938 reported by Vangelis Skarmoutsos 
against 2015.0.0 beta2:
   quote
  When pressing the Create control points button, a window pops up which
  shows informational details of the procedure.
  In this window, if some directory names are not english (they were greek in
  my case) the non english letters are not readable and some strange symbols
  appear in their place.
   unquote

  I have doublechecked this and afaict the progress window interprets an
  UTF-8 encoded filename as ISO-8859-1 (Umlaut u (ü) displayed as ü).
  See attached screenshot.

  FWIW I have also tried it the other way round: Start a xterm  with env 
LC_ALL=de_AT (latin1, not UTF-8!), generate a directory with latin1 filename, 
and point hugin there. Hugin is not able to add images in such a directory
  ERROR: caught exception: 
  Precondition violation!
  Unable to open file ''.
  
(/build/libvigraimpex-WjlfM8/libvigraimpex-1.9.0+dfsg/src/impex/codecmanager.cxx:203)

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1459364] [NEW] progress window is not locale aware, fails at UTF-8 filenames

[Andreas Metzler]

Public bug reported:

Hello,

This is http://bugs.debian.org/786938 reported by Vangelis Skarmoutsos 
against 2015.0.0 beta2:
 quote
When pressing the Create control points button, a window pops up which
shows informational details of the procedure.
In this window, if some directory names are not english (they were greek in
my case) the non english letters are not readable and some strange symbols
appear in their place.
 unquote

I have doublechecked this and afaict the progress window interprets an
UTF-8 encoded filename as ISO-8859-1 (Umlaut u (ü) displayed as ü).
See attached screenshot.

FWIW I have also tried it the other way round: Start a xterm  with env 
LC_ALL=de_AT (latin1, not UTF-8!), generate a directory with latin1 filename, 
and point hugin there. Hugin is not able to add images in such a directory
ERROR: caught exception: 
Precondition violation!
Unable to open file ''.
(/build/libvigraimpex-WjlfM8/libvigraimpex-1.9.0+dfsg/src/impex/codecmanager.cxx:203)

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Attachment added: Screenshot
   
https://bugs.launchpad.net/bugs/1459364/+attachment/4405677/+files/hugin.bug.jpeg

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

Title:
  progress window is not locale aware, fails at UTF-8 filenames

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  This is http://bugs.debian.org/786938 reported by Vangelis Skarmoutsos 
against 2015.0.0 beta2:
   quote
  When pressing the Create control points button, a window pops up which
  shows informational details of the procedure.
  In this window, if some directory names are not english (they were greek in
  my case) the non english letters are not readable and some strange symbols
  appear in their place.
   unquote

  I have doublechecked this and afaict the progress window interprets an
  UTF-8 encoded filename as ISO-8859-1 (Umlaut u (ü) displayed as ü).
  See attached screenshot.

  FWIW I have also tried it the other way round: Start a xterm  with env 
LC_ALL=de_AT (latin1, not UTF-8!), generate a directory with latin1 filename, 
and point hugin there. Hugin is not able to add images in such a directory
  ERROR: caught exception: 
  Precondition violation!
  Unable to open file ''.
  
(/build/libvigraimpex-WjlfM8/libvigraimpex-1.9.0+dfsg/src/impex/codecmanager.cxx:203)

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1537368] [NEW] enblend 4.1.4 build-error with gcc-6

[Andreas Metzler]

Public bug reported:

Hello,
enblend 4.1.4 FTBFS with gcc/g++ 6 (tested with snapshot 20160117):

../../include/vigra_ext/impexalpha.hxx:252:78: error: no matching function for 
call to 
'std::auto_ptr::auto_ptr(std::unique_ptr)'
 std::auto_ptr decoder(vigra::decoder(import_info));
  ^

This does not apply to HG default!

See https://bugs.debian.org/811869 and https://wiki.debian.org/GCC6

cu Andreas

** Affects: enblend
 Importance: Undecided
 Status: New

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

Title:
  enblend 4.1.4 build-error with gcc-6

Status in Enblend:
  New

Bug description:
  Hello,
  enblend 4.1.4 FTBFS with gcc/g++ 6 (tested with snapshot 20160117):

  ../../include/vigra_ext/impexalpha.hxx:252:78: error: no matching function 
for call to 
'std::auto_ptr::auto_ptr(std::unique_ptr)'
   std::auto_ptr 
decoder(vigra::decoder(import_info));

^

  This does not apply to HG default!

  See https://bugs.debian.org/811869 and https://wiki.debian.org/GCC6

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1537368] Re: enblend 4.1.4 build-error with gcc-6

[Andreas Metzler]

Thank you, indeed a further error as popped up:

g++-6 -DHAVE_CONFIG_H -I. -I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I../../include 
-I../../src/layer_selection -I/usr/include/OpenEXR -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -pipe --param 
inline-unit-growth=60 -O2 -DNDEBUG -Wall -fopenmp -MT enblend-filespec.o -MD 
-MP -MF .deps/enblend-filespec.Tpo -c -o enblend-filespec.o `test -f 
'filespec.cc' || echo '../../src/'`filespec.cc
../../src/filespec.cc: In constructor 'enblend::Globbing::Globbing()':
../../src/filespec.cc:420:113: error: ambiguous overload for 'operator=' 
(operand types are 'enblend::Globbing::algorithm_map {aka 
std::map >}' and 
'boost::assign_detail::generic_list >')
 ("shell", MAKE_ALGORITHM(new ShellGlobbingAlgorithm))

 ^
In file included from /usr/include/c++/6/map:61:0,
 from ../../src/filespec.cc:36:
/usr/include/c++/6/bits/stl_map.h:296:7: note: candidate: std::map<_Key, _Tp, 
_Compare, _Alloc>& std::map<_Key, _Tp, _Compare, _Alloc>::operator=(const 
std::map<_Key, _Tp, _Compare, _Alloc>&) [with _Key = 
std::__cxx11::basic_string; _Tp = std::pair; _Compare = 
std::less; _Alloc = 
std::allocator > >]
   operator=(const map& __x)
   ^~~~
/usr/include/c++/6/bits/stl_map.h:305:7: note: candidate: std::map<_Key, _Tp, 
_Compare, _Alloc>& std::map<_Key, _Tp, _Compare, 
_Alloc>::operator=(std::map<_Key, _Tp, _Compare, _Alloc>&&) [with _Key = 
std::__cxx11::basic_string; _Tp = std::pair; _Compare = 
std::less; _Alloc = 
std::allocator > >]
   operator=(map&&) = default;
   ^~~~
In file included from /usr/include/c++/6/map:61:0,
 from ../../src/filespec.cc:36:
/usr/include/c++/6/bits/stl_map.h:319:7: note: candidate: std::map<_Key, _Tp, 
_Compare, _Alloc>& std::map<_Key, _Tp, _Compare, 
_Alloc>::operator=(std::initializer_list) [with 
_Key = std::__cxx11::basic_string; _Tp = std::pair; _Compare = 
std::less; _Alloc = 
std::allocator > >]
   operator=(initializer_list __l)
   ^~~~
Makefile:646: recipe for target 'enblend-filespec.o' failed
make[5]: *** [enblend-filespec.o] Error 1
make[5]: Leaving directory '/tmp/ENBLEND/enblend-enfuse-4.1.4/build-tree-mp/src'
Makefile:821: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1

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

Title:
  enblend 4.1.4 build-error with gcc-6

Status in Enblend:
  Fix Committed

Bug description:
  Hello,
  enblend 4.1.4 FTBFS with gcc/g++ 6 (tested with snapshot 20160117):

  ../../include/vigra_ext/impexalpha.hxx:252:78: error: no matching function 
for call to 
'std::auto_ptr::auto_ptr(std::unique_ptr)'
   std::auto_ptr 
decoder(vigra::decoder(import_info));

^

  This does not apply to HG default!

  See https://bugs.debian.org/811869 and https://wiki.debian.org/GCC6

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1537368] Re: enblend 4.1.4 build-error with gcc-6

[Andreas Metzler]

On 2016-02-15 Christoph Spiel  wrote:
> Broken compilation with gcc-6 as reported in #2 should
> be fixed in rev 73e6f16de80a.

> Dropped the dependency on `boost::assign' at the offending position;
> it did not buy us that much anyhow.

Thanks, confirmed. I got a successful build with the gcc6 snapshot.

cu Andreas

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

Title:
  enblend 4.1.4 build-error with gcc-6

Status in Enblend:
  In Progress

Bug description:
  Hello,
  enblend 4.1.4 FTBFS with gcc/g++ 6 (tested with snapshot 20160117):

  ../../include/vigra_ext/impexalpha.hxx:252:78: error: no matching function 
for call to 
'std::auto_ptr::auto_ptr(std::unique_ptr)'
   std::auto_ptr 
decoder(vigra::decoder(import_info));

^

  This does not apply to HG default!

  See https://bugs.debian.org/811869 and https://wiki.debian.org/GCC6

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1565269] [NEW] enblend 4.2 build error without latex

[Andreas Metzler]

Public bug reported:

enblend 4.2 has a hard dependency on (pdf)latex:

checking for perl module Time::Zone... ok
checking for latex... no
checking for elatex... no
checking for lambda... no
../configure: line 8623: WARNING:: command not found
checking for pdflatex... ../configure: line 8655: WARNING:: command not found
no
checking for latex... no
checking for elatex... no
checking for lambda... no
configure: error: Unable to find a LaTeX application

Afaict this code in configure.ac fails to work as expected:
---
can_build_doc=yes

AC_PATH_PROGS(LATEX, [latex elatex lambda],
  [AC_MSG_WARN(missing LaTeX translator)
   can_build_doc=no
   missing_for_doc="$missing_for_doc latex"])
AC_PATH_PROG(PDFLATEX, pdflatex,
 [AC_MSG_WARN([missing PDFLaTeX translator -- no direct translation 
of LaTeX to PDF available])
  missing_for_doc="$missing_for_doc pdflatex"])

if test "$latex" != 'no'
then
  AC_LATEX_CLASS(report,report,[],
 [AC_MSG_WARN(missing document class report.cls)
  can_build_doc=no
  missing_for_doc="$missing_for_doc report.cls"])
-
AC_PATH_PROGS would set $LATEX  ("upper case") on success and can_build_doc=no 
otherwise but the code checks "$latex" != 'no' instead of 
'"$can_build_doc'='yes'. Therefore AC_LATEX_CLASS is always invoked which 
afaict invokes AC_PROG_LATEX and throws a hard error of AC_PROG_LATE fails.

cu Andreas

** Affects: enblend
 Importance: Undecided
 Status: New

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

Title:
  enblend 4.2 build error without latex

Status in Enblend:
  New

Bug description:
  enblend 4.2 has a hard dependency on (pdf)latex:

  checking for perl module Time::Zone... ok
  checking for latex... no
  checking for elatex... no
  checking for lambda... no
  ../configure: line 8623: WARNING:: command not found
  checking for pdflatex... ../configure: line 8655: WARNING:: command not found
  no
  checking for latex... no
  checking for elatex... no
  checking for lambda... no
  configure: error: Unable to find a LaTeX application

  Afaict this code in configure.ac fails to work as expected:
  ---
  can_build_doc=yes

  AC_PATH_PROGS(LATEX, [latex elatex lambda],
[AC_MSG_WARN(missing LaTeX translator)
 can_build_doc=no
 missing_for_doc="$missing_for_doc latex"])
  AC_PATH_PROG(PDFLATEX, pdflatex,
   [AC_MSG_WARN([missing PDFLaTeX translator -- no direct 
translation of LaTeX to PDF available])
missing_for_doc="$missing_for_doc pdflatex"])

  if test "$latex" != 'no'
  then
AC_LATEX_CLASS(report,report,[],
   [AC_MSG_WARN(missing document class report.cls)
can_build_doc=no
missing_for_doc="$missing_for_doc report.cls"])
  -
  AC_PATH_PROGS would set $LATEX  ("upper case") on success and 
can_build_doc=no otherwise but the code checks "$latex" != 'no' instead of 
'"$can_build_doc'='yes'. Therefore AC_LATEX_CLASS is always invoked which 
afaict invokes AC_PROG_LATEX and throws a hard error of AC_PROG_LATE fails.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1666030] [NEW] cpfind fails to run if custom temporary directory is set

[Andreas Metzler]

Public bug reported:

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@googlegroups.com/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.

** Affects: hugin
 Importance: Undecided
 Status: New

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

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

Status in Hugin:
  New

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@googlegroups.com/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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1666030] Re: assistant fails to run if custom temporary directory is set

[Andreas Metzler]

On 2017-02-25 tmodes <1666...@bugs.launchpad.net> wrote:
> 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
[...]

Is the fix easy to cherrypick? Could you point out the fixing commit?

Thanks, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

-- 
You received this bug notification because you are a member of Hugin Bug
Hunters, 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@googlegroups.com/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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1813404] [NEW] 2019.0 beta1 segfault on exit

[Andreas Metzler]

Public bug reported:

2019.0 beta1 segfaults on exit when started on a fresh system, i.e.
without preconfigured ~/.hugin et.al.

How to reproduce:
mkdir /dev/shm/ametzler-hugin-home/
chmod 0755 /dev/shm/ametzler-hugin-home/
env HOME=/dev/shm/ametzler-hugin-home hugin
[exit hugin]


Thread 1 "hugin" received signal SIGSEGV, Segmentation fault.
0x5568bec0 in MainFrame::CloseProject (this=0x55d25230, 
cancelable=false, reason=reason@entry=MainFrame::CLOSE_PROGRAM) at 
./src/hugin1/hugin/MainFrame.cpp:820
820 ./src/hugin1/hugin/MainFrame.cpp: No such file or directory.

This is on Debian/testing, i.e. with wx 3.0.4.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  2019.0 beta1 segfault on exit

Status in Hugin:
  New

Bug description:
  2019.0 beta1 segfaults on exit when started on a fresh system, i.e.
  without preconfigured ~/.hugin et.al.

  How to reproduce:
  mkdir /dev/shm/ametzler-hugin-home/
  chmod 0755 /dev/shm/ametzler-hugin-home/
  env HOME=/dev/shm/ametzler-hugin-home hugin
  [exit hugin]

  
  Thread 1 "hugin" received signal SIGSEGV, Segmentation fault.
  0x5568bec0 in MainFrame::CloseProject (this=0x55d25230, 
cancelable=false, reason=reason@entry=MainFrame::CLOSE_PROGRAM) at 
./src/hugin1/hugin/MainFrame.cpp:820
  820 ./src/hugin1/hugin/MainFrame.cpp: No such file or directory.

  This is on Debian/testing, i.e. with wx 3.0.4.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1813402] Re: xdg: fails to save recently-used.xbel

[Andreas Metzler]

Obviously hugin needs to be invoked as
env HOME=/dev/shm/ametzler-hugin-home hugin

This is on Debian/testing, i.e. with wx 3.0.4.

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

Title:
  xdg: fails to save recently-used.xbel

Status in Hugin:
  New

Bug description:
  With 2019.0.0 saving recently opened files fails if ~/.local does not
  already exist:

  (hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to store
  changes into `/dev/shm/ametzler-hugin-home/.local/share/recently-
  used.xbel', but failed: Failed to create file ?/dev/shm/ametzler-
  hugin-home/.local/share/recently-used.xbel.YXWZVZ?: No such file or
  directory

  (hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to set the
  permissions of `/dev/shm/ametzler-hugin-home/.local/share/recently-
  used.xbel', but failed: No such file or directory

  How to reproduce:
  mkdir /dev/shm/ametzler-hugin-home/
  chmod 0755 /dev/shm/ametzler-hugin-home/
  hugin
  File->Open
  [Cancel]

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1813402] [NEW] xdg: fails to save recently-used.xbel

[Andreas Metzler]

Public bug reported:

With 2019.0.0 saving recently opened files fails if ~/.local does not
already exist:

(hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to store changes
into `/dev/shm/ametzler-hugin-home/.local/share/recently-used.xbel', but
failed: Failed to create file ?/dev/shm/ametzler-hugin-home/.local/share
/recently-used.xbel.YXWZVZ?: No such file or directory

(hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to set the
permissions of `/dev/shm/ametzler-hugin-home/.local/share/recently-
used.xbel', but failed: No such file or directory

How to reproduce:
mkdir /dev/shm/ametzler-hugin-home/
chmod 0755 /dev/shm/ametzler-hugin-home/
hugin
File->Open
[Cancel]

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  xdg: fails to save recently-used.xbel

Status in Hugin:
  New

Bug description:
  With 2019.0.0 saving recently opened files fails if ~/.local does not
  already exist:

  (hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to store
  changes into `/dev/shm/ametzler-hugin-home/.local/share/recently-
  used.xbel', but failed: Failed to create file ?/dev/shm/ametzler-
  hugin-home/.local/share/recently-used.xbel.YXWZVZ?: No such file or
  directory

  (hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to set the
  permissions of `/dev/shm/ametzler-hugin-home/.local/share/recently-
  used.xbel', but failed: No such file or directory

  How to reproduce:
  mkdir /dev/shm/ametzler-hugin-home/
  chmod 0755 /dev/shm/ametzler-hugin-home/
  hugin
  File->Open
  [Cancel]

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1813404] Re: 2019.0 beta1 segfault on exit

[Andreas Metzler]

tmodes wrote 
> Fixed in repository.
> Please retest.

Thank you. Works for me.

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

Title:
  2019.0 beta1 segfault on exit

Status in Hugin:
  Fix Committed

Bug description:
  2019.0 beta1 segfaults on exit when started on a fresh system, i.e.
  without preconfigured ~/.hugin et.al.

  How to reproduce:
  mkdir /dev/shm/ametzler-hugin-home/
  chmod 0755 /dev/shm/ametzler-hugin-home/
  env HOME=/dev/shm/ametzler-hugin-home hugin
  [exit hugin]

  
  Thread 1 "hugin" received signal SIGSEGV, Segmentation fault.
  0x5568bec0 in MainFrame::CloseProject (this=0x55d25230, 
cancelable=false, reason=reason@entry=MainFrame::CLOSE_PROGRAM) at 
./src/hugin1/hugin/MainFrame.cpp:820
  820 ./src/hugin1/hugin/MainFrame.cpp: No such file or directory.

  This is on Debian/testing, i.e. with wx 3.0.4.

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

[Andreas Metzler]

FWIW I have just switched Debian's hugin binary to python 3.

As a minimal test I have tried running the included examples (after
fixing the shebang and bumping api-max). Two of them fail.

woa.py:
 run python script: /usr/share/hugin/data/plugins/woa.py
hpi: accessing plugin file /usr/share/hugin/data/plugins/woa.py
matching pair (0, 1) failed with TypeError: "cannot use a string pattern on a 
bytes-like object"
stack traceback:
  File "/usr/share/hugin/data/plugins/woa.py", line 1759, in process_image_set
cps_added = cps_from_overlap ( pano , *pair )
  File "/usr/share/hugin/data/plugins/woa.py", line 1625, in cps_from_overlap
xoff1 , yoff1 = get_tiff_offset ( nona_output[0] )
  File "/usr/share/hugin/data/plugins/woa.py", line 237, in get_tiff_offset
fieldname = re.match ( r'[^\(]+' , t ) . group(0) . strip()
  File "/usr/lib/python3.7/re.py", line 173, in match
return _compile(pattern, flags).match(string)

crop_cp.py
hpi: plugin crop_cp.py failed with TypeError: "in method 
'Panorama_setCtrlPoints', argument 2 of type 'HuginBase::CPVector const &'"
hpi: stack traceback:
  File "/usr/lib/python3/dist-packages/hpi.py", line 44, in hpi_dispatch
success = plugin [ 'entry' ] ( *args )
  File "/usr/share/hugin/data/plugins/crop_cp.py", line 237, in entry
return crop_cps ( pano , inside )
  File "/usr/share/hugin/data/plugins/crop_cp.py", line 158, in crop_cps
pano.setCtrlPoints ( ncpv )
  File "/usr/lib/python3/dist-packages/hsi.py", line 7626, in setCtrlPoints
return _hsi.Panorama_setCtrlPoints(self, points)

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

Title:
  Building current default in Fedora 30 fails due to Python plugins

Status in Hugin:
  New

Bug description:
  Building current hugin default 8203 01e87b730bb3 in Fedora 30, fails
  with the following message...

  Bytecompiling .py files below 
/home/terry/rpmbuild/BUILDROOT/hugin-2019.1.0-0.1.20190516hg.fc30.x86_64/usr/lib/debug/usr/lib64/python2.7
 using /usr/bin/python2.7
  Bytecompiling .py files below 
/home/terry/rpmbuild/BUILDROOT/hugin-2019.1.0-0.1.20190516hg.fc30.x86_64/usr/lib64/python2.7
 using /usr/bin/python2.7
  + /usr/lib/rpm/brp-python-hardlink
  + /usr/lib/rpm/redhat/brp-mangle-shebangs
  *** ERROR: ambiguous python shebang in 
/usr/share/hugin/data/plugins/shooting_pattern.py: #!/usr/bin/env python. 
Change it to python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in 
/usr/share/hugin/data/plugins/top_five.py: #!/usr/bin/env python. Change it to 
python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in 
/usr/share/hugin/data/plugins/crop_cp.py: #!/usr/bin/env python. Change it to 
python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in /usr/share/hugin/data/plugins/woa.py: 
#!/usr/bin/env python. Change it to python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in 
/usr/share/hugin/data/plugins-templates/plugin_skeleton.py: #!/usr/bin/env 
python. Change it to python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in 
/usr/share/hugin/data/plugins-templates/dual_use.py: #!/usr/bin/env python. 
Change it to python3 (or python2) explicitly.
  *** ERROR: ambiguous python shebang in 
/usr/lib64/python2.7/site-packages/hpi.py: #!/usr/bin/env python. Change it to 
python3 (or python2) explicitly.
  error: Bad exit status from /var/tmp/rpm-tmp.eEpDLf (%install)

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1858272] [NEW] AppStream metadata in legacy format

[Andreas Metzler]

Public bug reported:

Hugin's appstream data does not implement the current specification.
 
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent

It is installed in the legacy path /usr/share/appdata/ with obsolete
format (toplevel node is ).

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  AppStream metadata in legacy format

Status in Hugin:
  New

Bug description:
  Hugin's appstream data does not implement the current specification.
   
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent

  It is installed in the legacy path /usr/share/appdata/ with obsolete
  format (toplevel node is ).

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1909484] Re: 2020.0.0 calibrate_lens_gui - multiple assertions at startup

[Andreas Metzler]

On 2020-12-29 tmodes <1909...@bugs.launchpad.net> wrote:
> I can't reproduce the issue. I get no assert on Windows and also not on
> Ubuntu.

> The issue seems to stem from wxWidgets see
> http://trac.wxwidgets.org/ticket/18520 and seems to fixed up-streams
> already in the 3.1.x series.

> Could you please test if the attached patch fixes the issue for you?

It does. Thanks a lot!

cu Andreas

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

Title:
  2020.0.0 calibrate_lens_gui - multiple assertions at startup

Status in Hugin:
  New
Status in hugin package in Debian:
  Unknown

Bug description:
  Hello,

  starting calibrate_lens_gui generates assertion errors:

  ASSERT INFO:
  ../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in 
SetSourceSurface(): no bitmap data

  BACKTRACE:
  [1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour 
const*) const
  [2] wxBitmap::Draw(_cairo*, int, int, bool, wxColour const*, wxColour const*) 
const
  [3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
  [4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
  [5] wxEvtHandler::TryHereOnly(wxEvent&)
  [6] wxEvtHandler::ProcessEventLocally(wxEvent&)
  [7] wxEvtHandler::ProcessEvent(wxEvent&)
  [8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
  [9] wxWindow::GTKSendPaintEvents(_cairo*)
  [10] g_closure_invoke
  [11] g_signal_emit_valist
  [12] g_signal_emit
  [13] gtk_container_propagate_draw
  [14] gtk_container_propagate_draw
  [15] gtk_container_propagate_draw
  [16] g_closure_invoke
  [17] g_signal_emit_valist
  [18] g_signal_emit
  [19] gtk_container_propagate_draw
  [20] g_closure_invoke
  [21] g_signal_emit_valist
  [22] g_signal_emit
  [23] gtk_container_propagate_draw
  [24] gtk_container_propagate_draw
  [25] gtk_main_do_event
  [26] g_signal_emit_valist
  [27] g_signal_emit
  [28] g_main_context_dispatch
  [29] g_main_loop_run
  [30] gtk_main
  [31] wxGUIEventLoop::DoRun()
  [32] wxEventLoopBase::Run()
  [33] wxAppConsoleBase::MainLoop()
  [34] wxEntry(int&, wchar_t**)
  [35] __libc_start_main

  
  Te error is shown three times. After clicking though (Continue) the program 
is stuck (no window refresh) and nned to be Ctrl-C-ed.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1909484] Re: 2020.0.0 calibrate_lens_gui - multiple assertions at startup

[Andreas Metzler]

** Bug watch added: Debian Bug tracker #978475
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978475

** Also affects: hugin (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978475
   Importance: Unknown
   Status: Unknown

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

Title:
  2020.0.0 calibrate_lens_gui - multiple assertions at startup

Status in Hugin:
  New
Status in hugin package in Debian:
  Unknown

Bug description:
  Hello,

  starting calibrate_lens_gui generates assertion errors:

  ASSERT INFO:
  ../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in 
SetSourceSurface(): no bitmap data

  BACKTRACE:
  [1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour 
const*) const
  [2] wxBitmap::Draw(_cairo*, int, int, bool, wxColour const*, wxColour const*) 
const
  [3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
  [4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
  [5] wxEvtHandler::TryHereOnly(wxEvent&)
  [6] wxEvtHandler::ProcessEventLocally(wxEvent&)
  [7] wxEvtHandler::ProcessEvent(wxEvent&)
  [8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
  [9] wxWindow::GTKSendPaintEvents(_cairo*)
  [10] g_closure_invoke
  [11] g_signal_emit_valist
  [12] g_signal_emit
  [13] gtk_container_propagate_draw
  [14] gtk_container_propagate_draw
  [15] gtk_container_propagate_draw
  [16] g_closure_invoke
  [17] g_signal_emit_valist
  [18] g_signal_emit
  [19] gtk_container_propagate_draw
  [20] g_closure_invoke
  [21] g_signal_emit_valist
  [22] g_signal_emit
  [23] gtk_container_propagate_draw
  [24] gtk_container_propagate_draw
  [25] gtk_main_do_event
  [26] g_signal_emit_valist
  [27] g_signal_emit
  [28] g_main_context_dispatch
  [29] g_main_loop_run
  [30] gtk_main
  [31] wxGUIEventLoop::DoRun()
  [32] wxEventLoopBase::Run()
  [33] wxAppConsoleBase::MainLoop()
  [34] wxEntry(int&, wchar_t**)
  [35] __libc_start_main

  
  Te error is shown three times. After clicking though (Continue) the program 
is stuck (no window refresh) and nned to be Ctrl-C-ed.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1909484] [NEW] 2020.0.0 calibrate_lens_gui - multiple assertions at startup

[Andreas Metzler]

Public bug reported:

Hello,

starting calibrate_lens_gui generates assertion errors:

ASSERT INFO:
../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in 
SetSourceSurface(): no bitmap data

BACKTRACE:
[1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour 
const*) const
[2] wxBitmap::Draw(_cairo*, int, int, bool, wxColour const*, wxColour const*) 
const
[3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[5] wxEvtHandler::TryHereOnly(wxEvent&)
[6] wxEvtHandler::ProcessEventLocally(wxEvent&)
[7] wxEvtHandler::ProcessEvent(wxEvent&)
[8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[9] wxWindow::GTKSendPaintEvents(_cairo*)
[10] g_closure_invoke
[11] g_signal_emit_valist
[12] g_signal_emit
[13] gtk_container_propagate_draw
[14] gtk_container_propagate_draw
[15] gtk_container_propagate_draw
[16] g_closure_invoke
[17] g_signal_emit_valist
[18] g_signal_emit
[19] gtk_container_propagate_draw
[20] g_closure_invoke
[21] g_signal_emit_valist
[22] g_signal_emit
[23] gtk_container_propagate_draw
[24] gtk_container_propagate_draw
[25] gtk_main_do_event
[26] g_signal_emit_valist
[27] g_signal_emit
[28] g_main_context_dispatch
[29] g_main_loop_run
[30] gtk_main
[31] wxGUIEventLoop::DoRun()
[32] wxEventLoopBase::Run()
[33] wxAppConsoleBase::MainLoop()
[34] wxEntry(int&, wchar_t**)
[35] __libc_start_main


Te error is shown three times. After clicking though (Continue) the program is 
stuck (no window refresh) and nned to be Ctrl-C-ed.

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Affects: hugin (Debian)
 Importance: Unknown
 Status: Unknown

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

Title:
  2020.0.0 calibrate_lens_gui - multiple assertions at startup

Status in Hugin:
  New
Status in hugin package in Debian:
  Unknown

Bug description:
  Hello,

  starting calibrate_lens_gui generates assertion errors:

  ASSERT INFO:
  ../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in 
SetSourceSurface(): no bitmap data

  BACKTRACE:
  [1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour 
const*) const
  [2] wxBitmap::Draw(_cairo*, int, int, bool, wxColour const*, wxColour const*) 
const
  [3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
  [4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
  [5] wxEvtHandler::TryHereOnly(wxEvent&)
  [6] wxEvtHandler::ProcessEventLocally(wxEvent&)
  [7] wxEvtHandler::ProcessEvent(wxEvent&)
  [8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
  [9] wxWindow::GTKSendPaintEvents(_cairo*)
  [10] g_closure_invoke
  [11] g_signal_emit_valist
  [12] g_signal_emit
  [13] gtk_container_propagate_draw
  [14] gtk_container_propagate_draw
  [15] gtk_container_propagate_draw
  [16] g_closure_invoke
  [17] g_signal_emit_valist
  [18] g_signal_emit
  [19] gtk_container_propagate_draw
  [20] g_closure_invoke
  [21] g_signal_emit_valist
  [22] g_signal_emit
  [23] gtk_container_propagate_draw
  [24] gtk_container_propagate_draw
  [25] gtk_main_do_event
  [26] g_signal_emit_valist
  [27] g_signal_emit
  [28] g_main_context_dispatch
  [29] g_main_loop_run
  [30] gtk_main
  [31] wxGUIEventLoop::DoRun()
  [32] wxEventLoopBase::Run()
  [33] wxAppConsoleBase::MainLoop()
  [34] wxEntry(int&, wchar_t**)
  [35] __libc_start_main

  
  Te error is shown three times. After clicking though (Continue) the program 
is stuck (no window refresh) and nned to be Ctrl-C-ed.

  cu Andreas

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 2041687] [NEW] does not show/log enblend error messages

[Andreas Metzler]

Public bug reported:

Hello,

hugin does not show/log enblend errors. I think it did previously. This
is on 2023.0~beta1+dfsg-1.

This was originally reported by Michael Deegan in
https://bugs.debian.org/1054129

It is easy to reproduce by replacing enblend with a dummy-script like this one
-#!/bin/sh
echo status on stdout
echo error in stderr 1>&2
exit 1
--

The corresponding logfile ends with 
Remapping LDR images...
Blending images...

Process took 9 s

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  does not show/log enblend error messages

Status in Hugin:
  New

Bug description:
  Hello,

  hugin does not show/log enblend errors. I think it did previously.
  This is on 2023.0~beta1+dfsg-1.

  This was originally reported by Michael Deegan in
  https://bugs.debian.org/1054129

  It is easy to reproduce by replacing enblend with a dummy-script like this one
  -#!/bin/sh
  echo status on stdout
  echo error in stderr 1>&2
  exit 1
  --

  The corresponding logfile ends with 
  Remapping LDR images...
  Blending images...

  Process took 9 s

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 2041687] Re: does not show/log enblend error messages

[Andreas Metzler]

Thank you, works for me.

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

Title:
  does not show/log enblend error messages

Status in Hugin:
  Fix Committed

Bug description:
  Hello,

  hugin does not show/log enblend errors. I think it did previously.
  This is on 2023.0~beta1+dfsg-1.

  This was originally reported by Michael Deegan in
  https://bugs.debian.org/1054129

  It is easy to reproduce by replacing enblend with a dummy-script like this one
  -#!/bin/sh
  echo status on stdout
  echo error in stderr 1>&2
  exit 1
  --

  The corresponding logfile ends with 
  Remapping LDR images...
  Blending images...

  Process took 9 s

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 2037164] [NEW] 2023.0 beta1 assert after klick on [Stitch]

[Andreas Metzler]

Public bug reported:

Hello,

klicking Stitch! on the Stitcher tab yields assert errors like this one:

-
ASSERT INFO:
/usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype & 
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): 
format specifier doesn't match argument type

BACKTRACE:
[1] HuginQueue::detail::GenerateFinalArgfile(HuginBase::Panorama const&, 
wxString const&, wxConfigBase const*, std::set, std::allocator > const&, double)
[2] HuginQueue::GetStitchingCommandQueue(HuginBase::Panorama const&, wxString 
const&, wxString const&, wxString const&, wxString&, wxArrayString&, 
wxArrayString&, std::ostream&)
[3] RunStitchPanel::StitchProject(wxString const&, wxString const&, wxString 
const&)
[4] wxEntry(int&, wchar_t**)
[5] __libc_start_main
-

(2023.0 beta1, built against libepoxy)

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  2023.0 beta1 assert after klick on [Stitch]

Status in Hugin:
  New

Bug description:
  Hello,

  klicking Stitch! on the Stitcher tab yields assert errors like this
  one:

  -
  ASSERT INFO:
  /usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype & 
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): 
format specifier doesn't match argument type

  BACKTRACE:
  [1] HuginQueue::detail::GenerateFinalArgfile(HuginBase::Panorama const&, 
wxString const&, wxConfigBase const*, std::set, std::allocator > const&, double)
  [2] HuginQueue::GetStitchingCommandQueue(HuginBase::Panorama const&, wxString 
const&, wxString const&, wxString const&, wxString&, wxArrayString&, 
wxArrayString&, std::ostream&)
  [3] RunStitchPanel::StitchProject(wxString const&, wxString const&, wxString 
const&)
  [4] wxEntry(int&, wchar_t**)
  [5] __libc_start_main
  -

  (2023.0 beta1, built against libepoxy)

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 2037164] Re: 2023.0 beta1 assert after klick on [Stitch]

[Andreas Metzler]

Thank you - fix confirmed.

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

Title:
  2023.0 beta1 assert after klick on [Stitch]

Status in Hugin:
  Fix Committed

Bug description:
  Hello,

  klicking Stitch! on the Stitcher tab yields assert errors like this
  one:

  -
  ASSERT INFO:
  /usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype & 
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): 
format specifier doesn't match argument type

  BACKTRACE:
  [1] HuginQueue::detail::GenerateFinalArgfile(HuginBase::Panorama const&, 
wxString const&, wxConfigBase const*, std::set, std::allocator > const&, double)
  [2] HuginQueue::GetStitchingCommandQueue(HuginBase::Panorama const&, wxString 
const&, wxString const&, wxString const&, wxString&, wxArrayString&, 
wxArrayString&, std::ostream&)
  [3] RunStitchPanel::StitchProject(wxString const&, wxString const&, wxString 
const&)
  [4] wxEntry(int&, wchar_t**)
  [5] __libc_start_main
  -

  (2023.0 beta1, built against libepoxy)

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1989723] Re: aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

On 2022-09-16 tmodes <1989...@bugs.launchpad.net> wrote:
> Please test the attached patch.
[...]

That fixes the warning, thanks.

I have found a third issue. After starting up, klicking on [Preview
Panorama (OpenGL)] yields an error (and nothing else:

--
Error initializing GLEW
Fast preview window cannot be opened.
--
with this message on the console:
ERROR: 14:13:49.978869 (./src/hugin1/hugin/GLViewer.cpp:133) SetUpContext(): 
Error initialising GLEW: Unknown error.

Klicking on [Preview Panorama (OpenGL)] succeeds.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  Incomplete

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1989723] Re: aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

On 2022-09-15 tmodes <1989...@bugs.launchpad.net> wrote:
> What was the last working wxWidgets versions?
> Was it from the 3.0.x series? If so then it is only faint related to the 
> wxWidgets 3.2 version.
> It was already fixed in the repository (changeset edfddc6070ca). See also 
> https://groups.google.com/g/hugin-ptx/c/kSrBFdINUnY
[...]

Hello Thomas,

3.0.x. I will doublecheck and report back.

thanks, cu Andreas

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  Incomplete

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1989723] [NEW] aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

Public bug reported:

Hello,

I have tried building hugin 2021.0 against wxwidgets3.2. It builds fine
(some new deprecation warnings), but the binary is non-functional. It
aborts immediately on startup, offering to save some debugging info
(attached).

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Attachment added: "debugging info"
   
https://bugs.launchpad.net/bugs/1989723/+attachment/5616083/+files/hugin_dbgrpt-36901-20220915T152815.zip

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  New

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1989723] Re: aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

On 2022-09-25 tmodes <1989...@bugs.launchpad.net> wrote:
> Hi Andreas,

> does it works now?
> How can the build instruction be more clear? Suggestions are always welcome.
[...]

Hello Thomas,

I do not think hugin can do anything about it but the EGL situation
seems to broken globally.

WX really should be built with EGL and everybody seems to be doing so.
Quoting https://bugs.debian.org/1020640
| AIUI, wxWidgets needs EGL for wxGLCanvas to work under Wayland.
| 
| With 3.0, we had a hack in place to force use of X11 if the wx GL
| library was loaded:
| 
| 
https://sources.debian.org/src/wxwidgets3.0/3.0.5.1%2Bdfsg-5/debian/patches/force-x11-for-wxgl.patch/
| 
| That was better than not working, but doesn't seem a desirable long term
| solution.

OTOH glew EGL support does not seem to ready. Debian does not enable it,
afaict fedora does not either and OpenSuse has dropped it again:
| * Sat Aug 21 2021 Atri Bhattacharya 
| - Revert building with EGL support, as it breaks mutliple apps
|   (boo#1189524).
There is known breakage on the glew side:
https://github.com/nigels-com/glew/issues/321
https://github.com/nigels-com/glew/issues/315

Archlinux builds with EGL but does some patching
https://archlinuxarm.org/packages/armv7h/glew/files

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  Incomplete

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 1989723] Re: aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

** Bug watch added: Debian Bug tracker #1020640
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020640

** Bug watch added: github.com/nigels-com/glew/issues #321
   https://github.com/nigels-com/glew/issues/321

** Bug watch added: github.com/nigels-com/glew/issues #315
   https://github.com/nigels-com/glew/issues/315

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  Incomplete

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

Re: [Hugin-bug-hunters] [Bug 1989723] Re: aborts on startup when built against wxwidgets3.2

[Andreas Metzler]

On 2022-09-15 Andreas Metzler <1989...@bugs.launchpad.net> wrote:
> On 2022-09-15 tmodes <1989...@bugs.launchpad.net> wrote:
>> What was the last working wxWidgets versions?
>> Was it from the 3.0.x series? If so then it is only faint related to the 
>> wxWidgets 3.2 version.
>> It was already fixed in the repository (changeset edfddc6070ca). See also 
>> https://groups.google.com/g/hugin-ptx/c/kSrBFdINUnY
> [...]

> 3.0.x. I will doublecheck and report back.
[...]

Indeed the patch fixes the crash. Thanks!

However I get a assertion error when running [Create panorama...] from
the assistant:

ASSERT INFO:
./src/common/sizer.cpp(2267): assert "CheckSizerFlags(!((flags) & 
(wxALIGN_RIGHT)))" failed in DoInsert(): wxALIGN_RIGHT will be ignored in this 
sizer: only vertical alignment flags can be used in horizontal sizers

DO NOT PANIC !!

If you're an end user running a program not developed by you, please
ignore this message, it is harmless, and please try reporting the
problem to the program developers.

You may also set WXSUPPRESS_SIZER_FLAGS_CHECK environment variable to
suppress all such checks when running this program.

If you're the developer, simply remove this flag from your code to avoid
getting this message. You can also call
wxSizerFlags::DisableConsistencyChecks() to globally disable all such
checks, but this is strongly not recommended.

BACKTRACE:
[1] wxBoxSizer::DoInsert(unsigned long, wxSizerItem*)
[2] wxEntry(int&, wchar_t**)
[3] __libc_start_main


cu Andreas

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

Title:
  aborts on startup when built against wxwidgets3.2

Status in Hugin:
  Incomplete

Bug description:
  Hello,

  I have tried building hugin 2021.0 against wxwidgets3.2. It builds
  fine (some new deprecation warnings), but the binary is non-
  functional. It aborts immediately on startup, offering to save some
  debugging info (attached).

  cu Andreas

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


___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help   : https://help.launchpad.net/ListHelp

[Hugin-bug-hunters] [Bug 2002559] [NEW] build error with flann 1.9.2

[Andreas Metzler]

Public bug reported:

Hello,

this was originally reported in https://bugs.debian.org/1027934 hugin
2022.0.0 fails to build against flann 1.9.2 since it does not use
FLANN_LIBRARY_DIRS as set by CMakeModules/FindFLANN.cmake

~~~
[ 50%] Linking CXX executable cpfind
cd /dev/shm/HUGIN/hugin-2022.0.0/obj-x86_64-linux-gnu/src/hugin_cpfind/cpfind 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/cpfind.dir/link.txt 
--verbose=1
/usr/lib/ccache/c++ -g -O2 -ffile-prefix-map=/dev/shm/HUGIN/hugin-2022.0.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs 
-fopenmp CMakeFiles/cpfind.dir/PanoDetector.cpp.o 
CMakeFiles/cpfind.dir/PanoDetectorLogic.cpp.o 
CMakeFiles/cpfind.dir/TestCode.cpp.o CMakeFiles/cpfind.dir/Utils.cpp.o 
CMakeFiles/cpfind.dir/main.cpp.o -o cpfind  
-Wl,-rpath,/dev/shm/HUGIN/hugin-2022.0.0/obj-x86_64-linux-gnu/src/hugin_cpfind/localfeatures:/dev/shm/HUGIN/hugin-2022.0.0/obj-x86_64-linux-gnu/src/celeste:/dev/shm/HUGIN/hugin-2022.0.0/obj-x86_64-linux-gnu/src/hugin_base:
 ../localfeatures/liblocalfeatures.so.0.0 
/usr/lib/x86_64-linux-gnu/libvigraimpex.so 
/usr/lib/x86_64-linux-gnu/libOpenEXR.so 
/usr/lib/x86_64-linux-gnu/libImath-3_1.so 
/usr/lib/x86_64-linux-gnu/libIex-3_1.so 
/usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-
 linux-gnu/libtiff.so /usr/lib/x86_64-linux-gnu/libpng.so 
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/libpano13.so 
../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so 
/usr/lib/x86_64-linux-gnu/libfftw3.so 
/usr/lib/x86_64-linux-gnu/libvigraimpex.so 
/usr/lib/x86_64-linux-gnu/libOpenEXR.so 
/usr/lib/x86_64-linux-gnu/libImath-3_1.so 
/usr/lib/x86_64-linux-gnu/libIex-3_1.so 
/usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libtiff.so 
/usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libexiv2.so 
/usr/lib/x86_64-linux-gnu/liblcms2.so ../../celeste/libceleste.so.0.0 -lflann 
-lflann_cpp -lhdf5 -lmpi -llz4 ../../hugin_base/libhuginbase.so.0.0 
/usr/lib/x86_64-linux-gnu/libX11.so /usr/lib/x86_64-linux-gnu/libOpenGL.so 
 /usr/lib/x86_64-linux-gnu/libGLX.so /usr/lib/x86_64-linux-gnu/libGLU.so 
/usr/lib/x86_64-linux-gnu/libsqlite3.so /usr/lib/x86_64-linux-gnu/libpano13.so 
../../foreign/levmar/libhuginlevmar.a /usr/lib/x86_64-linux-gnu/libGLEW.so 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libfftw3.so 
/usr/lib/x86_64-linux-gnu/libvigraimpex.so 
/usr/lib/x86_64-linux-gnu/libOpenEXR.so 
/usr/lib/x86_64-linux-gnu/libImath-3_1.so 
/usr/lib/x86_64-linux-gnu/libIex-3_1.so 
/usr/lib/x86_64-linux-gnu/libIlmThread-3_1.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so 
/usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libjpeg.so 
/usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libtiff.so 
/usr/lib/x86_64-linux-gnu/libexiv2.so /usr/lib/x86_64-linux-gnu/liblcms2.so 
/usr/bin/ld: cannot find -lhdf5: No such file or directory
collect2: error: ld returned 1 exit status
~~~

Find attached the patch used in the Debian package patch to fix this.

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

** Patch added: "45_flann_ftbfs.diff"
   
https://bugs.launchpad.net/bugs/2002559/+attachment/5640783/+files/45_flann_ftbfs.diff

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

Title:
   build error with flann 1.9.2

Status in Hugin:
  New

Bug description:
  Hello,

  this was originally reported in https://bugs.debian.org/1027934 hugin
  2022.0.0 fails to build against flann 1.9.2 since it does not use
  FLANN_LIBRARY_DIRS as set by CMakeModules/FindFLANN.cmake

  ~~~
  [ 50%] Linking CXX executable cpfind
  cd /dev/shm/HUGIN/hugin-2022.0.0/obj-x86_64-linux-gnu/src/hugin_cpfind/cpfind 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/cpfind.dir/link.txt 
--verbose=1
  /usr/lib/ccache/c++ -g -O2 -ffile-prefix-map=/dev/shm/HUGIN/hugin-2022.0.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -Wl,-z,defs 
-fopenmp CMakeFiles/cpfind.dir/PanoDetector.cpp.o 
CMakeFiles/cpfind.dir/PanoDetectorLogic.cpp.o 
CMakeFiles/cpfind.dir/TestCode.cpp.o CMakeFiles/cpfind.dir/Utils.cpp.o 
CMakeFiles/cpfind.dir/main.cpp.o -o cpfind