Bug 113570 - YaST2 printer config fails to list configured CUPS printer
Summary: YaST2 printer config fails to list configured CUPS printer
Status: RESOLVED DUPLICATE of bug 113305
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-27 17:55 UTC by Lenz Grimmer
Modified: 2005-08-30 09:38 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
ylog (18.37 KB, text/plain)
2005-08-27 17:56 UTC, Lenz Grimmer 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lenz Grimmer 2005-08-27 17:55:24 UTC 
I configured printing to a remote CUPS print server and the configuration seems
to have succeeded. However, the YaST2 printer module does not display the
configured printer in it's list.

I performed the following steps:

 - Start YaST2
 - Select Hardware -> Printer
 - Click "Add"
 - Choose "Print via CUPS Network Server"
 - Click "Next"
 - Choose "CUPS Client-Only"
 - Click "Next"
 - Confirm the Popup with "Yes"
 - Entered "192.168.2.106" as "Server Name"
 - Click "Test Repote IPP Access", Confirm with "OK"
 - "Use Server's default queue" is checked
 - Click "OK"

The configuration returns to the Printer Configuration start screen, the list of
configured printers is still empty. Exiting the module with OK saves the
settings and the printer is indeed configured and accessible ("lpq" shows the
printer queue status correctly)
Comment 1 Lenz Grimmer 2005-08-27 17:56:21 UTC 
Created attachment 47869 [details]
ylog

y2log from starting the Y2 control center until finishing the printer
configuration.
Comment 2 Michal Zugec 2005-08-30 09:38:55 UTC 
Its the same problem as bug 113305

*** This bug has been marked as a duplicate of 113305 ***