This is not a YaST problem, it's related to the hotplug-system. As the system completely changed, I'm not sure what information is required.

Christian: Can you help here? If not, please reassign it or assign it back to us.

I guess it's best to ask coolo. 

Why would you want to configure the USB device twice? If it's configured, it's configured and works.

Yeah I know this may sound a bit weird, but sometimes I remove devices from YaST when I don´t need them. And also when I test hardware and remove it later I don´t want configurations for that devices remain on my system, IMHO removing a device from YaST should put the system in the state where it was before installing the device (just like in Windows for example, when I re-plug such a device I´m asked again to install it).

I'm afraid you need to tell us what device that is as this is done per yast module

How do you 'remove the configuration'?

It´s a WLAN USB adapter
I remove the device from YaST "network" and then unplug it.

Ok, this is a conceptual problem in YaST, then. YaST would have to delete
the stored config file or probably better set the 'configured' status
to 'new'.

Michael, can you check that this works for you? You can use e.g.
'hwinfo --usb' to get the UDI for your device, locate the config
file (/var/lib/hardware/udi/<your_UDI>) and change the key
'hwinfo.configured' from 'yes' to 'new'. You should get a popup
when you plug the device in after that.

Yes it works as you said.
Just from my perspective as a user (or better "tester" *g). When I remove a device from YaST2 I mean I don´t use it any more and I want the settings to be deleted. Just like in e.g. Windows device manager. No settings or udev rules should remain. If I just unplug an USB adapter the configuration stays of course but when I explicitely delete it it should be deleted. Then, when I insert the device again the hardware is again seen as "new" and the popup is displayed.

IMO you are right. YaST should set the 'configured' state to 'new' for
hardware it removes.

this is a job for yast2-network

... but may be a feature request for other yast modules as well
@emap: do you take care of that?

I opened a new bug about that (and other things which go into the same category) for 10.1

Coolo, I think that at least yast2-network does not touch the configured status. Who changes it from unconfigured to configured? The applet when it runs yast?

it can't, that information is stored in /var/lib/hardware as root. This is done somewhere in yast - Steffen is your contact person I guess.

It's done in yast. There's a status change function somewhere.

Reassigning to the new maintainer of yast2-network.

Steffen, do we have any documentation about that?
It's not clean for me what to do

You'd have to run the ycp-equivalent of hd_change_config_status(); see sample
C-code below. 'id' is either (hd_t)->uid or (hd_t)->unique_id.


hd_data_t *hd_data;
hd_status_t status = { configured:status_new };
const char *id = "/org/freedesktop/Hal/devices/pci_1106_3059";

hd_data = calloc(1, sizeof *hd_data);
hd_change_config_status(hd_data, id, status, NULL);
hd_free_hd_data(hd_data);
free(hd_data);

thanks, got it!
reminder for me(example):
file /var/lib/hardware/udi/org/freedesktop/Hal/devices/pci_10ec_8180
hwinfo.res.interrupts = { '169,1818818,1' }
hwinfo.res.memory = { '0xe6000000,0x200,0,3,1' }
hwinfo.res.io = { '0xa000,0x4000,0,3' }
hwinfo.hwclasslist = '00000220000000'
hwinfo.sysfsbusid = '0000:16:00.0'
hwinfo.sysfsid = '/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0000:16:00.0'
hwinfo.subdeviceid = 98688 (0x18180)
hwinfo.subvendorname = 'Realtek Semiconductor Co., Ltd.'
hwinfo.subvendorid = 69868 (0x110ec)
hwinfo.devicename = 'RTL8180L 802.11b MAC'
hwinfo.deviceid = 98688 (0x18180)
hwinfo.vendorname = 'Realtek Semiconductor Co., Ltd.'
hwinfo.vendorid = 69868 (0x110ec)
hwinfo.revisionid = 32 (0x20)
hwinfo.baseclass = 2 (0x2)
hwinfo.slot = 5632 (0x1600)
hwinfo.bus = 4 (0x4)
hwinfo.active = 'unknown'
hwinfo.needed = 'no'
hwinfo.available = 'yes'
hwinfo.configured = 'no'
hwinfo.hwclass = 'network'
hwinfo.model = 'Realtek RTL8180L 802.11b MAC'
hwinfo.parentid = '4Ivu.QoLDkQcpy16'
hwinfo.uniqueid = 'm862.moeRe+D9b3F'
info.udi = '/org/freedesktop/Hal/devices/pci_10ec_8180'


edit "hwinfo.configured"

Sorry for long delay.
Unfortunate it's not enought - whole configuration file must be be removed.

And second - this seems per-user depend because of suseplugger configuration - UDI is stored in ~/kde/share/config/susepluggerrc

KDE-maintainers: is that possible to improve suseplugger to ignore devices in ~/kde/share/config/susepluggerrc without /var/lib/hardware/udi/$UDI ? I mean to show popup when I remove /var/lib/hardware/udi/$UDI configuration?

When you'll be able to provide requested informations (from comment #20), reopen this bug.