phablet-config: unplugging device before reboot finishes causes tight-loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
phablet-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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/
main()
File "/usr/bin/
args.func(adb, args)
File "/usr/bin/
adb.
File "/usr/lib/
call(cmd)
File "/usr/lib/
subprocess.
File "/usr/lib/
raise CalledProcessEr
subprocess.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: phablet-tools 1.0+14.
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelMo
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)
PackageArchitec
SourcePackage: phablet-tools
UpgradeStatus: Upgraded to trusty on 2014-02-05 (68 days ago)