To silence the cron messages, an easy workaround is to disable log
compression in /etc/default/tomcat7 by setting "LOGFILE_COMPRESS=0".
This will bypass the problematic section of /etc/cron.daily/tomcat7.
I check the cron job from tomcat8 and it is identical so maybe the
problem also affects it.
Public bug reported:
We keep receiving cron messages from our tomcat machines:
/etc/cron.daily/tomcat7:
gzip: /var/log/tomcat7/lnhpd-catalina.2016-08-15.log.gz already exists; not
overwritten
And when looking at /var/log/tomcat7:
# ll /var/log/tomcat7/lnhpd-catalina.2016-08-15.*
-rw-r--r-- 1
This is fixed in Trusty and maybe earlier releases too, I haven't check
Precise.
** Changed in: tomcat7 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems that those Apparmor denials are responsible for severe slowdown
of guests boot when the host boots up.
This simple fix makes the guests boot swiftly:
# diff -Naur /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper.orig
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
---
Hi Ryan, have you been able to test a downgrade to 2.0.0+dfsg-
2ubuntu1.21?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545821
Title:
The upstream patch was included in NM 1.2.2 so Yakkety is not affected,
only Xenial is.
The attached debdiff contains the upstream patch backported to Xenial.
The resulting package resolve the issue. If anything is missing for the
SRU process, please let me know.
** Patch added:
This was fixed upstream:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3d505b3f87c9cb9bfdc9b9a1fc67f57330701d03
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568829
Title:
Thanks Alberto. https://bugzilla.gnome.org/show_bug.cgi?id=769324
** Description changed:
+ Steps to reproduce:
+
+ 1. (Re-)mount /proc with hidepid=1 (or =2)
+ 2. Restart nm-applet
+
+ nm-applet's icon does not reappear after the restart. This used to work
+ with version 1.0.
+
+
+ Original
** Summary changed:
- nm-applet icon not showing
+ nm-applet icon not showing when /proc is mounted with hidepid!=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568829
Title:
nm-applet icon not
A kernel side fix was proposed (https://lkml.org/lkml/2016/6/22/682) but
remains to be merged upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599428
Title:
checkarray doesn't work
To
According to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=787950#10, this is a combination of how dash reads
files and the kernel version (4.0+).
If that's true, even Trusty machines could be affected when running the
HWE kernels.
--
You received this bug notification because you are a
Public bug reported:
Problem description:
The script /usr/share/mdadm/checkarray exits before checking any array.
Steps to reproduce:
1) Check the status of every arrays
/usr/share/mdadm/checkarray --all --status
2) Expected output
md0: idle
3) Problematic output: nothing
Additional
After some more debugging, it seems to be a behavior change in dash
between Xenial:
# /bin/sh -c 'read cur_status < /sys/block/md0/md/sync_action; echo $cur_status'
i
# /bin/bash -c 'read cur_status < /sys/block/md0/md/sync_action; echo
$cur_status'
idle
And Trusty:
# /bin/sh -c 'read
** Patch added: "Workaround for Xenial's dash"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1599428/+attachment/4696310/+files/checkarray-workaround-for-lp1599428.diff
** Bug watch added: Debian Bug tracker #787950
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787950
** Also
There is a nice explanation of the bug in the duplicate LP: #1598522.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580356
Title:
OpenVPN causes reboot failure on Xenial in AWS
To manage
Based on Douglas' last comment, I believe that the 2 Strongswan profiles
are missing the "flags=(attach_disconnected)" to make NetworkManager-
l2tp happy. The first patch needs a little cleanup but the bug is valid
IMHO.
--
You received this bug notification because you are a member of Ubuntu
Hi Douglas, thanks for digging this down and providing a patch. The 2
profiles don't ship with any flags so you probably added "complain"
before generating your diff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Nish, I used the simple test case from comment #20 on Yakkety:
3.8.5-2: fails
4.5.0-4: fails
4.5.0-4ubuntu1: works
As for the autopkgtest failures, I don't know what's going on either as
it works for me too in a LXD container.
--
You received this bug notification because you are a member of
I'm chasing a bug similar in behavior but I'm using "qemu-system-x86_64
-enable-kvm" so it's not TCG, AFAICT. Would it be possible this problem
also manifests in KVM mode? Or should I open a new bug?
@pboldin, when you get a chance, could you please check if the 2.0.0
+dfsg-2ubuntu1.23 version
This is similar to LP: #1541678 which has a simpler and more generic
patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519120
Title:
Xenial: VLAN interfaces don't work until after a reboot
To
This is still a problem on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939105
Title:
upstart should consult /usr/sbin/policy-rc.d
To manage notifications about this bug go to:
** Changed in: openvpn (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580356
Title:
OpenVPN causes reboot failure on Xenial in AWS
To manage
When I fool puppet into thinking that Yakkety is version 16.04, it
works. Here's what I did in a Yakkety container:
# upstart is required to confuse Puppet
apt-get install -y puppet upstart tftpd-hpa # note: puppet-common is gone
# fails
puppet apply -e "service { 'tftpd-hpa': ensure => stopped
@nacc, the proposed version in Yakkety (4.5.0-4) is also affected. This
probably makes sense because upstream only enables systemd handling
based on known and hardcoded version numbers. Since 16.10 is not one of
those, upstart is implied by default.
--
You received this bug notification because
Same debdiff but with a proper address in the changelog.
** Patch removed: "lp1570472-version-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4675541/+files/lp1570472-version-2.debdiff
** Patch added: "lp1570472-version-2.debdiff"
@nacc, I aggregated all the commits you mentioned in update 5. I needed
to apply some parts manually, especially for the spec/ tests portions.
# upstart is required to confuse Puppet
apt-get install -y puppet-common upstart tftpd-hpa
# fails
puppet apply -e "service { 'tftpd-hpa': ensure =>
On 2016-06-01 10:24 AM, Douglas Kosovic wrote:
> UEFI Lenovo desktop PC is what I'm running Xenial on.
OK.
> I'm the new maintainer for network-manager-l2tp VPN plugin for NetworkManger :
>https://github.com/nm-l2tp/network-manager-l2tp
Oh nice!
> I started an IPSec/L2TP connection using
Hi Douglas,
I'm unable to reproduce this on a Xenial host. Are you running in a
container or something similar? Also, have you altered the strongswan
systemd unit?
** Changed in: strongswan (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Reproduced with:
lxc launch ubuntu-daily:14.04 tgt -c
raw.lxc="lxc.aa_profile=unconfined"
The proposed package fixes the issue, thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Apache was removed ~26 minutes before installing nginx-full. Then dpkg
reports being unable to start nginx during post-install, maybe Apache
was still running after the removal? The next day, nginx was able to
start without problem.
Skimming dmesg revealed this which may or may not be relevant at
Louie, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22
provides a simple way to reproduce. If you could give it a try that
would be appreciated.
FYI, when my hypervisor was running Trusty (3.13), the problem was
reproducible on fresh VMs with brand new ext4 FSes, so hopefully that
@Patrick, thanks for working on this. When you have done the
verification, you can update the tags list that's below the initial
issue description at the top. More details on that:
https://wiki.ubuntu.com/StableReleaseUpdates#Verification
--
You received this bug notification because you are a
This is reproducible on Trusty (after removing sgio='filtered' which
isn't supported). The same workaround works as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573192
Title:
apparmor
Simon's patch [1] was included in version 2.72 (Vivid and later).
Marking as fix released.
1:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=006c162382aaa30f63413b876ecbe805280c3d36
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug
Hi Scott,
I just finished migrating my VPN to Xenial. I cannot reproduce your
issue using a static IP configuration in /etc/network/interfaces. I'll
try to set things up with DHCP and see how it goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Nginx logs an error when started on a machine with a single CPU:
systemctl start nginx
systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:
enabled)
In the above workaround, I forgot the first step (mkdir) so here it is
again:
Workaround:
mkdir /etc/systemd/system/nginx.service.d
printf "[Service]\nExecStartPost=/bin/sleep 0.1\n" >
/etc/systemd/system/nginx.service.d/override.conf
systemctl daemon-reload
--
You received this bug
It seems to be a race between systemd and nginx. As if systemd was
expecting the PID file to be populated before nginx had the time to
create it.
Workaround:
printf "[Service]\nExecStartPost=/bin/sleep 0.1\n" >
/etc/systemd/system/nginx.service.d/override.conf
systemctl daemon-reload
--
You
Extract of the changelog:
ca-certificates-java (20120524) unstable; urgency=low
[ Marc Deslauriers ]
[...]
* debian/postinst: don't put a symlink in / if jvm doesn't contain nss
configuration. (Closes: #665754, #665749).
This means that Trusty and later are not affected.
** Bug watch
*** This bug is a duplicate of bug 1065877 ***
https://bugs.launchpad.net/bugs/1065877
** This bug has been marked a duplicate of bug 1065877
A link /libnss3.so is created when installing the package or when updating
the jks-keystore
--
You received this bug notification because you are
Thanks Scott. Could you also attach the OpenVPN configs since they
apparently don't match the gist [1].
Thanks
1: https://gist.github.com/sc250024/001e05d64cd02fe746ae1772baccd24a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you could attach "ip addr" and "ip route" output here that would be
good, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580356
Title:
OpenVPN causes reboot failure on Xenial in AWS
To
Scott, could you please provide some information about the routing/IP
configuration before the reboot?
** Changed in: openvpn (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I noticed the nginx-*.postinst files had the same logic that is
implemented by "service nginx upgrade". Please find a patch dropping the
duplicated code and reusing the one from the init script. This is the
same patch that was attached to https://bugs.debian.org/cgi-
It seems that it wants the certificate to cover the name "localhost"
instead or in addition to the FQDN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366455
Title:
qemu+tls server certificate
Ishmael, on Ubuntu, the default location for CA cert is /etc/ssl/certs.
Maybe you could try putting your trusted CA in there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366455
Title:
qemu+tls
I recently reinstalled the affected host to run Xenial so I can no
longer test the proposed fix for the 3.13 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423672
Title:
May I suggest a simpler version of the bamfdaemon-dbus-runner script:
#!/bin/sh
if [ -n "$UPSTART_SESSION" ]; then
initctl status bamfdaemon | grep -q start || initctl start bamfdaemon
else
/usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
fi
Regards,
Simon
--
You received this bug notification
** Summary changed:
- if-post-down.d/vlan and if-pre-up.d/vlan should support en* interfaces
+ if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have unity 7.4.0+16.04.20160415-0ubuntu1 (from Xenial) and I'm still
affected by the double lock problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292451
Title:
screensaver re-locks itself
One more data point, my 4x1Gbps NIC appears as:
enp3s0f0
enp3s0f1
enp4s0f0
enp4s0f1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541678
Title:
if-post-down.d/vlan and if-pre-up.d/vlan should
On 2016-04-22 05:08 PM, Hideki Saito wrote:
> I think I see what's going on. This seems to happen when hidepid is
> set to anything other than 0.
Hmm, I use hidepid=2,gid=27. Where gid 27 is the sudo group which I'm
part of. Nice catch.
It would be really nice not to have to resort to hidepid=0
As mentioned in a duplicated LP, I think the vlan up/down script could
be simplified.
The part extracting VLANID and IF_VLAN_RAW_DEVICE seems overly complex.
The "case" statement already ensures we operate on vlan device so I
think something much simpler like this would work:
VLANID=`echo
** Description changed:
Trying to pass a SCSI device from the host to a VM with this XML
definition:
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Results in Apparmor denials like this during the VM startup:
apparmor="DENIED"
Public bug reported:
Trying to pass a SCSI device from the host to a VM with this XML
definition:
Results in Apparmor denials like this during the VM startup:
apparmor="DENIED" operation="open"
profile="libvirt-65e0d1b9-f6b1-4926-8648-dc685778555a"
Thanks Chris. So far, no regression with the Trusty kernel:
$ uname -a
Linux xeon 3.13.0-86-generic #130~lp1423672v201604200743 SMP Wed Apr 20
12:44:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Since the issue only happens rarely, more people testing it would be
welcome.
--
You received this
** Patch added: "lp1571278.debdiff"
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1571278/+attachment/4638857/+files/lp1571278.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This error is because BackupPC cannot locate the CGI module. This is a
regression as this module was part of the package 'perl-modules' but is
not included in the 'perl-modules-5.22' package.
** Affects: backuppc (Ubuntu)
Importance: Undecided
Status: New
**
The fix included in 4.4.0-20-generic works well, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566465
Title:
[regression]: Failed to call clock_adjtime(): Invalid argument
To manage
** Patch added: "Working debdiff"
https://bugs.launchpad.net/debian/+source/backuppc/+bug/1570987/+attachment/4637847/+files/lp1570987.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570987
** Patch removed: "lp1570987.debdiff"
https://bugs.launchpad.net/debian/+source/backuppc/+bug/1570987/+attachment/4637843/+files/lp1570987.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1570987.debdiff"
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1570987/+attachment/4637843/+files/lp1570987.debdiff
** Bug watch added: Debian Bug tracker #820110
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820110
** Also affects: backuppc (Debian) via
This is fixed in Xenial.
** Changed in: backuppc (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243476
Title:
Apache 2.4 transition broke the web
Public bug reported:
Starting the backuppc services results in those warnings:
Apr 15 15:56:52 bck backuppc[700]: Unescaped left brace in regex is deprecated,
passed through in regex; marked by <-- HERE in m/\${ <-- HERE (\w+)}(\+?)/ at
/usr/share/backuppc/lib/BackupPC/Lib.pm line 1281.
Apr 15
This is fixed now:
backuppc (3.3.0-2) unstable; urgency=low
* Depends on apache2-utils
** Changed in: backuppc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1515986 ***
https://bugs.launchpad.net/bugs/1515986
** This bug has been marked a duplicate of bug 1515986
unable to properly install backuppc on wily 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A lot changed in BackupPC and Samba since the problem was originally reported.
Hardy and Intrepid are long EOL.
Are you still affected by this bug in supported releases?
** Changed in: backuppc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
I am also interested in this so here's a debdiff.
** Patch added: "lp1570472.debdiff"
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+attachment/4637132/+files/lp1570472.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
As Ondřej mentioned, not having /usr/sbin in $PATH is weird though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567740
Title:
Unbound depends on /usr/sbin in path
To manage notifications about
Yes and a patch was attached to the Debian bug: https://bugs.debian.org
/cgi-bin/bugreport.cgi?filename=use-full-path-to-
checkconf.patch;msg=10;bug=820458;att=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bogdan, please make sure to have all the updates applied. Network-
Manager and the OpenVPN plugin were refreshed post beta 2 so maybe this
got implemented.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Debian maintainer never commented in the Debian bug so I think there
is no other way than carrying an Ubuntu delta for this. The attached
debdiff fixes the problem.
** Patch added: "lp654065.debdiff"
The Debian maintainer forwarded the bug upstream and they fixed it right
away. So here's a debdiff that fixes the problem for me. I uploaded it
to my PPA and it successfully built on amd64 [1] but not i386 [2].
On i386 the libmount/lock test failed so it seems unrelated to this new
commit. It's
So I stopped NM and started it back only to notice that my old nm-applet
was still running (still no icon). To be sure I was doing it the way you
needed I killed nm-applet, then started NM with --debug (that's what
I've attached).
When NM was running with --debug, it didn't spawn nm-applet but I
** Bug watch added: Debian Bug tracker #820843
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820843
** Also affects: util-linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820843
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Description changed:
Steps to reproduce:
1) Start script session (same issue when script is saving to /dev/null)
script # or: script /dev/null
2) Tail a file
- tail -f /var/log/syslog
+ tailf /var/log/syslog
3) Press "Enter" 2 times
4) Notice the script process taking 100% CPU
The above commit is from Debian's git. The problem still exists upstream
in https://git.kernel.org/cgit/utils/util-linux/util-
linux.git/commit/?id=44338f7fe6a529cef1f206dccd95e7282625c483
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
FYI, the current master (d38bcd109e9) still has 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/1553353
Title:
tail'ing a file in a script session hangs
To manage notifications about
After bisecting util-linux, the problematic commit is:
54c6611d6f7b73609a5331f4d0bcf63c4af6429e is the first bad commit
commit 54c6611d6f7b73609a5331f4d0bcf63c4af6429e
Author: Karel Zak
Date: Wed Jun 17 15:48:50 2015 +0200
script: fix EOF problems
* remove STDIN
Apologies, the AA profile is not shipped with Samba. Please ignore my
previous comments (#1 and #2).
The test packages work well on Trusty!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569497
On some other configurations I've also seen the sys_admin capability to
be needed. I think this capability is needed when using the "force
user/group" options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Prior to this update, the usr.sbin.smbd profile was missing those
Apparmor rules:
capability audit_write,
/usr/lib/@{multiarch}/samba/*.so{,.[0-9]*}mr,
/usr/lib/@{multiarch}/samba/**/ r,
/usr/lib/@{multiarch}/samba/**/*.so{,.[0-9]*} mr,
Now with
Hi Thomas, this indeed looks like the upstream bug you've found. Since
your package comes from precise-backports/universe, it's unlikely that
it will receive a bug fix from Ubuntu. Upgrading to Trusty or later
should give you a fixed version at least.
** Bug watch added: nlnetlabs.nl/bugs-script/
** Changed in: libvirt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561553
Title:
unable to create a ZFS pool
To manage notifications about
** Patch removed: "lp1560149.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1560149/+attachment/4633185/+files/lp1560149.debdiff
** Changed in: qemu (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Seems I was too slow, thanks Serge!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560149
Title:
missing seccomp whitelist for qemu-kvm
To manage notifications about this bug go to:
The attached debdiff fixes the problem and built successfully in PPA.
** Patch added: "lp1560149.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1560149/+attachment/4633185/+files/lp1560149.debdiff
--
You received this bug notification because you are a member of Ubuntu
The sysinfo syscall was discussed in
https://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg01365.html
so upstream is aware of this at least and Eduardo being the qemu-seccomp
maintainer is good.
@otubo, if you have a patch that needs testing please don't hesitate.
--
You received this bug
** Patch added: "xenial-lp1568993.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1568993/+attachment/4633077/+files/xenial-lp1568993.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
mdadm is IMHO unneeded in a container.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mdadm 3.3-2ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion:
** Patch added: "xenial-lp1568954.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1568954/+attachment/4633058/+files/xenial-lp1568954.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lxc images now use the -server flavor so they always have irqbalance
running.
https://github.com/Irqbalance/irqbalance/issues/27#issuecomment-172279943
says that in rare cases, one might want to run irqbalance in a
container. I _think_ those are sufficiently rare to not consider.
** Patch added:
Public bug reported:
lvmetad is IMHO unneeded in a container.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
Hi Michael,
doko's fix is not required with 1.5.8 because this was fixed upstream:
25 January 2016: Wouter
- Fix #738: Swig should not be invoked with CPPFLAGS.
This was also filled/fixed in Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=809055
As such, Nish's package
Public bug reported:
Since I upgraded to -proposed network-manager and network-manager-gnome
versions, nm-applet no longer works.
Manually starting it on a console give:
$ nm-applet
(nm-applet:6250): nm-applet-WARNING **:
On 2016-04-09 12:53 AM, Egmont Koblinger wrote:
> See https://bugs.launchpad.net/terminator/+bug/1030562 .
Thanks for the pointer.
> Until then, I recommend to you to ditch the version shipped by Xenial
> and use the one from the terminator-gtk3 bzr branch.
I badly need a reliable Terminator so
** Bug watch added: Debian Bug tracker #820482
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820482
** Also affects: acpid (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820482
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
acpid is IMHO unneeded in a container.
** Affects: acpid (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/1568155
Title:
** Patch added: "xenial-lp1568155.debdiff"
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1568155/+attachment/4629714/+files/xenial-lp1568155.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568155
Title:
acpid shouldn't run in a container
To manage notifications about this bug go to:
901 - 1000 of 2435 matches
Mail list logo