Fixed in repository.
It took some time to tackle this down. It does not happen on Ubuntu 2022.4 LTS
with wxWidgets 3.0.5 in my test virtual machine.
After upgrading to 2023.4 with wxWidgets 3.2.2 I could reproduce the issue. It
is related to 0x0 characters in the output, which wxWidgets 3.2.x pass through
while 3.0.5 seems to have them filtered out.
This causes issues like the one you observed.
It should now be fixed in repository in 2023.0 branch.
Initially I had the plan to release rc1 this weekend. But it has to wait until
the fix is confirmed (that it is working and does not break anything else).
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2023.0rc1
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/2041687
Title:
does not show/log enblend error messages
Status in Hugin:
Fix Committed
Bug description:
Hello,
hugin does not show/log enblend errors. I think it did previously.
This is on 2023.0~beta1+dfsg-1.
This was originally reported by Michael Deegan in
https://bugs.debian.org/1054129
It is easy to reproduce by replacing enblend with a dummy-script like this one
-------------#!/bin/sh
echo status on stdout
echo error in stderr 1>&2
exit 1
--------------
The corresponding logfile ends with
Remapping LDR images...
Blending images...
Process took 9 s
cu Andreas
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/2041687/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : [email protected]
Unsubscribe : https://launchpad.net/~hugin-bug-hunters
More help : https://help.launchpad.net/ListHelp
