Comment 10 for bug 1867465

@Steve Langasek, thank you for your time triaging that. I was thinking the problem is that the installer doesn't handle this in a user-friendly way. From my perspective the installer should:

1. Inform the user that it located a possibly better driver, and the connection will drop. (In my case, I had a seemingly perfect wifi connect, then it dropped without explanation. I was clicking, trying to get it to reconnect -- when it probably wasn't ready yet. I almost got up to reboot the router. An informative message would be nice if the network is already connected.).

2. An additional courtesy (not as important as #1) would be to detect that the wireless interface reappeared under a different name, and connect using that. I.e., I don't think the underlying process for replacing drivers has to preserve the name. It seems like the installer could know that it's replacing a driver for an active connection, and anticipate that the device name will change.(But, manually reconnecting wouldn't be bad. I think what's bad is #1, not knowing what's happening.).

Thanks. If either point is worth pursuing or advancing to the installer maintainer, I know that it's low priority. I'm sure it doesn't affect many people. Once someone knows what's happening, they can live with it, etc. (It just seems rough for the first-timer. A courtesy msg seems appropriate so the user knows what's happening. I've used Linux for quite some time. It never occured to me that it was installing the 3rd-party driver then.).