Therefore I've created a small wrapper script around pdftoraster which records command-line arguments, environment variables and the output from the "real" pdftoraster, which is then used as input to a "stand-alone" (i.e. I noticed, however, that everything seems to get piped through /usr/lib/ cups/filter/ pdftoraster before it is fed to rastertoqpdl. Unfortunatelly, I don't know how to efficiently debug a CUPS filter. Lp -d "ML-2510_(Ubuntu)" -o media=letter input.psĪs already mentioned, the Samsung-driver works fine in both cases. # no crash/ black printout see / target_ media_a4/ * # ML-2510_(Ubuntu) is using Splix (rastertoqpdl): I've attached a small LaTeX document and the resulting input.ps/input.pdf files to demonstrate the problem. However, even if rastertoqpdl doesn't crash, the printouts still are completely black. This probably has caused the crashes I observed earlier.
My printer is set to A4 media, while all KDE programs use "Letter" by default. It seems that, if the print-job's media size differs from the printer's default media-size, rastertoqpdl segfaults. I'm sorry that the information provided so far ist too thin. Using Samsung's Unified Linux Driver (see Samsung website), the printer works fine.ĭescription: Ubuntu intrepid (development branch) Whenever I try to print anything on my Samsung ML-2510 the printout is either completely black or the printer doesn't print at all and the following messages appear in /var/log/ cups/error_ log:Į PID 14178 (/usr/lib/ cups/filter/ rastertoqpdl) crashed on signal 11!Į Can't write page 1 imageĮ PID 14177 (/usr/lib/ cups/filter/ pdftoraster) stopped with status 1!Į Job stopped due to filter errors.
0 kommentar(er)
