Bug 1257635
Summary: | [fix available] sometimes LO doesn't see cups printers | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Bill Sanford <bsanford> |
Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | astepano, dtardon, lmiksik, modehnal, tjamrisk, tpelka |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-03 19:01:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1297830, 1313485 |
Description
Bill Sanford
2015-08-27 13:54:15 UTC
Fresh install of RHEL-7.2 + yum update to LibreOffice 4.3.7.2 (etc) + vpn into redhat network. Followed the exact steps to reproduce and I get a full list of printers. But if I leave libreoffice alone for a while, and revisit then it says just "generic printer", but another attempt to launch the print dialog will show them again. Maybe there is a timeout issue or something of that nature at work. *** Bug 1257715 has been marked as a duplicate of this bug. *** We're calling httpConnectEncrypt and then httpClose on its get and then using cupsGetDests and sometimes we get 0 printers back. If I change this to the more logical httpConnectEncrypt and use its result with cupsGetDests2 and then clean up with httpClose I consistently get results so I reckon we can solve this that way. Fixed by rebase to 5.0.x: bug 1290148. Verified RHEL-7.3-20160901.1 libreoffice-5.0.6.2-3.el7.x86_64 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. https://rhn.redhat.com/errata/RHSA-2016-2579.html |