I'm YET AGAIN having to build screen from source for a "SUPPORTED"
distro.
HEOO
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to screen in Ubuntu.
https://bugs.launchpad.net/bugs/1333630
Title:
screen caught signal 11
Unfortunately I just rolled 20 servers to 15.10 and this bug bit me big time.
Is there a workaround or estimate when
complete or do I need to roll back to 15.04. Is it possible to just install the
autofs from the 15.04 distro ?
--
You received this bug notification because you are a member of
Hello Mike, or anyone else affected,
Accepted lxc into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.1.4-0ubuntu1.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu
Ah, thanks for that info.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
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/1508577
Title:
[wily] installing juju-local on ARM
I don't think we will want to push updates to disable ssl3 on existing
systems, and I'm not sure how feasible it would be to push an update
that only modifies the defaults for brand-new installs. I suspect the
only thing to be done for 14.04 LTS is to educate system administrators
about the risks o
Thanks! In that case that should be fixed as soon as we sync the new
0.2.8-1 from unstable into x. Then we can sru the patch itself.
** Also affects: virt-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: netcf (Ubuntu Xenial)
Importance: Undecided
That seems like an unrelated bug. Please open a new bug, giving as much
information as possible about the two hosts and the vms.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
T
I don't see where anyone has identified what patches actually fixed
this, and no obvious message in git log , so offhand I'd say chances are
slim. Could you use the cloud archive, which should have the newer
versions?
--
You received this bug notification because you are a member of Ubuntu
Serve
** Patch added: "And one more to fix in vms"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503681/+files/lxcneta.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad
Any chance of having the fixes (or fixed version) backported to trusty?
We need this for the HP Moonshot hardware we're using in ScalingStack
and am currently working around it with a backport of the version in
Vivid[1]
[1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra-
workaro
Handle one more corner case
** Patch added: "lxcnet9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503630/+files/lxcnet9.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
http
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
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/1509414
Title:
pre-installed lxc in cloud image prod
** Changed in: openstack-ansible/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1488815
Title:
Kernel traces with skb_warn_bad_of
Final proposed patch for now. Uploaded to ppa:serge-hallyn/lxc-natty
for wily.
Installing this on a fresh ubuntu-cloud wily container (i.e. a broken
one) results in working lxcbr0 on new subnet.
** Patch added: "lxcnet8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+att
Action plan:
Stage 1 - Configure lxc-net at boot rather than at install.
* This addresses the network failure for 15.10 containers started on 15.10
hosts (patch above in comment #6)
Stage 2 - Start lxc-net through systemd on the first launch of an LXC container.
* This mitigates the unroutable
new patch.
It upgrades a broken container fine, but lxc-net is not properly started
until I manually call
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
/usr/lib/x86_64-linux-gnu/lxc/lxc-net start
or reboot
** Patch added: "lxcnet6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/15
** Summary changed:
- lxc postinst script checks available interfaces, can choose
+ pre-installed lxc in cloud image produces broken lxc (and later lxd)
containers
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst pac
I've had similar problems. It seems to me that the default Akonadi
options for MySQL include a table_cache parameter, but it's been
deprecated since 5.1 and in 5.6 prevents a start of the database.
Removing this options did the trick for me.
In MariaDB documentation there's a remark that "all vers
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0
fwiw, this isn't a general arm64 problem. I can install juju-local on a
mustang running wily w/o a problem. I suspect it maybe due to using a
custom kernel, possibly with some networking features disabled in the
config. I've asked Manoj to set -x /usr/lib/aarch64-linux-gnu/lxc/lxc-
net to see if th
Updated debdiff, which
1. stops creation of /etc/default/lxc-net on package install
2. removes that file only if upgrading from the 1.0.4ubuntu4 version with an
umodified /etc/default/lxc-net file
** Patch added: "lxcnet4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+
** Also affects: python-os-testr (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-json-patch in Ubuntu.
https://bugs.launchpad.net/bugs/1509422
Title:
package uses versioned
I have the same issue amd64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1509457
Title:
SMBD User authentication doesn't work after dist upgrade to 15.10
To manage notifications ab
Thank you for your quick response.
However, the tag "wishlist" does not sound very convincing to me. TIPC
is not a one-man or small interest group project, despite still being
little known. It is the main IPC solution used by my company, telco
vendor Ericsson, as well as by WindRiver, Huawei an
Having trouble with this still. I've installed the packages and made
the changes to machine type and qemu as stated above. These are the
errors I'm getting.
2015-10-23 19:25:57.491+: 7277: warning :
qemuDomainObjEnterMonitorInternal:1274 : This thread seems to be the async job
owner; enter
** Also affects: python-invoke (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-json-patch in Ubuntu.
https://bugs.launchpad.net/bugs/1509422
Title:
package uses versioned sh
** Also affects: python-osprofiler (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-future (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-bashate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
I don't like disabling lxc-net, because it's simpler to tell a user to
apt-get install lxd
than to
systemctl enable lxc-net
or
echo "USE_LXC_BRIDGE=true" | sudo tee -a /etc/default/lxc-net
systemctl restart lxc-net
--
You received this bug notification because you are a member of Ubuntu
Serv
Putthing this in debian/patch/fix-virtmanager and adding fix-virtmanager
to debian/patch/series solved this issue:
diff --git a/src/dutil_linux.c b/src/dutil_linux.c
index a3b0176..5d69d19 100644
--- a/src/dutil_linux.c
+++ b/src/dutil_linux.c
@@ -1041,7 +1041,14 @@ static void add_link_info(struc
The root cause is netcf not handling network alias
https://bugzilla.redhat.com/show_bug.cgi?id=1185850
https://rhn.redhat.com/errata/RHBA-2015-0363.html
Patch located in this post:
https://lists.fedorahosted.org/pipermail/netcf-devel/2015-January/000924.html
** Also affects: netcf (Ubuntu)
Im
Public bug reported:
After upgrading to 15.10 my samba share stopped working. Guest shares
work, but user authentication does not. After browsing to the share the
user and password prompt is displayed but fails even with the correct
credentials.
I tried purging the samba packages and rewriting th
Not sure I like this approach. An init script should never change a
system config, so this is a packaging policy violation...
To be fair, anything we come up with which picks a random/unused subnet
will still break users who may have this subnet in use behind a router,
so that's not really an opti
** Description changed:
[Problem]
The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0
** Description changed:
- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to
Debdiff which works for me.
I tested this by creating a cloud container, temporarily setting
USE_LXC_BRIDGE=false, rebooting, building the package, setting
USE_LXC_BRIDGE=true (leaving 10.0.3 as the lxcbr0 subnet), rebooting.
lxcbr0 comes up with 10.0.4.1 as expected. A nested trusty container
wo
Public bug reported:
as seen in
https://launchpadlibrarian.net/222329745/buildlog_ubuntu-xenial-amd64.python-json-patch_1.3-5build1_BUILDING.txt.gz
the package builds with 3.5 as the default, but still depends on 3.4,
because of the homegrown install step. please use vanilla pybuild to
avoid thes
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
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/1509414
Title:
lxc postinst script checks available interfaces, can choos
> Can a MaaS customer still get the hwe-t kernel through manual steps if
desired?
they could apt-get install it after the fact (same as for option 'b').
> What are consequences to support on hwe-u? Are they know forced up to
16.04 sooner (since hwe-u does not have lifetime of hwe-t)?
Well, no.
Does not affect LXD only because the LXD metadata for simple-streams is
out of date. We are going to hold off updating it until this bug is
fixed and sru'ed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => 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/1509414
T
** Tags added: cloud-installer
--
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/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage notifications about t
Public bug reported:
The released wily image preinstalls lxc, which breaks the assumption
that lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0.3.0 when it was installed
Public bug reported:
systemd socket activation
(http://www.freedesktop.org/software/systemd/man/systemd.socket.html)
was added to the service yaml some time ago. ListenStream= in the
systemd unit supports both file-based sockets (start with '/') and
abstract sockets (start with '@'). However, snap
Public bug reported:
Flake8 uses setuptools in flake8/main.py: import setuptools but the binary
packages do not depend on it.
It used to work in many cases because the pep8 package that python-flake8
depends on was depending on setuptools, but not anymore since version
1.6.2-0.1ubuntu1 uploaded
** Description changed:
=
Changelog
=
-
1.8.3
=
See https://launchpad.net/maas/+milestone/1.8.3 for full details.
Bug Fix Update
--
- #1495064Declare dependency on metadataserver migration 0015 by maasserver
- migration 0
Reviews on screenlets indicate this is still useful to someone in 2014.
(3 Stars), closing that task as it's not blocking anything.
** Changed in: indiv-screenlets (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Judging by jjohansen's comment #8, I guess the shipped common
configuration files in precise's lxc should be updated to include the
new rule. Precise's lxc is in universe, community supported. Can you
provide a proposed, tested debdiff and ping me? I'll sponsor it when
ready if needed.
--
You
I think the pinger is an optional component in Squid.
As a workaround it might help to set "pinger_enable off" in
/etc/squid3/squid.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
As seen in
http://launchpadlibrarian.net/222126620/pep8_1.6.2-0.1_1.6.2-0.1ubuntu1.diff.gz
pep8 starts depending on python3-pep while the package is python3-pep8
(or python-pep8). This prevents currently building packages that depend
on pep8.
** Affects: pep8 (Ubuntu)
I
Same issue like Guillaume. Please set importance to high.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1346740
Title:
drac plugin in dovecot uses wrong plugin version string
To m
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dovecot (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/13
Same issue with Ubuntu 14.04 AMD64.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/1346740
Title:
drac plugin in dovecot uses wrong plugin version string
To manage notifications ab
Thank you for trying. It might be a reasonable feature request for apt
to make it possible to call a shell or to provide arguments so that we
can call a shell though, in order to resolve this bug. It would be a
reasonably generic solution.
--
You received this bug notification because you are a m
I can help you to identify the upstream patch in upstream VCS for now ;)
The revision:
http://svn.apache.org/viewvc?view=revision&revision=1524368
The path:
http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/proxy/mod_proxy_fcgi.c?r1=1524368&r2=1524367&pathrev=1524368&view=patch
Regards,
--
Experiments show that
Acquire::http::ProxyAutoDetect "/bin/sh -c 'true'";
produces this error:
Failed to exec method /bin/sh -c 'true'
so I'm afraid options 1 and 2 are out :(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Hi Robin,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This request looks reasonable to me. I'll add it to the queue. To help
process it faster, we will need:
Identification of the upstream patch in upstream VCS (commit ID and
preferably a link to the commi
You have been subscribed to a public bug by Robie Basak (racb):
As suggested by Manfred Hampl, I now open a bug report from this
question:
I use Apache 2.4.7 with mod_proxy_fcgi which is affected of this bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973 .
Is it possible to backport this
As Eugene said, there is a bug affecting precise with the latest 3.2 and
3.13 (supported LTS trusty kernel for precise) and the official LXC
package. No backports or ppa used.
The bug is marked as duplicate but no fix for 12.04 is released.
--
You received this bug notification because you are a
59 matches
Mail list logo
