I recently reviewed OpenOffice 2.0.1- running on Windows. Admittedly, my experience wasn’t the best that I have had with software but after a few bumps I got things working. It is fair to say that I did not read the documentation where they warn not to install 2.x over the top of 1.x. Since I never had a problem before I figured that just installing an upgrade would work like most other software - it wasn’t of course.
Today’s post comes on the heels of upgrading to OOo2 on the K12LTSP install that runs over at the office. This is a Fedora Core 4 based install. I was recently informed that OOo didn’t print - at all. I spent the better part of two days trying to get printing to work, afterall it was only OOo that refused to print. After searching for other people experiencing *nix printing problems I ran across a few notes, reminding me that once upon a time, on my own RedHat 6.2 system I had to run spadmin (renamed to oopadmin in newer versions of OOo)…. to configure the printer to work with OOo. I have never had to configure the printer on the K12LTSP machines. They use CUPS very well, even sharing the printer with Windows based machines through Samba. Now, though, through some strangeness I had to configure the printer under OOo. I found spadmin - not renamed to oopadmin on K12LTSP, but renamed on Debian based systems, and most likely in the main package from openoffice.org. I ran spadmin, and a selection list of printers came up. There was no choice to use the system default, no choice to point to CUPS, and dammit no choice to use the printer that was hooked directly up to the machine. So not only did I have to set up a printer twice for use with this program, but it didn’t even see the drivers that were already available… including the one that drives the printer that we use.
After more ‘net searching (I was trying to find the “right” format for print drivers, OOo looks like it uses a postscript type printer driver file as it will only look for files with a .ps extension) I ran across a posting that reads in part:
“edit psprint.conf and change:
Command=
to
Command=/usr/bin/kprinter”
Amazingly, that worked; until I installed the OOo upgrade from v 2.0 to 2.0.1… then I had to do it again. So whether it is the combination of K12LTSP and OpenOffice.org that doesn’t print, or the fact that somewhere in the configuration OpenOffice.org changed the print settings doesn’t really matter. The point is that I shouldn’t have to install a different printer for each piece of software that I run.
Despite the fact that OpenOffice.org is a great piece of software -I dare say it not only challenges that “Other Office Suite”, it beats it in most areas - little idiosyncracies like “breaking” when installing over the top of the previous version - even if warned about (hardly anyone really reads the installation docs, and then not for every single version upgrade) - and for its convoluted printer setup in Linux based systems, choosing to use an entirely different set of print drivers than the ones actually used to every other program on the system - the only way that I found the answer to this was to search the internet for user complaints to mailing lists - could prevent some people from installing it for their use.
The printer configuration wasn’t in the setup or installation guides available from openoffice.org.
Luckily, the print issues did not cost my company any money - beyond the value of my time. Had this been a situation where we needed the docs immediately this would have been a different story and OOo would have lost.