GNOME Bugzilla – Bug 447612
Print Job Isn't Released Until Evince Closed
Last modified: 2012-02-08 12:50:01 UTC
Please describe the problem: We are trying to use Evince for viewing multi-page TIFF images. When you print, nothing comes out of the printer. But, when you close out of evince the print job is released and it works. I compiled and tested on 0.9 and it's doing the same thing. The files are NFS mounted, possible that that is causing a problem? Print output is perfect once it works :) Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Ok, gtk print job is cleared now in finished callback too. I hope it helps. Thanks for the bug report.
Still broken: Pulled down from SVN, verified it's in the ChangeLog 2007-06-17 Carlos Garcia Campos <carlosgc@gnome.org> * shell/ev-window.c: (ev_window_clear_print_job): Clear gtk print job when job has finished. Fixes bug #447612. Compiled and tested and it's doing the same thing. When you enter in the print command and click OK it should immediately start to print. It's getting buffered somehow and waits until you physically close the software and then it's released to the printer.
Is it specific to evince? or do you have the same problems with other applications like epiphany or ego? does it only happen with tiff documents? Thanks again.
It's specific to evince. EOG works and sends output to the printer. The problem is that eog doesn't support multi-page TIFFs which is the reason we are trying to use evince. Evince failed on a postscript file in the same way, and I had to close the program to kick off the print job. Other possible differences: 1) We are printing multi-page TIFF images...but they appear to work fine once evince is closed. 2) It's built with PDF support disabled. Poppler libraries on OpenSuse 10.2 are too old. We don't need PDF support anyway, using Acrobat. 3) The old style printer dialog is opening in evince. It doesn't generate a list of printers as it should, but instead comes up and asks you to enter in the command line information for the printer. (attaching shots). 4)Computer has 75 printers, and people don't just print to lpr. They are entering lpr -P <foobar>
Created attachment 90219 [details] Old printer dialog that evince is using, requires to enter commands (ick!).
Created attachment 90220 [details] Printer dialog that is working in eog
Created attachment 90221 [details] Test document, multi-page tiff image
The print dialog used by evince is not the old one, but the new one. And the dialog used by eog is the old one. So it seems to be a problem in gtk+ printing system, since it's not detecting your printers, right?
I think that not detecting printers would be another issue to open? Because in theory one should be able to enter right into that box the printer command. It's like the file is locked or something. When I Print To File, it correctly writes out a .ps : [root@nas drichard]# ls -lad out.ps -rw-r--r-- 1 root root 1908496 Jun 18 12:42 out.ps [root@nas drichard]# The UI was still open when I issued this command and the file was closed and written correctly. But yes, it's not displaying printer names in the UI. I have 2 options, Print to LPR and Print to File and the printers never appear in the dialog. I assumed that because they did not, that it was supposed to work that way. I just verified the total number of printers: browser:/users/drichard # lpstat -a | wc 57 513 3338
It looks like a problem in the gtk+ printing system anyway, so I'm going to move this bug there. Thank you very much for you help.
Wrt to comment 9: That is just the way the lpr print backend works. Changing that would need someone to write a better lpr backend. If you use the cups backend, printers will appear in the dialog (and a lot more). Of course, that doesn't help if you are not using cups...
Hi David, I can not reproduce this bug with gtk+ 2.17.5 and evince 2.27.4. Could you confirm that the problem persist? Thank you Marek
NEEDINFO as per last comment.
Dave: Is this still an issue or can this be closed as OBSOLETE nowadays?
Indeed, very old bug report and closing.