[Bug 1579988] Re: Image will not delete

If you are looking for a quick way to 'start over', this is what I did: sudo service lxd stop sudo service lxd-bridge stop sudo rm -rf /var/lib/lxd sudo mkdir /var/lib/lxd sudo service lxd start sudo service lxd-bridge start sudo lxd init -- You received this bug notification because you are a

Re: [Bug 1579988] Re: Image will not delete

What is the recommended method of recovery? I assume deleting the zpool will break sync with data stored anywhere else (if there is anything stored outside /var/lib/lxd?). On Tue, May 10, 2016, 8:41 AM Stéphane Graber wrote: > In such cases, container creation is still

[Bug 1579988] [NEW] Image will not delete

Public bug reported: lxc version: 2.0.0 Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial Linux 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 Not entirely sure how to reproduce this. All my other images were able to be deleted with no

[Bug 1579981] [NEW] LXD overwrites /etc/apt/sources.list during 'lxc image copy'

Public bug reported: lxc version: 2.0.0 Distributor ID: Ubuntu Description:Ubuntu 16.04 LTS Release:16.04 Codename: xenial Linux 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 Steps to repeat: Computer A: lxc launch ubuntu:xenial x {modify

[Bug 1575386] Re: Proxy issue with 16.04

Might be of use (I have to look through the capture before I can upload it), but another developer here commented (if what he notes is true, then the TCP attempt wouldn't work behind an HTTP proxy, anyway. Does you environment block all non-proxied traffic?): With the following remote:

[Bug 1575386] Re: Proxy issue with 16.04

I'll forward this bug along to one of the members of our IS department. Thanks! (I'll keep watching in case I can be of help) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575386 Title: Proxy

[Bug 1575386] Re: Proxy issue with 16.04

As a note, the last command seems to work for all use cases, so it allows me to be productive. I'm still interested in narrowing down why the cloud-images.ubuntu.com source doesn't seem to be working. $ lxc launch images:ubuntu/xenial/amd64 mine Creating mine Retrieving image: 100% Starting mine

[Bug 1575386] Re: Proxy issue with 16.04

The output of strace is attached. Output of the second command seemed to work just fine: $ lxc image info images:ubuntu/xenial/amd64 Fingerprint: 2c09a4b4143fa9d87f9e8399e1f1883cc11712e94a571b2f41bf68a455cd6fe7 Size: 76.92MB Architecture: x86_64 Public: yes Timestamps: Created: 2016/04/27

[Bug 1575386] Re: Proxy issue with 16.04

Works fine, with and without the leading proxy variables set (pulls from environment when not set in command). I can see the full file (trailing lines included for reference): "com.ubuntu.cloud:server:14.10:amd64", "com.ubuntu.cloud:server:14.10:i386" ], "path":

[Bug 1575386] Re: Proxy issue with 16.04

Below are the results. (The last command was running while I tried running the first two commands in another window, but no additional log entries were generated after startup) In case it is really just an issue with the company's proxy configuration (blocking specific ports, etc...), are the

[Bug 1575386] [NEW] Proxy issue with 16.04

Public bug reported: This seems to be a new issue as LXD 2.0.0 was working perfectly well in 14.04 prior to re-installation. Currently on 16.04 with 'lxc version' of 2.0.0. Issue is as follows: lxc launch ubuntu:xenial test Creating test error: Get

[Bug 1574702] [NEW] 'snap' does not appear to use proxy settings

Public bug reported: Configured proxy variables from /etc/environment: http_proxy=http://proxy.company.com:8080 https_proxy=http://proxy.company.com:8080 HTTP_PROXY=http://proxy.company.com:8080 HTTPS_PROXY=http://proxy.company.com:8080 no_proxy=127.0.0.1,localhost,10.0.0.0/8

[Bug 1292961] Re: Xorg crashed with SIGABRT

I had the same problem. Installing the Intel Graphics Installer and updating to the latest Intel driver has, at least so far (normally crashes in seconds and I'm up to 10 minutes without a crash), has fixed the issue. https://01.org/linuxgraphics/downloads/2014/intelr-graphics-

[Bug 1298255] Re: Xorg crashed with SIGSEGV after logging in to VMware VCenter in rdesktop session

*** This bug is a duplicate of bug 1292961 *** https://bugs.launchpad.net/bugs/1292961 I had the same problem. Installing the Intel Graphics Installer and updating to the latest Intel driver has, at least so far (normally crashes in seconds and I'm up to 10 minutes without a crash), has fixed

[Bug 1152912] Re: TortoiseHg doesn't start

I can confirm kmansoft's diagnosis: In /usr/lib/python2.7/dist-packages/tortoisehg/hgqt/ I renamed qtlib.pyc - qtlib.pyc.backup I backed up qtlib.py - qtlib.py.backup I commented out lines 27-32 and was able to start and use TortoiseHg normally. (Not the recommended fix, but it served my

[Bug 621467] [NEW] BUG: scheduling while atomic: run-parts/1501/0x10000001

Public bug reported: Occurred on Alpha 3 during first boot after updates. Everything seems to work fine. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-16-generic 2.6.35-16.22 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-16.22-generic

[Bug 621467] Re: BUG: scheduling while atomic: run-parts/1501/0x10000001

** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/621467/+attachment/1506169/+files/AcpiTables.txt ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/621467/+attachment/1506170/+files/AlsaDevices.txt ** Attachment added: AplayDevices.txt

[Bug 317094] Re: meta bug to collect lshal touchscreen info

** Attachment added: Output for Chinese http://launchpadlibrarian.net/32474944/evtouch_hal.out -- meta bug to collect lshal touchscreen info https://bugs.launchpad.net/bugs/317094 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 317094] Re: meta bug to collect lshal touchscreen info

Netbook touchscreen output. ** Attachment added: Output for Chinese netbook http://launchpadlibrarian.net/32474952/evtouch_hal.out -- meta bug to collect lshal touchscreen info https://bugs.launchpad.net/bugs/317094 You received this bug notification because you are a member of Ubuntu Bugs,