This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge
in Saucy.
Steps to reproduce:
- Install maas using the saucy server install CD.
- Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic
- Configure the rest of MaaS, click the import boot images in the UI
Further information:
Relevant stacktrace: https://pastebin.canonical.com/99705/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1240215
Title:
changing the default arches in
Sorry, I used a private pastebin, here's the public equivalent:
http://pastebin.ubuntu.com/6340916/
@rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try
and report back!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll
subscribe to bug 1181334 instead! Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1240215
Can confirm, it would save us (the landscape team, but also other users
I wager) a lot of time and disk space if we could only download amd64
images and use that successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Yes, I should have attached that log file in my initial report. It's the
same problem :(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1247886
Title:
squid-deb-proxy is not started
Changing back to juju-core since this affects me, and I'm not using LXC
containers at all.
** Package changed: lxc (Ubuntu) = juju-core (Ubuntu)
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
I hit the same problem, and don't use LXC at all on my setup. I
therefore will change this bug to point back to juju-core.
My MaaS lives in a KVM machine on my laptop.
It can PXE boot/start-stop other KVM machines living on the same NAT'ed
network.
- juju bootstrap --upload-tools works (the
For the record, this affects the precise package as well.
I would strongly recommend uploading a fixed package to the
cloud-archive:tools repository since most people installing maas will use
this (it's the recommended way).
tribaal@maas:~$ apt-cache policy squid-deb-proxy
squid-deb-proxy:
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1303617
Title:
Latest curtin version prevents Juju from
** Description changed:
Curtin version: 0.1.0~bzr124-0ubuntu1
Curtin-common: 0.1.0~bzr124-0ubuntu1
Bootstrapping a juju environment on an up-to-date trusty MAAS server
fails. The bootstrap node becomes pingable but never allows connections
to the juju agent.
Cloud init output
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1303903
Title:
sgdisk zap/clear doesn't wipe all GPT tables
To manage notifications about this bug go to:
The linked branch should help with the problem, at the cost of an extra
round-trip to the upstream archive.
** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
This is fixed since the python code (instead of bash) behaves properly
now. Closing this bug (it's old, bug triage has taken a lot of dust).
Feel free to reopen should this sting you again.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug
This should be fixed in the next version of squid-deb-proxy when it's
released.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
** Branch linked: lp:~tribaal/ubuntu/precise/opensc/fix-for-872019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872019
Title:
pkcs15 profiles not packaged, pkcs15-init not functional
To manage
Ok so I put a branch up for review and assigned this to myself.
I hope the process is correct...
** Changed in: opensc (Ubuntu)
Status: Confirmed = In Progress
** Changed in: opensc (Ubuntu)
Assignee: (unassigned) = Chris Glass (tribaal)
--
You received this bug notification
-man-
page
** Changed in: landscape-client
Assignee: Andreas Hasenack (ahasenack) = Chris Glass (tribaal)
** Changed in: landscape-client
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: landscape-client
Status: In Progress = Fix Committed
** Changed in: landscape-client (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I should have attached that log file in my initial report. It's the
same problem :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247886
Title:
squid-deb-proxy is not started when installing
Changing back to juju-core since this affects me, and I'm not using LXC
containers at all.
** Package changed: lxc (Ubuntu) = juju-core (Ubuntu)
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hit the same problem, and don't use LXC at all on my setup. I
therefore will change this bug to point back to juju-core.
My MaaS lives in a KVM machine on my laptop.
It can PXE boot/start-stop other KVM machines living on the same NAT'ed
network.
- juju bootstrap --upload-tools works (the
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge
in Saucy.
Steps to reproduce:
- Install maas using the saucy server install CD.
- Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic
- Configure the rest of MaaS, click the import boot images in the UI
Further information:
Relevant stacktrace: https://pastebin.canonical.com/99705/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240215
Title:
changing the default arches in import_pxe_files
Sorry, I used a private pastebin, here's the public equivalent:
http://pastebin.ubuntu.com/6340916/
@rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try
and report back!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll
subscribe to bug 1181334 instead! Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240215
Title:
Can confirm, it would save us (the landscape team, but also other users
I wager) a lot of time and disk space if we could only download amd64
images and use that successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the record, this affects the precise package as well.
I would strongly recommend uploading a fixed package to the
cloud-archive:tools repository since most people installing maas will use
this (it's the recommended way).
tribaal@maas:~$ apt-cache policy squid-deb-proxy
squid-deb-proxy:
** Description changed:
Landscape Client 13.07.3 has been released. We would like to get these
changes into raring, quantal, precise and lucid.
As far as released version of Ubuntu are concerned, the required pieces
of information for the needed SRU follow (as laid out in the Procedure
The lucid debdiff
** Patch added: lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff
https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879404/+files/lucid_12.05-0ubuntu0_to_13.07.3-0ubuntu0.debdiff
--
You received this bug notification because you are a member of Ubuntu
The precise debdiff
** Patch removed: precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff
https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868474/+files/precise_12.05-0ubuntu1_to_13.07.3-0ubuntu0.debdiff
** Patch removed: quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff
The quantal debdiff
** Patch added: quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff
https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879401/+files/quantal_12.05-0ubuntu2_to_13.07.3-0ubuntu0.debdiff
--
You received this bug notification because you are a member of
The raring debdiff
** Patch added: raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff
https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3879403/+files/raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff
--
You received this bug notification because you are a member of Ubuntu
The raring debdiff for 13.07.3
** Patch added: raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff
https://bugs.launchpad.net/landscape-client/+bug/1190510/+attachment/3868478/+files/raring_12.12-0ubuntu3_to_13.07.3-0ubuntu0.debdiff
** Also affects: landscape-client (Ubuntu)
Importance:
The lucid debdiff for 13.07.3
** Summary changed:
- Update raring, quantal, precise to landscape-client 13.07.3
+ Update lucid, raring, quantal, precise to landscape-client 13.07.3
** Description changed:
- Landscape Client 13.07.1 has been released. We would like to get these
+ Landscape
As said in the title, running sudo lightdm-session from a tty fails with:
x-session-manager: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol:
wl_registry_interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
(Since this is opened by hand I am unsure how to upload relevant logs)
Since some of the following updates http://pastebin.ubuntu.com/1589997/
lightdm fails to start on boot.
The Ubuntu loading screens loads, then lightdm fails.
It is possible to switch to a tty, and
So the way I fixed my installation was to downgrade libwayland0 to
1.0.3-0ubuntu2, and remove ~/.Xauthority (otherwise you can't login).
But yeah, this is introduced by using the qt5 PPA as suggested by the
phone sdk tutorial, AFAICT.
--
You received this bug notification because you are a
This is still a problem on Precise.
@keks9n - Would you provide a PPA for precise? That would be really
appreciated, worked a treat on Oneiric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/644898
** Changed in: landscape-client
Status: In Progress = Fix Committed
** Changed in: landscape-client
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When trying to load a file in the saucy version of DS9
(http://pastebin.ubuntu.com/6599685/), the program exits with the
following stacktrace: http://pastebin.ubuntu.com/6599657/
The same procedure on raring succeeds.
Steps to reproduce:
- On Ubuntu 13.10 x86_64, install
Public bug reported:
Steam for Ubuntu fails to paint its windows after upgrading to 13.04
(see attached screenshot).
Since my steam version didn't change during the upgrade to raring I
assume this is a graphics stack regression, although I am not sure if
this applies to xorg.
ProblemType: Bug
This bug was fix with the latest update to xserver-xorg-video-
intel:amd64
Marking as invalid.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303617
Title:
Latest curtin version prevents Juju from bootstrapping on
** Description changed:
Curtin version: 0.1.0~bzr124-0ubuntu1
Curtin-common: 0.1.0~bzr124-0ubuntu1
Bootstrapping a juju environment on an up-to-date trusty MAAS server
fails. The bootstrap node becomes pingable but never allows connections
to the juju agent.
Cloud init output
Public bug reported:
Upstream released a new version - 0.5
The Ubuntu package in utopic should be updated as well.
** Affects: ubumirror (Ubuntu)
Importance: Undecided
Assignee: Chris Glass (tribaal)
Status: In Progress
** Changed in: ubumirror (Ubuntu)
Assignee
The linked branch should help with the problem, at the cost of an extra
round-trip to the upstream archive.
** Branch linked: lp:~tribaal/squid-deb-proxy/refresh-ims
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303903
Title:
sgdisk zap/clear doesn't wipe all GPT tables
To manage notifications about this bug go to:
As of this morning I got 38.0.2125.111-0ubuntu0.14.10.1.1103 0 in
Utopic.
Thanks for your hard work Chad!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386455
Title:
Chromium 37 has 159 known
to submit to the
ubuntu ubumirror packaging branch.
Since this is my first contribution to Ubuntu (on the packaging side),
please feel free to point errors in the workflow/procedure :)
** Affects: ubumirror (Ubuntu)
Importance: Undecided
Assignee: Chris Glass (tribaal)
Status
** Branch linked: lp:~tribaal/ubuntu/utopic/ubumirror/1341523-upstream-
release
** Description changed:
Hi, I recently took over the upstream development of ubumirror.
I just created a new upstream release that fixes a few of the bugs
- reported here (as well as general cleanup o fthe
** Summary changed:
- New upstream release
+ Update to upstream 0.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1341523
Title:
Update to upstream 0.4
To manage notifications about this bug go
This should be fixed in the upstream reelase 0.4
(https://launchpad.net/ubumirror/trunk/0.4).
A branch against this package was openened to update the packaged verion to
upstream, but it is currently in need of sponsorship:
https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523
--
Removing myself as assignee as per
https://wiki.ubuntu.com/SponsorshipProcess
** Changed in: ubumirror (Ubuntu)
Assignee: Chris Glass (tribaal) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
This should be fixed in the upstream release 0.4
(https://launchpad.net/ubumirror/trunk/0.4).
A branch against this package was openened to update the packaged verion to
upstream, but it is currently in need of sponsorship:
https://bugs.launchpad.net/ubuntu/+source/ubumirror/+bug/1341523
--
This is fixed since the python code (instead of bash) behaves properly
now. Closing this bug (it's old, bug triage has taken a lot of dust).
Feel free to reopen should this sting you again.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug
This should be fixed in the next version of squid-deb-proxy when it's
released.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification was done for individual bugs on lucid.
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401523
Title:
Update lucid, precise, trusty, utopic to
Verified with the package in lucid-proposed. As noted there is no
arm64 port for lucid, so I simply asserted the code was there (and it
is).
tribaal@ubuntu:~$ apt-cache policy landscape-client
landscape-client:
Installed: 14.12-0ubuntu0.10.04
Candidate: 14.12-0ubuntu0.10.04
Version table:
Verified with the package in lucid-proposed:
tribaal@ubuntu:~$ apt-cache policy landscape-client
landscape-client:
Installed: 14.12-0ubuntu0.10.04
Candidate: 14.12-0ubuntu0.10.04
Version table:
*** 14.12-0ubuntu0.10.04 0
500 http://deb-mirror.habari.co.tz/ubuntu/
Verified with the package in precise-proposed:
tribaal@ubuntu:~$ apt-cache policy landscape-client
landscape-client:
Installed: 14.12-0ubuntu0.12.04
Candidate: 14.12-0ubuntu0.12.04
Version table:
*** 14.12-0ubuntu0.12.04 0
500 http://deb-mirror.habari.co.tz/ubuntu/
Verification was done for all individual bugs on Precise.
All individual bugs have been verified for all target releases.
** Tags removed: verification-needed
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verified with the pacakge in precise-proposed. I checked the code is the
same as the utopic version that succeeds at solving the bug.
tribaal@ubuntu:/usr/lib/python2.7/dist-packages/landscape$ apt-cache policy
landscape-client
landscape-client:
Installed: 14.12-0ubuntu0.12.04
Candidate:
I tested 14.12-0ubuntu0.14.04 and this fixes the bug for me (no problems
discovered).
Changing to verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(Re-flipping the tag since it appears it was done a bit prematurely)
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401523
** Also affects: nvidia-graphics-drivers-346 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-346-updates (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The nested LXC functionality seems to be broken on Vivid, at least with
the following setup:
Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC)
What happens:
The Inner LXC start command fails when trying to start with:
http://pastebin.ubuntu.com/10682639/
( 631 cgroup
Public bug reported:
The nested LXC functionality seems to be broken on Vivid, at least with
the following setup:
Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC)
What happens:
The Inner LXC start command fails when trying to start with:
http://pastebin.ubuntu.com/10682639/
( 631 cgroup
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications about this bug go to:
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications about this bug go to:
So, the new lxcfs in vivid-proposed does *not* solve this particular
problem.
Again, running the daily PPA code solved this, but that means using the
ppa for both vivid and trusty, not just vivid.
Don't hesitate to let me know how I can test more/further versions of
LXC, including git branches,
So, the new lxcfs in vivid-proposed does *not* solve this particular
problem.
Again, running the daily PPA code solved this, but that means using the
ppa for both vivid and trusty, not just vivid.
Don't hesitate to let me know how I can test more/further versions of
LXC, including git branches,
Ok, so it seems this isn't fixed after all.
Following the exact steps reported in my original message result in a
non-starting container (same error message)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, so it seems this isn't fixed after all.
Following the exact steps reported in my original message result in a
non-starting container (same error message)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage
** Changed in: lxc (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications
This seems to be fixed in vivid with lxc 1.1.2:
tribaal@vivid-test:~$ apt-cache policy lxc
lxc:
Installed: 1.1.2-0ubuntu1
Candidate: 1.1.2-0ubuntu1
Version table:
*** 1.1.2-0ubuntu1 0
500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100
This seems to be fixed in vivid with lxc 1.1.2:
tribaal@vivid-test:~$ apt-cache policy lxc
lxc:
Installed: 1.1.2-0ubuntu1
Candidate: 1.1.2-0ubuntu1
Version table:
*** 1.1.2-0ubuntu1 0
500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100
** Description changed:
The nested LXC functionality seems to be broken on Vivid, at least with
the following setup:
Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC)
What happens:
The Inner LXC start command fails when trying to start with:
** Description changed:
The nested LXC functionality seems to be broken on Vivid, at least with
the following setup:
Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC)
What happens:
The Inner LXC start command fails when trying to start with:
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu-
lxc/daily, the tested scenario works.
sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and
at leas the outer guest (trusty).
N.b. Only works if both the host and the first guest run the ppa code -
seems
If both the host (vivid) and the outer guest run LXC from ppa:ubuntu-
lxc/daily, the tested scenario works.
sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and
at leas the outer guest (trusty).
N.b. Only works if both the host and the first guest run the ppa code -
seems
Oh, good to hear.
Can I easily test what's in vivid-proposed, and/or somehow influence the
landing? Since I have a pretty good test set up for this particular
scenario I might as well help you guys :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oh, good to hear.
Can I easily test what's in vivid-proposed, and/or somehow influence the
landing? Since I have a pretty good test set up for this particular
scenario I might as well help you guys :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Adding ppa:ubuntu-lxc/daily seems to solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications about this
Adding ppa:ubuntu-lxc/daily seems to solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications
On the host.
Sorry for taking so long to answer, launchpad seems to have eaten my
email answer...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on
On the host.
Sorry for taking so long to answer, launchpad seems to have eaten my
email answer...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC
Correction, on the host and on outer (just tried).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications
Correction, on the host and on outer (just tried).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage notifications about this bug go
** Branch unlinked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-
phases
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/add-zap-fix-patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
** Branch unlinked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-
phases
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/add-zap-fix-patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475247
** Changed in: ceph-osd (Juju Charms Collection)
Status: In Progress = Fix Committed
** Changed in: ceph (Juju Charms Collection)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ceph-osd (Juju Charms Collection)
Status: In Progress = Fix Committed
** Changed in: ceph (Juju Charms Collection)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-phases
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475247
Title:
ceph-disk-prepare --zap-disk hang
To manage notifications about
** Branch linked: lp:~tribaal/ubuntu/trusty/ceph/ceph-zap-in-two-phases
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1475247
Title:
ceph-disk-prepare --zap-disk hang
To manage
** Changed in: ceph (Ubuntu Trusty)
Assignee: (unassigned) = Chris Glass (tribaal)
** Changed in: ceph (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https
** Changed in: ceph (Ubuntu Trusty)
Assignee: (unassigned) = Chris Glass (tribaal)
** Changed in: ceph (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
While auditing my wireless network I realized the -wpa attacks do not
work currently since it seems wifite is unable to capture handshake
packets (it keeps cycling between deauthing and listening but never
manages to capture handshakes).
This obviously makes attacks against
As a quick drive-by comment: HTTPS absolutely destroys package
cacheability, which is a rather desirable feature for invariant,
versionned and signed binary blobs (what deb packages are from an HTTP
perspective).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
1 - 100 of 200 matches
Mail list logo
