Description of problem: old. New much enhanced version available Version-Release number of selected component: 1.3 Released march 2019: 3.0.0 Changelog: http://www.boomaga.org/releases/ The most noticeable change are: A new backend that works more reliably in modern distributions. Added support for Wayland sessions. Support for Postscript input files. Simplification of the program structure, reduced the number of executable files. Faster processing of large PDF files. SELinux support. Some GUI improvements. Updated translations. Suggestions for changes in package descriptions: 1) "boomaga - A virtual printer for viewing a document before printing" : Add that it support duplexing as we are many users who want this, but did not fins it. Suggestion: "Use this virtual printer to view, duplex and more before printing" 2) The url shown in our package details is http://boomaga.github.io/, and gets directed to http://www.boomaga.org/, i think it should be updated. Developer version is at https://github.com/Boomaga/boomaga I can test an update for mga7-64, plasma.
Also see Bug 26033 - Suggest boomaga: print previewer that support manual duplexing and more
Thank you for pointing out that our version of this program is very dated. The new version is already (since August) in Cauldron thanks to DavidG. He can judge whether it can be built & pushed as a Mageia 7 update. If that happens: > I can test an update for mga7-64 Please do. CC'ing Dimitrios (registered maintainer) for info.
Assignee: bugsquad => geiger.david68210CC: (none) => dglent
I can test it, too. I didn't need it until recently, as my inkjet printers had a duplexer attachment available. The recent gift of a Color Laserjet CP1215 changed that. Manual duplexing with this printer is an annoying process, requiring the user to go through the application's "print" dialog twice, increasing the chance of error. Just fixing that issue alone makes boomaga a valuable tool, but it does so much more. Oh, and I heartedly endorse changing the description so that users can see the duplex printing capability at a glance in drakrpm, for the reasons Morgan stated. As it is, the user has to read the full description to realize it can handle duplex printing, and because of that is quite likely to skip over the app in a quick search.
CC: (none) => andrewsfarm
boomaga-3.0.0 now in 7/Core/Updates_testing repo. Please test it!
Looks good on my Plasma system, David. Used my Laserjet CP1215 to print a two-page document double-sided, then four pages double-sided, then all four pages on one sheet. Everything was perfect. Send it to QA, and I'll be happy to OK it and validate forthwith.
Assigning to QA, Advisory: ============================= This updates boomaga to a version which is supported upstream and enhances some printer features. ============================= Packages in 7/core/updates_testing: ======================== boomaga-3.0.0-1.mga7.i586.rpm boomaga-3.0.0-1.mga7.x86_64.rpm Source RPM: ======================== boomaga-3.0.0-1.mga7.src.rpm
Assignee: geiger.david68210 => qa-bugs
(In reply to Thomas Andrews from comment #5) > Looks good on my Plasma system, David. > > Used my Laserjet CP1215 to print a two-page document double-sided, then four > pages double-sided, then all four pages on one sheet. Everything was perfect. > > Send it to QA, and I'll be happy to OK it and validate forthwith. MGA7-64-OK Validating. Advisory pushed to SVN.
CC: (none) => ouaurelien, sysadmin-bugsWhiteboard: (none) => MGA7-64-OKKeywords: (none) => advisory, validated_update
I was just getting to that, and you beat me to it. Thanks, Aurelien.
Than you for packaging it. But i have to hold it because update do not work; I had the previous version installed. When I updated to this version the printer disappeared. To try what a user would do: I rebooted, still no. After having added it again using MCC, it cant print; "ERROR: Can't create job file: File exists"
Keywords: validated_update => (none)
Try using system-config-printer to re-install the Boomaga printer. I did have to do that, but I thought it was because of something I did months ago. It could be, however, that for some reason the system isn't recognizing the new Boomaga printer as being the same as the old one. I will see what I can do with another install, and pay better attention to what happens this time.
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0004.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
...Also the description have not improved, see last paragraphs of comment 3 and 0. In description there are two lines that mean about the same: * Print several pages on one sheet. * 1, 2, 4, 8 pages per sheet The first line is duplicating one page, the last should say side instead of sheet..., so to partly fix both problems, I suggest edit the lines to: * Facilitates manual duplexing; printing on both sides * 1, 2, 4, 8 document pages per side Also suggestion improve the short description summary: Now: A virtual printer for viewing a document before printing Suggestion: A virtual printer to preview, duplex, booklet, arrange, more pages per side... before printing ---- (Dont mind comment about URL, as the current seem OK now)
Resolution: FIXED => (none)Whiteboard: MGA7-64-OK => (none)Status: RESOLVED => REOPENED
@ Morgan Leijström Please see that directly with upstream at https://github.com/Boomaga/boomaga to enhance this. Description and summary come from upstream. Thanks in advance! And I'll not do an other update just for a description and summary, sorry.
CC: (none) => geiger.david68210Status: REOPENED => RESOLVEDResolution: (none) => FIXED
(In reply to Morgan Leijström from comment #9) > > I had the previous version installed. > > When I updated to this version the printer disappeared. > > To try what a user would do: I rebooted, still no. > > After having added it again using MCC, it cant print; "ERROR: Can't create > job file: File exists" Confirmed that while the old version automatically installed the "boomaga" printer, the update removes it. It has to be re-added. Also, attempting to print a test page from system-config-printer generates an error that "stops" the boomaga printer. Root then has to clear the job queue and re-enable the printer before it will proceed. Workaround for this would be to change the setting for what to do if an error is generated to "abort job." @ Morgan: A new bug would be the best way to deal with this test page problem, and perhaps, if that is somehow addressed, David GEIGER would consider a change to our boomaga description at the same time. Restoring the validated keyword.
Keywords: (none) => validated_update
(In reply to Thomas Andrews from comment #14) > (In reply to Morgan Leijström from comment #9) > > > > I had the previous version installed. > > > > When I updated to this version the printer disappeared. > > > > To try what a user would do: I rebooted, still no. > > > > After having added it again using MCC, it cant print; "ERROR: Can't create > > job file: File exists" > > Confirmed that while the old version automatically installed the "boomaga" > printer, the update removes it. It has to be re-added. Thank you for that confirmation. I just repeated the process too. I also find that if you do not have Boomaga installed, and install the new version, it is added automatically and as default - good. > Also, attempting to print a test page from system-config-printer generates > an error that "stops" the boomaga printer. Ah, that was what I additionally hit, as test pages was the first thing i tested after upgrade... More specifically it works to print a normal test page, but not self test page. And.. in this test round the self test page is not blocking, it just stay in queue, and other prints pass. Not perfect but it works. This time. But in first plain update i could not print after that error... > Root then has to clear the job > queue and re-enable the printer before it will proceed. Workaround for this > would be to change the setting for what to do if an error is generated to > "abort job." > > @ Morgan: A new bug would be the best way to deal with this test page > problem, and perhaps, if that is somehow addressed, David GEIGER would > consider a change to our boomaga description at the same time. There will probably not be another update needed for mga7, and i am really already over my time budget on this hobby... We can tell users to reinstall Boomaga if they ask, and if more problem a new bug. But maybe at least the update issue shold be noted and improved for future updates in mga8+ > Restoring the validated keyword.