GNOME Bugzilla – Bug 99526
Printing doesn't report back errors lrom lpr
Last modified: 2006-06-06 11:47:51 UTC
Gimp printing doesn't report back from lpr the error message when the job is too long. Default limitation for print job is 1MB. Undless option mx in /etc/printcap sets it differently. lpr run standalone reports: lpr: gimp.ps: copy file is too large
I can confirm this problem on Linux. I haven't looked at the code but I fear the communication between gimp and lpr is one-way only...
I had a quick look at the code for the print plug-in. I did not see anything that could collect the output of the lpr command (or lp, or whatever else). Note that the code in 1.2.4-pre1 is quite different from the one in 1.2.3 because of the new dependency on libgimpprint.
This is fixed on the 4.2 stable branch and the mainline, and will be in the next Gimp-print release. It requires a new plugin, and for best results a new libgimpprint.
Robert, how are we supposed to proceed? Can you provide a patch for the print plug-in as included with gimp-1.2 ?
Changed target milestone of several bugs to 2.0 - these are not features, and don't look to me like blockers for a pre-release, but they have to be addressed before 2.0. Dave.
We're not planning to fix this in the 4.2 version of the plugin; we had some deadlock problems with the fix. If this is important, we can discuss it. However, I would like to see the 2.0 release move toward the 4.3/next stable release line, as it contains a lot more features.
Seems this bug wont be fixed until we depend on gimp-print-4.3.x (or 4.4.x?)... Marking as depending on #120162 which states that the print plug-in doesn't compile against 4.3.x (yet).
We should attempt to update to a newer version of libgimpprint after the 2.0 release. We don't necessarily need to wait until 2.2.
Since we are targetting a quick 2.2 release, we should do this change after we branched for 2.2.
I believe you meant to say that we are targetting a quick 2.0.1 release.
Well, no, I meant a quick (3 months) 2.2 release. I didn't want people to wait for an updated print plug-in for too long but if we go for short development cycle then we don't need to do such changes in the stable branch as we had planned before.
This bug depends on bug #127957.
*** This bug has been marked as a duplicate of 127957 ***