Print jobs to boomaga are not executed

[androidonis]

I used Boomaga for years without problems. But today I can not use it anymore.
System: Mabox (Arch-Linux)
First the GUI did not open with a library error. I deinstalled and reinstalled.
Now I can open GUI.
But when I print anything to boomaga the print job is pending and never shows up in Boomaga.
Other print jobs to other printers work well.
I am not a system expert - so no idea where to look into deeper.
Regards
Andreas

[sm-9651]

I've exactly the same problem on Linux Mint V22 and I too did exactly the same and I too have exactly the same outcome

[androidonis]

In the meantime I solved it. Key was opening CUPS with http://localhost:631/admin/
With http://localhost:631/printers/Boomaga the Boomaga printer was shown 'busy' not 'idle'.
I did remove Boomaga and re-add it. But maybe there is a more elegant method to solve the problem.

[sm-9651]

Thanks, tried your suggestion multiple time uninstalling and reinstalling and finding and deleting the boomaga folders and deleting the printer listed in cups and multiple combinations of all that via both the http page and the linux mint print manager and nothing gets boomaga working for me. :(

[sphh]

I encountered the same problem. CUPS's web interface told me:

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

So I checked the permissions of /var/spool/cups/:

$ ls -l /var/spool/cups/
drwx--x--- 3 root lp 20480 Oct 25 23:04 /var/spool/cups/

and then the groups I belong to:

$ groups
...

which does not show the lp group. Voilà, that's the problem!

Quickly adding myself to the lp group:

$ sudo usermod -a -G lp myusername

log out and in again and the boomaga gui opens again!

[sm-9651]

Thanks @sphh ,

Adding myself to the lp group worked.
The actual steps I followed was to run "sudo usermod -a -G lp myusername" then remove prior Boomaga install, remove boomaga printer from printer list, reboot, check things removed, then reboot again, then install Boomaga again, then reboot again, and again. (probably didn't need all the reboots but I'm so used to the prior OS reboots)

Boomaga is working and behaves just like Fineprint for windows.

[sphh]

For me there was no need to remove/reinstall boomaga or reboot the computer. But to log out and in is important, so that the graphical session runs with the new privileges.