Description of problem: Please see bug 4099 which has been validated. It was found during QA that printing in tuxpaint caused an error message to be displayed in the program saying "Sorry! Your picture could not be printed". The picture is actually printed despite this message but appears in print queue and cups log as being sent from '(stdin)'. My printer is on a remote cups server but that shouldn't make any difference really. Version-Release number of selected component (if applicable): Current version tuxpaint-0.9.21-3.1.mga1.src.rpm Also release version, it was not a regression. How reproducible: 1) Paint pretty picture. 2) Click print 3) Notice message saying it didn't print 4) Paint & Print some more 5) Cry when you find out all your ink is gone because they all actually printed!
Sorry claire (about bug 4099) for some reasons reassigning that bug did not add me in cc :( I will check this asap, thanks for reporting it.
It's OK. I don't think it does add you automatically. It wasn't a blocker but I thought it worth creating a bug for :)
It's an upstream bug, i'm not able to fix it by my self at the moment. I'll open an upstream bug as soon as possible.
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Manuel i do hope you used a bot for this :) Either claire or I are into mageia process, so we know what happens. Anyway as discussed here this bug is an upstream bug and it is not easy to fix. I will check if any upstream bugzilla exists, and push as upstream. Angelo
> Manuel i do hope you used a bot for this :) yes of courses, ie the bugzilla function
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
It's not only on mga1, but since it's an upstream bug i'm not able to fix it at the moment.