Arch Linux User Repository

Since version v1.7.0 the Qt5 backend is no longer actively maintained and supported.

Control environment variable can be used to force build against qt5

• ENABLE_QT5=1 to build against qt5 (default:off)

Usage cases:

• makepkg ENABLE_QT5=1
• yay -S openboard --mflags="ENABLE_QT5=1"

Yay users warning:

If you want to build against qt5, you have to call pacman -S qt5-{base,declarative,multimedia,tools,svg,webchannel,webengine} beforehand.

@unphysicalix: That's correct, you have to rebuild after dependency packages are updated. Let me make this post sticky to avoid people running into this again and again.

If OpenBoard stops working and when starting it from the command line you get an error message of the type:

openboard: error while loading shared libraries: *.so.1.1: cannot open shared object 

Then you most likely just need to rebuild OpenBoard (either with makepkg or with your favourite AUR helper) because a dependency package has been updated.

(That's the one disadvantage of AUR packages. I don't know what the threshold is for the package to be migrated into the community repository instead.)

The pinned comment is still relevant, because it always happens when poppler gets updated. If you want to know more, search for "shared library" and "dynamic linking".

Basically, when building openboard, the system searches for the current version of poppler and tells openboard "Use this version". Every time that openboard starts, it asks for that version. If poppler gets updated, that version can't be found anymore and the error occurs. So we have to tell openboard that there is a new version and the simplest way is rebuilding it.

So this is not an issue with this PKGBUILD, because rebuilding still works.

OK I'll do that, but why was it working previously ? (last week, and the pinned message is from January 2024)

Can't it be fixed on the AUR side ? (sorry for the dumb question, I'm kind of a Linux noob ^^)

@SeeDborg Your analysis is correct and this issue is known, see pinned comment. This is not an issue with this PKGBUILD, you have to fix it yourself by rebuilding the package.

Since this morning, impossible to launch openboard (nothing happens). When I launch it via the terminal I have this error :

openboard: error while loading shared libraries: libpoppler.so.149: cannot open shared object file: No such file or directory

I think it might be because libpoppler updated to v150 :

❯ ls /usr/lib/libpoppler.so* lrwxrwxrwx - root 12 juin 11:26  /usr/lib/libpoppler.so -> libpoppler.so.150 lrwxrwxrwx - root 12 juin 11:26  /usr/lib/libpoppler.so.150 -> libpoppler.so.150.0.0 .rwxr-xr-x 4,1M root 12 juin 11:26  /usr/lib/libpoppler.so.150.0.0

I am using openboard through [arch4edu] and recommend it strongly, the nice feature is that every time poppler upgrades, openboard recompiles again too.

@luuuciano You could create a package from the .deb release build. It's built for Debian 12, so I'd expect issues with the poppler version.

The best way would be to have the Arch binary in a repo. That needs a PM to adopt it. There is also arch4edu which distributes an openboard package, though the usual caveats around external repos apply.

I have seen other packages has a "bin" version... can that be done with openboard? I mean to save energy, and time...

@carlosal1015 Fixed.

Error: https://pastebin.com/raw/feid10HZ

The compile error is a known issue in OpenBoard: https://github.com/OpenBoard-org/OpenBoard/issues/958.

A fix is in the works. Update: Fix is merged upstream and backported.