Bug 476221
| Summary: | psprint.conf should be flagged as a config file in openoffice.org-core RPM | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Dan Astoorian <djast> |
| Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.4 | CC: | llim |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-02 09:09:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dan Astoorian
2008-12-12 15:43:03 UTC
FWIW It is not recommended to use spadmin to add a printer that OOo alone can use, just use the normal desktop printer adding software. spadmin really only exists for the moment in RHEL to give a way to support fax numbers for printing direct to fax. Okay, then /usr/{lib,lib64}/openoffice.org/share/psprint/psprint.conf should be marked as a configuration file so that the fax printers defined in that file don't get removed when OpenOffice is updated.
At our site we need to add printers via psprint.conf because we cannot use CUPS for printing due to its lack of support for user authentication. (E.g.: the GTK2 CUPS print backend does not work at all when any type of CUPS authentication is enabled; cf. bug #476232.)
Conversely, I don't see a downside to marking psprint.conf as a config file in the RPM.
In general I think this is a bad idea to need to modify the OOo config specifically to hackaround a problem, i.e. problems still persist for e.g. evince and the rest of the desktop stack. That said, it doesn't hurt to be able to at least print from OOo. Yes, needing to modify the OOo config to work around a problem is less than ideal; however, being unable to do so where no better solution exists is worse. psprint.conf is, by its suffix, clearly a configuration file: if the user customizes it (irrespective of whether that customization is recommended or not), it is difficult to understand how destroying these customizations during a package update can be the right thing to do. checked in for >= 2.3.0-6.11 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1248.html |