Trusty: testing .2 the oem session on i386 leaves the oem wifi password in place

[Dave Morley]

STEPS:
1. Put the install media into the device
2. Boot it
3. Hit a key to get to the selection menu
4. Hit F4
5. Select OEM mode
6. Complete the install
7. Cd is ejected
8. Tap enter to reboot
9. On reboot select your wifi network
10. Add the wifi password
11. Select the Prepare for shipping to end user
12. Reboot the machine
13. Boot into the user setup mode
14. Note there is a wifi connection to your network

EXPECTED:
I wouldn't expect the wifi connection to be remembered from the OEM session

ACTUAL:
The wifi connects automatically to the local wifi as it was setup in oem mode.

[Mathieu Trudel-Lapierre (cyphermox)]

This is unlikely to be new, since the network configs are saved system-wide by default, OEM setup requires wiping /etc/NetworkManager/system-connections.

In progress/High. I'm testing my changes now to make sure I didn't forget something along the way.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 2.21.12

---------------
ubiquity (2.21.12) vivid; urgency=medium

  * Clean up after NetworkManager's system-connections files in prepare job
    for oem-config: we shouldn't keep wireless connections (or any, really)
    on the system that may have been setup by OEM, unless done *after* running
    oem-prepare. (LP: #1418105)
  * Force the GTK-based installer to be visible when starting, this should fix
    it being running but hidden on some Xubuntu only-ubiquity installs, which
    meant users had to Alt-Tab to it and switch language for it to appear.
    (LP: #1423161)
  * Automatic update of included source packages: grub-installer
    1.78ubuntu25.
 -- Mathieu Trudel-Lapierre <email address hidden> Fri, 20 Feb 2015 17:15:16 -0500

[Chris J Arges (arges)]

Hello Dave, or anyone else affected,

Accepted ubiquity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/2.18.8.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Shih-Yuan Lee (fourdollars)]

I have verified ubiquity 2.18.8.10 by http://cdimage.ubuntu.com/trusty/daily-live/current/trusty-desktop-i386.iso and it does fix this issue.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 2.18.8.10

---------------
ubiquity (2.18.8.10) trusty; urgency=medium

  * Clean up after NetworkManager's system-connections files in prepare job
    for oem-config: we shouldn't keep wireless connections (or any, really)
    on the system that may have been setup by OEM, unless done *after* running
    oem-prepare. (LP: #1418105)

 -- Mathieu Trudel-Lapierre <email address hidden> Wed, 05 Aug 2015 00:43:54 -0400

[Chris J Arges (arges)]

The verification of the Stable Release Update for ubiquity has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.