Issue 391

Summary: OpenOffice fails to find default printer under CUPS
Product: General Reporter: issues@www <issues>
Component: codeAssignee: sander_traveling
Status: CLOSED NOT_AN_OOO_ISSUE QA Contact: issues@www <issues>
Severity: Trivial    
Priority: P3 CC: issues, sander_traveling
Version: 614   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description issues@www 2001-02-08 03:06:04 UTC
I just downloaded OpenOffice6.0.  When I start the application './soffice' I get
the following error message:

SIOCGIFADDR got '00:00:00:00:00:00'
SIOCGIFADDR got '00:00:00:00:00:00'
Could not connect to Xprint server. Xprinting disabled.

When I attempt to access 'Printer Settings' I get the following:

No default printer found.
Please choose a printer and try again.

I am using Mandrake 7.2 with KDE 2.1 beta and the latest stable build of CUPS
(cups-1.1.6-3.1mdk).  I have an HP LaserJet set as my default printer under
CUPS.  I am currently a user of Star Office 5.2 and am very impressed with the
new Open Office product.
Comment 1 thorsten.martens 2001-02-08 11:46:02 UTC
Seems to be the known problem with Xprnt and not with openoffice. So please 
check this one.   
Comment 2 sander_traveling 2001-02-12 19:03:50 UTC
As it is clear that he is not running Xprint sever - or is not pointing the
XPRINTER varaible at the Xprint server "display", I don't see an issue here ...

There is documentation about teh Xprint server and how it's interactions with
OpenOffice.org application suite on the printing.openoffice.org web site.
Comment 3 michael.bemmer 2003-03-12 14:13:55 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-12 14:33:01 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.