Bug 445543

Summary: Printer module Test Connection does not work
Product: [openSUSE] openSUSE 11.1 Reporter: Atri Bhattacharya <badshah400>
Component: YaST2Assignee: Johannes Meixner <jsmeix>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: jsmeix
Version: Beta 5   
Target Milestone: RC 2   
Hardware: 32bit   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Atri Bhattacharya 2008-11-17 05:27:08 UTC
In the connection wizard for the printer module in yast, the Test Connection button does nothing. In openSUSE 11.0 this used to inform me if I had, for instance, given the correct IP address for a printer connected over a network.
Comment 1 Alexander Orlovskyy 2008-11-17 14:45:01 UTC
Please provide y2logs.
more info on http://en.opensuse.org/Bugs/YaST
Comment 2 Johannes Meixner 2008-11-21 14:07:52 UTC
Known issuse.
Comment 3 Stanislav Visnovsky 2008-11-27 18:32:43 UTC
Johannes, is this fixed now?
Comment 4 Johannes Meixner 2008-11-28 07:57:45 UTC
Michal,
Stanislav,
anybody else,
feel free to re-assign any bug regarding the new YaST printer module
i.e. regarding yast2-printer in openSUSE 11.1 (and later ;-)
to me.
Comment 5 Johannes Meixner 2008-11-28 08:51:54 UTC
Fixed as good as possible at the moment in
yast2-printer version 2.17.47

See
https://bugzilla.novell.com/show_bug.cgi?id=440903#c16
Comment 6 Johannes Meixner 2008-11-28 12:19:08 UTC
In yast2-printer version 2.17.48 which should be
available soon via the openSUSE build service at
http://download.opensuse.org/repositories/home:/jsmeix/
the connection tests in the Connection Wizard should
again work as good as before in the old yast2-printer module:

I removed the nasty inline bash scripts in connectionwizard.ycp
and replaced them by our well known external tools from
the old yast2-printer module test_device, test_remote_socket,
test_remote_lpd, test_remote_ipp, test_remote_smb, and
test_remote_novell and called them in a safe environment
via Printerlib::ExecuteBashCommand (in particular using a safe
locale which is required for the scripts to work correctly)
and provided an error popup with details when a test fails.