Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nagios-nrpe (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-nrpe in Ubuntu.
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Upstream has a new patch that fixes this without any known breakage. I
tested it and confirmed it fixes things for me. However, it doesn't
apply to 1.7.4. I propose setting CONFIG_VGA_ALLOCATE_EXTRA_STACK=n
until the next seabios release after 1.8.1.
--
You received this bug notification because
Public bug reported:
Ubuntu 14.04.2 LTS/ Release14.04
apt-cache policy libpcap0.8
libpcap0.8:
Installed: 1.4.0-2
Candidate: 1.5.3-2
Version table:
1.5.3-2 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
*** 1.4.0-2 0
100 /var/lib/dpkg/status
i
Please open a new bug report using ubuntu-bug linux if the problem
involves the same stacktrace in dmesg. If not it is even more likely a
different problem and you should start with ubuntu-bug vsftp (in any
case the command should be run on the affected server). Also note, that
this bug here was
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpcap in Ubuntu.
https://bugs.launchpad.net/bugs/1432986
Title:
i get error while trying to downgrade libpcap0.8_1.5.3-2_amd64.deb to
1.4.0-2
Public bug reported:
Bug 1323930 is marked as Fix released but the problem still exists:
If I enable the module lua in the apache2 default installation, I
cannot start the server:
$ docker run -it --rm ubuntu:trusty bash
root@6b882ad1774a:/# apt-get update
root@6b882ad1774a:/# apt-get install
The problem still exists. I've opened bug 1432989 for that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1323930
Title:
mod_lua.so missing from 14.04 install (apache2-bin,
i remove lipcap 1.5.3-2 with Synaptic Manager and reinstall libpcap0.8
apt-cache policy libpcap0.8
libpcap0.8:
Installed: 1.5.3-2
Candidate: 1.5.3-2
Version table:
*** 1.5.3-2 0
500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
--- Comment From thierry.fa...@fr.ibm.com 2015-03-05 10:05 EDT---
Verified:
gcc test.c -ldl -o test
ubuntu@vm19:~$ ./test 80
80
cpu 80 belongs to node 2
ubuntu@vm19:~$ numactl -H
available: 4 nodes (0-3)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
25 26
** Also affects: wheel (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1433324
Title:
provide whl packages in trusty to enable
--- Comment From helle...@us.ibm.com 2015-03-17 17:11 EDT---
*** Bug 122793 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1432758
Title:
cloud-config.service, cloud-final.service do not run if previous
cloud-init
Public bug reported:
to enable pyvenv in trusty, we need a number of -whl packages in trusty.
For the normal case, this is just adding a new separate binary package,
sometimes the build system needs to use setuptools. Other needed changes
are described below. The python3.4 update is tracked in
This bug was fixed in the package cloud-init - 0.7.7~bzr1084-0ubuntu1
---
cloud-init (0.7.7~bzr1084-0ubuntu1) vivid; urgency=medium
* New upstream snapshot.
* systemd: update config and final to run even if init jobs fail
(LP: #1432758)
* emit_upstart: fix use of
** Tags added: hs-arm64
--
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/1423613
Title:
maas needs to support systemd for Ubuntu = 15.04
To manage notifications about this bug go to:
Actually, I'd like to retract part of what I said above. Via tcpdump, I
was able to confirm that --push on the server for dhcp-option DNS ...
and redirect-gateway ARE ACTUALLY WORKING, though the changes are not
visible in /etc/resolv.conf. Rather, they are updated in dnsmasq and
resolv.conf
** Branch linked: lp:~james-page/ubuntu/vivid/ceph/0.93
--
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/1432786
Title:
upgrade of ceph in vivid breaks qemu-system-arm
To manage
** Changed in: ceph (Ubuntu Vivid)
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://bugs.launchpad.net/bugs/1432786
Title:
upgrade of ceph in vivid breaks qemu-system-arm
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I just ran into this problem while configuring Ubuntu 14.04 to forward
WIFI packets through an ethernet interface with NAT masquerading in
order to give access to another machine that has no WiFi Interface. I
manually set an ip address of 10.1.1.1 for eth0 and everything was
working fine, until
There is no way to prevent rpcbind from listening on all interfaces for
TCP connections. The setting -h only applies to UDP connections.
Without the attached patch, starting rpcbind with -h makes no effect to
listen on a specific address:
$ rpcbind -h 192.168.100.2
tcp0 0
** Also affects: rpcbind (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: rpcbind (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: rpcbind (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: rpcbind (Ubuntu Vivid)
Hi Mathieu,
The workaround seems good, but there still tends to be issues bringing up
the multipath devices on boot with QEMU in my testing; just the workaround
isn't always sufficient: break=pre-multipath then resuming helps out there.
May you describe the issues you're seeing?
I guess I
The workaround seems good, but there still tends to be issues bringing
up the multipath devices on boot with QEMU in my testing; just the
workaround isn't always sufficient: break=pre-multipath then resuming
helps out there.
I think this all goes back to multipath-tools updates that would help a
Public bug reported:
this fixes a test failure seen in a test rebuild of trusty with a newer
python version. it's not clear if we will update to this new version,
but the fix for this is obvious.
ERROR: utils_tests.test_jslex (unittest.loader.ModuleImportFailure)
Thanks. The cause of this is that /lib/init/apparmor-profile-load is
not installed. It comes with the 'upstart-bin' package. It is used by
the script /usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (which is an
ExecStartPre for lxc) to load the profiles.
** Changed in: lxc (Ubuntu)
This bug was fixed in the package open-vm-tools -
2:9.4.6-1770165-8ubuntu1
---
open-vm-tools (2:9.4.6-1770165-8ubuntu1) vivid; urgency=medium
* Sync from Debian (LP: #1430109)
- Added systemd support.
- Applied patches from opensuse to support kernels between 3.16 and 3.19.
From the Apache 2.2 documentation:
TLSv1.1 (when using OpenSSL 1.0.1 and later)
A revision of the TLS 1.0 protocol, as defined in RFC 4346.
TLSv1.2 (when using OpenSSL 1.0.1 and later)
A revision of the TLS 1.1 protocol, as defined in RFC 5246.
I suspect that the issue is that the current
I get something similar when I run that command for my own domain name:
SSL-Session:
Protocol : TLSv1.2
Cipher: DHE-RSA-AES256-GCM-SHA384
However, I still get the warning in apachectl configtest :
SSLProtocol: Illegal protocol 'TLSv1.2'
Action 'configtest' failed.
I am going to
** Description changed:
to enable pyvenv in trusty, we need a number of -whl packages in trusty.
For the normal case, this is just adding a new separate binary package,
sometimes the build system needs to use setuptools. Other needed changes
are described below. The python3.4 update is
The verification of the Stable Release Update for heimdal has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
You have been subscribed to a public bug:
For PCI compliance, one must not be vulnerable to the POODLE or BEAST or
CRIME attacks. POODLE suggests removing SSLv2 and SSLv3, and BEAST
suggests removing TLSv1. However, since TLSv1.1 and TLSv1.2 do not seem
to be supported by apache 2.2 on 12.04
While apache in Ubuntu 12.04 does support TLSv1.2, it doesn't allow
specifying the configuration options to selectively disable TLSv1.0.
The following commit needs to be backported:
https://svn.apache.org/viewvc?view=revisionrevision=1445104
** Package changed: openssl (Ubuntu) = apache2
Synced from Debian. I've dropped the Ubuntu customizations so that we
are a whole lot closer to Debian, including support for vmhgfs.
** Changed in: open-vm-tools (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server
This is a connection to the default configuration of apache on Ubuntu
12.04, showing it does support TLSv1.2:
$ openssl s_client -tls1_2 -connect test-precise:443
snip
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Public bug reported:
jakarta-taglibs-standard (1.1.2-3) unstable; urgency=high
* Team upload.
* Fix CVE-2015-0254 XXE and RCE via XSL extension in JSTL XML tags:
- Introduce new patch: d/patches/CVE-2015-0254.patch.
- Adjust source and target JVM parameters to 1.5.
(Closes:
** Patch added: ubuntu-ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/jakarta-taglibs-standard/+bug/1433365/+attachment/4348575/+files/ubuntu-ubuntu.debdiff
** Changed in: jakarta-taglibs-standard (Ubuntu)
Importance: Undecided = Medium
** Changed in: jakarta-taglibs-standard
** Patch added: debian-ubuntu.debdiff
https://bugs.launchpad.net/ubuntu/+source/jakarta-taglibs-standard/+bug/1433365/+attachment/4348574/+files/debian-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
to enable pyvenv in trusty, we need a number of -whl packages in trusty.
For the normal case, this is just adding a new separate binary package,
sometimes the build system needs to use setuptools. Other needed changes
are described below. The python3.4 update is
This bug was fixed in the package heimdal - 1.6~git20131207+dfsg-
1ubuntu1.1
---
heimdal (1.6~git20131207+dfsg-1ubuntu1.1) trusty; urgency=medium
* Add 048_kdc_memleak patch based on Debian bug #746486. LP: #1422359
-- Patrik Lundin patrik.lun...@su.se Tue, 03 Mar 2015 08:16:15
Confirmed in Ubuntu 14.04.02 LTS after recent upgrade from Ubuntu 12.04
LTS.
--
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/1257186
Title:
memory leakage messages (no talloc
** Also affects: requests (Ubuntu)
Importance: Undecided
Status: New
** Changed in: requests (Ubuntu)
Status: New = Fix Released
** Also affects: chardet (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chardet (Ubuntu)
Status: New = Fix Released
--
** Also affects: python-setuptools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-setuptools (Ubuntu)
Status: New = Fix Released
** Also affects: python-scripttest (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python-pip (Ubuntu)
** Changed in: juju-core (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1316272
Title:
juju destroy-environment =256 nodes fails
To
** Changed in: rpcbind (Ubuntu)
Assignee: (unassigned) = Jorge Niedbalski (niedbalski)
** Changed in: rpcbind (Ubuntu)
Importance: Undecided = Medium
** Changed in: rpcbind (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of
Also on Raspberry Pi 2 with irqbalanxe 1.0.6-3ubuntu1 (vivid). It was
using 270MB, I've now disabled the service.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1247107
Title:
** Changed in: requests (Ubuntu Vivid)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to requests in Ubuntu.
https://bugs.launchpad.net/bugs/1432555
Title:
Please fix handling of cookies on
I see delays in the devices being detected, which means after running
through the initramfs scripts and other startup scripts, the installed
system will come up using /dev/sdb1 (for example) rather than the
equivalent device mapper device, and no swap.
If you can point me to the bug you filed
** Changed in: ebtables (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ebtables in Ubuntu.
https://bugs.launchpad.net/bugs/1400025
Title:
package ebtables 2.0.10.4-3ubuntu1 failed to
This looks like bug 1429327 ('multipath' runs *before* all disks show
up).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1431650
Title:
Multipath devices take long to
Hi Mauricio, I'd be very interested in looking at the patches you
propose, we can consider those alongside shipping multipath.conf with
user_friendly_names enabled.
** Changed in: multipath-tools (Ubuntu)
Status: New = Triaged
** Changed in: multipath-tools (Ubuntu)
Importance:
Hi Serge,
Many thanks for looking at the bug.
Here is information you requested.
ubuntu@vivid-lxc-bug:~$ uname -a
Linux vivid-lxc-bug 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@vivid-lxc-bug:~$ sudo aa-status
apparmor module is loaded.
6
** Tags added: hs-arm64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for = vivid
To manage notifications about this bug go to:
I will raise a seperate bug for qemu.
** Changed in: libvirt (Ubuntu)
Status: New = Invalid
** Changed in: qemu (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Branch linked: lp:~corey.bryant/nova/2014.1.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1432608
Title:
[SRU] icehouse 2014.1.4 point release
To manage notifications about
62 matches
Mail list logo
