Kubuntu Add printer wizard - network printer scan gives incorrect warning

[Brijam]

Kubuntu Dapper Flight 5:
System Settings -> Printers -> Add Printer -> Network printer (TCP) -> Settings

When you add the correct subnet, an incorrect warning popup appears:
You are about to scan a subnet (10.1.0.*) that does not correspond to the current subnet of this computer (127.0.1.*). Do you want to scan the specified subnet anyway?

Not sure why the wizard thinks it will find a network printer attached to localhost.

The wizard should correctly pull the current subnet and fill out the proper values.

[Manuel López-Ibáñez (manuellopezibanez)]

guessing package

[Till Kamppeter (till-kamppeter)]

Dapper Flight 5 is a development snapshot of Dapper and is not supported any more as Dapper was already released. Please test on final Dapper or better on Edgy.

[Brijam (brian-opensourcery)]

tested on final Dapper. There are still three issues with this UI if we are shooting for being ultra user-friendly:

1) 127.0.0 is the default entry for a network printer scan, obviously no network printer could be connected to that subnet. The app should automagically pull the current subnet and use that as the default entry. I doubt most people have any idea what a subnet is (see #2)

2) The box for entering a subnet is too small to see the entire subnet and while there is basic data validation, the error message is useless. A better approach would force an entry into a proper subnet, perhaps by breaking the field into three fields and modifiying the validation error message to say something like "Invalid subnet address. Valid subnet addresses are in this format: x.y.y where x is a number between 1 and 255 and y is a number between 0 and 255. For example, 192.168.0 or 10.0.0. Typical subnets for home networks are 192.168.0 or 192.168.1"

Thinking about it more, it doesn't seem to make sense to require manual entry of the subnet at all. If the subnet can't be detected there is something wrong with the network and the scan will fail anyway.

[Brijam (brian-opensourcery)]

These same bugs still exist in Edgy.

[Kieran Hogg (xerosis)]

Still present as of Gutsy tribe 1.

[Brijam (brian-opensourcery)]

Still present in 7.10.

[Brijam (brian-opensourcery)]

Still present in 8.04. Any chance this will be fixed in KDE 4.1?

[Harald Sitter (apachelogger)]

Yes. This complete feature was removed from KDE 4 (at least for now), therefore I am closing as invalid.

Should the feature reappear and still show this kind of behavior, please reopen this bug.