phablet-config: unplugging device before reboot finishes causes tight-loop

[Tony Espy]

I ran 'phablet-config writable-image' and then unplugged the device ( a mako running image #297 ) during the device reboot. This caused phablet-config to go into a tight loop continually writing the message:

error: device not found

I wasn't able to break out of this loop with Ctrl-C nor Ctrl-Z. Killing the term finally did the trick.

The second time I tried this, after going into the tight loop, I plugged the device back in and got the following backtrace:

error: device not found
Network connection failed to become active.
Traceback (most recent call last):
  File "/usr/bin/phablet-config", line 249, in <module>
    main()
  File "/usr/bin/phablet-config", line 246, in main
    args.func(adb, args)
  File "/usr/bin/phablet-config", line 119, in _handle_writable_image
    adb.wait_for_network()
  File "/usr/lib/python2.7/dist-packages/phabletutils/device.py", line 89, in wait_for_network
    call(cmd)
  File "/usr/lib/python2.7/dist-packages/phabletutils/device.py", line 26, in call
    subprocess.check_call(args, shell=True)
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'phablet-network --skip-setup' returned non-zero exit status 1

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: phablet-tools 1.0+14.04.20140414.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 15 12:21:13 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-09-12 (215 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130912)
PackageArchitecture: all
SourcePackage: phablet-tools
UpgradeStatus: Upgraded to trusty on 2014-02-05 (68 days ago)