View Issue Details

IDProjectCategoryView StatusLast Update
0004468ScribusPrintingpublic2008-06-05 17:22
ReporterDustyJ Assigned Toavox  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionduplicate 
Platformi386OSLinux FedoraOS VersionFedora Core 6
Product Version1.3.3.4 
Summary0004468: Prints blank pages
DescriptionPrinting produces the correct number of pages but they are always blank.
I can print by exporting as PDF and printing from KPDF.
(I can also print OK from Inkscape and Open Office.)
Using Ghostscript 8.15.2
Steps To ReproduceAny Scribus printing using Epson Stylus Photo R220 / Cups / Foomatic / Gimp-print
Additional InformationPlease let me know what error logs you need. Thanks.
TagsNo tags attached.
Patch

Relationships

duplicate of 0005413 assignedavox Cannot print with CUPS printer 
child of 0004475 acknowledged Metabug: Printing from Scribus 

Activities

chrisbaxter

2007-07-02 11:58

reporter   ~0016726

I seam to be having the same problem so i thought i'd add my experience.
I'm currently using Scribus 1.3.3.3 running on Gentoo Linux (x86)

Here's my (unfortunately not very reproducible) steps to create the problem:
1: Create new 24 page document, set up master pages etc, lay up a couple of pages of text
2: Export document as PDF to see how it looks so far - PDF Export works
3: layup more text
4: repeat steps 2 and 3 a few times (over a few days)
5: export again as PDF - PDF now contains 24 blank pages

So somewhere along the line something went wrong with the document. Exporting in any format produces the same result (eps, png etc), and even print preview shows only blank pages. Opening the document using Scribus 1.3.3.9 on Windows produces the same result upon export.

Opening a new document and exporting works fine, and it even works if i copy and paste the entire document into said new document (although this stuffs up the linked text frames - is that another bug?)

So as i say, it looks like there's a problem with the saved document. I don't have time now to try to create some more reproducable steps, but i'll have a go later in the week. Does anyone have any experiments they'd like me to try?

Also, i can upload an offending document if you wish

avox

2007-07-02 12:57

updater   ~0016727

The problem with Epson printers is known. Obviously Scribus uses the default parameters provided by CUPS wrongly.

The workaround is to specify "lpr" or "kprinter" as alternate print command.

chrisbaxter:

please attach the offending *.sla to this bug. I really hope that this has a simple cause such as setting the current layer to "non printable"...

chrisbaxter

2007-07-03 22:07

reporter   ~0016735

> I really hope that this has a simple cause such as setting the current layer to "non printable"...

Heh... oops.

So is it possible to do this by accident? I was looking at my setup, and i don't have the layers dialog open (actually until i read this I didn't even know scribus supported layers).
Oh well, most likely somebody opened it when they were subbing the magazine. Thanks for your help. I'll try to make sure my future bug reports are actually bugs :-)

avox

2007-07-03 22:51

updater   ~0016737

You know, we *do* place bugs into Scribus, you just need to try a little harder to find them! ;-)

deejay1

2008-06-05 15:50

developer   ~0019806

Sorry, this doesn't happen only with Epson printers, others are affected as well - see https://bugs.edge.launchpad.net/scribus/+bug/131442
I think this one should be still left open until either cups or Scribus itself can handle it better. Of course you'll do as you please :)

jghali

2008-06-05 17:21

administrator   ~0019807

Recent versions of CUPS in Ubuntu (Gutsy, Hardy....) have known multiple breakage, especially vs CMYK support and HP printers. See for eg. :
https://bugs.launchpad.net/hplip/+bug/182379
https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/138680
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/147369
This issue is at best a duplicate of 0005413. Closing again consequently

Issue History

Date Modified Username Field Change
2006-11-02 08:55 DustyJ New Issue
2006-11-03 09:11 mhanski Relationship added child of 0004475
2007-07-02 11:58 chrisbaxter Note Added: 0016726
2007-07-02 12:57 avox Note Added: 0016727
2007-07-03 22:07 chrisbaxter Note Added: 0016735
2007-07-03 22:51 avox Note Added: 0016737
2007-07-30 21:22 jghali Status new => assigned
2007-07-30 21:22 jghali Assigned To => avox
2007-07-30 21:22 jghali Status assigned => resolved
2007-07-30 21:22 jghali Resolution open => no change required
2007-07-30 21:23 jghali Status resolved => closed
2008-06-05 15:50 deejay1 Status closed => feedback
2008-06-05 15:50 deejay1 Resolution no change required => reopened
2008-06-05 15:50 deejay1 Note Added: 0019806
2008-06-05 17:21 jghali Relationship added duplicate of 0005413
2008-06-05 17:21 jghali Duplicate ID 0 => 5413
2008-06-05 17:21 jghali Status feedback => resolved
2008-06-05 17:21 jghali Resolution reopened => duplicate
2008-06-05 17:21 jghali Note Added: 0019807
2008-06-05 17:22 jghali Status resolved => closed