Installing emulator device fails if apt is running in background
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-touch-meta (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Environment on which this bug was seen:
Ubuntu 14.04 64-bit desktop installed as a VM on VMware Player 6.0 on Ubuntu 12.10 64-bit desktop.
Qt Creator 2.8.1
May be helpful:
lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
apt-cache policy ubuntu-sdk
ubuntu-sdk:
Installed: 1.110
Candidate: 1.110
Version table:
*** 1.110 0
500 http://
100 /var/lib/
How to reproduce this bug:
1. Run an apt instance in background which is installing a package(do not run apt-get update, which allows another apt instance to run).
2. Open ubuntu-sdk and go to Devices -> Emulators and press OK.
3. Now go to logs, you will see the following error message:
-------
E
:
Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E
:
Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Checking installed emulator package.
The package is not installed.
Detecting device..
* there is no device connected.
-------
4. You will notice that even downloading packages failed because of which installing an emulator device failed.
What I expected?
Installing an emulator device will wait for the background apt to exit and then continue installing the packages required to install an emulator.
Possible solution:
Implement a queue which will wait for background apt to exit and then continue downloading required packages.
description: | updated |
description: | updated |