Advisory: ======================== Updated boomaga package fix mga#23461 bug (unable to open files): Bug description : When opening a file to print the file cannot be opened with the failure message : "I can't open file /home/myusername/.cache/boomaga_tmp_4090.pdf" and the application exits References: https://bugs.mageia.org/show_bug.cgi?id=23461 https://github.com/Boomaga/boomaga/issues/50 ======================== Updated packages in core/updates_testing: ======================== boomaga-1.3.0-1.mga6 Source RPM: boomaga-1.3.0-1.mga6.src.rpm
Assignee: bugsquad => qa-bugsBlocks: (none) => 23461
MGA6-32 MATE on IBM Thinkpad R50e No installation issues. Googled "how to use boomaga" and found a nice guide on its github pages: https://github.com/Boomaga/boomaga/wiki/Things-To-Do-After-Installing-Boomaga Opened a 4 page odt file with LibreOfficeWriter and used boomaga to print it on a single sheet booklet. I love it.
Whiteboard: (none) => MGA6-32-OKCC: (none) => herman.viaene
Used Herman's link to investigate boomaga. Followed the setup instructions and used LO writer to create a two-page document. Tried to print it from LO via the default printer Boomaga and a boomaga window opened with a popup error window as well which stated that "Cannot open file /home/lcl/.cache/boomaga_tmp_23306-1.pdf/" This is actually an empty directory with 700 access permissions. There is also a boomaga.env file which holds "BOOMAGA_PROC_FILE=/proc/29099/environ". $ cat /proc/29099/environ contains a full listing of the environment in which process 29099 is or was running. That is probably OK. There is also a boomaga_in_file-7.pdf which on examination holds the two page output, exactly as it should look. Trying to print anything always gives the same errors so I have to remove Boomaga as the default. Selecting the printer under its original name is OK - it works but ignores duplex printing. I also tried this experiment from within the .cache directory to show that there is nothing wrong with access permissions. $ libreoffice -writer boomaga_tmp_30633-1.pdf/../boomaga_in_file-9.pdf The file opened without any problem but would still not print through Boomaga but output two pages using okda, the proper name for the printer. This is baffling. The only other thing that seems odd is that normal printing is single-sided even though the default has been set to long-edge standard. There is no way of setting duplex-mode manually so maybe the printer is broken. One last thing. Tried opening the odt file in boomaga but it objected. "I can't read file "/home/lcl/Documents/twopage.odt" because is either not a supported file type or because the file has been damaged." It is obviously not damaged because LO can deal with it. Updated boomaga and ran that last experiment again, with the same result. Also noted that boomaga cannot see any odt files under "all supported files" only under "all files". It seems to deal with pdf only so maybe we have to save the odt file as a pdf in LO but that cannot be right because Herman managed with odt and the utility is able to generate a pdf and store it in .cache. Just noticed that Boomaga has disappeared from the list of printers. Added Boomaga and tried LO. This time it did not object but there was no boomaga dialogue and the document failed to print. CUPS says that it is pending but rendering is finished. $ lpstat Boomaga Boomaga-16 lcl 10240 Tue 21 Aug 2018 23:21:21 BST Restarted cups service, then: $ sudo systemctl status cups [...] Aug 21 23:32:50 difda cupsd[31318]: REQUEST localhost - root "POST /admin/ HTTP/1.1" 200 10355 CUPS-Add-Modify-Printer successful-ok Aug 21 23:32:50 difda cupsd[31318]: [Client 5] Returning IPP client-error-bad-request for CUPS-Add-Modify-Printer (ipp://localhost:631/printers/okda) from localhost Aug 21 23:32:50 difda cupsd[31318]: REQUEST localhost - root "POST /admin/ HTTP/1.1" 200 177 CUPS-Add-Modify-Printer client-error-bad-request Cancelled the pending job. Tried LO again and sent the two-page odt file to Boomaga. Again it was pending in the queue. Also, the boomaga pdf files are no longer being created in .cache .
CC: (none) => tarazed25
On the positive side, the original bug seems to have been fixed. If I could get the utility to work then an OK would be in order.
@ Len I wonder whether boomaga is ment to be used "standalone". Note also that I didn't install the previous version, so I wonder if you didn't encounter any "leftover" from the previous version. To check: could you send your odt file, so I can try that one on my laptop?
Created attachment 10330 [details] Two page ODT file
Thanks Herman. I shall also try installing the updated boomaga on another machine in case, as you say, the buggy version left a problem.
@ Len No problems here opening your odt file here in LO and selecting boomaga as default printer. The dialogue opens OK without problems. I did not actually print it, but that's already ons step further than you had it.
@ Heman. Thanks for that test. Now I shall try the other workstation, starting from scratch.
OK, done that. boomaga is installed on the neighbouring machine and set up as the default printer pointing to the real printer okda, wifi HP5520. Printing to Boomaga from LO writer works perfectly for the two-page file and I see the PDF composite in .cache: boomaga_in_file_61[01].pdf. Since I followed the same setup procedure as before we can only conclude that Herman's suggestion of "interference" from the pre-update version caused the problem. Shall see if the 4-page booklet test works.
Did not actually try four pages but could see how it was supposed to work. Used the boomaga configuration window to switch duplex printing on and off. It looks good so it gets the 64-bit OK.
Whiteboard: MGA6-32-OK => MGA6-32-OK MGA6-64-OK
CC: (none) => sysadmin-bugsKeywords: (none) => validated_update
CC: (none) => tmbKeywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0146.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED