There is no authentication function when printing using CUPS on the network (such as localhost: 631) while in OOo (version 1.2) is a pop-up window requesting user name and password.
cups usually does not require authentication when talking to a local printer, it uses the socket cookie. This is not related to ConsoleKit at all; if cups is misbehaving, please report a bug against cups.
Excuse me but the LibreOffice has this error nevertheless.
When both the network printer and CUPS configured and worked on other computer and if somebody wish print some documents from any applications authentication is needed. Before printing applications should open the necessary window so that users have possibility to enter one's name and password. OpenOffice knew to make it. Unfortunately, we guess this source code was erased from LibreOffice when this project was forked from OepOffice.org.
I'm unsure if this report was filed against the right component, feel free to reassign. The issue is real, though.
The problem arises when printing to a network printer, e.g. over IPP, that requires a username/password combination. We have such printers in our enterprise environment. They are configured in my local CUPS printers.conf with the "AuthInfoRequired username,password" option.
This works fine with Gnome programs and Firefox, but LibreOffice doesn't request any credentials from the user and printing fails.
Is this a duplicate of bug #48414?
(In reply to comment #4)
> Is this a duplicate of bug #48414?
I think so. My understanding of the original report is:
* There is no way to authenticate when printing using CUPS on the network [to a printer with AuthInfoRequired username,password in its printers.conf entry]
* Whereas, in OpenOffice.org 1.2, there is a pop-up window requesting authentication [when attempting to print to such a printer]
*** Bug 48414 has been marked as a duplicate of this bug. ***
Yes, it's the same issue. For example Evince, Firefox and OpenOffice will have an authentication popup, LibreOffice lacks this functionality which makes the printing fail.
We do set a password handler via cupsSetPasswordCB which I imagine is what should then get called under these circumstances, but it doesn't work for me either while it does in evince.
Apparently we need to search for auth-info-required in the cups attributes and set auto-info on the job. afaik we never did this and either OOo 1.2 doesn't/didnt work, or worked for some unrelated reason
Created attachment 104625 [details]
something along these line, if I can figure out the right way to transmit the username+password to cups
Adolfo, Caolán, *
Setting back to NEW. I could be wrong butI don't believe the commit listed (from bug 84757) is actually against this CUPS authentication issue--although it was annotated such in gerrit review, removed the whiteboard notation.
I've found a workaround - you can set LibreOffice to use the system's native print dialog.
- Navigate to Tools -> Options -> LibreOffice -> Advanced.
- Check "Enable experimental features"
- Change to LibreOffice -> General tab
- Under heading "Print dialogs", Uncheck "Use LibreOffice Dialogs"
I hope this provides some relief to users who have been waiting a long time for a fix
The workaround of using native print dialogs fails on Gnome 3.22 (Debian unstable), where it crashes OOo 5.2.2 with warnings (see Debian bug#839701):
GLib-GObject-CRITICAL **: g_object_new_valist: invalid unclassed object pointer for value type 'GtkPrinter'
Gtk-CRITICAL **: gtk_printer_get_backend: assertion 'GTK_IS_PRINTER (printer)' failed
A more reliable workaround might instead be to print to PDF.
I've reported the native (gtk3/gnome) print dialog crash in bug#102999.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
*** Bug 114590 has been marked as a duplicate of this bug. ***