Package Details: boomaga 3.0.0-3

Git Clone URL: https://aur.archlinux.org/boomaga.git (read-only, click to copy)
Package Base: boomaga
Description: Virtual printer for viewing a document before printing it out using the physical printer
Upstream URL: https://www.boomaga.org/
Licenses: GPL2, LGPL2.1
Submitter: mrbit
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 24
Popularity: 0.004508
First Submitted: 2013-02-06 22:15 (UTC)
Last Updated: 2025-08-11 12:17 (UTC)

Pinned Comments

FabioLolix commented on 2024-05-12 10:04 (UTC)

With this version I had an error loading libpoppler

Likely libpoppler had a soname update

  • every time you have error while loading shared libraries: libXXX.so.XXX: cannot open shared object file: No such file or directory for build from source programs you have to rebuild it so it link against the new library version

hough it does take longer to install from source.

This build from source too

Latest Comments

1 2 3 4 Next › Last »

archisman commented on 2026-05-19 22:17 (UTC)

It looks like the upstream developers stopped working on this project a while ago, and Qt5 is now deprecated. Qt6 port is available on this pool request (and approved by community devs) https://github.com/Boomaga/boomaga/pull/146

GaryScottMartin commented on 2025-12-19 03:14 (UTC) (edited on 2025-12-23 02:05 (UTC) by GaryScottMartin)

NOTE OF CAUTION for users of the proprietary NVIDIA driver under Wayland: My research indicates that Boomaga relies on functionality that is fragile when using the proprietary NVIDIA driver on Wayland. A recent update to the NVIDIA driver apparently broke Boomaga for me. Not only would the GUI not start, but even after being started from the command line, printing to Boomaga failed. NVIDIA driver release 580.119.02-2 fixed part of the issue. I could print to Boomaga after starting the GUI from the command line, but the GUI still failed to start if it hasn't already been opened from my desktop session. (Printing from the command line with lpr avoided the GUI starting problem). Even after successful prints, I still got the error message:

[Boomaga GUI] WARNING: Can\'t read DBUS session direcory /var/spool/cups/tmp/.dbus/session-bus

in /var/log/cups/error_log

As far as I can determine, a robust solution to this issue would require overhauling Boomaga to make it fully compatible with Wayland. Since that seems very unlikely at this point, be aware that NVIDIA driver updates may at times break Boomaga.

  • NVIDIA driver release 590.48.01-1 appears to have restored full functionality to boomaga. The boomaga GUI starts normally and no boomaga error messages are left in /var/log/cups/error_log.

FabioLolix commented on 2025-09-10 19:45 (UTC) (edited on 2025-09-10 19:45 (UTC) by FabioLolix)

Gui starts normally for me, it is the same error reported here (fix comment) https://github.com/Boomaga/boomaga/issues/131#issuecomment-2438876699

Can't say why boomaga-git works or why it stopped to work

FabioLolix commented on 2025-06-07 22:29 (UTC)

Shouldn't be a problem apply the patch

zordsdavini commented on 2025-04-18 14:02 (UTC)

to build edit PKGBUILD with adding to cmake -DCMAKE_POLICY_VERSION_MINIMUM=3.5

FabioLolix commented on 2024-05-12 10:04 (UTC)

With this version I had an error loading libpoppler

Likely libpoppler had a soname update

  • every time you have error while loading shared libraries: libXXX.so.XXX: cannot open shared object file: No such file or directory for build from source programs you have to rebuild it so it link against the new library version

hough it does take longer to install from source.

This build from source too

1 2 3 4 Next › Last »