scribus prints blank page with LJ4V

Bug #131442 reported by Gigs
10
Affects Status Importance Assigned to Milestone
Scribus
In Progress
Unknown
scribus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: scribus

Attempting to print from Scribus 1.3.3.9 in Gutsy produces a blank page or a page of dots. Other applications can print fine.

Printer is LaserJet4V, default cups stuff is being used.

Print preview looks fine, and I can print to PDF then print the resulting PDF out from evince fine.

Revision history for this message
Gigs (gigs) wrote :

"Alternative print command" and entering "lpr" then advanced and "set page size" allows working around this bug.

Revision history for this message
TerryG (tgalati4) wrote :

Thanks for the bug submission. I generated a one-page scribus document with one text box and a few lines of text. I was able to generate a PDF file that evince was able to render, print preview, and print to an Officejet7110. I was using 1.3.3.11. You might have to enable the backports repository to update your version. I have an old Laserjet4 but it's not setup for testing at this moment.

Marking Incomplete pending tests with newer version of scribus. Seems to be working for me.

Changed in scribus:
status: New → Incomplete
Revision history for this message
Erdal Ronahi (erdalronahi) wrote :

I have the same problem in Hardy (also had it in Gutsy) with a Samsung ML-2010. "lpr" helps.

I cannot print horizontal pages, however, but that is not specific to scribus.

Revision history for this message
spitenmalice (atbakken) wrote :

I can confirm this in Hardy as well. I can use lpr however landscape pages will print out as portrait, setting the "set media size" on the advanced options does not give a desired output for landscape pages either. I have also noticed when trying to print the original way (non alternative print command) that setting the "grey scale" option will produce an entire black page rather than a blank page.

Revision history for this message
Łukasz Jernaś (deejay1) wrote :

Which PostScript level do you use?

Revision history for this message
Erdal Ronahi (erdalronahi) wrote :

I use postscript level 3, probably the default.

Revision history for this message
spitenmalice (atbakken) wrote :

I have tried all three postscript levels with the same outcome.

Revision history for this message
MMarking (cpt-mocha) wrote :

Same problem here with Hardy and Scribus out of the repository, using an Epson Stylus Photo 825. Prints a page of little dots or a page of gray or a totally blank page, it depends on the color model chosen; RGB, CMYK, etc.. I have to export as a PNG and open in another program to print.

Revision history for this message
Caroline Ford (secretlondon) wrote :

Upstream has closed as a bug in version of CUPS.

"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 "

Revision history for this message
LaserJock (laserjock) wrote :

Does the workaround of setting "lpr" as a custom command (from comment #1) work? As Caroline has said, this appears to be not just a Scribus problem but perhaps also a CUPS issue.

Changed in scribus:
status: Unknown → In Progress
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in scribus (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.