|· Hosting provided by Anduin.net / Øverby Consulting ·|
|Anonymous | Login | Signup for a new account||2013-05-22 03:38 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005413||Scribus||Printing||public||07-Mar-02 22:04||07-Jul-09 00:39|
|Target Version||Fixed in Version|
|Summary||0005413: Cannot print with CUPS printer|
|Description||I cannot print with my default CUPS printer (Epson Stylus Photo 870 in printer's dropdown listbox). The work begin and end without anything printed on the papersheet. I have to enter this command line "/usr/bin/lpr -o/usr/bin/lpr -o landscape" witch is working. The is no problem with other software.|
|Tags||No tags attached.|
|Attached Files|| Capture-Configuration de l'impression.png [^] (36,614 bytes) 07-Mar-02 22:04
error_log [^] (1,050,284 bytes) 07-Mar-05 20:00
scribus-error_log [^] (725,294 bytes) 07-Jun-05 23:02
kmail-error_log [^] (1,048,602 bytes) 07-Jun-05 23:04
term-out.txt [^] (1,525 bytes) 07-Jun-10 17:13 [Show Content]
|I would change the Postscript Niveau to 2. It is quite possible your printer cannot handle PS3 - even when filtered with CUPS. Scribus generates more complex PS3 with advanced operators than probably any other application on Linux.|
|Even when I use PS level two or one, there nothing printed on the paper...|
This is most likely a CUPS problem or a configuration problem.
* does CUPS record any errormessage in its logs?
* check in Scribus's General Preferences->Printer the settings for "Alternate Print Command"
* does it work if you print to file and send this file to CUPS manually?
* when you print to file, does this file show in gsview or gs?
As a work-around you can always export as PDF and print the PDF from Acrobat Reader.
when i start printing "tail -f error_log" gives me :
I [03/Mar/2007:15:47:08 +0100] Adding start banner page "none" to job 141.
I [03/Mar/2007:15:47:08 +0100] Adding end banner page "none" to job 141.
I [03/Mar/2007:15:47:08 +0100] Job 141 queued on "Stylus" by "franck".
I [03/Mar/2007:15:47:08 +0100] Started filter /usr/lib/cups/filter/pstops (PID 8704) for job 141.
I [03/Mar/2007:15:47:08 +0100] Started filter /usr/lib/cups/filter/pstoraster (PID 8705) for job 141.
I [03/Mar/2007:15:47:08 +0100] Started filter /usr/lib/cups/filter/rastertogutenprint.5.0 (PID 8706) for job 141.
I [03/Mar/2007:15:47:08 +0100] Started backend /usr/lib/cups/backend/usb (PID 8707) for job 141.
E [03/Mar/2007:15:47:08 +0100] [Job 141] No %%BoundingBox: comment in header!
I can export to any file format and print it. For the moment, I use gtklp in command line as a work-around.
Can my system be missing some important package ?
(Sorry for my English...)
Hm, AFAIK the "BoundingBox:" comment is only required for EPS files. Scribus does not produce it for normal PostScript files.
I'd be interested which executable prooduces this error so we can work out the problem. Can you do a "grep -r 'No %%BoundingBox: comment in header!' /usr/lib/cups" ?
edited on: 07-Mar-04 19:20
"grep -r 'No %%BoundingBox: comment in header!' /usr/lib/cups" gives me /usr/lib/cups/filter/pstops. The file's a binary.
Maybe can I install the src package ??
For information, cupsys's version is 1.2.4-2.
> Rest of files are binary.
Those are the interesting ones (looking for an executable, right?).
The errormessage must be contained in some executable and most likely as clear text.
|Yes, I re-read you answer and change my note. The binary file is /usr/lib/cups/filter/pstops.|
edited on: 07-Mar-04 19:46
(forget that: output of "/usr/lib/cups/filter/pstops --version" ?
Or maybe -V, -version, -?, -h ?)
I'll look into cups source now.
Hm, the BoundingBox error might just be a waring and not the cause of the failure. Can your switch on the "debug" mode in the LogLevel directive for your CUPS daemon?
Edit /etc/cups/cupsd.conf (or wherever this configuration file is installed in your case) to have the line "LogLevel debug" there. Then restart your CUPS daemon /etc/software/init.d/cups start (the command may be customized by your Linux distribution).
Then post the error_log here?
|I've just attach the log.|
|Current 18.104.22.168cvs now writes a BoundingBox comment. If you dont mind compiling from cvs, you could try if this solves your problem.|
|I only find a Win32 exe on sourceforce. Where can I found tar.gz archive or something like that ?|
Thanks for proving the log. This tells me Scribus is not guilty this time.
Line # 280
D [05/Mar/2007:19:42:59 +0100] PID 8094 (/usr/lib/cups/filter/pstops) exited with no errors
If Scribus did something wrong, I suspect the error would be here. I would report this with Ubuntu as a CUPS or driver issue upstream.
Ok, I think your Cups installation has problems with CMYK:
D [05/Mar/2007:19:42:59 +0100] [Job 144] argv="outputorder=Normal number-up=1
number-up-layout=btlr nowrap position=center PageSize=A4
StpColorPrecision=Best MediaType=Inkjet InputSlot=Standard StpQuality=High Resolution=720hq StpInkSet=quadtone noStpFullBleed StpPrintingDirection=Unidirectional StpWeave=Alternate
This means Cups is accepting this job as Cmyk.
D [05/Mar/2007:19:42:59 +0100] [Job 144] cupsEncodeLUT = 0
D [05/Mar/2007:19:42:59 +0100] [Job 144] cupsEncodeLUT = 1
D [05/Mar/2007:19:42:59 +0100] [Job 144] num_components = 1, depth = 1
D [05/Mar/2007:19:42:59 +0100] [Job 144] cupsColorSpace = 3, cupsColorOrder = 0
D [05/Mar/2007:19:42:59 +0100] [Job 144] cupsBitsPerPixel = 1, cupsBitsPerColor
D [05/Mar/2007:19:42:59 +0100] [Job 144] max_gray = 1, dither_grays = 2
D [05/Mar/2007:19:42:59 +0100] [Job 144] max_color = 0, dither_colors = 0
D [05/Mar/2007:19:42:59 +0100] [Job 144] Subtractive gray mapping not implementedSubtractive gray mapping not implementedDEBUG2: cups_open(0x8612e0c)
Subtractive Gray mapping would be needed to output grayscale as CMYK. My guess is, that debug message comes from the routines which read the cupsraster format.
Advice: update Cups / eps-gs / gutenprint
|Please report this bug to Ubuntu. We cannot fix it as it currently stands. Thanks for the helpful logging.|
|open bug so Bandipat can attach his log|
I've uploaded two files, both the kmail printout, cups debug error log and the scribus pageout, cups debug error log. Hopefully that will help in determining where the problem lies.
Not really, your CUPS doesnt include the options with which the job is started in the debug output. Compare with the other errorlog.
What version of CUPS are you running?
I've got 1.2.11 installed presently. I believe that is the latest build, but I doubt that is affecting it, since this problem showed up in earlier builds as well. I'm sure also many that are having the problem are running an earlier build as well.
I see what you mean in the error logs, but that creates another question in my mind. If this info is being shown with the kmail printout, then I would guess that kprinter is sending that. So, if that's the case, why isn't Scribus sending that info as well when it creates and sends the info to be printed?
It's neither shown in kmail nor in scribus output.
Your CUPS is configured differently than zugol's.
No, I think you can be pretty sure Zenwalk is not like Ubuntu! If it were, I would not be using it! Don't want no Debian branch on my machines, they are just too quirky to deal with all the time. If you do a bit of research, you'll find Zenwalk to be a direct branch of Slackware. Have you asked John Cullerton if his Slackware will print directly? Bet it won't either.
Hope you're able to find the problem because a dtp program that won't print is not much use. I guess you can say that's not totally true since you can go around the elbow to get to the hand and finally a printout of something.
|Still, your CUPS doesnt provide enough information to analyze this bug on your machine.|
Ok, sorry, but I'm confused. Andreas, you seem to be convinced it's a CUPS problem or that's the impression I've gotten all along when this thread/bug started. I might strongly suspect that as well, if it were only happening on one distro or one version of CUPS, but that's just not the case! I also get the impression nothing is being looked at the source, Scribus, from which the problem is being generated?!? Why is that or what makes you so certain that Scribus is not the problem?
As I mentioned, I guess it's not a problem worthy of anyone's time, since it's been around so long. I guess I didn't expect it to be resolved either with all you guys instantly blaming CUPS/Gutenprint/Distro for the problem. I guess that's easier to do than run the problem down. Guess I won't worry about it if you aren't.
> Ok, sorry, but I'm confused. Andreas, you seem to be convinced it's a
> CUPS problem or that's the impression I've gotten all along when this
> thread/bug started.
I've an open mind about this, otherwise I wouldnt have reopened this bug.
> I might strongly suspect that as well, if it were
> only happening on one distro or one version of CUPS, but that's just
> not the case! I also get the impression nothing is being looked at
> the source, Scribus, from which the problem is being generated?!?
I did look at the source. But the only suspect I've left are the options
which Scribus queries from CUPS and then passes on to lpr. Not knowing
what those options are in your case makes debugging this impossible.
> is that or what makes you so certain that Scribus is not the problem?
I'm not (any more).
> As I mentioned, I guess it's not a problem worthy of anyone's time,
> since it's been around so long. I guess I didn't expect it to be
> resolved either with all you guys instantly blaming
> CUPS/Gutenprint/Distro for the problem. I guess that's easier to do
> than run the problem down.
That's an (incorrect) speculation on your part. Are you trying to aggravate me?
> Guess I won't worry about it if you aren't.
I'm still interested in getting useful debugging information.
If you don't know how to make CUPS provide that level of debug information, try this:
* create a file "lpr" in ~/tmp/
* enter the following 2 lines in that file:
* enter this on commandline:
chmod a+x ~/tmp/lpr
* run Scribus like this (all on one commandline):
* print from Scibus and note the output on the terminal
Yes, I suppose I was trying to aggravate you a bit, in hopes you would give me something more to try for this problem. I've included the text from the shell in the uploaded text file. I tried 2 different printouts, using 2 different files to determine if there were any differences in the file being printed. I don't think there were any. I was also expecting much more info to be shown, but as you can see, there was only a small amount.
Thanks for your patience and help on this bug.
Ok, those options look all bogus. Try setting them to this values when printing from Scribus:
StpBlackGamma = None
StpBlackDensity = None
StpFullBleed = False
StpBrightness = None
StpCDXAdjustment = 0
StpCDInnerDiameter = 121
StpCDOuterDiameter = 329
StpCDYAdjustment = 0
ColorModel = RGB
StpGamma = None
StpContrast = None
StpCyanGamma = None
StpCyanBalance = None
StpCyanDensity = None
StpDensity = None
StpGCRLower = None
StpBlackTrans = None
StpGCRUpper = None
StpImageType = TextGraphics
StpInkLimit = None !!
StpInkType = None
StpLightCyanTransition = None
StpLightMagentaTransition = None
StpMagentaGamma = None
StpMagentaBalance = None
StpMagentaDensity = None
OutputOrder = Reverse
StpQuality = Standard (or High)
Resolution = None
StpSaturation = None
StpYellowGamma = None
StpYellowBalance = None
StpYellowDensity = None
Any setting of inklimit, saturation, brightness, contrast or density to zero would probably result in empty pages.
I can see how Scribus might have messed up the default: it shows the first entry as default and not the one marked as default by the CUPS driver. Once you make any change, Scribus will store the new value in prefs.
I reset everything I saw in options set to zero to none. Guess what? Yep, I got a printed page! A whole page of 3 shades of grey that is. One shade over-printed the other resulting in one whole dark grey page. That's it! So I guess it's nothing or a whole page of dark grey nothing.
FYI: I did try playing with things after that in the options and nothing seemed to work or cause any change. Either a blank page or a dark grey page. That's all that it would do. It seems there is no way to control the number of pages it ejects either, very aggravating.
Looks as if you still didnt get all options right.
We'll provide a better way to control those CUPS options in the future (including to turn them all off).
For now you'll have to use the workaround with specifying 'lpr' as custom command.
|07-Mar-02 22:04||zugol||New Issue|
|07-Mar-02 22:04||zugol||File Added: Capture-Configuration de l'impression.png|
|07-Mar-02 22:19||plinnell||Note Added: 0015430|
|07-Mar-02 22:19||plinnell||Status||new => feedback|
|07-Mar-03 14:43||zugol||Note Added: 0015437|
|07-Mar-03 15:20||avox||Note Added: 0015439|
|07-Mar-03 16:06||zugol||Note Added: 0015440|
|07-Mar-03 17:45||avox||Note Added: 0015441|
|07-Mar-04 19:14||zugol||Note Added: 0015447|
|07-Mar-04 19:20||zugol||Note Edited: 0015447|
|07-Mar-04 19:23||avox||Note Added: 0015448|
|07-Mar-04 19:28||zugol||Note Added: 0015449|
|07-Mar-04 19:42||avox||Note Added: 0015450|
|07-Mar-04 19:46||avox||Note Edited: 0015450|
|07-Mar-05 16:36||avox||Note Added: 0015465|
|07-Mar-05 20:00||zugol||File Added: error_log|
|07-Mar-05 20:01||zugol||Note Added: 0015466|
|07-Mar-06 17:06||avox||Note Added: 0015479|
|07-Mar-06 19:22||zugol||Note Added: 0015481|
|07-Mar-10 00:54||plinnell||Status||feedback => resolved|
|07-Mar-10 00:54||plinnell||Resolution||open => no change required|
|07-Mar-10 00:54||plinnell||Assigned To||=> plinnell|
|07-Mar-10 00:54||plinnell||Note Added: 0015511|
|07-Mar-10 01:14||avox||Note Added: 0015512|
|07-Mar-18 01:31||plinnell||Status||resolved => closed|
|07-Mar-18 01:31||plinnell||Note Added: 0015553|
|07-Mar-18 01:31||plinnell||Relationship added||related to 0004423|
|07-Jun-05 22:25||avox||Status||closed => feedback|
|07-Jun-05 22:25||avox||Resolution||no change required => reopened|
|07-Jun-05 22:25||avox||Note Added: 0016444|
|07-Jun-05 23:02||BandiPat||File Added: scribus-error_log|
|07-Jun-05 23:04||BandiPat||File Added: kmail-error_log|
|07-Jun-05 23:07||BandiPat||Note Added: 0016446|
|07-Jun-05 23:37||avox||Note Added: 0016447|
|07-Jun-06 05:30||BandiPat||Note Added: 0016453|
|07-Jun-06 12:30||avox||Note Added: 0016456|
|07-Jun-07 05:02||BandiPat||Note Added: 0016474|
|07-Jun-08 18:41||avox||Note Added: 0016493|
|07-Jun-10 04:29||BandiPat||Note Added: 0016502|
|07-Jun-10 11:45||avox||Note Added: 0016503|
|07-Jun-10 17:13||BandiPat||File Added: term-out.txt|
|07-Jun-10 17:17||BandiPat||Note Added: 0016506|
|07-Jun-10 20:13||avox||Note Added: 0016507|
|07-Jun-11 04:22||BandiPat||Note Added: 0016511|
|07-Jun-11 13:40||avox||Note Added: 0016514|
|07-Jul-09 00:39||plinnell||Assigned To||plinnell => avox|
|07-Jul-09 00:39||plinnell||Status||feedback => assigned|
|08-Jun-05 19:21||jghali||Relationship added||has duplicate 0004468|
|Main | My View | View Issues | Change Log | Roadmap|
|Copyright © 2000 - 2013 MantisBT Team|