Arch Linux User Repository

Sorry lads, I'm at the Polish Ukraine border helping allocate refugees. Expect no update until this hell is over, wish us luck. Have no time nor access to my rig and AUR keys to test/post updates. If you have a patch, ping me on email - I'll add you as co-maintainer. Posted with my old script - https://github.com/bartoszek/aur-post

This is a package is also hosted on GitHub.

• Please submit patches and report issues to AUR-meshroom-git/github.com

• Travis CI Status: <img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-meshroom-git.svg?branch=master" />

Use env vars to control build process:

• DISABLE_CUDA=1 disable CUDA components. (note: valid only when alice-vision builds with DISABLE_CUDA=1)
• ENABLE_QTALICEVISION=1 build Alice-Vision QT plugin (currently bugged: https://github.com/alicevision/meshroom/issues/1499 )

Usage cases:

• makepkg DISABLE_CUDA=1
• export DISABLE_CUDA=1 before build
• {yay,paru} -S alice-vision --mflags "DISABLE_CUDA=1"
• DISABLE_CUDA=1 ~your-aur-helper~

Notice for Yay users:

Since yay relies solely on aur-rpc to solve dependencies instead of calling makepkg --sync it can't follow dependencies logic defined in PKGBUILD. That's why it's up to the user to provide dependencies to enable optional features, otherwise yay will throw a missing dependency error.

Optional features:

• popsift\cuda: GPU accelerated feature matching for Alice-Vision

Sorry lads, I'm at the Polish Ukraine border helping allocate refugees. Expect no update until this hell is over, wish us luck. Have no time nor access to my rig and AUR keys to test/post updates. If you have a patch, ping me on email - I'll add you as co-maintainer. Posted with my old script - https://github.com/bartoszek/aur-post

Hi, you need to update .SRCINFO. Regards, Ralf

Thanks, I'll retry later today with the wheel-based PySide2.

According to the bug you reported, we might also be able to get this to work with gcc-git, although I haven't tried that. Eventually we should be able to revert the wheel-pyside once GCC and Qt5 all get back to working well.

Thanks for all your work on this package!

@attilaolah:

Made an override for pyside2 now it runs for me (package size growth by ~180MB :)

@attilaolah:

The problem lays in Arch pyside2 build. As suggested by Christian@pyside-bugtracer the wheel package for pyside2=5.14.1 is free of this issue.

I've reported this to Arch-bagtracker, lets see what's they response - in worst case will pack pyside2 wheel with meshroom and call it a quite.

I'll go ahead and re-build everything with debug symbols, maybe that will help us figure out what's the issue here.

OK, I managed to get it to segfault now (but only with meshroom, not with meshroom-git, maybe something has changed upstream). Here is my trace:

#0  0x00007ffff7c61f25 in raise () from /usr/lib/libc.so.6        
#1  0x00007ffff7c4b897 in abort () from /usr/lib/libc.so.6      
#2  0x00005555556168f3 in ?? ()
#3  0x000055555561690b in Py_FatalError ()
#4  0x00007ffff703df93 in ?? () from /usr/lib/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.14
#5  0x00007ffff7040b35 in SetError_Argument () from /usr/lib/libshiboken2.cpython-38-x86_64-linux-gnu.so.5.14
#6  0x00007fffedb622f0 in ?? () from /usr/lib/Meshroom-2019.2.0/lib/PySide2/QtQuick.cpython-38-x86_64-linux-gnu.so
#7  0x0000555555726c7f in ?? ()
#8  0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#9  0x00005555556db01b in _PyEval_EvalCodeWithName ()
#10 0x000055555574d1bc in _PyFunction_Vectorcall ()
#11 0x000055555574a15d in PyObject_Call ()
#12 0x00007ffff7092dcb in PySide::Property::setValue(PySideProperty*, _object*, _object*) ()
   from /usr/lib/libpyside2.cpython-38-x86_64-linux-gnu.so.5.14
#13 0x00007ffff70930c8 in ?? () from /usr/lib/libpyside2.cpython-38-x86_64-linux-gnu.so.5.14
#14 0x00007ffff707b2af in PySide::SignalManager::qt_metacall(QObject*, QMetaObject::Call, int, void**) ()
   from /usr/lib/libpyside2.cpython-38-x86_64-linux-gnu.so.5.14
#15 0x00007ffff674959d in ?? () from /usr/lib/libQt5Qml.so.5
#16 0x00007ffff674a0b0 in ?? () from /usr/lib/libQt5Qml.so.5
#17 0x00007ffff6746e62 in QQmlBinding::update(QFlags<QQmlPropertyData::WriteFlag>) () from /usr/lib/libQt5Qml.so.5
#18 0x00007ffff67587be in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /usr/lib/libQt5Qml.so.5
#19 0x00007ffff66e126b in ?? () from /usr/lib/libQt5Qml.so.5
#20 0x00007ffff66e17b3 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib/libQt5Qml.so.5
#21 0x00007ffff66de142 in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /usr/lib/libQt5Qml.so.5
#22 0x00007fffed8e1f5b in ?? () from /usr/lib/libQt5Quick.so.5
#23 0x00007fffed8e200b in ?? () from /usr/lib/libQt5Quick.so.5
#24 0x00007ffff675899d in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /usr/lib/libQt5Qml.so.5
#25 0x00007ffff66e126b in ?? () from /usr/lib/libQt5Qml.so.5
#26 0x00007ffff66e17b3 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib/libQt5Qml.so.5
#27 0x00007fffed599320 in ?? () from /usr/lib/libQt5QmlModels.so.5
#28 0x00007fffed5994c5 in QQmlDelegateModel::object(int, QQmlIncubator::IncubationMode) () from /usr/lib/libQt5QmlModels.so.5
#29 0x00007fffed96db0f in ?? () from /usr/lib/libQt5Quick.so.5
#30 0x00007fffed9700e4 in ?? () from /usr/lib/libQt5Quick.so.5
#31 0x00007ffff675899d in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /usr/lib/libQt5Qml.so.5
#32 0x00007ffff66e126b in ?? () from /usr/lib/libQt5Qml.so.5
#33 0x00007ffff66e17b3 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib/libQt5Qml.so.5
#34 0x00007fffed599320 in ?? () from /usr/lib/libQt5QmlModels.so.5
--Type <RET> for more, q to quit, c to continue without paging--
#35 0x00007fffed5994c5 in QQmlDelegateModel::object(int, QQmlIncubator::IncubationMode) () from /usr/lib/libQt5QmlModels.so.5
#36 0x00007fffed96db0f in ?? () from /usr/lib/libQt5Quick.so.5
#37 0x00007fffed9700e4 in ?? () from /usr/lib/libQt5Quick.so.5
#38 0x00007ffff675899d in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /usr/lib/libQt5Qml.so.5
#39 0x00007ffff66dc072 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) ()
   from /usr/lib/libQt5Qml.so.5
#40 0x00007ffff66dc194 in QQmlComponentPrivate::completeCreate() () from /usr/lib/libQt5Qml.so.5
#41 0x00007ffff66dbafc in QQmlComponent::create(QQmlContext*) () from /usr/lib/libQt5Qml.so.5
#42 0x00007ffff674d2f7 in QQmlApplicationEnginePrivate::finishLoad(QQmlComponent*) () from /usr/lib/libQt5Qml.so.5
#43 0x00007ffff674d709 in QQmlApplicationEnginePrivate::startLoad(QUrl const&, QByteArray const&, bool) () from /usr/lib/libQt5Qml.so.5
#44 0x00007ffff674d8fe in QQmlApplicationEngine::load(QString const&) () from /usr/lib/libQt5Qml.so.5
#45 0x00007ffff080216d in ?? () from /usr/lib/Meshroom-2019.2.0/lib/PySide2/QtQml.cpython-38-x86_64-linux-gnu.so
#46 0x0000555555726c7f in ?? ()
#47 0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#48 0x00005555556db01b in _PyEval_EvalCodeWithName ()
#49 0x000055555568fff3 in ?? ()
#50 0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#51 0x00005555556db01b in _PyEval_EvalCodeWithName ()
#52 0x0000555555706997 in ?? ()
#53 0x000055555574a94f in _PyObject_MakeTpCall ()
#54 0x00005555556e0e4d in _PyEval_EvalFrameDefault ()
#55 0x00005555556db01b in _PyEval_EvalCodeWithName ()
#56 0x00005555556dc14a in PyEval_EvalCodeEx ()
#57 0x00005555557b0afc in PyEval_EvalCode ()
#58 0x00005555557512b3 in ?? ()
#59 0x0000555555726e37 in ?? ()
#60 0x00005555556dc79c in _PyEval_EvalFrameDefault ()
#61 0x000055555574cfe5 in _PyFunction_Vectorcall ()
#62 0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#63 0x000055555574cfe5 in _PyFunction_Vectorcall ()
#64 0x000055555574cb04 in _PyObject_FastCallDict ()
#65 0x0000555555664201 in main ()

I'm not sure whether this is the same issue as PYSIDE-1218 or not.

To provide some additional info.

When it hangs, it hangs at the following call:

#0  0x00007ffff7d1a9ef in poll () from /usr/lib/libc.so.6
#1  0x00007ffff5c9c120 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007ffff5c9c1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007ffff6d9f020 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007ffff6d454cc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007ffff6d4d4d6 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007ffff1d340e2 in ?? () from /usr/lib/Meshroom-2019.2.0/lib/PySide2/QtWidgets.cpython-38-x86_64-linux-gnu.so
#7  0x00005555556584be in ?? ()
#8  0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#9  0x00005555556db01b in _PyEval_EvalCodeWithName ()
#10 0x00005555556dc14a in PyEval_EvalCodeEx ()
#11 0x00005555557b0afc in PyEval_EvalCode ()
#12 0x00005555557512b3 in ?? ()
#13 0x0000555555726e37 in ?? ()
#14 0x00005555556dc79c in _PyEval_EvalFrameDefault ()
#15 0x000055555574cfe5 in _PyFunction_Vectorcall ()
#16 0x00005555556e0f21 in _PyEval_EvalFrameDefault ()
#17 0x000055555574cfe5 in _PyFunction_Vectorcall ()
#18 0x000055555574cb04 in _PyObject_FastCallDict ()
#19 0x0000555555664201 in main ()

I'm trying to get it to segfault now, to have a look at the backtrace, but now I can no longer get it to segfault either, it just hangs :/

No, it looks like I also get the segfault :(

When I run Meshroom inside a Docker container, then I get no output. It simply blocks, with very little output, even with --verbose trace, I only get this:

WARNING:root:== The following "submitters" plugins could not be loaded ==
  * simpleFarmSubmitter: No module named 'simpleFarm'

WARNING:root:QQmlApplicationEngine failed to load component

When I run it outside the Docker container, on Crostini (which itself is an LXD container), the UI flashes for a bit, but then I get the dreaded segfault. Same thing if I run PYTHONPATH=/usr/lib/Meshroom-2019.2.0/lib python -m meshroom.ui: I get the segfault.

I'm not sure how to go about this, maybe let's just wait until PYSIDE-1218 gets fixed.