printer crashing when printing PDF

Bug #147759 reported by BullCreek
This bug report is a duplicate of:  Bug #175449: Eye of Gnome print fails. Edit Remove
6
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Confirmed
Low
Ubuntu Desktop Bugs
gtk+2.0 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evince

This probably shouldn't be filed against evince, but some part of the cups subsystem but I wasn't sure which part so I filed it against evince.

When I try to print the attached PDF from evince in gutsy latest, all I get is a page of paper that says:

ERROR NAME:
  ioerror
COMMAND;
  fill
OPERAND STACK;

Variations of this have always happened in feisty, but since better printing is one of the things touted in gutsy (and it is a lot better), I thought I'd report it. It just happens when I print to the usb printer attached to the machine. If I print to the other network printer it works fine. It also seems to only happen with this PDF file - as I tried a few others on the usb printer and they worked.

I've attached my printer details as the PNG files. The printer that causes the problem is the MFC-8840D - the printer that works is the HL-2070N. Let me know what other info would be helpful.

Revision history for this message
BullCreek (jeff-openenergy) wrote :
Revision history for this message
BullCreek (jeff-openenergy) wrote :
Revision history for this message
BullCreek (jeff-openenergy) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Does it happens with another application like eog? May you try please?

Changed in evince:
status: New → Incomplete
Revision history for this message
BullCreek (jeff-openenergy) wrote : Re: [Bug 147759] Re: printer crashing when printing PDF

I tried printing several of the sample ODT files in oowriter and they all came thru fine. I tried the previously attached HL-2070N.png file in eog, and it gave the same error as the problematic PDF. Hope that helps.

----- "Pedro Villavicencio" <email address hidden> wrote:
> Does it happens with another application like eog? May you try
> please?

Revision history for this message
Rob Taylor (robtaylor) wrote :

I see this too. Printing out a test page works fine, some applications print fine, others (certainly Evince) cause an ioerror on the printer. It seems to be slightly document dependant.

Revision history for this message
Rob Taylor (robtaylor) wrote :

Note that ioerror would indicate that the file has been truncated before the end, maybe this is a cups spooling issue?

Changed in evince:
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

What applications create the issue? Do you have anything to the cupsys log?

Changed in evince:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
John Rose (johnaaronrose) wrote :

I've tried a number of permutations. There is a web page and 2 pdf files in the attached tar.gzip file.

This webpage (in Firefox) fails to print on Feisty, Gutsy upgrade from Feisty & Gutsy clean install. But when I paste the contents into Open Office Word Processor, it prints OK on any of the above PCs.

The User Guide pdf file (using evince Document Viewer) succeeds in printing pages 1-2 on Gutsy upgrade from Feisty & Gutsy clean install. It fails on Feisty as it can't find the printer (but I think that's another issue).

The d12 pdf file (using evince Document Viewer) fails to print pages 1-2 on Gutsy upgrade from Feisty & Gutsy clean install. It fails on Feisty as it can't find the printer (as other pdf file). When the contents are pasted into Open Office Word Processor, it prints OK on any of the above PCs.

Revision history for this message
John Rose (johnaaronrose) wrote :

Sorry, I forgot to include the cups logs in the attached file on my previous message. So here they are in the attached tar.gz.

Regards,
John

Revision history for this message
Jo Shields (directhex) wrote :

Same symptom, on a network-attached MFC-7820N, with my own (private, unfortunately for bug-test purposes) document.

Evince prints the ioerror page. Acroread does not.

Revision history for this message
BullCreek (jeff-openenergy) wrote :

FWIW, all my problems went away when I actually installed the Brother driver rather than using the built-in one that Gutsy suggest. You might try it.

----- "directhex" <email address hidden> wrote:
> Same symptom, on a network-attached MFC-7820N, with my own (private,
> unfortunately for bug-test purposes) document.
>
> Evince prints the ioerror page. Acroread does not.
>
> --
> printer crashing when printing PDF
> https://bugs.launchpad.net/bugs/147759
> You received this bug notification because you are a direct
> subscriber
> of the bug.

Revision history for this message
Jo Shields (directhex) wrote :

On Wed, 2007-11-28 at 16:06 +0000, BullCreek wrote:
> FWIW, all my problems went away when I actually installed the Brother
> driver rather than using the built-in one that Gutsy suggest. You might
> try it.

I'm on x86-64. I don't believe the Brother driver works on anything but
i386

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug occurs when printing from an application which uses the GTK print API via the Foomatic BR-Script3 drivers.
Evince & EOG use the GTK print API. (xpdf & acroread don't - these print OK)
This problem occurs in evince when printing pdf files with graphics.
This problem occurs with EOG always.

For the Brother MFC-7820N this problem does not occur when using the GPL print drivers from Brother ( http://solutions.brother.com/linux/en_us/index.html ).

This problem occurs for the Brother HL-5050, HL-5250DN, MFC7820N, MFC-8840D (and possibly any Brother printer using the Foomatic BR-Script 3 driver set).

This problem has been reported upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=504705
 and has been referred to gtk+.

A parallel bug report for this bug with EOG is Bug #175449

Revision history for this message
Pedro Villavicencio (pedro) wrote :

gtk+ bug

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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