Summary: | Attached pdf file cannot be printed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Current packages | Assignee: | Printing Team <printing> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.gnome.org/show_bug.cgi?id=628530 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Error message
example test pdf |
Description
Sergey S. Starikoff
2009-08-31 06:22:05 UTC
could you try printing stuff from evolution and tell us if it behaves the same ? (In reply to comment #1) > could you try printing stuff from evolution and tell us if it behaves the same > ? > No. I'm using mozilla-thunderbird as mail client (it doesn't use the evince for preview function) and haven't entire GNOME installation. But by experience know, that installing in Gentoo GNOME-oriented applications without GNOME may be followed by some additional bugs. Thaits why I'm not shure, that installing evolution for test is a good idea. the point is abiword uses the old libgnomeprint so it handles the preview on its own afaik and gnumeric might be using gtkprint but clicking on the print button in the preview simply does nothing here. Please find an example that is not firefox or thunderbird or the two previous apps. please get back to us. (In reply to comment #3) > the point is abiword uses the old libgnomeprint so it handles the preview on > its own afaik and gnumeric might be using gtkprint but clicking on the print > button in the preview simply does nothing here. Please find an example that is > not firefox or thunderbird or the two previous apps. > Excuse me, yesterday I was a little bit busy and hadn't time to check the idea. Currently I can say, that my guess was right: The root of this problem is in that the temporary pdf file for preview creates in 0600 mode with the owning of user, running [in current case] gnumeric. So, I think, cups can't read it and thatis why can't print it (successfully printed by evince pdf files had the rather standard mode 0644). Do you still suffer this problem with 2.30? (In reply to comment #6) > Do you still suffer this problem with 2.30? > > (In reply to comment #6)
> > Do you still suffer this problem with 2.30?
Excuse me the late answer.
app-text/evince-2.30.3
The same issue.
May be this info will be useful:
aboword-2.8 writes the window to select printer and after that prints OK.
evince as print previewer when receive "print" command sends the fake page on default printer (no window of printer selection).
Reproduced and reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=628530 Looks to work fine for me now with Gnome 2.32, could you try if fixed also for you? Good luck! Created attachment 258157 [details]
Error message
Earlier I've seen the items, which work correctly in complete GNOME installation and don't work without it.
This bug is the same:
I'm using stable branch (x86) without complete GNOME installation.
For the test I've unmasked the following packages:
=app-text/evince-2.32.0 ~x86
=x11-libs/gtk+-2.22.1 ~x86
=dev-libs/glib-2.26.0-r1 ~x86
=x11-libs/gdk-pixbuf-2.22.1 ~x86
=x11-libs/cairo-1.10.0-r3 ~x86
=x11-libs/pixman-0.20.0 ~x86
=gnome-base/librsvg-2.32.1 ~x86
May be it's already another bug. But...
Trying to check with evince-2.32.0 showed the same error (see the attach: cannot open 'null' printer, no printer selection window is echoed).
In my case I was getting no error at all, simply nothing was printed, then, maybe your issue is a bit different :-/ Have you tried on a new created user account? Please try to run "evince-previewer 'you pdf file'.pdf" from a terminal and look for any message reported in it when trying to reproduce. Gnome 2.32 is going to stable, please retry with it on a fully updated system (In reply to comment #13) > Gnome 2.32 is going to stable, please retry with it on a fully updated system > Yesterday I've updated the system (I have no complete GNOME installation). The same issue (no window of printer selection and cannot open null printer error). Perhaps the bug is not reproducable in native (GNOME) environment. May be this bug is has the same root with #353166 Did you tested directly running "evince-previewer"? (In reply to comment #15) > Did you tested directly running "evince-previewer"? > No. Just now I've made recheck with direct invocation of "evince-previewer". Error was the same (can't open 'null' printer, no window to select printer echoed). No console output. Should I try to rebuild evince with 'debug' USE and try to extract some additional info (how?)? Have you tried on a new created user account? ping (In reply to comment #17) > Have you tried on a new created user account? In newly created account the behaviour was like the very early (in my monitoring of this bug) one: the print goes, but on page is printed only two garbage symbols (far from appearance of oryginal page). (In reply to comment #19) > (In reply to comment #17) > > Have you tried on a new created user account? > > In newly created account the behaviour was like the very early (in my > monitoring of this bug) one: the print goes, but on page is printed only two > garbage symbols (far from appearance of oryginal page). Keep then on newly created account for testing: 1. Does "lpr file.pdf" work ok for you in that account? 2. Please attach a pdf for letting me to try to reproduce. (In reply to comment #20) > Keep then on newly created account for testing: > 1. Does "lpr file.pdf" work ok for you in that account? > 2. Please attach a pdf for letting me to try to reproduce. Both on newly created and current profiles the $ lpr file.pdf produces a marked by two garbage symbols page (the same with evince-previewer file.pdf on clean profile). Should I attach a file.pdf for checking? Yes, as I cannot reproduce and, if lpr is also failing, it would point a more general issue Created attachment 266091 [details] example test pdf (In reply to comment #22) > Yes, as I cannot reproduce and, if lpr is also failing, it would point a more > general issue I do so. The test pdf (I've checked lpr print on newly created test account --- the same issue). But, because of this issue reproduces with most (all tested by me) pdf files this attach seems to be unnecessary to my mind. In your case lpr works correctly? About this weekend I'll try to make a check on another system. > (In reply to comment #22) > > Yes, as I cannot reproduce and, if lpr is also failing, it would point a more > > general issue > I do so. > The test pdf (I've checked lpr print on newly created test account --- the same > issue). > Do you get any error in lpr output? Please also take a look to /var/log/messages and /var/log/cups/error_log after reproducing > But, because of this issue reproduces with most (all tested by me) pdf files > this attach seems to be unnecessary to my mind. > > In your case lpr works correctly? > About this weekend I'll try to make a check on another system. Works fine for me with lpr and evince-previewer, maybe it's a printer configuration problem, try to reconfigure it or use another driver if possible (In reply to comment #24) Last check showed the following: 1. On my home PC I've a little bit misconfigurated printer. After I've changed it's description in printers.conf to DefaultPrinter everything (i.e. lpr test.pdf) works correctly (the system is localized as recommended in UTF8). 2. On my workstation (where I still have to use KOI8-R locale) the original issue reproduces always. So, I think the bug was fixed only for upstream (UTF8 locale), not for other ones (I know that it's very painful). I am not sure if this is a problem with LOCALEs (but would be interesting to confirm), anyway, it's clear to me that, specially after seeing lpr also failing, this is a more general issue related with printing system (cups, ghostscript...) (In reply to comment #26) I disagree with your last commint in this bug. The oryginal issue was reproduced on both of my PCs. Also it was reproduced independently on reporter (im thic case --- me). This issue was successfully solved. While final check was discovered some another issue with printing system. Which wasn't reproduced on my home PC (localised in UTF8). On my workstation (localised in KOI8-R) it's reproduces always, with any tested pdf. I think that the original bug should be renamed back and closed. The discussion of current issue should be moved to another bug. P.S. Working under currently seen issue it seems to me to be useful to try to print via lpr some plain text files. On both of my PCs. (In reply to comment #27) In addition: Generally (directly from browser (GNU/IceCat), mail client Mozilla Thunderbird, Office applications or evince itself) print function works well. This issue for me looks very similiar with print issue with AbiWord (in about 2.4-2.6 versions). Is this still a problem? (In reply to comment #29) > Is this still a problem? Seems not. |