Can\'t read DBUS session direcory /var/spool/cups/tmp/.dbus/session-bus

[LanThrusteR]

virtual printer fails constantly with:
[Job 87] [Boomaga GUI] WARNING: Can't read DBUS session direcory /var/spool/cups/tmp/.dbus/session-bus

for example when printing PDF from Okular. Rebooting cups won't help. Rebooting Okular won't help either. I can't find the system to get boomaga back online with cups2.3,2-r2 but somehow sometimes the virtual printer works. May be the warning is irrelevant.

the second issue is speed sometimes, when boomaga gui loads it takes quite some time for it to enter Print readiness state. During this time one CPU thread is 100% for quite a while. I use it on 1025C Asus, it has limited GPU hardware support (through GMA3600 in-kernel) may be it has something to do with QT trying to hardware accelerate some processes.

[LanThrusteR]

I can remember when this started to happen. I printed from Okular to boomaga, GUI opened, and then I printed from the same Okular another document to boomaga while GUI was still opened, and since then Boomaga virtual printer is no longer opening GUI, when you print to Boomaga printer nothing happens, cups shows no change in document queue, remaining in state idle. The warning can't read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus appears and that's all.

[AndreasHupfer]

do you have a solution? Same problem here!

[Cris70]

Same here on openSuse Tumbleweed 20220604.
Did anybody find a solution?
I do not have a /var/spool/cups/tmp/.dbus/session-bus. My tree only goes down to /var/spool/cups/tmp/.
Even after manually creating a .dbus directory, nothing happens. Always "can't read DBUS session directory...".

[Cris70]

After reading the wiki document "Boomaga backend, how it works" I tried to manually start boomaga with one of the cboo files in the /var/cache/boomaga/cris directory.
So I issued the command:
boomaga --started-from-cups /var/cache/boomaga/cris/in_854.cboo.autoremove
and the result was:

Seems the same error as in bug #113
After that, the in_854.cboo.autoremove file vanished from the /var/cache/boomaga/cris directory, but that is how it is supposed to work if I understand correctly.

[monkeysHK]

Facing the same issue when printing to boomaga from cups.
lp file fails to launch the GUI.
sudo lp file works.
It might be an issue with the permission to read /var/spool/cups.