"Assertion Failed" on Debian 12 (Hugin 2022)

[ChameleonScales]

Hi,

Since Debian 12 and its upgrade to Hugin 2022, we're getting "Assertion failed" error dialogs when performing specific tasks. One of them being drawing a rectangle to delete control points and another being clicking on an image in the mask tab to, for example, deselect all mask points.

Here's the full error message and backtrace for the latter situation:

An assertion failed!

./src/common/overlaycmn.cpp(75): assert "m_inDrawing==false" failed in Reset(): cannot reset overlay during drawing

Backtrace:

ASSERT INFO:

./src/common/overlaycmn.cpp(75): assert "m_inDrawing==false" failed in Reset(): cannot reset overlay during drawing

BACKTRACE:

[1] wxOverlay::Reset()

[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)

[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)

[4] wxEvtHandler::TryHereOnly(wxEvent&)

[5] wxEvtHandler::ProcessEventLocally(wxEvent&)

[6] wxEvtHandler::ProcessEvent(wxEvent&)

[7] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&)

[8] wxEvtHandler::SafelyProcessEvent(wxEvent&)

[9] g_closure_invoke

[10] g_signal_emit_valist

[11] g_signal_emit

[12] gtk_main_do_event

[13] g_main_context_dispatch

[14] g_main_loop_run

[15] gtk_main

[16] wxGUIEventLoop::DoRun()

[17] wxEventLoopBase::Run()

[18] wxAppConsoleBase::MainLoop()

[19] wxEntry(int&, wchar_t**)

[20] __libc_start_main

I've tried the Hugin 2023 flatpak and it doesn't have this issue. However, I can't use it because it can't navigate to the hard drive containing all my projects.

I was wondering if there's something I can do to get the system version not throw me these error messages every time I use Hugin (I know I can check the box to ignore the error next time it occurs but it reappears every time I close and reopen Hugin).

[chaosjug]

Hi

> I've tried the Hugin 2023 flatpak and it doesn't have this issue. However, I
> can't use it because it can't navigate to the hard drive containing all my
> projects.

You can use bind mounts to get the hard drive mounted into your home dir. Then
the flatpak should be able to access it.

Regards,
Stephan

[ChameleonScales]

Thanks. This is not really ideal though.
Isn't there a way to instead add the /media root directory so that I could keep my file paths identical to my system ?
I'm also not fond of using the flatpak because it would mess with all our scripts and most likely require to update them all with rather ugly commands like:

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=pto_gen --file-forwarding net.sourceforge.Hugin @@ %F @@

instead of:

pto_gen %F

I can't even add functions in bashrc to make the regular names of programs work in order to keep my scripts untouched because it doesn't deal with the multiline arguments present in my scripts.

Basically flatpak seems like a no-go for us (our small company), or at least we much prefer having benine error messages bother us. But it would sure be neat to find a somewhat easy way to make them disappear permanently.

Debian being one of the most popular and stable distros, I'm surprised not to find more messages about this issue, as I tried Hugin on a fresh Debian 12 install and this error appears immediately.

[ChameleonScales]

... upon performing the previously mentioned tasks, that is.

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/tIc4OvkDDrXg2qXmIbDGB3yjk4rdmNwR1RfWEdPFHoEUDew41yN-_tO3GvyPC95xf0bbjQaA0hPPp5evPBffi0YGtZ_vVh4SFMEANRYtjlc%3D%40protonmail.com.

[Gnome Nomad]

I used to see that in Hugin 2022 on Debian Bookworm whenever I clicked in an image when manually creating control points. Someone on the list said that Debian had compiled a lib Hugin used as a debug version.

I haven't encountered it since compiling Hugin 2023.0 RC myself. I don't know if it was an update to Debian that fixed it, or how I compiled Hugin.

I just followed the instructions on the Hugin page about compiling. I'm no guru at compiling things so I have no idea what the command line options listed there do.

Maybe that will help. I'm another person that's allergic to flatpacks.

--
David W. Jones
gnome...@gmail.com
exploring the landscape of god
http://dancingtreefrog.com

Sent from my Android device.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/j3b32-3EtgSLlNSAB_Ph9NZDLbgi_bny2fsRGcElieDby16hzF2fUbOChrqwc3kwexvj3nOTL3bOet-MR4pHQeJPIM__AS5asbQQ7lbFj9k%3D%40protonmail.com.

[ChameleonScales]

Thanks. Indeed compiling from source was the answer (as always).