See this bugreport on FreeBSD: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278633 Summary: app-arch/snappy-1.2.0 uses symbols that un-bumped versions of qtwebengine-5 don't have defined, so apps using qtwebengine-5 (notably for me, frescobaldi, the last PyQt5 app on my system) will have runtime failures: ------------------ $ frescobaldi Traceback (most recent call last): File "/usr/lib/python-exec/python3.11/frescobaldi", line 42, in <module> import main File "/usr/lib/python3.11/site-packages/frescobaldi_app/main.py", line 34, in <module> import app # Instantiate global signals etc ^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/frescobaldi_app/app.py", line 38, in <module> import PyQt5.QtWebEngineWidgets ImportError: /usr/lib64/libQt5WebEngineCore.so.5: undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm ----------------- Reproducible: Always Steps to Reproduce: 1. emerge -uD world, updating snappy 2. run PyQt5 application 3. undefined symbol and failure to start masking =app-arch/snappy-1.2.0 to force a downgrade back to -1.1.10 works around the issue.
That's strange, this should already be resolved when snappy-1.2.0-r1 got a new subslot to trigger a qtwebengine rebuild. Did you not upgrade to 1.2.0-r1, but rather the old 1.2.0? emerge --info?
(In reply to Ionen Wolkens from comment #1) > That's strange, this should already be resolved when snappy-1.2.0-r1 got a > new subslot to trigger a qtwebengine rebuild. > > Did you not upgrade to 1.2.0-r1, but rather the old 1.2.0? > > emerge --info? I say strange given the fix is about ~18 days old, so you'd need to not have sync'ed in that long, please sync before reporting bugs if so. Probably a duplicate of bug #929199 anyhow.
ah, I see my problem. qtwebengine-5.15.13_p20240322 failed to build on my system, so I'm still stuck with _p20240122. I'll try to get the newer version to build properly. If that fails, I'll post a separate bugreport for that. Sorry for the trouble :(
(In reply to N. Andrew Walsh from comment #3) > ah, I see my problem. qtwebengine-5.15.13_p20240322 failed to build on my > system If I were to guess, you ran into bug #930107 then (aka fails to build with the new ninja-1.12.0)
(In reply to Ionen Wolkens from comment #4) > (In reply to N. Andrew Walsh from comment #3) > If I were to guess, you ran into bug #930107 then (aka fails to build with > the new ninja-1.12.0) That was, indeed, the problem. Applying the qt5 patch posted in that bugreport got qtwebengine:5 to compile without failure (which means frescobaldi lives to see another day, hurrah). Many thanks.
