Description of problem:
Openoffice Writer does not print on remote samba printer after upgrade from F12 to F13. Other applications, including other openoffice Applications (calc, impress) print without problems. Printing in F12 worked without issues.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to print on printer smb:// (see below)
something gets sent to printer (printer queue reports no errors), but then there's no job in the queue. Nothing is printed.
Here'S the entry in printer.conf
MakeModel Ricoh Aficio MP 6001 PS
Filter application/vnd.cups-raw 0 -
Filter application/vnd.cups-postscript 0 foomatic-rip
JobSheets none none
Option fitplot True
impress and calc work, but writer doesn't ? That's surprising, so say the least, to me.
And this is with even a simple newly created writer document with e.g. just "hello world" on it.
Yes - I just tried to make sure:
new document with a few words in writer: no print.
Printing from impress: job submitted to queue and printed
(although I haven't looked at the printout yet because it's a remote printer in a different building, but recent prints with calc and impress worked fine)
I'd be interested in finding out what happens if you use print to file in writer, save as some example.ps, and the open that example.ps in evince and try and print from there. Does that work or fail ?
caolanm->twaugh: Do we have a list of easy-to-set-by-user flags to get some useful logging as to how far the output .ps got.
Printing ps from evince works, however, I was asked for authentication. Entering my linux user password (NOT samba password) worked, and the document got printed.
Created attachment 424733 [details]
Cupsd error_log with loglevel debug2
Above attachment is the error_log after setting cupsd loglevel to debug2. Attempt to print from OOWriter starts at 11:30
I realized that the recent prints worked??!! I'm wondering whether this is due to the authentication during the evince print above, or due to the yum upgrade I just did. I'll keep an eye on this, and will close the bug if it doesn't reappear.
(In reply to comment #4)
> caolanm->twaugh: Do we have a list of easy-to-set-by-user flags to get some
> useful logging as to how far the output .ps got.
Information about debugging printing issues is here:
(In reply to comment #0)
> <Printer ps>
> AuthInfoRequired username,password
This part says that at some point in the past, the backend failed and told CUPS that it needed a username and password in order to succeed next time. Perhaps some configuration changed on the Windows machine.
Works after the update, even after reboot. Still not clear why openoffice writer was the only program affected.
Thanks for helping.