After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 748017 - Printing landscape page with "auto center and rotate" on outputs nothing
Printing landscape page with "auto center and rotate" on outputs nothing
Status: RESOLVED DUPLICATE of bug 739723
Product: evince
Classification: Core
Component: printing
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-17 03:15 UTC by Damian Pereira
Modified: 2015-04-17 05:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
File which is not printed (58.40 KB, application/pdf)
2015-04-17 03:15 UTC, Damian Pereira 		Details

Description Damian Pereira 2015-04-17 03:15:44 UTC 
Created attachment 301770 [details]
File which is not printed

I'm using evince 3.14.1 from elementaryOS with epson office tx320f, I have a single page landscape document which does not print at all.

The following happens after I click print:

-Printer makes preparation sounds.

-Printer let starts blinking (the data start transfering)

-Printing stops with no paper being touched.

This problem only happens with page handling > "auto rotate and center" turned on. It happens with both epscr and seiko epson drivers. And the same document prints perfectly on chrome. I'd be happy to provide any logs.

Cups only shows this:
access_log:

localhost - - [17/Apr/2015:00:06:10 -0300] "POST / HTTP/1.1" 200 186 Renew-Subscription successful-ok
localhost - - [17/Apr/2015:00:08:10 -0300] "POST /printers/Epson-Stylus-Office-TX320F HTTP/1.1" 200 1182 Print-Job successful-ok

error_log is empty.
Comment 1 Germán Poo-Caamaño 2015-04-17 05:18:24 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 739723 ***