Apache OpenOffice (AOO) Bugzilla – Issue 18287
lpc not found
Last modified: 2004-04-24 20:05:59 UTC
My linux system has lpc-cups,but not lpc, so every time I start OOo from a terminal window (RC3, but showed up from RC1 on), I get a message "lpc not found." I have no idea why the message.
I don't know for certain if this is a bug, since I'm not certain if "lpc" and "lpc-cups" are the same thing.
This no longer occurs in 1.1.0 or 1.1.1a. It should be marked as "fixed" or "worksforme."
Joost->Robert: As OpenOffice.org wasn't able to know which printing system was in use it had to call all printer status commands like lpstat, lpc and lpq to get information about the printer queues. Unfortunately the console message of lpc wasn't suppressed. As you mentioned I'll close this issue as worksforme.
JA: closing issue
sparcmoz-->rblackeagle: can you try the latest 1.1.1rc? I get this with linux sparc build of 1.1.1rc2 jim@sun:~/OpenOffice.org1.1.1$ ./soffice sh: line 1: /usr/sbin/lpc: No such file or directory sh: line 1: lpc: command not found sh: line 1: lpstat: command not found
I get it under 1.1.0, but not under 1.1.1rc on linux.
confirming with 1.1.1rc3 linux build OOo will output a "X command not found" message on the console, when one of the following commands could not be found. in order of probing: 1) lpc 2) lpstat Note: if lpc, lpstat _and_ lpq is missing in the system, probing for a nonexistent _lpq_ will not result in a "X command not found" console message.
It makes sense. However, as I mentioned, apparently 1.1.1rc takes note that CUPS is being used and does not probe for lpc as the message no longer appears.
SBA: It is not productive to have the issues mutate. The initial problem is solved. It makes no sense to make people read through 10 to 20 comments until the "current" issue is clear. Much better: If you end up somewhere, close the issue and write a new one. This is the case when the initial submitter tells: "My problem is solved." Maybe you should have a look at issue 1820 to get my point: When pasted to a Writer document, the comments sum up to more than 40 pages of text! Some comments "somewhere in the middle" clearly show that the respective "contributers" did NOT take the time to read the rest above, thus continued to "run in circles". According to Joosts and Roberts comments "in the upper half" this one gets closed as worksforme. Please leave it there. There is no way to erase time-eating (thus unproductive) comments about "initial problems" that at most gave the hint tp current findings. Feel free to write new issues. But don't make others read outdated stuff by keeping solved issues open. Last not least: Even closing a "tracked-down, really existing defect" makes sense: Sometimes it really does take time (and many comments) to get to a core problem. That's not unusual. But once the "final" description is "available", how to avoid time-eating read-through all the outdated comments? Only by closing such an issue and write a new one with a short and clear "step-by-step" problem description. This is the kind of issues we "love" to proceed. :-) If you disagree, read through issue 1820 (all the 130-plus comments!) and then tell me (1) how long it took you (2) a way to avoid such "books". Thank you for your comprehension.
SBA: Set to Worksforme.
SBA: Closed.
The longest comment was by sbc. In any case, the problem is fixed.