Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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):
libreoffice-core-4.0.4.2-9.el6.x86_64
How reproducible:
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.
Actual results:
After step 3. libreoffice print dialog does not show the new printer.
Restart libreoffice, and the print dialog now shows the new printer.
Expected results:
After step 3. libreoffice print dioalog should show the new printer.
Additional info:
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.
Thanks.
BTW - removal of printers cause the same issue in reverse - print queues for non-existent printers are shown.
This should fix that as well.
Comment 5RHEL Program Management
2014-03-26 00:14:54 UTC
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.
http://rhn.redhat.com/errata/RHBA-2014-1423.html