A fix for this has been merged upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/134
I believe this should make it into the 14.0 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
*** This bug is a security vulnerability ***
Public security bug reported:
>From the Debian security advisory at
https://www.debian.org/security/2018/dsa-4126
Kelby Ludwig and Scott Cantor discovered that the Shibboleth service
provider is vulnerable to impersonation attacks and information
*** This bug is a security vulnerability ***
Public security bug reported:
>From the Debian bug report at
https://www.debian.org/security/2018/dsa-4085:
Philip Huppert discovered the Shibboleth service provider is
vulnerable to impersonation attacks and information disclosure due to
mishandl
Hi,
This still affects both 14.04 and 16.04 (and probably affects the newer
non-LTS releases). We apply a patch downstream, which I've attached.
Regards
** Patch added: "pulse.patch"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+attachment/4879559/+files/pulse.patch
-
This problem is still present on more recent versions of Ubuntu. We
currently locally patch it to allow home directories to be owned by
either the relevant user, or root.
It would be great if this was patched upstream.
--
You received this bug notification because you are a member of Ubuntu
Bug
This was reported as an upstream kernel bug:
http://archive.linuxvirtualserver.org/html/lvs-devel/2017-04/msg00014.html
An IPVS kernel developer has responded to the issue and a patch has been
tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
Title:
IPVS incorrectly reverse-NATs traffic to LVS host
To manage notifications about this bug go
I've attempted to patch this out by adding checks where snat_handler and
dnat_handler are called (ip_vs_core.c and ip_vs_xmit.c), with no success. I
have to surmise that either:
- My patches aren't being built correctly
- My checks don't work
- This isn't the code that's mangling the packets
- T
I think I may have tracked this down, but I haven't had a go at patching
it yet.
In net/netfilter/ipvs/ip_vs_core.c - in handle_response():
/* mangle the packet */
if (pp->snat_handler && !pp->snat_handler(skb, pp, cp, iph))
goto drop;
This calls the protocol-speci
I've tested this with the latest upstream kernel (4.11.0-041100rc6), and
the problem is still present.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
It's hard to tell whether this was the result of an upgrade - I think
this behaviour has always been present in the 14.04 stock kernels, but
we noticed it less until recently.
I'll look into testing the latest upstream kernel and get back to you.
If I get a chance I'll also try to look through th
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860197/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860198/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
Title:
IP
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860199/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860200/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Tags added: apport-collected trusty
** Description changed:
We have observed the following behaviour on our LVS systems, which is
causing issues with our monitor scripts. The systems are running Ubuntu
14.04.5 LTS and I've tested both with the stock 3.13.0 kernel (-1
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860194/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860192/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860196/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/168
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860195/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1681847/+attachment/4860193/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681847
Title:
IPVS
** Description changed:
We have observed the following behaviour on our LVS systems, which is
causing issues with our monitor scripts. The systems are running Ubuntu
14.04.5 LTS and I've tested both with the stock 3.13.0 kernel (-100 and
-116) and the 4.4.0-72 xenial kernel.
Our syst
Public bug reported:
We have observed the following behaviour on our LVS systems, which is
causing issues with our monitor scripts. The systems are running Ubuntu
14.04.5 LTS and I've tested both with the stock 3.13.0 kernel (-100 and
-116) and the 4.4.0-72 xenial kernel.
Our systems are set up
Backport of relevant section in mountall.c for 2.36.4; this should make
mountall respect nobootwait, even if the mountpoint is under /usr or
/var.
** Patch added: "Backport of relevant fix in 2.38 for 2.36.4"
https://bugs.launchpad.net/ubuntu/precise/+source/mountall/+bug/654545/+attachment/44
Public bug reported:
The logic in mountall.c forces the system to wait for all mounts within
/usr and /var before continuing the boot process. Sometimes, networked
filesystems are mounted within these directories.
Because the services that support networked filesystems aren't
necessarily started
25 matches
Mail list logo
