Description of problem:
Libreoffice does not recognize new printers that are being created on a local print server while the app is running.
Version-Release number of selected component (if applicable):
Always - libreoffice 3.x had the same problem
Steps to Reproduce:
1. Start cups with X printers defined
2. Start libreoffice (tested with writer and calc) and check printer targets that are visible. Should show all X printers from the local print server.
3. While libreoffice is running, add a new printer to the local print server. Local-attach or network printer does not seem to make any difference.
After step 3. libreoffice print dialog does not show the new printer.
Restart libreoffice, and the print dialog now shows the new printer.
After step 3. libreoffice print dioalog should show the new printer.
I wonder if visiting "printer settings..." and then cancel it and then visit print if that would refresh it.
It looks like that should work as a workaround, i.e. launch the "printer settings" dialog and then revisit print and it should be there.
What I can do safely is to refresh the printer list when the print dialog is launched as well as the printer settings dialog (http://cgit.freedesktop.org/libreoffice/core/commit/?id=02efbed152a3a9e364cdb73628af0aed0f5d6f7a)
Additionally we could do like the gtk print dialog does and continuously poll for new printers every 200ms while its open, but that's a bit riskier and presumably redoing file->print to refresh the list is an acceptable compromise.
Doing a refresh once when the dialog is invoked is a sufficient compromise.
This solves the issue of libreoffice running all day with different docs, and printer getting added during the day.
BTW - removal of printers cause the same issue in reverse - print queues for non-existent printers are shown.
This should fix that as well.
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.