| Summary: | Printing to boomaga fails since recently. CUPS/DBUS incompatibility? | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Morgan Leijström <fri> |
| Component: | RPM Packages | Assignee: | David GEIGER <geiger.david68210> |
| Status: | NEW --- | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | Keywords: | IN_ERRATA9, UPSTREAM |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/Boomaga/boomaga | ||
| Whiteboard: | |||
| Source RPM: | boomaga-3.0.0-6.mga9.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Morgan Leijström
2023-05-31 12:28:53 CEST
Morgan Leijström
2023-05-31 12:29:18 CEST
CC:
(none) =>
thierry.vignaud Only cups package to have been updated since i think boomaga worked ok is lib64cups-filters1-1.28.16-6.mga9.x86_64.rpm That does not sound like a possible culprit to me. On my Cauldron system, the only relevant packages updated recently are: cups-filters-1.28.16-6.mga9.x86_64 Dydd Sul 28 mis Mai 2023 21:32:49 lib64cups-filters1-1.28.16-6.mga9.x86_64 Dydd Sul 28 mis Mai 2023 21:32:47 but note: boomaga-3.0.0-6.mga9.x86_64 Dydd Sul 21 mis Mai 2023 16:21:36 Trying to print to Boomaga, nothing happens. Journal: Mai 31 20:39:56 cupsd[1821]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 36077 Print-Job successful-ok Mai 31 20:39:56 cupsd[1821]: [Job 47] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus Mai 31 20:39:56 dbus-daemon[2493]: [session uid=1001 pid=2493] Activating service name='org.boomaga' requested by ':1.120' (uid=1001 pid=7242 comm="boomaga --started-from-cups /var/cache/boomaga/lew") Mai 31 20:39:56 dbus-daemon[2493]: [session uid=1001 pid=2493] Successfully activated service 'org.boomaga' Mai 31 20:39:57 cupsd[1821]: Boomaga lewis 47 [31/May/2023:20:39:57 +0200] total 0 - localhost bugsquad.txt - - Mai 31 20:39:57 org.boomaga[7245]: double free or corruption (fasttop) So this looks down to Boomaga, which was updated Tue May 2 by DavidG. So assigning to you! Un-CC'ing tv. Source RPM:
(none) =>
boomaga-3.0.0-6.mga9.src.rpm
Lewis Smith
2023-05-31 20:48:30 CEST
Assignee:
bugsquad =>
geiger.david68210 Thank you Lewis. That boomaga was installed here already at fresh install beta2 + updates during install. Probably I remembered wrong about it ever working on *this* system. But it is strange difference you (but not me) get in your log "Successfully activated service 'org.boomaga'", (and later it crash) I think this issue should be reported upstream, I'm not the boomaga developer so I can't do more for this. Searching internet, I found similar reports. Upstream seem to not have time anymore, since years :( https://github.com/Boomaga/boomaga/issues/117 at a straight question, https://github.com/Boomaga/boomaga/issues/123 two weeks ago. Darn, this "intermediate printer" is so useful. Good thing is that developer at least answers :) So IF someone wants to step up and take it on... lets hope! Boomaga is still working in updated Mageia 8. Tedious workaround: print to pdf, open in a pdf page shuffler (we have some packaged), then print. Severity:
normal =>
major https://wiki.mageia.org/en/Mageia_9_Errata#Boomaga_virtual_printer Keywords:
FOR_ERRATA9 =>
IN_ERRATA9 Now I get really confused: It works perfectly on my laptop. That install have never had printing installed. Originally installed from mga9 beta 1 classic i think, then updated, used sparsely. Now I: 1) Installed boomaga package 2) opened MCC > Hardware > Printer -> it installed packages, then boomaga icon showed up used that icon to print test page: boomaga popped up and showed it! 3) rebooted 4) started firefox, which i let open a pdf, print to boomaga: perfect! Go figure... Edited Errata. After reboot of the problematic system in Comment 0, it works again. (Print from Kolourpaint -> boomaga popped up showing the picture) Maybe some state of DBUS, CUPS, whatever needed to be reset? Edited Errata to suggest reboot. @Lewis: does rebooting help on your system? |