Bug 392266

Summary: YaST2 - Printing Wizard crashes when attempting to setup network printer on system installed from GNOME LiveCD
Product: [openSUSE] openSUSE 11.0 Reporter: Eric Ward <eward>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot of error
y2log

Description Eric Ward 2008-05-19 19:48:27 UTC
Problem -
If the user attempts to setup a network printer using the /sbin/yast2 printer wizard on a system that was installed from the GNOME LiveCD, the wizard will crash near the end and the printer setup fails.

Steps to Reproduce -
- Install a system to the machines harddrive using the openSUSE 11.0 beta 3 GNOME Live CD
- After rebooting the system, open the YaST2 Printer dialog
- In the Printer Wizard under the "Printers and Queues" section select to "Add" a new Printer.
- When prompted select the "Network Printers" radio button and press next
- When prompted select the "Print Directly to a Network Printer" radio button and press next
- When prompted select the "Direct TCP Port Printing" radio button and press next
- Enter the HostName of Printer Server. On my test system I pointed to the following HPLaserJet 8150 DN at 137.65.135.7
- Once you've entered the IP address of the Print Server press next
- When prompted for Queue Name and Spooler Settings, just press the next button.
- On the Printer Queue Edit Dialog press the next button. At this point the Wizard should crash. See attachment for error message.



Expected Behavior
- The Printer Wizard should work when run from a system installed from a GNOME Live CD.
Comment 1 Eric Ward 2008-05-19 19:48:56 UTC
Created attachment 216603 [details]
screenshot of error
Comment 2 Eric Ward 2008-05-19 19:51:27 UTC
Created attachment 216604 [details]
y2log
Comment 3 Michal Zugec 2008-05-20 10:43:58 UTC

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