Thank you, works for me.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2041687
Title:
does not show/log enblend error messages
Status in Hugin:
Fix Committed
Bug description:
Hello,
Public bug reported:
Hello,
hugin does not show/log enblend errors. I think it did previously. This
is on 2023.0~beta1+dfsg-1.
This was originally reported by Michael Deegan in
https://bugs.debian.org/1054129
It is easy to reproduce by replacing enblend with a dummy-script like this one
Thank you - fix confirmed.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2037164
Title:
2023.0 beta1 assert after klick on [Stitch]
Status in Hugin:
Fix Committed
Bug description:
Hello,
Public bug reported:
Hello,
klicking Stitch! on the Stitcher tab yields assert errors like this one:
-
ASSERT INFO:
/usr/include/wx-3.2/wx/strvararg.h(484): assert "(argtype &
(wxFormatStringSpecifier::value)) == argtype" failed in wxArgNormalizer():
format specifier doesn't match
Public bug reported:
Hello,
this was originally reported in https://bugs.debian.org/1027934 hugin
2022.0.0 fails to build against flann 1.9.2 since it does not use
FLANN_LIBRARY_DIRS as set by CMakeModules/FindFLANN.cmake
~~~
[ 50%] Linking CXX executable cpfind
cd
** Bug watch added: Debian Bug tracker #1020640
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020640
** Bug watch added: github.com/nigels-com/glew/issues #321
https://github.com/nigels-com/glew/issues/321
** Bug watch added: github.com/nigels-com/glew/issues #315
On 2022-09-25 tmodes <1989...@bugs.launchpad.net> wrote:
> Hi Andreas,
> does it works now?
> How can the build instruction be more clear? Suggestions are always welcome.
[...]
Hello Thomas,
I do not think hugin can do anything about it but the EGL situation
seems to broken globally.
WX really
On 2022-09-16 tmodes <1989...@bugs.launchpad.net> wrote:
> Please test the attached patch.
[...]
That fixes the warning, thanks.
I have found a third issue. After starting up, klicking on [Preview
Panorama (OpenGL)] yields an error (and nothing else:
--
Error initializing GLEW
Fast
On 2022-09-15 Andreas Metzler <1989...@bugs.launchpad.net> wrote:
> On 2022-09-15 tmodes <1989...@bugs.launchpad.net> wrote:
>> What was the last working wxWidgets versions?
>> Was it from the 3.0.x series? If so then it is only faint related to the
>> wxWidge
On 2022-09-15 tmodes <1989...@bugs.launchpad.net> wrote:
> What was the last working wxWidgets versions?
> Was it from the 3.0.x series? If so then it is only faint related to the
> wxWidgets 3.2 version.
> It was already fixed in the repository (changeset edfddc6070ca). See also
>
Public bug reported:
Hello,
I have tried building hugin 2021.0 against wxwidgets3.2. It builds fine
(some new deprecation warnings), but the binary is non-functional. It
aborts immediately on startup, offering to save some debugging info
(attached).
cu Andreas
** Affects: hugin
On 2020-12-29 tmodes <1909...@bugs.launchpad.net> wrote:
> I can't reproduce the issue. I get no assert on Windows and also not on
> Ubuntu.
> The issue seems to stem from wxWidgets see
> http://trac.wxwidgets.org/ticket/18520 and seems to fixed up-streams
> already in the 3.1.x series.
> Could
** Bug watch added: Debian Bug tracker #978475
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978475
** Also affects: hugin (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978475
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
Hello,
starting calibrate_lens_gui generates assertion errors:
ASSERT INFO:
../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in
SetSourceSurface(): no bitmap data
BACKTRACE:
[1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour
Public bug reported:
Hugin's appstream data does not implement the current specification.
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent
It is installed in the legacy path /usr/share/appdata/ with obsolete
format (toplevel node is ).
**
FWIW I have just switched Debian's hugin binary to python 3.
As a minimal test I have tried running the included examples (after
fixing the shebang and bumping api-max). Two of them fail.
woa.py:
run python script: /usr/share/hugin/data/plugins/woa.py
hpi: accessing plugin file
tmodes wrote
> Fixed in repository.
> Please retest.
Thank you. Works for me.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1813404
Title:
2019.0 beta1 segfault on exit
Status in Hugin:
Public bug reported:
2019.0 beta1 segfaults on exit when started on a fresh system, i.e.
without preconfigured ~/.hugin et.al.
How to reproduce:
mkdir /dev/shm/ametzler-hugin-home/
chmod 0755 /dev/shm/ametzler-hugin-home/
env HOME=/dev/shm/ametzler-hugin-home hugin
[exit hugin]
Thread 1
Obviously hugin needs to be invoked as
env HOME=/dev/shm/ametzler-hugin-home hugin
This is on Debian/testing, i.e. with wx 3.0.4.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1813402
Title:
Public bug reported:
With 2019.0.0 saving recently opened files fails if ~/.local does not
already exist:
(hugin:9626): Gtk-WARNING **: 16:04:28.655: Attempting to store changes
into `/dev/shm/ametzler-hugin-home/.local/share/recently-used.xbel', but
failed: Failed to create file
On 2017-02-25 tmodes <1666...@bugs.launchpad.net> wrote:
> Fixed in repository.
> PS: For diagnosing there is the option "Copy log messages to clipboard"
> in the preferences. Then you can paste the full log of the failed step.
> ** Summary changed:
> - cpfind fails to run if custom temporary
Public bug reported:
If preferences->file name->Temporary dir is set to an non-empty value,
running from cpfind from the Assistant ([2. Align]-button]) fails. The
cpfind window pops up and closes immediately, an error message about
unconnected images is shown.
Running cpfind from the main window
Public bug reported:
enblend 4.2 has a hard dependency on (pdf)latex:
checking for perl module Time::Zone... ok
checking for latex... no
checking for elatex... no
checking for lambda... no
../configure: line 8623: WARNING:: command not found
checking for pdflatex... ../configure: line 8655:
On 2016-02-15 Christoph Spiel wrote:
> Broken compilation with gcc-6 as reported in #2 should
> be fixed in rev 73e6f16de80a.
> Dropped the dependency on `boost::assign' at the offending position;
> it did not buy us that much anyhow.
Thanks, confirmed. I got a successful
Thank you, indeed a further error as popped up:
g++-6 -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I../../include
-I../../src/layer_selection -I/usr/include/OpenEXR -g -O2
-fstack-protector-strong -Wformat
Public bug reported:
Hello,
enblend 4.1.4 FTBFS with gcc/g++ 6 (tested with snapshot 20160117):
../../include/vigra_ext/impexalpha.hxx:252:78: error: no matching function for
call to
'std::auto_ptr::auto_ptr(std::unique_ptr)'
std::auto_ptr decoder(vigra::decoder(import_info));
Hello,
I wrote: FWIW I have also tried it the other way round [...].
This side-issue seems to be already tracked in
https://bugs.launchpad.net/hugin/+bug/678808
cu Andreas
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Public bug reported:
Hello,
This is http://bugs.debian.org/786938 reported by Vangelis Skarmoutsos
against 2015.0.0 beta2:
quote
When pressing the Create control points button, a window pops up which
shows informational details of the procedure.
In this window, if some directory names are
Public bug reported:
Hello,
two of the newly added manpages in 2015.0.0 have slightly broken formatting,
the whatis entry cannot be parsed and will theefore not be included into the
apropos database. Trivial patch attached. (See also
Public bug reported:
Hello,
on Debian some of our users still see assertion errors with hugin
2014.0.0 (plus 52_044b08eb6adf_Several_fixes_to_treelistctrl.diff and
53_f88dc95914ae_Use_correct_class_wxStaticBitmap_for_bitmap_controls.diff)
either in hugin itself or in PTBatcherGUI:
in
On 2014-05-25 tmodes 1316...@bugs.launchpad.net wrote:
Okay. I was now able to reproduce the crash. It happens only if in
simple mode. In all other modes it worked. Committed a workaround
in changeset 10aa8ea89d9e. Please report back if this works. TIA.
Marvellous. Works for me, too.
I have
On 2014-05-23 tmodes 1316...@bugs.launchpad.net wrote:
Some more question, because I can't currently not reproduce the crash.
* Which wxWidgets version? (With 2.8.12 it runs fine with the test
images.)
Hello,
3.0.0
* I used the images from the original ticket. Are there some special
chars
Hello,
here is what I get with rc3 (hugin built with -O0):
[...]
[Thread 0xe5bfeb40 (LWP 12214) exited]
Error: XMP Toolkit error 203: Duplicate property or field node
Warning: Failed to decode XMP metadata.
[New Thread 0xe5bfeb40 (LWP 12215)]
ContractViolation:
Precondition violation!
Unable to
On 2014-05-17 tmodes 1318...@bugs.launchpad.net wrote:
Default branch should compile with wx 2.8 again.
After confirmation that all works again, I think this should go also in
2014.0 branch.
Thanks, 2014.0.0rc2 + 5e144ef0d7fb + 6022165a79d9 builds for me with both
wx 2.8 and 3.0 and fixes the
On 2014-05-16 tmodes 1318...@bugs.launchpad.net wrote:
Thanks for update. Could you please try if changeset 5e144ef0d7fb
fixes the issue?
(I have currently no Linux version of wxWidgets 3.0 running.)
Hello,
It fixes the crash with wx3.0, thank you. (I have tried tried
2014.0.0rc2 plus this
On 2014-05-13 tmodes 1318...@bugs.launchpad.net wrote:
I know that Hugins works fine with wxWidgets 3.0 on Windows and
MacOS (the last release was in both cases compiled with wxWidgets
3.0). So the problem is specific to the wxGTK port.
Unfortunately the back trace does not help really
Public bug reported:
Hello,
hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
against wxwidgets3.0 (instead of 2.8):
Program received signal SIGSEGV, Segmentation fault.
0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
(gdb) bt
#0
On 2014-05-06 tmodes 1316...@bugs.launchpad.net wrote:
Tried to fix in changeset 1df056cbbdd8 in default branch.
If there is a confirmation, that the bug is fixed we need a decision
how to proceed with 2014.0.
If the bug is considered as critical, it needs to ported to 2014.0.
This will need
Public bug reported:
Hello,
hugin 2014.0.0-rc2 segfaults when multiple images are loaded at once
using the simple interface ([Load Images] button on preview window.
ERROR: 19:30:12.852684
(/tmp/HUGIN/hugin-2014.0.0/src/hugin_base/huginapp/ImageCache.cpp:697)
loadImageSafely(): Error during
Hello,
I just got a similar report on Debian 2014.0 rc1
http://bugs.debian.org/741466
cu Andreas
---
Philipp Marek writes:
With Interface - Simple, clicking on _any_ tab (except the first visible,
Assistant) crashes Hugin with a segfault; please see the backtrace
Public bug reported:
Hello,
hugin fails to stitch images in a directory generated with mktemp -d if
PTBatcherGUI is used.
How to reproduce (starting without ~/.hugin):
8X--
surfonly@argenau:~$ mktemp -d
/tmp/tmp.GWy5J6KUny
surfonly@argenau:~$ cp /tmp/*JPG
Public bug reported:
Hello,
building hugin 2013.0.0 rc2 against boost 1.54 yields this warning
(compared to boost 1.53):
/usr/include/boost/signal.hpp:17:4: warning: #warning Boost.Signals is
no longer being maintained and is now deprecated. Please switch to
Boost.Signals2. To disable this
Public bug reported:
Hello,
this is http://bugs.debian.org/712997 reported by Yuri D'Elia against
2013.0.0~beta1+dfsg-3
-
I can't seem to be able to drag any image in the Move/Drag panel in any mode
(normal, mosaic or the individual combinations). This used to work some time
Hello,
please re-open this report. It has appeared again in
http://bugs.debian.org/71199.
The system in question is using intel graphics, probably with a broken
configuration. However the fact that hugin simply crashes instead of handling
the error is clearly a bug. More info below:
Hello,
I have /somehow/ succeeded with these steps:
#1 Drop geq and leq macros from auxmac.texi.
#2 Make sure any macro-reference on a macro using a conditional is on a line of
its own. (@classictimes, @semilog,
@inline*)
#3 Drop export TEXINPUTS=$(top_builddir):$(srcdir) from doc/Makefile.am
Public bug reported:
Hello,
documentation generation fails with texinfo 5.1. texinfo seems to have stopped
supporting colons in variable names (@set - @value), causing errors like this
one:
-
doc/enfuse.texi:564: bad syntax for @value
-
According to texinfo 5.1 documentation
Hello,
thanks for trying, there is still some stuff texinfo fails on. - See
attached log.
cu Andreas
** Attachment added: errors on generating enblend.info
https://bugs.launchpad.net/enblend/+bug/1181678/+attachment/3680880/+files/buildlog-hg
--
You received this bug notification because
@Logan: This bug has nothing to do with the Ubuntu packaging. Any
(semi-)official Debian/Ubuntu package of a newly enough hugin version
already ships pto_gen.
Please note that this binary is not present in latest hugin release
2011.4, which is what Ubuntu ships. Only Debian/experimental and
Thomas' seems to be correct. Updating to swig 2.0.6 fixed the issue.
Thank you!
** Changed in: hugin
Status: New = Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/999833
Title:
Public bug reported:
Hello,
hugin 2011.4.0 does not build with gcc-4.7. There is an easy to fix
error about a missing include (already tracked and patched in
https://bugs.launchpad.net/hugin/+bug/913250) however there is another
issue that I have only seen on s390 yet:
On 2012-03-06 tmodes 679...@bugs.launchpad.net wrote:
Previously Andreas wrote:
[...]
The correct fix is to only run clean after all has finished (make all
make clean). Removing MAKEFLAGS from the environment might not hurt but
should be configurable.
See also
On 2011-11-27 Bruno Postle 892...@bugs.launchpad.net wrote:
I don't see this crash on 64bit fedora 15, hugin 2011.3.0 2011-10-31
snapshot
As I tried to note in the original report this does not apply to
2011.4.0beta1. I am still forwarding this since some doublechecking
whether the issue is
Public bug reported:
On 2011.2.0 this bug is reproducible on amd64:
-
Francesco Potortì writes in http://bugs.debian.org/649171
I call calibrate_lens_gui, have it load the image at
http://fly.isti.cnr.it/tmp/hugin-bug.jpeg. I set Focal lenght
VIGRA 1.8.0 was released today. It contains the patches from hugin which
were forwarded upstream
http://comments.gmane.org/gmane.comp.video.vigra/42.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Public bug reported:
There is is a typo in cpfind's documentation. Patch against hg tip
attached.
** Affects: hugin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
On 2011-09-11 T. Modes thomas.mo...@gmx.de wrote:
Hi Andreas,
some questions to your bug report:
Have you also tried current tip? I did a change in the last week to
deactivate the tray icon. Does the mainwindow also disappear if no
stitch was started (because I don't really understand, why
Public bug reported:
With 2011.2.0 the old Stich Now! is gone, I am using PTBatcherGUI
instead.
The window handling is very annoying. The main autobatcher window and
the progress window are automatically if switch to another virtual
desktop and back again.
It would also be very nice if closing
** Attachment added: screenshot after starting a stitch
https://bugs.launchpad.net/bugs/811864/+attachment/2213175/+files/screenshot_startup.jpg
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
On 2011-06-26 Yuv 801...@bugs.launchpad.net wrote:
can you try with something along the following please? sorry I do not
have time right now to do it myself.
[...]
Hello,
seems to work with minor changes.
Comparing build logs against 2.6.7 and 3.2.1 (actually 2.6.7 with an
edited
Find attached a simple one-line-patch, selecting the V2 interface of
boost_filename. This should work up to boost 1.47 and will break with
1.48_:
http://live.boost.org/doc/libs/1_46_1/libs/filesystem/v3/doc/index.htm
Version 3 is a major revision with many new and improved
Still present in 2011.0.0 beta3. It invokes make -f /tmp/huginmk_pViQ5m
info test all clean
** Changed in: hugin
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Find attached a patch that changes hugin to use an external zthread if
available and fall back to the included copy otherwise. The code does
not do any version testing.
I think this should be a a sufficient solution for this issue. Afaiu the
big problem is not that hugin source contains a copy of
Please note that FLANN is not packaged for Debian.
http://bugs.debian.org/581903
** Bug watch added: Debian Bug tracker #581903
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581903
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
On 2011-03-07 Yuv 703...@bugs.launchpad.net wrote:
FindTclap.cmake is broken on Ubuntu. The automatic build from the Hugin
PPA reports:
-- checking for module 'tclap=1.1'
-- package 'tclap=1.1' not found
CMake Error at CMakeLists.txt:274 (MESSAGE):
Tclap library not found
for Lucid,
FWIW I have compared src/foreign/tclap with upstream releases. The copy
in src/foreign is 1.1.0 (released 2006-08-19) + two one-line changes
instead of the latest release 1.2.0 (2009-09-28).
** Patch added: upstream 1.1.0 versus included copy
works-for-me patch attached.
** Patch added: search for external tclap with pkg-cponfig
https://bugs.launchpad.net/hugin/+bug/703735/+attachment/1890075/+files/searchfortclap.diff
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
** Patch added: fix pod errorrs
https://bugs.launchpad.net/bugs/729607/+attachment/1887361/+files/fixpoderrors.diff
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/729607
Title:
perldoc
Current hugin impossible to make a reasonable screenshot of or actually
use at screenwidth below 1200.
The Cp-detector list control element takes up lots of horizontal space
(Hugins CPFind + Celeste (slower but more accurate, no cps on clouds))
and the [Create control points] button is placed
Public bug reported:
cpfind is missing a option to limit the the number of control points per
pair of images (like autopano-sift-c's --maxmatches option).
Having a large number of control points (cpfind adds 30+) increases the
amount of work to get rid of the bad ones.
** Affects: hugin
Hello,
I really do not understand what sieve2width, sieve2height and sieve2size
do. The description is not very helpful to people who do not know (or
care ;-) about the algoritm and its implementation. What combination of
parameters do I have to set to get e.g. 7 cp-points per image pair?
And if
On 2010-12-05 tmodes wrote:
The sieve2* switches are used to get a better distribution of the cps.
As far as I unterstood the image is divided in sieve2width *
sieve2height parts/rectangles. In each of it cpfind keeps only
sieve2size control points.
Thank you for the explanation. That clears
Verified in 2010.4.0. Hugin nowadays invokes make -f ... info test all
clean, but this does not make a difference, clean and all still run
in parallell.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
*** This bug is a duplicate of bug 679427 ***
https://bugs.launchpad.net/bugs/679427
Marking as duplicate, removing fix-released.
** Changed in: hugin
Status: Fix Released = Confirmed
** This bug has been marked a duplicate of bug 679427
hugin seg faults at launch
* You can
** Attachment added: bugfix
https://bugs.launchpad.net/bugs/684357/+attachment/1753300/+files/52_build_on_kFreeBSD
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/684357
Title:
2010.4.0
74 matches
Mail list logo