[Hugin-bug-hunters] [Bug 1635992] Re: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField")
Hi Yuv I can not reproduce this on Ubuntu Xenial and Hugin 2016.2.0.be8da0221960 either. However, the images in your testcase are awfully small, maybe the tiff format problem has been stripped away by reducing their size? With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1635992 Title: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField") Status in Hugin: New Bug description: Hugin 2016.2.0.be8da0221960 from PPA on Xubuntu 16.04 Trying to stitch a couple of TIFFs created with Darktable The following error keeps popping up: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField") Hugin does its work, but clicking away the multiple error message (for each image, and it seems to come up every time the image is displayed) is a painful papercut To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1635992/+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 1630172] Re: Unadequate stitching of a HDR panorama
Dear Alex Fliker autopano-sift-c has been deprecated for quite some time now due to concerns about the use of a patented algorithm, IIRC. It has not seen any maintenance since 2009. No wonder it has fallen behind regarding support of current features. Why don't you use cpfind instead? With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1630172 Title: Unadequate stitching of a HDR panorama Status in Enblend: New Bug description: HDR files: https://fliker09.tk/sharedstuff/launchpad/1.hdr https://fliker09.tk/sharedstuff/launchpad/2.hdr https://fliker09.tk/sharedstuff/launchpad/3.hdr https://fliker09.tk/sharedstuff/launchpad/4.hdr Project file: https://fliker09.tk/sharedstuff/launchpad/panorama_8_panomodify.pto Execute: nona -m EXR_m -o panorama panorama_8_panomodify.pto I get 4 EXR files. For visualization I tone-mapped them using mai11 operator: https://fliker09.tk/sharedstuff/launchpad/panorama.jpg https://fliker09.tk/sharedstuff/launchpad/panorama0001.jpg https://fliker09.tk/sharedstuff/launchpad/panorama0002.jpg https://fliker09.tk/sharedstuff/launchpad/panorama0003.jpg Looks all good. After that I try to stitch them using enblend 4.2 (nft and graph-cut algorithms) and verdandi 2016.2.0 (watershed algorithm): enblend --wrap=horizontal --blend-colorspace=IDENTITY -o panorama_original.exr --primary-seam-generator=nearest-feature-transform panorama000*.exr enblend --wrap=horizontal --blend-colorspace=IDENTITY -o panorama_original.exr panorama000*.exr verdandi --wrap --seam=blend --output=panorama_original.exr panorama000*.exr I again tone-mapped the results for visualization: https://fliker09.tk/sharedstuff/launchpad/hdr/ I hope no commentaries are needed... Next, I decided to tone-map the nona's output: pfsin panorama000$i.exr | pfstmo_mai11 | pfsout panorama000$i.tiff convert panorama000$i.tiff -channel a -negate +channel panorama000$i.tif After that I stitched again: enblend --wrap=horizontal --compression=none --blend-colorspace=IDENTITY --fine-mask -o panorama_original.tif --primary-seam-generator=nearest-feature-transform panorama000*.tif enblend --wrap=horizontal --compression=none --blend-colorspace=IDENTITY -o panorama_original.tif panorama000*.tif verdandi --wrap --seam=blend --output=panorama_original.tif panorama000*.tif And here are the results: https://fliker09.tk/sharedstuff/launchpad/tmo/ Difference is huge... Much better results! Now the question - why so bad with EXR files? Am I doing something wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/1630172/+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 1597594] Re: Enblend-4.3-1472 fails to build in FC24
Hi Thomas
Thank you for your patches, I can confirm that it builds now for both xenial
(boost 1.58) and yakkety (boost 1.60).
With kind regards
Stefan Peter
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1597594
Title:
Enblend-4.3-1472 fails to build in FC24
Status in Enblend:
Fix Committed
Bug description:
Attempting to build Enblend-4.3-1472 (current default branch) in Fedora 24,
using rpmbuild.
The build fails with the following message...
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:81:0:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/optional_transitional.hpp:51:31:
error: no matching function for call to 'boost::none_t::none_t()'
constexpr ::boost::none_t nullopt;
^~~
In file included from /usr/include/boost/none.hpp:16:0,
from /usr/include/boost/optional/optional.hpp:51,
from /usr/include/boost/optional.hpp:15,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/optional_transitional.hpp:47,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:81:
/usr/include/boost/none_t.hpp:32:12: note: candidate:
boost::none_t::none_t(boost::none_t::init_tag)
explicit none_t(init_tag){} // to prevent default constructor
^~
/usr/include/boost/none_t.hpp:32:12: note: candidate expects 1 argument, 0
provided
/usr/include/boost/none_t.hpp:29:8: note: candidate: constexpr
boost::none_t::none_t(const boost::none_t&)
struct none_t
^~
/usr/include/boost/none_t.hpp:29:8: note: candidate expects 1 argument, 0
provided
/usr/include/boost/none_t.hpp:29:8: note: candidate: constexpr
boost::none_t::none_t(boost::none_t&&)
/usr/include/boost/none_t.hpp:29:8: note: candidate expects 1 argument, 0
provided
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:190:0:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/common.h: In
function 'std::__cxx11::string enblend::expandFilenameTemplate(const string&,
unsigned int, const string&, const string&, unsigned int)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/common.h:760:25:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/mask.h:42:0,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.h:46,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:193:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/fillpolygon.hxx:
In function 'void vigra_ext::detail::group_to_pairs(Iterator, Iterator,
BackInsertIterator)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/fillpolygon.hxx:255:21:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc: In
function 'int process_options(int, char**)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:926:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:933:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:965:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1051:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1063:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1355:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1390:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1495:13
Re: [Hugin-bug-hunters] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24
Hi Terry Am 05.07.2016 um 09:10 schrieb tduell: > the latest default includes fixes to CMakelists.txt to correct FindOptional, > which seems to be related to this problem. > Attempting to build the current default (1473) cmake reports... > > -- Could not find OPTIONAL package Optional > -- No optional headers found, fall back to boost > > Fedora 24 is using boost-1.60.0-6, and there doesn't seem to be any sign of > the file "boost/optional.hpp". But the error message you quoted shows the presence of In file included from /usr/include/boost/none.hpp:16:0, from /usr/include/boost/optional/optional.hpp:51, from /usr/include/boost/optional.hpp:15, from /home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg- In the case of Ubuntu, the only difference between xenial (which compiles) and yakkety (which fails) is that xenial uses boost-1.58.0 whereas yakkety uses boost-1.60.0. So my conclusion is that something in the libboost implementation of optional has changed between 1.58 and 1.60. And lo and behold, in the release notes of boost 1.60 [1] you can find: Optional: Changed the implementation of boost::none again. Now it is a const object with internal linkage (as any other tag). This fixes #11203. So, this may be the root issue. How to fix this, however, is beyond my pay grade. With kind regards Stefan Peter [1] http://www.boost.org/users/history/version_1_60_0.html ___ 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 1597594] Re: Enblend-4.3-1472 fails to build in FC24
Hi Terry
enblend fails for the upcoming Ubuntu Yakkety with the very same error.
Complete build log at
https://launchpadlibrarian.net/264810247/buildlog_ubuntu-yakkety-amd64.enblend-enfuse_4.3.0+hg1472+dfsg-0ubuntu1~yakkety_BUILDING.txt.gz
Interestingly, the same package succeeds for the latest Ubuntu release
(xenial). Build logs:
https://launchpad.net/~s-peter/+archive/ubuntu/hugin-test/+build/9907747/+files/buildlog_ubuntu-xenial-amd64.enblend-enfuse_4.3.0+hg1472+dfsg-0ubuntu1~xenial_BUILDING.txt.gz
I have not reported this yet because I expected the failure to be caused
by some work in progress on the upcoming release which is expected this
October. Now I'm not so sure anymore.
With kind regards
Stefan Peter
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1597594
Title:
Enblend-4.3-1472 fails to build in FC24
Status in Enblend:
New
Bug description:
Attempting to build Enblend-4.3-1472 (current default branch) in Fedora 24,
using rpmbuild.
The build fails with the following message...
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:81:0:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/optional_transitional.hpp:51:31:
error: no matching function for call to 'boost::none_t::none_t()'
constexpr ::boost::none_t nullopt;
^~~
In file included from /usr/include/boost/none.hpp:16:0,
from /usr/include/boost/optional/optional.hpp:51,
from /usr/include/boost/optional.hpp:15,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/optional_transitional.hpp:47,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:81:
/usr/include/boost/none_t.hpp:32:12: note: candidate:
boost::none_t::none_t(boost::none_t::init_tag)
explicit none_t(init_tag){} // to prevent default constructor
^~
/usr/include/boost/none_t.hpp:32:12: note: candidate expects 1 argument, 0
provided
/usr/include/boost/none_t.hpp:29:8: note: candidate: constexpr
boost::none_t::none_t(const boost::none_t&)
struct none_t
^~
/usr/include/boost/none_t.hpp:29:8: note: candidate expects 1 argument, 0
provided
/usr/include/boost/none_t.hpp:29:8: note: candidate: constexpr
boost::none_t::none_t(boost::none_t&&)
/usr/include/boost/none_t.hpp:29:8: note: candidate expects 1 argument, 0
provided
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:190:0:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/common.h: In
function 'std::__cxx11::string enblend::expandFilenameTemplate(const string&,
unsigned int, const string&, const string&, unsigned int)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/common.h:760:25:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
In file included from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/mask.h:42:0,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.h:46,
from
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:193:
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/fillpolygon.hxx:
In function 'void vigra_ext::detail::group_to_pairs(Iterator, Iterator,
BackInsertIterator)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/fillpolygon.hxx:255:21:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc: In
function 'int process_options(int, char**)':
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:926:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:933:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:965:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1051:13:
warning: attributes at the beginning of statement are ignored [-Wattributes]
[[fallthrough]];
^
/home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:1063:13:
warning: attributes at the beginning of statement are ignored [-Wattrib
[Hugin-bug-hunters] [Bug 1589269] Re: compiler failure in FindPanoDialog.cpp, "void value not ignored as it ought to be"
Hi Matthias There are working trusty builds for 2016.3 (currently hg7426) at https://launchpad.net/~hugin/+archive/ubuntu/nightly. Are you using the same dependencies like these builds? hg7369 was quite some time ago, the nightly builds have been active then and I don't remember this breakage. With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1589269 Title: compiler failure in FindPanoDialog.cpp, "void value not ignored as it ought to be" Status in Hugin: New Bug description: [ 85%] Building CXX object src/hugin1/ptbatcher/CMakeFiles/PTBatcherGUI.dir/FindPanoDialog.cpp.o cd /home/mandree/VCS-other/hugin/src/hugin/hugin.build/src/hugin1/ptbatcher && /usr/bin/c++ -DGLEW_STATIC -DHUGIN_HSI -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -O2 -g -DNDEBUG -I/home/mandree/VCS-other/hugin/src/hugin/hugin.build/src -I/home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/hugin_base -I/home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/celeste -I/home/mandree/VCS-other/hugin/src/hugin/hugin.build/src/celeste -I/home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src -I/usr/include/x86_64-linux-gnu -I/usr/include/OpenEXR -I/usr/local/include -I/home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/foreign -I/usr/include/python2.7 -I/home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/hugin1 -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-release-2.8 -isystem /usr/include/wx-2.8-fopenmp -pthread -std=gnu++11 -o CMakeFiles/PTBatcherGUI.dir/FindPanoDialog.cpp.o -c /home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/hugin1/ptbatcher/FindPano Dialog.cpp /home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/hugin1/ptbatcher/FindPanoDialog.cpp: In member function 'void FindPanoDialog::OnSplitPanos(wxCommandEvent&)': /home/mandree/VCS-other/hugin/src/hugin/hugin.hg/src/hugin1/ptbatcher/FindPanoDialog.cpp:444:126: error: void value not ignored as it ought to be int newItem = m_list_pano->Insert(m_panos[selectedPano + 1]->GetItemString(m_start_dir), selectedPano + 1); ^ make[2]: *** [src/hugin1/ptbatcher/CMakeFiles/PTBatcherGUI.dir/FindPanoDialog.cpp.o] Error 1 (the marker is at the final closing parenthesis) This is with #define VERSION_MAJOR 2016 #define VERSION_MINOR 3 #define VERSION_PATCH 0 #define HUGIN_WC_REVISION 7cf531fff7d2 #define HUGIN_API_VERSION "2016.3" To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1589269/+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 1557749] Re: Latest default branch fails to build
Hi Terry
thank you very much for the fixes, the latest ( (2016.1.0+hg7307) build
succeeded.
With kind regards
Stefan Peter
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1557749
Title:
Latest default branch fails to build
Status in Hugin:
Fix Committed
Bug description:
Attempting to build the default branch (6944dd3eb874 7306 ) on Fedora
23 x86_64 using Fedora's rpmbuild, I get the following output from
rpmbuild...
/home/terry/rpmbuild/BUILD/hugin-2016.1.0/src/hugin1/hugin/PapywizardImport.cpp:100:83:
required from here
/home/terry/rpmbuild/BUILD/hugin-2016.1.0/src/hugin_base/hugin_utils/utils.h:130:36:
error: cannot convert 'const wxChar* {aka const wchar_t*}' to 'const char*' in
initialization
const char * p = str.c_str();
^
src/hugin1/hugin/CMakeFiles/hugin.dir/build.make:1481: recipe for target
'src/hugin1/hugin/CMakeFiles/hugin.dir/PapywizardImport.cpp.o' failed
make[2]: *** [src/hugin1/hugin/CMakeFiles/hugin.dir/PapywizardImport.cpp.o]
Error 1
Cheers,
Terry
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1557749/+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 1557749] Re: Latest default branch fails to build
Hi
the nightly builds of Hugin 2016.1.0.6944dd3eb874 hg7306 for Ubuntu
failed, too. But differently:
cd /«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/obj-x86_64-linux-gnu/src/hugin1/hugin
&& /usr/bin/x86_64-linux-gnu-g++ -DGLEW_STATIC -DHUGIN_HSI -DWXUSINGDLL
-D_FILE_OFFSET_BITS=64 -D__WXGTK__ -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall
-D_FORTIFY_SOURCE=2 --std=c++11 -pthread
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/obj-x86_64-linux-gnu/src
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin_base
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/celeste
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/obj-x86_64-linux-gnu/src/celeste
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src -I/usr/include/x86_64-linux-gnu
-I/usr/include/OpenEXR -I/usr/include/python2.7
-I/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1 -isystem
/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -isystem
/usr/include/wx-3.0-fopenmp -o CMakeFiles/hugin.dir/PluginItems.cpp.o -c
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PluginItems.cpp
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:62:5:
error: extra qualification ‘Papywizard::PapywizardSettings::’ on member
‘PapywizardSettings’ [-fpermissive]
PapywizardSettings::PapywizardSettings()
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:
In function ‘bool Papywizard::ParseShoot(wxXmlNode*,
Papywizard::PapywizardSettings&)’:
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:173:27:
warning: comparison between signed and unsigned integer expressions
[-Wsign-compare]
if (longVal < id)
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:
At global scope:
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:288:5:
error: extra qualification ‘Papywizard::PapywizardImportDialog::’ on member
‘PapywizardImportDialog’ [-fpermissive]
PapywizardImportDialog::~PapywizardImportDialog()
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:296:10:
error: extra qualification ‘Papywizard::PapywizardImportDialog::’ on member
‘EnableStack’ [-fpermissive]
void PapywizardImportDialog::EnableStack(const bool hasStacks)
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:301:16:
error: extra qualification ‘Papywizard::PapywizardImportDialog::’ on member
‘LinkStacks’ [-fpermissive]
const bool PapywizardImportDialog::LinkStacks() const
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:305:16:
error: extra qualification ‘Papywizard::PapywizardImportDialog::’ on member
‘RunCpfind’ [-fpermissive]
const bool PapywizardImportDialog::RunCpfind() const
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:309:20:
error: extra qualification ‘Papywizard::PapywizardImportDialog::’ on member
‘GetCPFindParam’ [-fpermissive]
const wxString PapywizardImportDialog::GetCPFindParam() const
^
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:
In function ‘bool Papywizard::ImportPapywizardFile(const wxString&,
HuginBase::Panorama&)’:
/«BUILDDIR»/hugin-2016.1.0+hg7306+dfsg/src/hugin1/hugin/PapywizardImport.cpp:467:13:
warning: unused variable ‘ret’ [-Wunused-variable]
int ret = MyExecuteCommandQueue(commands, wxGetActiveWindow(),
_("Searching control points"));
^
make[4]: *** [src/hugin1/hugin/CMakeFiles/hugin.dir/PapywizardImport.cpp.o]
Error 1
Full build logs are available at
https://launchpadlibrarian.net/248319659/buildlog_ubuntu-trusty-amd64.hugin_2016.1.0+hg7306+dfsg-0ubuntu1~trusty_BUILDING.txt.gz
Regards
Stefan Peter
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1557749
Title:
Latest default branch fails to build
Status in Hugin:
New
Bug description:
Attempting to build the default branch (6944dd3eb874 7306 ) on Fedora
23 x86_64 using Fedora's rpmbuild, I get the following output from
rpmbuild...
/home/terry/rpmbuild/BUILD/hugin-2016.1.0/src/hugin1/hugin/PapywizardImport.cpp:100:83:
required from here
/home/terry/rpmbuild/BUILD/hugin-2016.1.0/src/hugin_base/hugin_utils/utils.h:130:36:
error: cannot convert 'const wxChar* {aka const wchar_t*}' to 'const char*' in
initialization
const char * p = str.c_str();
^
src/hugin1/hugin/CMakeFiles/hugin.dir/build.make:1481: recipe for target
'src/hugin1/hugin/CMakeFiles/hugin.dir/PapywizardImport.cpp.o' failed
make[2]: *** [src/hugin1/hugin/CMakeFiles/hugin.dir/PapywizardImport.cpp.o]
Error 1
Cheers,
Terry
To manage notif
[Hugin-bug-hunters] [Bug 1500181] Re: enblend not working
This probably is a debian sid related bug, please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798850 With kind regards Stefan Peter ** Bug watch added: Debian Bug tracker #798850 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798850 -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1500181 Title: enblend not working Status in Hugin: New Bug description: When I use a builtin blender, the panorama is stitched succesfully, but when I use the enblend, the stitching process fails with this message: # Stitching panorama... Platform: Linux 4.1.0-2-686-pae i686 Version: 2015.0.0.cdefc6e53a58 Working directory: /home/roman/Desktop/YE/00 Output prefix: 20150919_164418 - 20150919_164425 Blender: enblend 4.1.3 ExifTool version: 10.00 Number of active images: 3 Output exposure value: 13.9 Canvas size: 2994x3461 ROI: (232, 52) - (2762, 2679) FOV: 54x61 Projection: Rectilinear(0) Using GPU for remapping: true Panorama Outputs: * Exposure corrected, low dynamic range Remapped Images: * Exposure corrected, low dynamic range First input image Number: 0 Filename: Size: 2560x1920 Projection: Normal (rectilinear) Response type: custom (EMoR) HFOV: 47 Exposure value: 12.8 Remapping LDR images... nona: using graphics card: NVIDIA Corporation GeForce GTX 650/PCIe/SSE2 Multiple images output loading 20150919_164418.jpg remapping 20150919_164418.jpg saving 20150919_164418 - 20150919_164425.tif loading 20150919_164422.jpg remapping 20150919_164422.jpg saving 20150919_164418 - 20150919_1644250001.tif loading 20150919_164425.jpg remapping 20150919_164425.jpg saving 20150919_164418 - 20150919_1644250002.tif Blending images... # No matter the Hugin settings, the result is always the same while using the enblend. uname -a: Linux debian-sid 4.1.0-2-686-pae #1 SMP Debian 4.1.6-1 (2015-08-23) i686 GNU/Linux Hugin: 2015.0.0.cdefc6e53a58 enblend: 4.1.3 nona: 2015.0.0.cdefc6e53a58 enfuse: 4.1.3 libc6: 2.19-22 libstdc++6: 5.2.1-17 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1500181/+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 679654] Re: updated levmar library
Hi Thomas Thank you very much for your explanations. I will try to add the lapack dependency to the Ubuntu packages I maintain and to the upstream Debian packages as well. However, this effort will be concentrate on hugin>2015.0.0 because I do not want to introduce a new dependency (and, maybe, a new behavior and new problem spots) before the upcoming 2015.0.0 release. Again, thank you very much for your advice. With kind regards Stefan On 24.06.2015 20:10, tmodes wrote: > Hi Stephan, > > there are 2 type of warnings in levmar. > > The first one is of type > #warning Linearly constrained optimization requires LAPACK and was not > compiled! > > levmar implement different unconstrained and constrained versions of the > Levenberg-Marquard algorithm. Some of the contrained version need LAPACK > to work. But Hugin is only using the unconstrained version. This type of > warning can therefore ignored, at least for Hugin. > > The second warning is > #warning LAPACK not available, LU will be used for matrix inversion when > computing the covariance; this might be unstable at times > > This warning is trigged in code which is used by Hugin. The warning > states that LAPACK could help to calculate the covariance. But as far as > I know Hugin is not using the returned covariance. So LAPACK could help > to make it more robust. But until now I have not seen any issues when > using levmar without LAPACK. > > The LAPACK is already in CMake, but needs explicitly activated: > ## > ## LAPACK (optional, enable by -DENABLE_LAPACK=ON) > ## > OPTION (ENABLE_LAPACK "Use LAPACK based solver in levmar" OFF) > -- Any technology that does not appear magical is insufficiently advanced. ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679654 Title: updated levmar library Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Last December, an updated levmar was released (2.2), with change that could be very interesting for hugin: - Fixed an error in the computation of the damping factor of levmar_dif() in lm_core.c. Thanks to John Ervin for reporting. This change is interesting, because levmar_dif is used for photometric optimisation by hugin. I took the liberty to try hugin with this newer version of the levmar library, and on my test panorama it took slightly longer but reached the same end result. This is of course not 0.7 material, but perhaps something for early 0.7.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679654/+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 679654] Re: updated levmar library
Hi Thomas The hugin nightlies of 2015.1.0.12f7dc74bbc2 compiled successfully, thank you very much for the prompt support. Do you have any insight regarding the #warning Linear inequalities constrained optimization requires LAPACK and was not compiled! in the levmar build? I don't think that an additional lapack dependency would do any harm. But I don't know if this really is needed. And I'd need help adapting the build system (if this is needed) to honour the lapack dependency. Or does it already support this and we just missed to specify it? With kind regards Stefan -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679654 Title: updated levmar library Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Last December, an updated levmar was released (2.2), with change that could be very interesting for hugin: - Fixed an error in the computation of the damping factor of levmar_dif() in lm_core.c. Thanks to John Ervin for reporting. This change is interesting, because levmar_dif is used for photometric optimisation by hugin. I took the liberty to try hugin with this newer version of the levmar library, and on my test panorama it took slightly longer but reached the same end result. This is of course not 0.7 material, but perhaps something for early 0.7.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679654/+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 679654] Re: updated levmar library
Hi Thomas Hugin 7031:461bf6f58d2e fails linking libhuginbase: ... Linking CXX shared library libhuginbase.so cd /«BUILDDIR»/hugin-2015.1.0+hg7031+dfsg/obj-x86_64-linux-gnu/src/hugin_base && /usr/bin/cmake -E cmake_link_script CMakeFiles/huginbase.dir/link.txt --verbose=1 /usr/bin/x86_64-linux-gnu-g++ -fPIC -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 --std=c++11 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs -fopenmp -shared -Wl,-soname,libhuginbase.so.0.0 -o libhuginbase.so.0.0 CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/CalculateCPStatistics.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/CalculateMeanExposure.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/CalculateOptimalScale.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/CalculateOptimalROI.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/RotatePanorama.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/TranslatePanorama.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/StraightenPanorama.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/CalculateOverlap.cpp.o CMakeFiles/huginbase.dir/algorithms/basic/LayerStacks.cpp.o CMakeFiles/huginbase.dir/algorithms/nona/CalculateFOV.cpp.o CMakeFiles/huginbase.dir/algorithms/nona/CenterHorizontally.cpp.o CMakeFiles/huginbase.dir/algorithms/nona/FitPanorama.cpp.o CMakeFiles/huginbase.dir/algorithms/nona/ComputeImageROI.cpp.o CMakeFiles/huginbase.dir/algorithms/optimizer/ImageGraph.cpp.o CMakeFiles/huginbase.dir/algorithms/optimizer/PhotometricOptimizer.cpp.o CMakeFiles/huginbase.dir/algorithms/optimizer/PTOptimizer.cpp.o CMakeFiles/huginbase.dir/algorithms/point_sampler/PointSampler.cpp.o CMakeFiles/huginbase.dir/algorithms/control_points/CleanCP.cpp.o CMakeFiles/huginbase.dir/appbase/ProgressDisplay.cpp.o CMakeFiles/huginbase.dir/huginapp/CachedImageRemapper.cpp.o CMakeFiles/huginbase.dir/huginapp/ImageCache.cpp.o CMakeFiles/huginbase.dir/hugin_math/eig_jacobi.cpp.o CMakeFiles/huginbase.dir/hugin_math/graph.cpp.o CMakeFiles/huginbase.dir/hugin_math/Matrix3.cpp.o CMakeFiles/huginbase.dir/hugin_math/Vector3.cpp.o CMakeFiles/huginbase.dir/hugin_utils/alphanum.cpp.o CMakeFiles/huginbase.dir/hugin_utils/utils.cpp.o CMakeFiles/huginbase.dir/hugin_utils/platform.cpp.o CMakeFiles/huginbase.dir/lensdb/LensDB.cpp.o CMakeFiles/huginbase.dir/nona/SpaceTransform.cpp.o CMakeFiles/huginbase.dir/nona/Stitcher1.cpp.o CMakeFiles/huginbase.dir/nona/Stitcher2.cpp.o CMakeFiles/huginbase.dir/nona/Stitcher3.cpp.o CMakeFiles/huginbase.dir/nona/Stitcher4.cpp.o CMakeFiles/huginbase.dir/nona/Stitcher.cpp.o CMakeFiles/huginbase.dir/nona/StitcherOptions.cpp.o CMakeFiles/huginbase.dir/panodata/ControlPoint.cpp.o CMakeFiles/huginbase.dir/panodata/Lens.cpp.o CMakeFiles/huginbase.dir/panodata/Mask.cpp.o CMakeFiles/huginbase.dir/panodata/Panorama.cpp.o CMakeFiles/huginbase.dir/panodata/PanoramaOptions.cpp.o CMakeFiles/huginbase.dir/panodata/PanoramaVariable.cpp.o CMakeFiles/huginbase.dir/panodata/PTScriptParsing.cpp.o CMakeFiles/huginbase.dir/panodata/SrcPanoImage.cpp.o CMakeFiles/huginbase.dir/panodata/ImageVariableGroup.cpp.o CMakeFiles/huginbase.dir/panodata/StandardImageVariableGroups.cpp.o CMakeFiles/huginbase.dir/panodata/Exiv2Helper.cpp.o CMakeFiles/huginbase.dir/panotools/PanoToolsInterface.cpp.o CMakeFiles/huginbase.dir/panotools/PanoToolsOptimizerWrapper.cpp.o CMakeFiles/huginbase.dir/panotools/PanoToolsUtils.cpp.o CMakeFiles/huginbase.dir/panotools/PanoToolsTransformGPU.cpp.o CMakeFiles/huginbase.dir/vigra_ext/emor.cpp.o CMakeFiles/huginbase.dir/vigra_ext/ImageTransformsGPU.cpp.o -lboost_filesystem -lboost_system -lpthread ../foreign/levmar/libhuginlevmar.a -lvigraimpex -lboost_filesystem -lboost_system -lexiv2 -lpano13 -ltiff -lGLU -lGL -lSM -lICE -lX11 -lXext -lGLEW -lpthread -lsqlite3 -llcms2 -lboost_filesystem -lboost_system -lvigraimpex -lexiv2 -lpano13 -ltiff -lGLU -lGL -lSM -lICE -lX11 -lXext -lGLEW -lsqlite3 -llcms2 -Wl,-rpath,:: /usr/bin/ld: ../foreign/levmar/libhuginlevmar.a(lm.c.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC ../foreign/levmar/libhuginlevmar.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status make[4]: *** [src/hugin_base/libhuginbase.so.0.0] Error 1 The full log is here: https://launchpadlibrarian.net/209767832/buildlog_ubuntu-trusty-amd64.hugin_2015.1.0%2Bhg7031%2Bdfsg-0ubuntu1~trusty_BUILDING.txt.gz Additionally, I have noticed several warnings sprinkeld through the compile stage of levmar: #warning Linear inequalities constrained optimization requires LAPACK and was not compiled! I have no idea if this warning actually applies in out case but I thought I should mention it. With kind regards Stefan Peter -- You received this bug notification because you are a member
[Hugin-bug-hunters] [Bug 1465823] Re: hugin batch processor stops after making pto
Hi Thomas I checked 2015.1.0.7acabc8c42f6 (from the nightly builds PPA) on ubuntu trusty and the error seems to be fixed with that. Thanks! With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1465823 Title: hugin batch processor stops after making pto Status in Hugin - Panorama Tools GUI: New Bug description: Hi, I am working with the current RC1 (2015.0.0.d497c7fc1866) on Ubuntu 14.04. My normal work flow is as follows: - put all single images in folder - start batch processer - look for pictures -start - select In between there is the message: Assertion failed! ... /usr/include/wx-3.0/wx/strvararg.h(451): Ok, I can click away that. - I start the batch. - First window opens: .processing of pto file (pto file is saved) - Second progress window opens (which should make the actual stiched panorama). Nothing further happens, I cannot close or make any changes have to xkill everything. Upon restarting the batcher withthe pto file. Image is made. Greetings, Georg PS: The image preview after looking for single pictures in the folder is great ! To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1465823/+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 1465823] Re: hugin batch processor stops after making pto
I can confirm this problem. You need at least two unfinished projects in the queue. The first job actually finishes but 'ps faxww' shows 12888 ?Sl 0:10 \_ PTBatcherGUI 15465 ?Z 0:00 | \_ [enblend] The final lines in the log of the first job: enblend: info: loading next image: 16597_3780-37890006.tif 1/1 enblend: info: loading next image: 16597_3780-37890007.tif 1/1 enblend: info: loading next image: 16597_3780-37890008.tif 1/1 enblend: info: loading next image: 16597_3780-37890009.tif 1/1 enblend: info: writing final output Updating metadata... 1 image files updated The log file of the second job remains empty. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1465823 Title: hugin batch processor stops after making pto Status in Hugin - Panorama Tools GUI: New Bug description: Hi, I am working with the current RC1 (2015.0.0.d497c7fc1866) on Ubuntu 14.04. My normal work flow is as follows: - put all single images in folder - start batch processer - look for pictures -start - select In between there is the message: Assertion failed! ... /usr/include/wx-3.0/wx/strvararg.h(451): Ok, I can click away that. - I start the batch. - First window opens: .processing of pto file (pto file is saved) - Second progress window opens (which should make the actual stiched panorama). Nothing further happens, I cannot close or make any changes have to xkill everything. Upon restarting the batcher withthe pto file. Image is made. Greetings, Georg PS: The image preview after looking for single pictures in the folder is great ! To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1465823/+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 1451985] Re: Another assert error message, this time in PTBatcherGUI
Hi Thomas On 07.05.2015 20:12, tmodes wrote: >> So, as long as I don't get a "shut up, you are annoying me with your >> nitpicking" from you, I will continue with the DEBUG variant of .. > > As long as the same message is not reported more than once or even often I > don't cry "shut up". > I will do what is in my capability to fix them. > I really appreciate this. With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1451985 Title: Another assert error message, this time in PTBatcherGUI Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Sorry, but I got another one. This has been observers using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Reproduce: Loding an existing pto Cange to the Sticher tab Press "Stich!" Confirm the save Result: ASSERT INFO: ../src/gtk/gauge.cpp(67): assert "0 <= m_gaugePos && m_gaugePos <= m_rangeMax" failed in DoSetGauge(): invalid gauge position in DoSetGauge() BACKTRACE: [1] wxGauge::DoSetGauge() [2] ProgressStatusBar::ProgressStatusBar(wxWindow*, int, long, wxString const&) [3] BatchFrame::OnCreateStatusBar(int, long, int, wxString const&) [4] wxFrameBase::CreateStatusBar(int, long, int, wxString const&) [5] BatchFrame::BatchFrame(wxLocale*, wxString) [6] PTBatcherGUI::OnInit() [7] wxEntry(int&, wchar_t**) [8] main [9] __libc_start_main [10] _start The error mesage windows states PTBatcherGUI, not hugin. I had to confirm the error message 10 of times until the stitch actually started. I will make the pto available upon request. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451985/+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 1451985] Re: Another assert error message, this time in PTBatcherGUI
Dear Thomas Modes On 06.05.2015 18:15, tmodes wrote: > Should also be fixed in repository. Yes, I can confirm that I can not anymore reproduce this error using Operating System: Linux 3.13.0-52-generic x86_64 Architecture: 64 bit Free memory: 11166756 kiB Hugin Version: 2015.1.0.15309c132690 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 > > See http://docs.wxwidgets.org/3.0.0/overview_debugging.html for more > information about the assert message. > (Maybe defining the symbol NDEBUG is sufficient to suppress the assert > messages?) I may be tempted to investigate this for the upcoming RC versions. On the other hand, as long as you don't object, I feel that these asserts are there for a reason. The more of these we can fix now, the less problems we will encounter in the future on all of the systems we want to deploy to. So, as long as I don't get a "shut up, you are annoying me with your nitpicking" from you, I will continue with the DEBUG variant of hugin/wxwidgets during the beta versions, I will reconsider this decision for the rc releases. Thank you very much for your support. With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1451985 Title: Another assert error message, this time in PTBatcherGUI Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Sorry, but I got another one. This has been observers using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Reproduce: Loding an existing pto Cange to the Sticher tab Press "Stich!" Confirm the save Result: ASSERT INFO: ../src/gtk/gauge.cpp(67): assert "0 <= m_gaugePos && m_gaugePos <= m_rangeMax" failed in DoSetGauge(): invalid gauge position in DoSetGauge() BACKTRACE: [1] wxGauge::DoSetGauge() [2] ProgressStatusBar::ProgressStatusBar(wxWindow*, int, long, wxString const&) [3] BatchFrame::OnCreateStatusBar(int, long, int, wxString const&) [4] wxFrameBase::CreateStatusBar(int, long, int, wxString const&) [5] BatchFrame::BatchFrame(wxLocale*, wxString) [6] PTBatcherGUI::OnInit() [7] wxEntry(int&, wchar_t**) [8] main [9] __libc_start_main [10] _start The error mesage windows states PTBatcherGUI, not hugin. I had to confirm the error message 10 of times until the stitch actually started. I will make the pto available upon request. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451985/+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 1451985] Re: Another assert error message, this time in PTBatcherGUI
Dear Thomas Modes On 06.05.2015 18:15, tmodes wrote: > Should also be fixed in repository. Yes, I can confirm that I can not anymore reproduce this error using Operating System: Linux 3.13.0-52-generic x86_64 Architecture: 64 bit Free memory: 11166756 kiB Hugin Version: 2015.1.0.15309c132690 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 > > See http://docs.wxwidgets.org/3.0.0/overview_debugging.html for more > information about the assert message. > (Maybe defining the symbol NDEBUG is sufficient to suppress the assert > messages?) I may be tempted to investigate this for the upcoming RC versions. On the other hand, as long as you don't object, I feel that these asserts are there for a reason. The more of these we can fix now, the less problems we will encounter in the future on all of the systems we want to deploy to. So, as long as I don't get a "shut up, you are annoying me with your nitpicking" from you, I will continue with the DEBUG variant of hugin/wxwidgets during the beta versions, I will reconsider this decision for the rc releases. Thank you very much for your support. With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford ___ 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 1451985] Re: Another assert error message, this time in PTBatcherGUI
Hi Thomas On 05.05.2015 21:49, tmodes wrote: > Should be fixed in changeset c0173a975f27. > > At least somebody is testing the beta version ;-) and we don't get the > reports after we have released the final version. > > ** Changed in: hugin >Status: New => Fix Committed > > ** Changed in: hugin > Milestone: None => 2015.0beta2 > Sorry, now I get a couple of ASSERT INFO: /usr/include/wx-3.0/wx/strvararg.h(451): assert "(argtype & (wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type BACKTRACE: [1] HuginQueue::detail::PrintDetailInfo(HuginBase::Panorama const&, HuginBase::PanoramaOptions const&, std::set, std::allocator > const&, wxString const&, wxString const&, wxConfigBase*, double&) [2] HuginQueue::GetStitchingCommandQueue(HuginBase::Panorama const&, wxString const&, wxString const&, wxString const&, wxString&, wxArrayString&, wxArrayString&) [3] RunStitchPanel::StitchProject(wxString, wxString) [4] RunStitchFrame::StitchProject(wxString, wxString) [5] Batch::OnStitch(wxString, wxString, int) [6] Batch::RunNextInBatch() [7] Batch::RunBatch() [8] BatchFrame::RunBatch() [9] PTBatcherGUI::OnInit() [10] wxEntry(int&, wchar_t**) [11] main [12] __libc_start_main [13] _start from Operating System: Linux 3.13.0-52-generic x86_64 Architecture: 64 bit Free memory: 10428204 kiB Hugin Version: 2015.1.0.246eb732c486 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 I'm feeling tempted to replace the 3.0.0 wxWidgets with the old ones. Regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1451985 Title: Another assert error message, this time in PTBatcherGUI Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: Sorry, but I got another one. This has been observers using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Reproduce: Loding an existing pto Cange to the Sticher tab Press "Stich!" Confirm the save Result: ASSERT INFO: ../src/gtk/gauge.cpp(67): assert "0 <= m_gaugePos && m_gaugePos <= m_rangeMax" failed in DoSetGauge(): invalid gauge position in DoSetGauge() BACKTRACE: [1] wxGauge::DoSetGauge() [2] ProgressStatusBar::ProgressStatusBar(wxWindow*, int, long, wxString const&) [3] BatchFrame::OnCreateStatusBar(int, long, int, wxString const&) [4] wxFrameBase::CreateStatusBar(int, long, int, wxString const&) [5] BatchFrame::BatchFrame(wxLocale*, wxString) [6] PTBatcherGUI::OnInit() [7] wxEntry(int&, wchar_t**) [8] main [9] __libc_start_main [10] _start The error mesage windows states PTBatcherGUI, not hugin. I had to confirm the error message 10 of times until the stitch actually started. I will make the pto available upon request. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451985/+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 1451985] [NEW] Another assert error message, this time in PTBatcherGUI
Public bug reported: Sorry, but I got another one. This has been observers using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Reproduce: Loding an existing pto Cange to the Sticher tab Press "Stich!" Confirm the save Result: ASSERT INFO: ../src/gtk/gauge.cpp(67): assert "0 <= m_gaugePos && m_gaugePos <= m_rangeMax" failed in DoSetGauge(): invalid gauge position in DoSetGauge() BACKTRACE: [1] wxGauge::DoSetGauge() [2] ProgressStatusBar::ProgressStatusBar(wxWindow*, int, long, wxString const&) [3] BatchFrame::OnCreateStatusBar(int, long, int, wxString const&) [4] wxFrameBase::CreateStatusBar(int, long, int, wxString const&) [5] BatchFrame::BatchFrame(wxLocale*, wxString) [6] PTBatcherGUI::OnInit() [7] wxEntry(int&, wchar_t**) [8] main [9] __libc_start_main [10] _start The error mesage windows states PTBatcherGUI, not hugin. I had to confirm the error message 10 of times until the stitch actually started. I will make the pto available upon request. With kind regards Stefan Peter ** 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/1451985 Title: Another assert error message, this time in PTBatcherGUI Status in Hugin - Panorama Tools GUI: New Bug description: Sorry, but I got another one. This has been observers using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Reproduce: Loding an existing pto Cange to the Sticher tab Press "Stich!" Confirm the save Result: ASSERT INFO: ../src/gtk/gauge.cpp(67): assert "0 <= m_gaugePos && m_gaugePos <= m_rangeMax" failed in DoSetGauge(): invalid gauge position in DoSetGauge() BACKTRACE: [1] wxGauge::DoSetGauge() [2] ProgressStatusBar::ProgressStatusBar(wxWindow*, int, long, wxString const&) [3] BatchFrame::OnCreateStatusBar(int, long, int, wxString const&) [4] wxFrameBase::CreateStatusBar(int, long, int, wxString const&) [5] BatchFrame::BatchFrame(wxLocale*, wxString) [6] PTBatcherGUI::OnInit() [7] wxEntry(int&, wchar_t**) [8] main [9] __libc_start_main [10] _start The error mesage windows states PTBatcherGUI, not hugin. I had to confirm the error message 10 of times until the stitch actually started. I will make the pto available upon request. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451985/+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 1451172] Re: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask
Hi Thomas On 05.05.2015 18:48, tmodes wrote: > @Stefan: please try if changeset c0ae9038be6 fixes the issue (just > guessing). Also with your project file I can't reproduce the issue. > I can no longer reproduce this using Operating System: Linux 3.13.0-51-generic x86_64 Architecture: 64 bit Free memory: 11436008 kiB Hugin Version: 2015.1.0.c0ae9038be6b Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/stefan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0 wxWidgets Library (wxGTK port) Version 3.0.0 (Unicode: wchar_t, debug level: 1), compiled at Dec 2 2013 15:56:33 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.22. libpano13: 2.9.19 Boost: 1.54.0 Exiv2: 0.23 SQLite3: 3.8.2 Vigra: 1.10.0 available currently from https://launchpad.net/~hugin/+archive/ubuntu/nightly/+packages Thanks a bunch ! With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1451172 Title: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask Status in Hugin - Panorama Tools GUI: New Bug description: In hugin 2015.0.0-Beta1, when deleting a mask, the following is thrown ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451172/+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 1451172] Re: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask
On 04.05.2015 20:03, Stefan Peter wrote: > On 04.05.2015 17:36, tmodes wrote: >> I can't reproduce the issue. Tested on 2 different systems: Windows and >> Linux (both with wxWidgets 3.x). I can still reproduce this with hugin 2015.1.0+hg6912+dfsg-0ubuntu1~trusty currently available from https://launchpad.net/~hugin/+archive/ubuntu/nightly And I really wonder why nobody else has caught these. Maybe I do something wrong? With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1451172 Title: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask Status in Hugin - Panorama Tools GUI: New Bug description: In hugin 2015.0.0-Beta1, when deleting a mask, the following is thrown ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451172/+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 1451172] Re: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask
On 04.05.2015 17:36, tmodes wrote: > I can't reproduce the issue. Tested on 2 different systems: Windows and > Linux (both with wxWidgets 3.x). The following is done in "Expert mode" if this makes a difference. I can reproduce this easily in 2015.0.0-beta 1: o Create a new project o Add two images o Add a mask to the second image o save the project (attached as o press "Delete mask" in Masks and I immediately get this: ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start I can reproduce this by o loading the attached pto o changing to the Masks tab o selecting image 1 o selecting '0 Exclude region' o pressing the "Delete mask" button > > Could you provide the project file and mention with mask you are deleting > (image and mask number) when you get the assert message? > Maybe it is a coincidence of several different issues. I will try if I can reproduce this with the master. Maybe one of the fixes you applied in the meantime has an influence. > Is the option show extend of masks and crops switched on or off? it is disabled in my case. However, enabling it doe snot change the assert message: ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start Thank you for your time investigating this issue. Please let me know if I can do anything else to help find the issue. With kind regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford ** Attachment added: "test1451172.pto" https://bugs.launchpad.net/bugs/1451172/+attachment/4390784/+files/test1451172.pto -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin.
[Hugin-bug-hunters] [Bug 1451175] [NEW] hugin 2015.0.0-beta1 throws ASSERT INFO; format specifier doesn't match argument type when opening the control points list
Public bug reported: When opening the control points list, hugin 2015.0.0-beta1 throws ASSERT INFO: /usr/include/wx-3.0/wx/strvararg.h(451): assert "(argtype & (wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type BACKTRACE: [1] wxString wxString::Format(wxFormatString const&, unsigned long) [2] CPListCtrl::OnGetItemText(long, long) const [3] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const [4] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [5] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [6] wxEvtHandler::TryHereOnly(wxEvent&) [7] wxEvtHandler::ProcessEventLocally(wxEvent&) [8] wxEvtHandler::ProcessEvent(wxEvent&) [9] wxEvtHandler::SafelyProcessEvent(wxEvent&) [10] wxWindow::GTKSendPaintEvents(_GdkRegion const*) [11] g_closure_invoke [12] g_signal_emit_valist [13] g_signal_emit [14] gtk_main_do_event [15] gdk_window_process_all_updates [16] g_main_context_dispatch [17] g_main_loop_run [18] gtk_main [19] wxGUIEventLoop::DoRun() [20] wxEventLoopBase::Run() [21] wxAppConsoleBase::MainLoop() [22] wxEntry(int&, wchar_t**) [23] main [24] __libc_start_main [25] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter ** 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/1451175 Title: hugin 2015.0.0-beta1 throws ASSERT INFO; format specifier doesn't match argument type when opening the control points list Status in Hugin - Panorama Tools GUI: New Bug description: When opening the control points list, hugin 2015.0.0-beta1 throws ASSERT INFO: /usr/include/wx-3.0/wx/strvararg.h(451): assert "(argtype & (wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type BACKTRACE: [1] wxString wxString::Format(wxFormatString const&, unsigned long) [2] CPListCtrl::OnGetItemText(long, long) const [3] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const [4] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [5] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [6] wxEvtHandler::TryHereOnly(wxEvent&) [7] wxEvtHandler::ProcessEventLocally(wxEvent&) [8] wxEvtHandler::ProcessEvent(wxEvent&) [9] wxEvtHandler::SafelyProcessEvent(wxEvent&) [10] wxWindow::GTKSendPaintEvents(_GdkRegion const*) [11] g_closure_invoke [12] g_signal_emit_valist [13] g_signal_emit [14] gtk_main_do_event [15] gdk_window_process_all_updates [16] g_main_context_dispatch [17] g_main_loop_run [18] gtk_main [19] wxGUIEventLoop::DoRun() [20] wxEventLoopBase::Run() [21] wxAppConsoleBase::MainLoop() [22] wxEntry(int&, wchar_t**) [23] main [24] __libc_start_main [25] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451175/+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 1451174] [NEW] hugin 2015.0.0-beta1 throws ASSERT INFO; format specifier doesn't match argument type When removing controllpoints in masks
Public bug reported: When using the Edit -> Remove control points in masks menu entry, the following ASSERT is thrown ASSERT INFO: /usr/include/wx-3.0/wx/strvararg.h(451): assert "(argtype & (wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type BACKTRACE: [1] MainFrame::OnRemoveCPinMasks(wxCommandEvent&) [2] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) 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] wxWindowBase::TryAfter(wxEvent&) [9] wxEvtHandler::SafelyProcessEvent(wxEvent&) [10] wxMenuBase::SendEvent(int, int) [11] g_closure_invoke [12] g_signal_emit_valist [13] g_signal_emit [14] gtk_widget_activate [15] gtk_menu_shell_activate_item [16] g_closure_invoke [17] g_signal_emit_valist [18] g_signal_emit [19] gtk_propagate_event [20] gtk_main_do_event [21] g_main_context_dispatch [22] g_main_loop_run [23] gtk_main [24] wxGUIEventLoop::DoRun() [25] wxEventLoopBase::Run() [26] wxAppConsoleBase::MainLoop() [27] wxEntry(int&, wchar_t**) [28] main [29] __libc_start_main [30] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter ** 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/1451174 Title: hugin 2015.0.0-beta1 throws ASSERT INFO; format specifier doesn't match argument type When removing controllpoints in masks Status in Hugin - Panorama Tools GUI: New Bug description: When using the Edit -> Remove control points in masks menu entry, the following ASSERT is thrown ASSERT INFO: /usr/include/wx-3.0/wx/strvararg.h(451): assert "(argtype & (wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer(): format specifier doesn't match argument type BACKTRACE: [1] MainFrame::OnRemoveCPinMasks(wxCommandEvent&) [2] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) 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] wxWindowBase::TryAfter(wxEvent&) [9] wxEvtHandler::SafelyProcessEvent(wxEvent&) [10] wxMenuBase::SendEvent(int, int) [11] g_closure_invoke [12] g_signal_emit_valist [13] g_signal_emit [14] gtk_widget_activate [15] gtk_menu_shell_activate_item [16] g_closure_invoke [17] g_signal_emit_valist [18] g_signal_emit [19] gtk_propagate_event [20] gtk_main_do_event [21] g_main_context_dispatch [22] g_main_loop_run [23] gtk_main [24] wxGUIEventLoop::DoRun() [25] wxEventLoopBase::Run() [26] wxAppConsoleBase::MainLoop() [27] wxEntry(int&, wchar_t**) [28] main [29] __libc_start_main [30] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451174/+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 1451172] [NEW] hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask
Public bug reported: In hugin 2015.0.0-Beta1, when deleting a mask, the following is thrown ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter ** 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/1451172 Title: hugin 2015.0.0-beta1 throws ASSERT INFO; invalid list ctrl item index in SetItem when deleteing a mask Status in Hugin - Panorama Tools GUI: New Bug description: In hugin 2015.0.0-Beta1, when deleting a mask, the following is thrown ASSERT INFO: ../src/generic/listctrl.cpp(3367): assert "litem >= 0 && (size_t)litem < GetItemCount()" failed in SetItemState(): invalid list ctrl item index in SetItem BACKTRACE: [1] wxGenericListCtrl::SetItemState(long, long, long) [2] MaskEditorPanel::panoramaImagesChanged(HuginBase::Panorama&, std::set, std::allocator > const&) [3] HuginBase::Panorama::changeFinished(bool) [4] PanoCommand::PanoCommand::execute() [5] PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, bool) [6] MaskEditorPanel::OnMaskDelete(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] wxWindowBase::TryAfter(wxEvent&) [16] wxWindowBase::TryAfter(wxEvent&) [17] wxEvtHandler::SafelyProcessEvent(wxEvent&) [18] g_signal_emit_valist [19] g_signal_emit [20] g_closure_invoke [21] g_signal_emit_valist [22] g_signal_emit [23] g_closure_invoke [24] g_signal_emit_valist [25] g_signal_emit [26] gtk_propagate_event [27] gtk_main_do_event [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] main [36] __libc_start_main [37] _start This is under Ubuntu 14.04 LTS using 2015.0.0~beta1+dfsg-0ubuntu2~trusty from https://launchpad.net/~hugin/+archive/ubuntu/next. Please note that this version already has 6903:aace4a6969bc : Fixes a further assert message and 6904:213b546a477e: Fixes crash in cp editor [1449065] applied With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1451172/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi Kay On 29.04.2015 22:08, KFJ wrote: > Okay, I did something else. I hg pulled and upped, rebuilt, and all > seems fine now with the latest modifications applied. I can't reproduce > the error any more, so I suppose the problem is solved with the api max > updates. I noticed the two example plugins are still unmodified; I > recommend setting their api max as well, as by my patch. +1 > I still propose > removing the api min and max check code to prevent this problem from > reoccuriung every year. Does anyone feel the api check is really needed? > Yes, I do. In the future, the developers may want to be able to change the API/exposed functionality/whatever of the script interface. Unless we have a way to determine if a script should be runnable under a certain hugin version, there is no way to retire a script and replace it with an adapted heir. This is the stuff support nightmares are made of! Regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi As a side not, I am in the progress to revive the nightly builds in https://launchpad.net/~hugin/+archive/ubuntu/nightly I hope that this will give a wider exposure of the bleeding edge code to users not being able or not willing to compile from source. I really expect that this will enable us to catch such issues in an earlier stage by opening the development version to a wider audience. Kay, I let you know when you can download an ubuntu version of the latest (and greatest) hugin version. Cheers Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi Kay With what binary do you see this? How can I reproduce this? With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: New Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi Kay I share your frustration regarding the handling of the python scripting interface, However, I feel that you take a too dire look at it: We have released a beta1 and the one of the very _first_ official bug reports brought this issue to the front. So, I conclude that here are people in the hugin community who would dearly miss your python scripts. > I suppose I can live with a broken plugin every once in a while, and noone apart from me has ever written another plugin anyway. Yeah, I would have submitted a script myself if i had found a missing functionality. Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: New Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi Terry For the records, I have attached the patch I intend to use for the ubuntu packages of 2015.0-beta1. Please note that this patch only enables python scripting for 2015.0. With kind regards Stefan Peter ** Patch added: "Re-enabling python scripts by setting the api-max values in the scripts to 2015.0" https://bugs.launchpad.net/hugin/+bug/1448816/+attachment/4386573/+files/0004-Re-enabling-python-scripts-by-setting-the-api-max-va.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/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: New Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
On 27.04.2015 17:16, tmodes wrote: >> The .py modules mentioned shold be changed to have >> # @api-max 2015.0 >> instead of >> # @api-max 2014.1 > > I know. But it would be nice if someone could test the scripts and > report back if there are still running. (I never used them so I can not > judge if they are still okay.) I can not judge, either. But api-max was set to 2014.1, so I assume that these scripts were activated in the development version. I'd expect that a breakage would have been noticed there. > > Currently it seems that woa is currently not running, so for woa we can > not update the api-max. Only when the issue is fixed we need to update > api-min *and* api-max for woa then. > If this is true, it seems that no one cared during the development cycle then. Wouldn't it be more honest to axe woa if nobody gives a damn? Regards Stefan Peter -- Any technology that does not appear magical is insufficiently advanced." ~ Gregory Benford -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: New Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu
Hi tduell No, this seems to be because the version number has changed from 2014 to 2015. If you start hugin from the command line, you will notice: /usr/share/hugin/data/plugins/crop_cp.py CAT:Control Points NAM:Crop Control Points fails @api-max /usr/share/hugin/data/plugins/top_five.py CAT:Control Points NAM:keep 5 CPs per image pair fails @api-max /usr/share/hugin/data/plugins/woa.py CAT:Control Points NAM:Warped Overlap Analysis fails @api-max /usr/share/hugin/data/plugins/shooting_pattern.py CAT:initial distribution NAM:6-1-1 Shooting Pattern fails @api-max The .py modules mentioned shold be changed to have # @api-max 2015.0 instead of # @api-max 2014.1 Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1448816 Title: hugin-2015.0.0_beta1 has no 'Actions' menu Status in Hugin - Panorama Tools GUI: New Bug description: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of 2014.1.0 did return an error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1448816/+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 678513] Re: hugin crashes every time stitching high quality tiff
On 11.11.2014 18:12, Can wrote: > i am having the same problem. Hugin types lots of thing and gives me > error > Sorry, but this does not help. We need some additional information like o What operating system you use o What Hugin version you are using o Where did you get your Hugin version from o What exactly these "lots of things and error" are (verbatim!) o A project file in order to reproduce the problem. You may have seen that the state of this error report is "Fix Released". So your problem may already be fixed. But without further information, we can't help- Regards Stefan Peter -- "In summary, I think you are trying to solve a problem that may not need to be solved, using a tool that is not meant to solve it, without understanding what is causing your problems and without knowing how the tool actually works in the first place :)" Jeffrey J. Kosowsky on the backuppc mailing list -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678513 Title: hugin crashes every time stitching high quality tiff Status in Hugin - Panorama Tools GUI: Fix Released Bug description: as in top. everytime I try to create a high quality tiff pano it crash at around 1kb of first tiff image. doesn't give any error messages except this: $ /c/Program\ Files/hugin/nona_gui.exe Panorama obj created output image size: 2797x1398 export alpha factor: 1 this happens every single time. build from cvs from this morning To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/678513/+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 1361343] Re: Ubuntu 14.10, no automatic control points
** 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/1361343 Title: Ubuntu 14.10, no automatic control points Status in Hugin - Panorama Tools GUI: Invalid Bug description: No automatic control points any more (it worked under Ubuntu 12). I now always have to add them manually, even for "obvious" and easy panoramas. Système d'exploitation : Linux 3.16.0-10-generic i686 Architecture : 32 bits Mémoire libre : 467876 kio Hugin Version : 2014.0.0.45cf4a3e9573 Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Chemin vers la base de données lensfun de l'utilisateur : /home/maurice/.local/share/lensfun Bibliothèques wxWidgets: 3.0.1.0 libpano13: 2.9.19 Boost: 1.55.0 Exiv2: 0.24.0 Lensfun: 0.2.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1361343/+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 1361343] [NEW] Ubuntu 14.10, no automatic control points
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Maurice Am 26.08.2014 um 22:17 schrieb Maurice Clerc: > Sorry, my mistake. I did it now, and it indeed works. Great! BTW, RC4 versions for 14.10 are available now at https://launchpad.net/~hugin/+archive/ubuntu/next/+packages > Many thanks for your help and patience! > > Maurice Clerc > With kind regards Stefan Peter - -- In theory there is no difference between theory and practice. In practice there is. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJT/ap4AAoJEBgqi52L7+L/L0sIAIUIf71BoHRM2FS+j81IJdyH kWIpYkaRdsoZ71vLg+Ye+S03AZsGdCNFb8ZPPoyyOjPRKV36pUauFF3fd0VUkouv njMjpyE/shaOE/yGliI2xoIeT4SBDUu/lj85QTEqsriuzQZky9Wp9m557mOoa8ME rM/HIC2ar6Dpv6wfdYOeA9H0JT/+fDSQwsYtC+yDYY6FJYZoQj1hnEIRAseGsHeg 2n1dhAoP6vH56x/OJ56Z7JJ1KuYHSn92nNNR0rjQsUDkQQsA4HbuBOLp8aR4Ekbn b6PUchAe72uDhdxU/vJCdFo9zq3U6UNgc9DhoGCNrjKJp3ObN6uSsQTx56NAbXM= =k0Ny -END PGP SIGNATURE- -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1361343 Title: Ubuntu 14.10, no automatic control points Status in Hugin - Panorama Tools GUI: New Bug description: No automatic control points any more (it worked under Ubuntu 12). I now always have to add them manually, even for "obvious" and easy panoramas. Système d'exploitation : Linux 3.16.0-10-generic i686 Architecture : 32 bits Mémoire libre : 467876 kio Hugin Version : 2014.0.0.45cf4a3e9573 Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Chemin vers la base de données lensfun de l'utilisateur : /home/maurice/.local/share/lensfun Bibliothèques wxWidgets: 3.0.1.0 libpano13: 2.9.19 Boost: 1.55.0 Exiv2: 0.24.0 Lensfun: 0.2.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1361343/+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 1361343] [NEW] Ubuntu 14.10, no automatic control points
On 26.08.2014 18:11, Maurice Clerc wrote: > Le 26/08/2014 16:41, Stefan Peter a écrit : >> Am 26.08.2014 um 15:39 schrieb Maurice Clerc: >>>> Which control point detector do you use? Have you reset the >>>> preferences in hugin after installing RC3? You are aware of the fact >>>> that autopano-sift-c is not shipped anymore with the newer releases? >>> As I am not an expert, I did not change any value, and everything is by >>> default. >> No, if you upgraded from an older version, the old program settings are >> still around. Especially the settings for the control point detectors >> can not reliably be checked by Hugin. Therefore, Hugin pops up this >> warning when older settings are encountered and asks you to reset the >> settings to their (eventually new) default settings. You can avoid a lot >> of head scratching, swearing and (in your case) manual labor if you >> follow this advice!! > > I never have seen this advice. >> >> >>> I checked: Autopano -SHIFT (not Autopano-SHIFT-C). >> I bet if you change this to "Hugin's CPFind" it will work. > I do not see this choice. I have > Autopano-SHIFT(valeur par défaut) (BTW, it seems it should be SIFT) > Autopano-SHIFT-C > Panomatic > Match-n-shift > Align Image stack This is because you did not (yet) follow my urge to load the default preferences for the CPDs. > However, cpfind does exist on my computer (command line is possible). So > I added it in Hugin: > Program: /usr/bin/cpfind > Parameters: --celeste -o %o %i > and set it as the default choice. > But even like that, no control points are generated. Do you really know what you entered here? None of the default cpfind related CPD entries resemble what you used. If you really are that reluctant to loose your old settings, you can preserve them for later reference: o Close all Hugin apps o Open a terminal window on your home directory o Issue "mv .hugin .hugin.old" o Restart hugin o Re-create your project in Hugin The .hugin settings file is a normal text file you can open with any decent text editor (but you never should attempt to do changes using a text editor there). But you can easily spot the differences between the old and the new version and, if you really must, can copy back the .hugin.old to .hugin to get back to your old (non-working) settings. BTW, I got 12 CPs from the two images you attached to this bug report using the default Hugin's cpfind and, after optimization, I got a solution with average control point distance: 1.012091 standard deviation: 0.738920 maximum: 2.263629 Nice pics, BTW. > I completely removed Hugin, then reinstalled it from the Ubuntu Software > Center (version RC3). > Still the same problem. The problem are your outdated settings, not Hugin. And removing Hugin will *not* remove these settings. You either have to reload them from defaults, or, much easier, delete the .hugin file in your home directory. Hugin will recreate this file using the new defaults upon the next start up of Hugin. Regards Stefan Peter -- "In summary, I think you are trying to solve a problem that may not need to be solved, using a tool that is not meant to solve it, without understanding what is causing your problems and without knowing how the tool actually works in the first place :)" Jeffrey J. Kosowsky on the backuppc mailing list -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1361343 Title: Ubuntu 14.10, no automatic control points Status in Hugin - Panorama Tools GUI: New Bug description: No automatic control points any more (it worked under Ubuntu 12). I now always have to add them manually, even for "obvious" and easy panoramas. Système d'exploitation : Linux 3.16.0-10-generic i686 Architecture : 32 bits Mémoire libre : 467876 kio Hugin Version : 2014.0.0.45cf4a3e9573 Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Chemin vers la base de données lensfun de l'utilisateur : /home/maurice/.local/share/lensfun Bibliothèques wxWidgets: 3.0.1.0 libpano13: 2.9.19 Boost: 1.55.0 Exiv2: 0.24.0 Lensfun: 0.2.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1361343/+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 1361343] [NEW] Ubuntu 14.10, no automatic control points
Am 26.08.2014 um 15:39 schrieb Maurice Clerc: >> Which control point detector do you use? Have you reset the >> preferences in hugin after installing RC3? You are aware of the fact >> that autopano-sift-c is not shipped anymore with the newer releases? > As I am not an expert, I did not change any value, and everything is by > default. No, if you upgraded from an older version, the old program settings are still around. Especially the settings for the control point detectors can not reliably be checked by Hugin. Therefore, Hugin pops up this warning when older settings are encountered and asks you to reset the settings to their (eventually new) default settings. You can avoid a lot of head scratching, swearing and (in your case) manual labor if you follow this advice!! > I checked: Autopano -SHIFT (not Autopano-SHIFT-C). I bet if you change this to "Hugin's CPFind" it will work. Unless you compiled it yourself for your shiny new system, chances are dim that you sill have a usable autopano-sift on your system. You can try this from the command line, if you don't believe me. Just enter "autopano" and then press twice. With kind regards Stefan Peter -- In theory there is no difference between theory and practice. In practice there is. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1361343 Title: Ubuntu 14.10, no automatic control points Status in Hugin - Panorama Tools GUI: New Bug description: No automatic control points any more (it worked under Ubuntu 12). I now always have to add them manually, even for "obvious" and easy panoramas. Système d'exploitation : Linux 3.16.0-10-generic i686 Architecture : 32 bits Mémoire libre : 467876 kio Hugin Version : 2014.0.0.45cf4a3e9573 Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Chemin vers la base de données lensfun de l'utilisateur : /home/maurice/.local/share/lensfun Bibliothèques wxWidgets: 3.0.1.0 libpano13: 2.9.19 Boost: 1.55.0 Exiv2: 0.24.0 Lensfun: 0.2.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1361343/+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 1361343] [NEW] Ubuntu 14.10, no automatic control points
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Maurice Am 26.08.2014 um 11:05 schrieb Maurice Clerc: > I use the latest version available on the Ubuntu Software Centre. > On http://hugin.sourceforge.net/ I see only the 2013 version. Did this version work for you? > > So I tried this > > sudo add-apt-repository ppa:hugin/hugin-builds sudo apt-get update > > but got the error message > http://ppa.launchpad.net/hugin/hugin-builds/ubuntu/dists/utopic/main/binary-i386/Packages > 404 Not Found > > > Where can I find and download the 2014.0.0-RC4 version for Ubuntu 14.10? > Release canditates normally can be found in the "next Hugin builds" repository of the "Hugin PPA Packagers" team lauchpad site at https://launchpad.net/~hugin/+archive/ubuntu/next However, due to the fact that 14.10 was not in shape whe RC4 was crafted, no RC4 version for 14.10 exists there yet. I probably will have another go at it this evening. However, I have serious doubts that RC4 will fix your issues. At least the published changes do not mention the control point detection. Which control point detector do you use? Have you reset the preferences in hugin after installing RC3? You are aware of the fact that autopano-sift-c is not shipped anymore with the newer releases? With kind regards Stefan Peter - -- In theory there is no difference between theory and practice. In practice there is. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJT/Ga/AAoJEBgqi52L7+L/6OwH/1JiFpd0/61duUaav/vV5sI5 Ds6Er7KX9ksarKAVSsds+wFaq0glluZFWILyDo6jMjxDuJ4xV4AkCEqQcHHDdTtn ZN5q88YoUbFQlrugXuuhjKTl2l6Xm3a1byRtt0dgyEkCZY/lZhlsAUlppxi3JDSO VbehVuE+/2Cq3vA0rcVGlRxKjVOaBJEV+sVg4yLK4PNZqc8/95oXAaAkF6glVYrv j/KSBwf3StYoBwX2/LImOy9xvb8pMiAmaEfTf5lrJOY+WqOtI/yhGeHd4L1cwJ5S qm47mV1CcfZ3d7L+UoIXOU8jW2+R1O7vCe8uOgOpcItWVM67bxeOGxNk5S39rnI= =MR9n -END PGP SIGNATURE- -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1361343 Title: Ubuntu 14.10, no automatic control points Status in Hugin - Panorama Tools GUI: New Bug description: No automatic control points any more (it worked under Ubuntu 12). I now always have to add them manually, even for "obvious" and easy panoramas. Système d'exploitation : Linux 3.16.0-10-generic i686 Architecture : 32 bits Mémoire libre : 467876 kio Hugin Version : 2014.0.0.45cf4a3e9573 Chemin vers les ressources : /usr/share/hugin/xrc/ Chemin vers les données : /usr/share/hugin/data/ Chemin vers la base de données lensfun de l'utilisateur : /home/maurice/.local/share/lensfun Bibliothèques wxWidgets: 3.0.1.0 libpano13: 2.9.19 Boost: 1.55.0 Exiv2: 0.24.0 Lensfun: 0.2.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1361343/+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 1324024] Re: Stitching failed, but all control points are correct
This seems to be a known problem in enblend, see https://bugs.launchpad.net/enblend/+bug/1228601. Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1324024 Title: Stitching failed, but all control points are correct Status in Hugin - Panorama Tools GUI: New Bug description: Hi, i work with a Mac 10.7.3. All control points are OK. I can make some panoramas but sometimes it bug at the moment to stitch. All control points are OK but when i try to stitch it fail and it report this: Output options === Hugin Version: 2013.0.0 built by Matthieu DESILE Project file: /var/folders/82/634w11nd1kl3vrd5hgfv0cwcgp/T/huginpto_2GEnzh Output prefix: DSCF5983 - DSCF5989 Projection: Cylindrical (1) Field of view: 203 x 63 Canvas dimensions: 4140 x 1432 Crop area: (4,21) - (4134,1349) Output exposure value: -0.05 Output stacks minimum overlap: 0.700 Output layers maximum Ev difference: 0.50 Selected outputs Normal panorama * Blended panorama === Input images === Number of images in project file: 4 Number of active images: 4 Image 0: /Volumes/Perso/Photos - Vidéos/20140324 - Chili/Pano/Laguna verde 3/DSCF5983.tif Image 0: Size 2496x1664, Exposure: 0.00 Image 1: /Volumes/Perso/Photos - Vidéos/20140324 - Chili/Pano/Laguna verde 3/DSCF5985.tif Image 1: Size 2496x1664, Exposure: -0.14 Image 2: /Volumes/Perso/Photos - Vidéos/20140324 - Chili/Pano/Laguna verde 3/DSCF5987.tif Image 2: Size 2496x1664, Exposure: -0.19 Image 3: /Volumes/Perso/Photos - Vidéos/20140324 - Chili/Pano/Laguna verde 3/DSCF5989.tif Image 3: Size 2496x1664, Exposure: 0.12 === Testing programs === Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === /Applications/Hugin/PTBatcherGUI.app/Contents/MacOS/nona -z LZW -r ldr -m TIFF_m -o DSCF5983\ -\ DSCF5989 -i 0 /var/folders/82/634w11nd1kl3vrd5hgfv0cwcgp/T/huginpto_2GEnzh /Applications/Hugin/PTBatcherGUI.app/Contents/MacOS/nona -z LZW -r ldr -m TIFF_m -o DSCF5983\ -\ DSCF5989 -i 1 /var/folders/82/634w11nd1kl3vrd5hgfv0cwcgp/T/huginpto_2GEnzh /Applications/Hugin/PTBatcherGUI.app/Contents/MacOS/nona -z LZW -r ldr -m TIFF_m -o DSCF5983\ -\ DSCF5989 -i 2 /var/folders/82/634w11nd1kl3vrd5hgfv0cwcgp/T/huginpto_2GEnzh /Applications/Hugin/PTBatcherGUI.app/Contents/MacOS/nona -z LZW -r ldr -m TIFF_m -o DSCF5983\ -\ DSCF5989 -i 3 /var/folders/82/634w11nd1kl3vrd5hgfv0cwcgp/T/huginpto_2GEnzh /Applications/Hugin/PTBatcherGUI.app/Contents/MacOS/enblend --compression=NONE -f4130x1328+4+21 -o DSCF5983\ -\ DSCF5989.tif -- DSCF5983\ -\ DSCF5989.tif DSCF5983\ -\ DSCF59890001.tif DSCF5983\ -\ DSCF59890002.tif DSCF5983\ -\ DSCF59890003.tif enblend: info: loading next image: DSCF5983 - DSCF5989.tif 1/1 enblend: info: loading next image: DSCF5983 - DSCF59890001.tif 1/1 terminate called after throwing an instance of 'std::runtime_error' what(): Minimizer1D::set_bracket: minimum not bracketed To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1324024/+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 1330047] Re: Cannot Import jpegs from Darktable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Roland Am 18.06.2014 15:41, schrieb Roland Schuller: > @Stefan Peter > > The Output lookes good. I Tried to export the Jpegs from Darktable > with 100% -> Same Result. I have used Darktable 1.4.2 to convert your NEF files to jpeg using default settings: My jpegs are between 15 and 20 MBytes, compared to your 3.5 to 4.8 MBytes. Obviously this size difference can not be explained by different compression settings. While trying to find out what the difference between yoour and my DT jpgs may be, I noticed that your jpgs have been exported using your screens color profile instead of sRGB or AdobeRGB. I could not verify that this is the cause of the size difference because using my screen profile creates slightly larger jpgs than using sRGB, but my screen is calibrated. Can you try to export your NEFs using sRGB or AdobeRGB and give them a try? Other than that, I fear that we can not really help you. It actually *is* possible to create a panorama using your DT jpgs, as I have proven, although some manual intervention was required. So there is no bug we could fix, as far as I see. Regards Stefan Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJToq/IAAoJEBgqi52L7+L/5PAH/1S2IoEGtFz0YSa1MzCoXnKL uVhbAN0Qf9vUL8Ev/CrsohX1HftDug444eUoTzYbeJK4u1FNccLU7mwx0aQR/pVI 4/bsVlskQgX0X2+L0AApfQ2FEIagb9WR/nbHVIaW0pDVYUdLYRER08vq9RzkpM5v CxAd5IB4Blxj+nt7M9f1y2vw21ehm5z7SRZMKNhWK3Qn9+oXP1c645wb5LR0a8qa dblj1R2P8h70IVUoiVF9AZnZhnZHCbqUpNdoafW+83+Xfjq8110fl2nfs/LfBP6Q sP5USBUtfF2iwF2aAx/Xipa8FPTWI9wE9TpPdwFwW/8RTiZ9nACZeDcqO+6eh2c= =lAs4 -END PGP SIGNATURE- -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1330047 Title: Cannot Import jpegs from Darktable Status in Hugin - Panorama Tools GUI: New Bug description: I use my Nikon D610 with an Panorama Head for 360 Panos. I shoot with RAW+JPEG (FIne) When I try to stitch the Jpegs everything is Ok. Average error so around 2 - 6. But when I take the Jpegs form Darktable (NEF Raw just with Brighness correction, no Distortion correction) then it is not possible to stich them . Either it does not find where the Image belongs to or when I works the Preview an the Result are a complete mess. When I directly convert the Images using DCRAW to 16 Bit Tiff it works. Filed a Bug in Darktable, but they said that i should contact you. I'm a Photografer working on Linux. Plese help me to finish my Workflow. Thanx Hugin 2014.0.0.45cf4a3e9573 Debian Testing 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1330047/+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 1330047] Re: Cannot Import jpegs from Darktable
Hi Roland Interestingly the Darktable jpgs have less information that the original ones: -rwx-- 1 stefan stefan 15270635 Jun 8 12:30 Orig Jpeg/DSC_8317.JPG vs -rwxrwxr-x 1 stefan stefan 3777924 Jun 16 08:30 Darktable RAW2JPEG/DSC_8317.jpg Therefore, the control point detector finds less connections between the images and they are of lesser quality. From your ptos: OrigJpg.pto: Images are connected by 811 control points, Mean error after optimisation: 3.2 pixels, max 11.1. Good fit Darktable Jpegs - Fail.pto: Images are connected by 617 control points, Mean error after optimisation: 41.0 pixels, max 3945.2. Very bad fit As a result, this project has failed to stitch with the dreaded "Excessive overlap detected" error message. I have attempted a stitch with hugin 2014.0 RC2. After deleting the outlier points (distance > 30) and re-optimizing for "Positions and View", I got 495 control points, a mean error of 7.3 and max distance of 31.9 which is still a bad fit. However, the project did stitch (see http://hugin.stepet.ch). To summarize: I can see no specific problem with jpgs from Darktable and Hugin. But your Darktable images seem to miss some information which influences the control point detector negatively. Maybe you need to add some sharpening? Some contrast? With kind regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1330047 Title: Cannot Import jpegs from Darktable Status in Hugin - Panorama Tools GUI: New Bug description: I use my Nikon D610 with an Panorama Head for 360 Panos. I shoot with RAW+JPEG (FIne) When I try to stitch the Jpegs everything is Ok. Average error so around 2 - 6. But when I take the Jpegs form Darktable (NEF Raw just with Brighness correction, no Distortion correction) then it is not possible to stich them . Either it does not find where the Image belongs to or when I works the Preview an the Result are a complete mess. When I directly convert the Images using DCRAW to 16 Bit Tiff it works. Filed a Bug in Darktable, but they said that i should contact you. I'm a Photografer working on Linux. Plese help me to finish my Workflow. Thanx Hugin 2014.0.0.45cf4a3e9573 Debian Testing 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1330047/+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
On 06.05.2014 21:33, tmodes 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? I'd give it a week or two more and see what else may be cropping up. There is no reason to hasten the 2014.0 final release, we still have a couple of months until 2015 ;) >From a supporter POV, I'd like to have a bug like this fixed, though. Regards Stefan Peter -- 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 1302564] Re: Jpeg files created with the panorama tool are correctly read and displayed by digikam but are wrong and are not readable by other softwares
eog, the gnome image viewer, fails with Could not load image '201403_0444-201403_0442.jpg'. Error interpreting JPEG image file (Suspension not allowed here). The only other mentioning of this error wrt hugin I could find was here: https://groups.google.com/d/msg/hugin-ptx/9nRJ1VUMnYU/qsXZ6CYs2QYJ Unfortunately, a fix for this error is not deducable from this conversation. However, it seems to point to enfuse/enblend and vigra impex as the culprits. The error is not repoducable under ubuntu 13.10 (amd64) and hugin 2014.0.0 RC1. However, the source images have been recreated with ptodummy for this test. I will try this on a stock 13.10 this evening if time permits. Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1302564 Title: Jpeg files created with the panorama tool are correctly read and displayed by digikam but are wrong and are not readable by other softwares Status in Hugin - Panorama Tools GUI: New Bug description: When creating panorama, I get nice files (.jpg) that I can display and manipulate with Digikam. However, this files seems to have a problem, and they can not be read outside Digikam. I tried to send them to other users, and they can not read them etheir. It seems that gnview can read them, but not Firefox, neither most of windows programs. Ubuntu can not create miniatures, and the default Ubuntu image display software can not open them either. Something seems to be wrong in the file format. Reproducible: Always Steps to Reproduce: 1. Create a panorama 2. Save it I'm using the latest stable Hugin release, under Ubuntu 13.10. See the attached jpg file as an example. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1302564/+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 1192643] [NEW] Cmake error
Dear Lesnake. On 19.06.2013 19:41, Lesnake wrote: > Public bug reported: > > cmake fails to finish with 3 errors. ... > -- Found PythonInterp: /usr/bin/python (found version "2.7.4") > -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found > suitable version "2.7.4", minimum required is "2.7.4") > CMake Error at CMakeLists.txt:324 (FILE): > file STRINGS file > > "/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7/patchlevel.h" > cannot be read. ... This is a bug in 2013.0-beta1 which already is fixed in the hugin svn. A patch for beta1 can be found at http://patch-tracker.debian.org/patch/series/view/hugin/2013.0.0~beta1+dfsg-3/50_9928ad3bd989_python_multiarch.diff With kind regards Stefan Peter -- In theory there is no difference between theory and practice. In practice there is. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1192643 Title: Cmake error Status in Hugin - Panorama Tools GUI: New Bug description: cmake fails to finish with 3 errors. Here is my setup : - ubuntu 13.04 64 bits freshly installed - cmake version 2.8.10.1 -Python 2.7.4 (default, Apr 19 2013, 18:28:01) [GCC 4.7.3] on linux2 The command line : cmake ../hugin-2013.0.0 How it ends : -- Found PythonInterp: /usr/bin/python (found version "2.7.4") -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.4", minimum required is "2.7.4") CMake Error at CMakeLists.txt:324 (FILE): file STRINGS file "/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7/patchlevel.h" cannot be read. CMake Error at CMakeLists.txt:327 (FILE): file STRINGS file "/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7/patchlevel.h" cannot be read. CMake Error at CMakeLists.txt:331 (FILE): file STRINGS file "/usr/include/python2.7;/usr/include/x86_64-linux-gnu/python2.7/patchlevel.h" cannot be read. CMake Error at CMakeLists.txt:350 (IF): if given arguments: "EQUAL" "3" "AND" "GREATER" "1" Unknown arguments specified -- Configuring incomplete, errors occurred! Logging files contains no information related to python, only CMakeCache.txt (attached). I had the same bug building 2012.0.0 (but successfully built it with 12.04) My first bug report. Regards Lesnake To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1192643/+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 1184375] [NEW] make check fails under Ubuntu 13.04 x86_64
Public bug reported: all checks fail under Ubuntu 13.04 x86_64 due to a segmentation fault in PTmender. The two patches attached fix this. With kind regards Stefan Peter ** Affects: panotools Importance: Undecided Status: New ** Patch added: "fix errors caused by (u)int32_t types under x86_64" https://bugs.launchpad.net/bugs/1184375/+attachment/3687179/+files/fix_int32_issues_for_x86_64.patch -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Panotools. https://bugs.launchpad.net/bugs/1184375 Title: make check fails under Ubuntu 13.04 x86_64 Status in Panorama Tools: New Bug description: all checks fail under Ubuntu 13.04 x86_64 due to a segmentation fault in PTmender. The two patches attached fix this. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/panotools/+bug/1184375/+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 1178194] [NEW] make test fails for all psd related tests in 2.9.19
Public bug reported: This has been detected wile trying to do a nightly build of ubuntu packages for the upcomming libpano13-2.9.19 release: make test yelds the following: Running tests... Test project /home/stefan/src/launchpad/libpano/libpano.test Start 1: simpleStitch 1/8 Test #1: simpleStitch Passed0.27 sec Start 2: simpleTiff16 2/8 Test #2: simpleTiff16 Passed0.29 sec Start 3: simpleTiff2psd-1-layer 3/8 Test #3: simpleTiff2psd-1-layer ..***Failed0.02 sec Start 4: simpleTiff2psd-2-layers 4/8 Test #4: simpleTiff2psd-2-layers .***Failed0.02 sec Start 5: simpleTiff2psd-1-layer-uncropped 5/8 Test #5: simpleTiff2psd-1-layer-uncropped ***Failed0.03 sec Start 6: simpleTiff2psd-2-layers-uncropped 6/8 Test #6: simpleTiff2psd-2-layers-uncropped ...***Failed0.03 sec Start 7: simpleTiff16-16bit-1-layer 7/8 Test #7: simpleTiff16-16bit-1-layer ..***Failed0.03 sec Start 8: simpleTiff16-16bit-2-layers 8/8 Test #8: simpleTiff16-16bit-2-layers .***Failed0.03 sec 25% tests passed, 6 tests failed out of 8 Total Test time (real) = 0.73 sec The following tests FAILED: 3 - simpleTiff2psd-1-layer (Failed) 4 - simpleTiff2psd-2-layers (Failed) 5 - simpleTiff2psd-1-layer-uncropped (Failed) 6 - simpleTiff2psd-2-layers-uncropped (Failed) 7 - simpleTiff16-16bit-1-layer (Failed) 8 - simpleTiff16-16bit-2-layers (Failed) Errors while running CTest make: *** [test] Error 8 Using 'ctest -V' results in Binary files reference/simpleTiff16-16-_uncrop_2_layer.psd and tests/simpleTiff16-16-_uncrop_2_layer.psd differ error messages for the failed tests. It seems that either the references need updating or that the psd related conversions fail. With kind regards Stefan Peter ** 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/1178194 Title: make test fails for all psd related tests in 2.9.19 Status in Panorama Tools: New Bug description: This has been detected wile trying to do a nightly build of ubuntu packages for the upcomming libpano13-2.9.19 release: make test yelds the following: Running tests... Test project /home/stefan/src/launchpad/libpano/libpano.test Start 1: simpleStitch 1/8 Test #1: simpleStitch Passed0.27 sec Start 2: simpleTiff16 2/8 Test #2: simpleTiff16 Passed0.29 sec Start 3: simpleTiff2psd-1-layer 3/8 Test #3: simpleTiff2psd-1-layer ..***Failed0.02 sec Start 4: simpleTiff2psd-2-layers 4/8 Test #4: simpleTiff2psd-2-layers .***Failed0.02 sec Start 5: simpleTiff2psd-1-layer-uncropped 5/8 Test #5: simpleTiff2psd-1-layer-uncropped ***Failed0.03 sec Start 6: simpleTiff2psd-2-layers-uncropped 6/8 Test #6: simpleTiff2psd-2-layers-uncropped ...***Failed0.03 sec Start 7: simpleTiff16-16bit-1-layer 7/8 Test #7: simpleTiff16-16bit-1-layer ..***Failed0.03 sec Start 8: simpleTiff16-16bit-2-layers 8/8 Test #8: simpleTiff16-16bit-2-layers .***Failed0.03 sec 25% tests passed, 6 tests failed out of 8 Total Test time (real) = 0.73 sec The following tests FAILED: 3 - simpleTiff2psd-1-layer (Failed) 4 - simpleTiff2psd-2-layers (Failed) 5 - simpleTiff2psd-1-layer-uncropped (Failed) 6 - simpleTiff2psd-2-layers-uncropped (Failed) 7 - simpleTiff16-16bit-1-layer (Failed) 8 - simpleTiff16-16bit-2-layers (Failed) Errors while running CTest make: *** [test] Error 8 Using 'ctest -V' results in Binary files reference/simpleTiff16-16-_uncrop_2_layer.psd and tests/simpleTiff16-16-_uncrop_2_layer.psd differ error messages for the failed tests. It seems that either the references need updating or that the psd related conversions fail. With kind regards Stefan Peter To manage notifications about this bug go to: https://bugs.launchpad.net/panotools/+bug/1178194/+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 1115484] [NEW] cant upload images even with no indicated unusable symbols
On 04.02.2013 19:41, gary wrote: > Public bug reported: > > trying to use jpegs...ie IMG1609.JPG...will not accept...am i asleep? Probably. Otherwise, we would have received an error report with some facts like o what OS o what OS version o what hugin version o where did you get this hugin version from o where are you trying to load the files from o where did you get the files from o where can we download those files o what did you try to accomplish .. (sorry, couldn't resist) Regards Stefan Peter > > ** Affects: hugin > Importance: Undecided > Status: New > -- "In summary, I think you are trying to solve a problem that may not need to be solved, using a tool that is not meant to solve it, without understanding what is causing your problems and without knowing how the tool actually works in the first place :)" Jeffrey J. Kosowsky on the backuppc mailing list -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1115484 Title: cant upload images even with no indicated unusable symbols Status in Hugin - Panorama Tools GUI: New Bug description: trying to use jpegs...ie IMG1609.JPG...will not accept...am i asleep? To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1115484/+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 921215] Re: Segmentation Fault on HDR Blend
I have not been able to reproduce these problems here using your ptos on a similar machine (X86_64/4GBytes) using hugin 2011.04. However, the latest error message makes me think about bad memory in your machine. If you redo this stitch, do you get the same error every time? Did you experience other crashes with memory intensive applications? Can you install memtest86+ and give it a spin? Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/921215 Title: Segmentation Fault on HDR Blend Status in Hugin - Panorama Tools GUI: New Bug description: After, doing what appears to be everything correctly. I run the process, and the log ends up as this. It's 6 or 7 exposure different images, that I'm trying to blend into an HDR. Mainly testing purposes right now. I keep getting a Seg Fault at the last make exr step. -JAG === *** Panorama makefile generated by Hugin *** === System information === Operating system: GNU/Linux Release: 3.0.0-15-generic Kernel version: #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 Machine: x86_64 Disc usage FilesystemSize Used Avail Use% Mounted on /dev/sda1 55G 34G 19G 65% / udev 1.9G 8.0K 1.9G 1% /dev tmpfs 780M 1.1M 778M 1% /run none 5.0M 0 5.0M 0% /run/lock none 2.0G 1.7M 2.0G 1% /run/shm /dev/sdb1 466G 346G 121G 75% /media/A500 Memory usage total used free sharedbuffers cached Mem: 3895 3772122 0 10218 -/+ buffers/cache: 3544351 Swap: 4027677 3350 === Output options === Hugin Version: 2011.4.0.cf9be9344356 Project file: /tmp/huginpto_F5LgOK Output prefix: IMG_20120124_124742-IMG_20120124_124809 Projection: Rectilinear (0) Field of view: 52 x 42 Canvas dimensions: 2620 x 2062 Crop area: (62,113) - (2545,1932) Output exposure value: 14.91 Selected outputs HDR merging * Merged and blended panorama === Input images === Number of images in project file: 7 Number of active images: 7 Image 0: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124742.jpg Image 0: Size 2592x1944, Exposure: 10.84 Image 1: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124746.jpg Image 1: Size 2592x1944, Exposure: 12.01 Image 2: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124751.jpg Image 2: Size 2592x1944, Exposure: 12.97 Image 3: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124755.jpg Image 3: Size 2592x1944, Exposure: 14.12 Image 4: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124759.jpg Image 4: Size 2592x1944, Exposure: 15.87 Image 5: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124803.jpg Image 5: Size 2592x1944, Exposure: 18.77 Image 6: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124809.jpg Image 6: Size 2592x1944, Exposure: 19.77 === Testing programs === Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 0 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 1 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 2 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 3 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 4 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 5 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 6 /tmp/huginpto_F5LgOK hugin_hdrmerge -m avg -c -o IMG_20120124_124742-IMG_20120124_124809_stack_hd
[Hugin-bug-hunters] [Bug 921215] Re: Segmentation Fault on HDR Blend
Could you please post the pto causing this crash? Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/921215 Title: Segmentation Fault on HDR Blend Status in Hugin - Panorama Tools GUI: New Bug description: After, doing what appears to be everything correctly. I run the process, and the log ends up as this. It's 6 or 7 exposure different images, that I'm trying to blend into an HDR. Mainly testing purposes right now. I keep getting a Seg Fault at the last make exr step. -JAG === *** Panorama makefile generated by Hugin *** === System information === Operating system: GNU/Linux Release: 3.0.0-15-generic Kernel version: #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 Machine: x86_64 Disc usage FilesystemSize Used Avail Use% Mounted on /dev/sda1 55G 34G 19G 65% / udev 1.9G 8.0K 1.9G 1% /dev tmpfs 780M 1.1M 778M 1% /run none 5.0M 0 5.0M 0% /run/lock none 2.0G 1.7M 2.0G 1% /run/shm /dev/sdb1 466G 346G 121G 75% /media/A500 Memory usage total used free sharedbuffers cached Mem: 3895 3772122 0 10218 -/+ buffers/cache: 3544351 Swap: 4027677 3350 === Output options === Hugin Version: 2011.4.0.cf9be9344356 Project file: /tmp/huginpto_F5LgOK Output prefix: IMG_20120124_124742-IMG_20120124_124809 Projection: Rectilinear (0) Field of view: 52 x 42 Canvas dimensions: 2620 x 2062 Crop area: (62,113) - (2545,1932) Output exposure value: 14.91 Selected outputs HDR merging * Merged and blended panorama === Input images === Number of images in project file: 7 Number of active images: 7 Image 0: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124742.jpg Image 0: Size 2592x1944, Exposure: 10.84 Image 1: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124746.jpg Image 1: Size 2592x1944, Exposure: 12.01 Image 2: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124751.jpg Image 2: Size 2592x1944, Exposure: 12.97 Image 3: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124755.jpg Image 3: Size 2592x1944, Exposure: 14.12 Image 4: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124759.jpg Image 4: Size 2592x1944, Exposure: 15.87 Image 5: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124803.jpg Image 5: Size 2592x1944, Exposure: 18.77 Image 6: /media/A500/Dropbox/Dropbox/Public/Photos/hdr/2/IMG_20120124_124809.jpg Image 6: Size 2592x1944, Exposure: 19.77 === Testing programs === Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 0 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 1 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 2 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 3 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 4 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 5 /tmp/huginpto_F5LgOK nona -r hdr -m EXR_m -o IMG_20120124_124742-IMG_20120124_124809_hdr_ -i 6 /tmp/huginpto_F5LgOK hugin_hdrmerge -m avg -c -o IMG_20120124_124742-IMG_20120124_124809_stack_hdr_.exr -- IMG_20120124_124742-IMG_20120124_124809_hdr_.exr IMG_20120124_124742-IMG_20120124_124809_hdr_0001.exr IMG_20120124_124742-IMG_20120124_124809_hdr_0002.exr IMG_20120124_124742-IMG_20120124_124809_hdr_0003.exr IMG_20120124_124742-IMG_20120124_124809_hdr_0004.exr IMG_20120124_124742-IMG_20120124_124809_hd
[Hugin-bug-hunters] [Bug 907060] Re: hugin doesn't create panorama, instead gives back an error message
Hi Thomas
Neither the hugin versions nor the kernel version you mention are within the
bounds of what we handle here.
uname -a for ubuntu 11.10 is
Linux pcsp 3.0.0-15-generic #25-Ubuntu SMP Mon Jan 2 17:44:42 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
compared to your
Linux ivory 3.1.10 #1 SMP Fri Jan 20 14:33:07 CET 2012 x86_64 x86_64 x86_64
GNU/Linux
and huin versions should be
2011.0.0+dfsg-2build1
(or 2011.4.0+dfsg-0ubuntu1~oneiric if you use the package from the Hugin PPA
Packagers)
copmared to your
2011.4.0-oneiric~ppa1
Can you give me some more information regarding the source of the OS and the
packages mentioned in your error report?
And, while we're at it, is there any error message? ("doesn't work" just does
not cut it for me)
Regards
Stefan Peter
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/907060
Title:
hugin doesn't create panorama, instead gives back an error message
Status in Hugin - Panorama Tools GUI:
Fix Released
Bug description:
Opening hugin, then loading some photos to stitch together (worked
with an earlier version of hugin), clicking "Align.." starts hugin to
read the images, then trying to find matching points. After some time
passed hugin reports: "The assistant did not complete successfully.
Please check the resulting project file."
The resulting project files seem to be ok. I've attached them.
No panorama is created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/907060/+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 843742] Re: Hugin failed to output assemblage into a jpg image.
*** This bug is a duplicate of bug 720556 *** https://bugs.launchpad.net/bugs/720556 Hi Martin Thank you very much for this report. However, this bug is a duplicate of bug #720556 (https://bugs.launchpad.net/hugin/+bug/720556). It is caused by two identical images (at least hugin/enblend thinks so). In such a case, enblend aborts (rightly) with the error message enblend: warning: failed to detect any seam enblend: mask is entirely black, but white image was not identified as redundant If the images actually are identical, you can remove it from your project. However, in most cases one of the images does not have any control point assigned and therefore gets the same position as the anchor image. So please check if all images actually have several control points in your projects. Regards Stefan Peter -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/843742 Title: Hugin failed to output assemblage into a jpg image. Status in Hugin - Panorama Tools GUI: New Bug description: Hi! First of all, I would like to congratulate all the developpers of this very useful and nice program. Thank you for what you’re doing! I don’t know if this is an important bug or not, but as Hugin asked me to report it there, here I am. I was merging three images and Hugin failed to generate the output, whereas the preview seems good. I’m not sure at all, but it seems that it was a problem with my requested output (I asked Hugin to output a jpg image and not a tiff one). I don’t know if it is that or not (Hugin has already suceed in other works to output a jpg picture). Maybe there were some transparent areas left there? Nevertheless, I’m sending an archive with the problematic files as an attachment. Hoping it will be useful. Martin. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/843742/+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 843742] Re: Hugin failed to output assemblage into a jpg image.
*** This bug is a duplicate of bug 720556 *** https://bugs.launchpad.net/bugs/720556 ** This bug has been marked a duplicate of bug 720556 Blend fails with mask entirely black. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/843742 Title: Hugin failed to output assemblage into a jpg image. Status in Hugin - Panorama Tools GUI: New Bug description: Hi! First of all, I would like to congratulate all the developpers of this very useful and nice program. Thank you for what you’re doing! I don’t know if this is an important bug or not, but as Hugin asked me to report it there, here I am. I was merging three images and Hugin failed to generate the output, whereas the preview seems good. I’m not sure at all, but it seems that it was a problem with my requested output (I asked Hugin to output a jpg image and not a tiff one). I don’t know if it is that or not (Hugin has already suceed in other works to output a jpg picture). Maybe there were some transparent areas left there? Nevertheless, I’m sending an archive with the problematic files as an attachment. Hoping it will be useful. Martin. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/843742/+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 718116] Re: Opening Fast Preview Window crashes Hugin
Hi Vladimir On 25.08.2011 21:18, Vladimir Nadvornik wrote: > It looks like that boost::signals::trackable does not work at all. Even > the boost example fails for me. ... > # "OK!" should be printed just once > This is under Ubuntu Natty X86_64: stefan@nbstepet:~/src$ gcc button_click.cpp -o button_click -lboost_signals stefan@nbstepet:~/src$ ./button_click OK! stefan@nbstepet:~/src$ I got the same results under Maverick, both for 32 and 64 bits. Regards Stefan Peter -- In theory there is no difference between theory and practice. In practice there is. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/718116 Title: Opening Fast Preview Window crashes Hugin Status in Hugin - Panorama Tools GUI: Confirmed Bug description: Whenever I open the FPW, Hugin segfaults. I've attached the full backtrace of the segfault triggered by manually opening the FPW, but here are the top 19 lines (of 62): #0 0x00f7eae1 in wxWindow::DoSetSize(int, int, int, int, int) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #1 0x01072584 in wxSizerItem::SetDimension(wxPoint const&, wxSize const&) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #2 0x01072f6b in wxGridSizer::SetItemBounds(wxSizerItem*, int, int, int, int) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #3 0x010740ff in wxFlexGridSizer::RecalcSizes() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #4 0x010722d4 in wxSizer::Layout() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #5 0x01072409 in wxSizer::SetDimension(int, int, int, int) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #6 0x010725c1 in wxSizerItem::SetDimension(wxPoint const&, wxSize const&) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #7 0x01073512 in wxBoxSizer::RecalcSizes() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #8 0x010722d4 in wxSizer::Layout() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #9 0x01072409 in wxSizer::SetDimension(int, int, int, int) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #10 0x01084f55 in wxWindowBase::Layout() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #11 0x0107ee45 in wxTopLevelWindowBase::DoLayout() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #12 0x0107fd2d in wxTopLevelWindowBase::OnSize(wxSizeEvent&) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #13 0x00d3dc2f in wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const () from /usr/lib/libwx_baseu-2.8.so.0 #14 0x00ddc089 in wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) () from /usr/lib/libwx_baseu-2.8.so.0 #15 0x00ddd134 in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) () from /usr/lib/libwx_baseu-2.8.so.0 #16 0x00ddd233 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/libwx_baseu-2.8.so.0 #17 0x00fcaf65 in wxFrame::GtkOnSize() () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #18 0x00f73e03 in wxTopLevelWindowGTK::Show(bool) () from /usr/lib/libwx_gtk2u_core-2.8.so.0 #19 0x080bb5f1 in MainFrame::OnToggleGLPreviewFrame(wxCommandEvent&) () Running Ubuntu Maverick on an Intel DG45ID mobo with the G45 chipset and builtin GMA X4500HD GPU About→System says: Operating System: Linux 2.6.35-25-generic i686 Architecture: 32 bit Free memory: -1738088 kiB Hugin Version: 2010.4.0.854952d82c8f Path to ressources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/718116/+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 486303] Re: Every illegal character aren't well detected and forbidden
Am 24.03.2011 19:50, schrieb Thibault Lemaitre: > To conclude, for me, the minimal forbidden characters on Linux are: > =;:%?<>|\"$~. I would add ' and ` Regards Stefan Peter -- In theory there is no difference between theory and practice. In practice there is. -- You received this bug notification because you are a member of Hugin Bug Hunters, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/486303 Title: Every illegal character aren't well detected and forbidden Status in Hugin - Panorama Tools GUI: Fix Committed Status in “hugin” package in Ubuntu: Confirmed Bug description: Binary package hint: hugin Ubuntu 9.10n hugin version 0.8.0 : With some picture, i can load image on hugin but i can allign : Hugin crash when i try to "allign" pictures : Pop-up error : commande : autopano-complete --points 20 -o /tmp/ap_reskJ5efT "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L\\'île de Taquile.jpg" "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.49 - L\\'île de Taquile.jpg" "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.58 - L\\'île de Taquile.jpg" "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.06 - L\\'île de Taquile.jpg" "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.15 - L\\'île de Taquile.jpg" "/home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.23 - L\\'île de Taquile.jpg" a échoué avec un code erreur : 1 On the command ligne, error : MainFrame::RestoreLayoutOnNextResize() Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 2last access: 1 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 2 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 2 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.49 - L'île de Taquile.jpg CacheEntry: 1last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.49 - L'île de Taquile.jpg CacheEntry: 1last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.58 - L'île de Taquile.jpg CacheEntry: 1last access: 5 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.49 - L'île de Taquile.jpg CacheEntry: 1last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.58 - L'île de Taquile.jpg CacheEntry: 1last access: 5 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.06 - L'île de Taquile.jpg CacheEntry: 1last access: 6 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.49 - L'île de Taquile.jpg CacheEntry: 1last access: 4 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.58 - L'île de Taquile.jpg CacheEntry: 1last access: 5 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.06 - L'île de Taquile.jpg CacheEntry: 1last access: 6 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.58.15 - L'île de Taquile.jpg CacheEntry: 1last access: 7 8bit: 1 16bit: 1 float: 1 mask: 1 0x1c640d8: 20% Image: /home/roumano/Images/2008 05 Perou/Panoramique/2008-05-11--09.57.40 - L'île de Taquile.jpg CacheEntry: 3last access: 3 8bit: 1 16bit: 1 float: 1 mask: 1 Image: /home/roumano/Images/2008 05 Perou
