[Bug 1549136] [NEW] Move "lxc" dependencies to "lxc1"
Public bug reported: "lxc" now says "This is a transitional dummy package. It can safely be removed.", but this isn't true: $ sudo LANG= dpkg -P lxc dpkg: dependency problems prevent removal of lxc: lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43). lxd depends on lxc. juju-local depends on lxc (>= 1.0.0~alpha1-0ubuntu14). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Wed Feb 24 07:57:23 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc modified.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: [modified] modified.conffile..etc.default.lxc: [modified] mtime.conffile..etc.apparmor.d.lxc.lxc.default.with.nesting: 2016-02-22T23:39:08 mtime.conffile..etc.default.lxc: 2016-02-22T23:39:08 ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug xenial ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New -- 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/1549136 Title: Move "lxc" dependencies to "lxc1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1549136/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
It looks good to me, but I'm curious as to why libmcrypt isn't in main (and consequently able to be used as a PHP build dependency)? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1486073] Re: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
I can no longer reproduce this bug, following the release of fixes for bugs #1531747, #1534961 and #1535150 . ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- 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/1486073 Title: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1486073/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271531] Re: Specifying cgset -r multiple times fails
Of course it's not fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271531 Title: Specifying cgset -r multiple times fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271531/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549094] Re: named crashed with SIGABRT in isc_assertion_failed()
*** This bug is a duplicate of bug 1547386 *** https://bugs.launchpad.net/bugs/1547386 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1547386, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1549094/+attachment/4579602/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579604/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579608/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579609/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579610/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579611/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1549094/+attachment/4579613/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1547386 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1549094 Title: named crashed with SIGABRT in isc_assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549094/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
just installed 14.04 then upgraded to 16.04 today's daily build. unfortunately still see the DNS leaking issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546788] Re: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error
Fixed in 3.0.3-2, which eventually became 3.0.4-1 ** Changed in: postfix (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1546788 Title: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1546788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1549051] [NEW] /usr/bin/NUT-Monitor:6:__libc_message:malloc_printerr:_int_free:_int_realloc:__GI___libc_realloc
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nut. This problem was most recently seen with version 2.7.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ee8e685035f19f4234abf23ae7a5f67062be7b13 contains more details. ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1549051 Title: /usr/bin/NUT- Monitor:6:__libc_message:malloc_printerr:_int_free:_int_realloc:__GI___libc_realloc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1549051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543334] Re: upgrade to pkg-php-tools 1.32
The attachment "pkg-php-tools.1.32ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pkg-php-tools in Ubuntu. https://bugs.launchpad.net/bugs/1543334 Title: upgrade to pkg-php-tools 1.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkg-php-tools/+bug/1543334/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Wily) Importance: Undecided => Medium -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
php7.0 (7.0.3-7ubuntu1) xenial; urgency=medium * Merge with Debian unstable. Remaining changes: - Drop support for firebird, c-client, mcrypt, onig, qdbm and zip as they are in universe (LP #1547245): + d/control: drop Build-Depends on firebird-dev, libc-client-dev, libmcrypt-dev, libonig-dev, libqdbm-dev, libxmlrpc-epi and libzip-dev. + d/control: drop binary packages php7.0-imap, php7.0-interbase, php7.0-mcrypt and php7.0-xmlrpc and their reverse dependencies. + d/rules.d: drop makefile snippets for imap, interbase, mcrypt and xmlrpc extensions. - d/control: switch Build-Depends of netcat-traditional to netcat-openbsd as only the latter is in main. * Dropped changes: - Drop support for xmlrpc as it is in universe (LP #1547700): + d/control: drop Build-Depends on libxmlrpc-epi + d/control: drop binary package php7.0-xmlrpc and its reverse dependencies. + d/rules.d: drop makefile snippet for xmlrpc extension. - d/rules: drop configuration of qdgm and zip. + dropped in Debian. * Drop support for zip as it is in universe (LP: #1547245). - d/control: drop binary package php7.0-zip. - d/rules.d: drop makefile snippet for zip extension. -- Nishanth Aravamudan Tue, 23 Feb 2016 15:02:28 -0800 ** Patch added: "php7.0.7.0.3-7ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+attachment/4579528/+files/php7.0.7.0.3-7ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1540401] Comment bridged from LTC Bugzilla
--- Comment From mauri...@br.ibm.com 2016-02-23 17:56 EDT--- Hi @mathieu-tl, Cool, thanks; glad to see the patch made Xenial. This is still on the queue for Trusty, correct? - there's no 'Affects' line for Trusty on the LP bug header yet. -- 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/1540401 Title: ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The disk drive for /boot is not ready yet or not present" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543334] Re: upgrade to pkg-php-tools 1.32
Please merge with Debian bb557427 ("Prepare pkg-php-tools (1.32)")_ in order to pass the autopkgtests: pkg-php-tools (1.32ubuntu1) xenial; urgency=medium * tests/PhpcomposerSourceTest.php: update php-json error message (Debian #814858). * LP: #1543324. -- Nishanth Aravamudan Tue, 23 Feb 2016 14:31:06 -0800 I have sent the same fix to Debian in the above bug, and hopefully it also gets picked up in time for 1.32, in which case we can sync. ** Patch added: "pkg-php-tools.1.32ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/pkg-php-tools/+bug/1543334/+attachment/4579476/+files/pkg-php-tools.1.32ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pkg-php-tools in Ubuntu. https://bugs.launchpad.net/bugs/1543334 Title: upgrade to pkg-php-tools 1.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkg-php-tools/+bug/1543334/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271531] Re: Specifying cgset -r multiple times fails
cgset -r cpu.cfs_quota_us=10 -r cpu.cfs_period_us=1000 groupname cgset -r cpu.cfs_period_us=10 -r cpu.cfs_quota_us=1000 groupname Both work for me, although the first probably should not. I have libcgroup 0.41-7, probably similar to libcgroup 0.41-6ubuntu1 in Ubuntu 15.10 Wily Werewolf. Since this is the currently stable version, maybe you should check if it works there and close the bug as fixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271531 Title: Specifying cgset -r multiple times fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271531/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548994] [NEW] samba panic or segfault
Public bug reported: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 3147 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the problem persists, you are encouraged to first install the samba-dbg package, which contains the debugging symbols for the Samba binaries. Then submit the provided information as a bug report to Ubuntu by visiting this link: https://launchpad.net/ubuntu/+source/samba/+filebug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f83d82f37ea in __GI___waitpid (pid=3148, stat_loc=stat_loc@entry=0x7ffdabb94bd0, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31 #0 0x7f83d82f37ea in __GI___waitpid (pid=3148, stat_loc=stat_loc@entry=0x7ffdabb94bd0, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31 #1 0x7f83d826cffb in do_system (line=) at ../sysdeps/posix/system.c:148 #2 0x7f83d9c16251 in smb_panic_s3 () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 #3 0x7f83db361b7f in smb_panic () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0 #4 0x7f83db361d96 in ?? () from /usr/lib/x86_64-linux-gnu/libsamba-util.so.0 #5 #6 0x7f83daf73aa5 in smbXsrv_session_create () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #7 0x7f83daf0f966 in reply_sesssetup_and_X () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #8 0x7f83daf4a558 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #9 0x7f83daf4b9c1 in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #10 0x7f83daf4bc0b in ?? () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #11 0x7f83d9c2c837 in run_events_poll () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 #12 0x7f83d9c2ca97 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 #13 0x7f83d85f6a4d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #14 0x7f83daf4d0dd in smbd_process () from /usr/lib/x86_64-linux-gnu/samba/libsmbd_base.so.0 #15 0x55959f935120 in ?? () #16 0x7f83d9c2c837 in run_events_poll () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 #17 0x7f83d9c2ca97 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 #18 0x7f83d85f6a4d in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #19 0x55959f931e62 in main () A debugging session is active. Inferior 1 [process 3147] will be detached. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 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/1548994 Title: samba panic or segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1548994/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1544568] Re: [SRU] neutron 7.0.3 and ceilometer 5.0.2 stable releases
Hello James, or anyone else affected, Accepted ceilometer into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ceilometer/1:5.0.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ceilometer (Ubuntu Wily) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1544568 Title: [SRU] neutron 7.0.3 and ceilometer 5.0.2 stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1544568/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548497] Re: Cross-Container ARP Poisoning
With a recent kernel, libvirt can manage the MAC table [*] of the bridge so maybe this is something that can be done by LXC/LXD as well? *: see the "bridge" section of https://libvirt.org/formatnetwork.html#elementsConnect -- 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/1548497 Title: Cross-Container ARP Poisoning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Also affects: cloud-archive Importance: Undecided Status: New -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
The attachment "debian patch for qemu 1:2.2+dfsg" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: qemu (Ubuntu Wily) Status: New => Fix Released -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Changed in: qemu (Ubuntu Vivid) Status: New => Won't Fix ** No longer affects: qemu (Ubuntu Trusty) -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548497] Re: Cross-Container ARP Poisoning
Jesse, thanks for the excellent detailed report; please do report future findings. I'm setting this public as it's apparently public enough already. Thanks ** Information type changed from Private Security to Public Security -- 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/1548497 Title: Cross-Container ARP Poisoning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548497/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1540401] Re: ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The disk drive for /boot is not ready yet or not present"
This bug was fixed in the package multipath-tools - 0.5.0-7ubuntu15 --- multipath-tools (0.5.0-7ubuntu15) xenial; urgency=medium [ Mauricio Faria de Oliveira ] * Remove partition device nodes of individual paths (for LVM on multipath) (LP: #1540401) - debian/multipath-tools.dm-mpath-lvm.udev: udev rule for that. - debian/initramfs/hooks: copy the udev rule and partx to the initramfs. - debian/initramfs/init-top: load the dm-multipath module for 'multipath -c'. - debian/rules: install the udev rule (priority 56: after 55-scsi-sg3_id) * debian/rules: don't ship 95-multipath.rules udev rules anymore; they are not necessary with multipath-tools listening for udev events directly. -- Mathieu Trudel-Lapierre Thu, 11 Feb 2016 19:08:14 -0500 ** Changed in: multipath-tools (Ubuntu) Status: In Progress => Fix Released -- 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/1540401 Title: ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The disk drive for /boot is not ready yet or not present" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Also affects: qemu (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546445] Re: support vhost user without specifying vhostforce
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- 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/1546445 Title: support vhost user without specifying vhostforce To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1546445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546455] Re: Many instances of 'apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" sock_type="dgram" protocol=0' in syslog
This bug was fixed in the package apparmor - 2.10-3ubuntu2 --- apparmor (2.10-3ubuntu2) xenial; urgency=medium * debian/patches/parser-allow-unspec-in-network-rules.patch: Allow apparmor_parser to support rules that use 'unspec' as the network protocol family. (LP: #1546455) -- Tyler Hicks Thu, 18 Feb 2016 12:48:17 -0600 ** Changed in: apparmor (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1546455 Title: Many instances of 'apparmor="DENIED" operation="create" profile="/usr/sbin/ntpd" pid=15139 comm="ntpd" family="unspec" sock_type="dgram" protocol=0' in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1546455/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547738] Re: Request: Sync with Debian to get upstream fixes for autopkgtests
Ondřej seems to have made some fixes and the current git HEAD is at php7.0-7.0.3-7, so please pull that in. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1547738 Title: Request: Sync with Debian to get upstream fixes for autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1547738/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: neutron (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1393391 Title: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port- update_fanout.. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: neutron (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1393391 Title: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port- update_fanout.. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1535052] Re: xdebug and pecl are absolutely needed to make PHP7 usable
** Also affects: xdebug (Ubuntu) Importance: Undecided Status: New ** Also affects: php-pear (Ubuntu) Importance: Undecided Status: New ** No longer affects: php7.0 (Ubuntu) ** Changed in: php-pear (Ubuntu) Status: New => Fix Committed ** Changed in: xdebug (Ubuntu) Status: New => Fix Released ** Changed in: php-pear (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) ** Changed in: xdebug (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1535052 Title: xdebug and pecl are absolutely needed to make PHP7 usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-pear/+bug/1535052/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1543025] Re: Wrong UTC zoneinfo in cloud-images
** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1543025 Title: Wrong UTC zoneinfo in cloud-images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1543025/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1172692]
In comment #3 I wrote: >... > Finally, the pm_functions script uses "echo -n" (from line 318, including > the above patch) ... See also bug 91497. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1172692 Title: Please implement in-kernel suspend to both To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1172692/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1172692]
In comment #2 I wrote: > Comment on attachment 68712 [details] [review] >... > Although you could make the penultimate line as follows I don't recommend it > because it would hide any problems like the escaping issue that could cause > HIBERNATE_MODE_SAVE to be invalid: > > [ -n "$HIBERNATE_MODE_SAVE" ] && echo -n "$HIBERNATE_MODE_SAVE" > > > /sys/power/disk In fact there are 2 cases as the code is used now: 1HIBERNATE_MODE unset => normal hibernate 2HIBERNATE_MODE = suspend => suspend-hybrid Given which, I've revised my comment above and propose a new version of the modified do_hibernate() as follows: do_hibernate() { local hibernate_mode_save ret [ -n "${HIBERNATE_MODE}" ] && \ grep -qw "${HIBERNATE_MODE}" /sys/power/disk && \ hibernate_mode_save=$(cat /sys/power/disk) && \ hibernate_mode_save="${hibernate_mode_save##*\[}" && \ hibernate_mode_save="${hibernate_mode_save%%\]*}" && \ [ "$hibernate_mode_save" != "${HIBERNATE_MODE}" ] || \ hibernate_mode_save="" [ -n "$hibernate_mode_save" ] && \ echo -n "${HIBERNATE_MODE}" > /sys/power/disk echo -n "disk" > /sys/power/state ret=$? [ -n "$hibernate_mode_save" ] && \ echo -n "$hibernate_mode_save" > /sys/power/disk return $ret } The key points: - hibernate_mode_save is only set if the current HIBERNATE_MODE is being changed (which only happens, if it does, in the suspend-hybrid case); - on resume the hibernate mode is only restored if hibernate_mode_save was set. This fixes: - the failure to restore the hibernate mode with suspend-hybrid; - "sh: I/O error" on resume from suspend-hybrid - "sh: I/O error" on resume from hibernate. Finally, the pm_functions script uses "echo -n" (from line 318, including the above patch) and local declarations while the comment against function log() implies that the script is aiming for POSIX conformance and yet other functions use non-POSIX local declarations. local and "echo -n" usages are fine for Debian and derived environments. To achieve POSIX conformance such usages would have to be reviewed and modified; "echo -n" could be replaced with printf (the parameters to be echoed in each case being plain text not containing formatting commands); or a shell function echo() can be added based on log(). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1172692 Title: Please implement in-kernel suspend to both To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1172692/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1172692]
Comment on attachment 68712 Improved patch to save previous hibernation method Review of attachment 68712: - In do_hibernate() the attempt to save and restore the active mode in /sys/power/disk fails, causing "sh: I/O error" message in pm log (attempting to write something that isn't one of the modes in /sys/power/disk, namely an empty string). Instrumenting the function I found that HIBERNATE_MODE_SAVE was never set. The characters [] are special in a shell pattern (which is what follows the ## and %% shell variable expansion modifiers) and have to be escaped: \[ \]. The following works as you intended: do_hibernate() { [ -n "${HIBERNATE_MODE}" ] && \ grep -qw "${HIBERNATE_MODE}" /sys/power/disk && \ #df 2016-02-07 Shell patterns have to be escaped \[ \]! Fixes sh: I/O error when -z $HIBERNATE_MODE_SAVE HIBERNATE_MODE_SAVE=$(cat /sys/power/disk) && \ HIBERNATE_MODE_SAVE="${HIBERNATE_MODE_SAVE##*\[}" && \ HIBERNATE_MODE_SAVE="${HIBERNATE_MODE_SAVE%%\]*}" && \ echo -n "${HIBERNATE_MODE}" > /sys/power/disk echo -n "disk" > /sys/power/state RET=$? echo -n "$HIBERNATE_MODE_SAVE" > /sys/power/disk return "$RET" } Although you could make the penultimate line as follows I don't recommend it because it would hide any problems like the escaping issue that could cause HIBERNATE_MODE_SAVE to be invalid: [ -n "$HIBERNATE_MODE_SAVE" ] && echo -n "$HIBERNATE_MODE_SAVE" > /sys/power/disk -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1172692 Title: Please implement in-kernel suspend to both To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1172692/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
** Description changed: == Begin SRU Information == [Impact] Users of squid3 as a proxy on a host without ipv6 connectivity will see http '503' errors if they attempt to access a url through that proxy that has greater than 9 ipv6 addresses associated with it. The failure case is that affected ubuntu users specifically was: - a.) user uses squid from Ubuntu as a proxy - b.) security.ubuntu.com and archive.ubuntu.com had additional IPV6 addresses added to their dns, such that there were 10 ipv6 addresses for each. - c.) the squid system does not have access to the ipv6 addresses. Most likely that woudl be a result of having no routable ipv6 traffic. + a.) user uses squid from Ubuntu as a proxy + b.) security.ubuntu.com and archive.ubuntu.com had additional IPV6 addresses added to their dns, such that there were 10 ipv6 addresses for each. + c.) the squid system does not have access to the ipv6 addresses. Most likely that woudl be a result of having no routable ipv6 traffic. The change as described in the upstream commit is: | Update forward_max_tries to permit 25 server paths - | + | | With cloud sites becoming more popular more CDN servers are producing | long lists of IPv6 and IPv4 addresses. If there are not enough paths | selected the IPv4 ones may never be reached. - [Test Case] The attached 'lp-1547640.sh' can be run with: - ./lp-1547640.sh setup - ./lp-1547640.sh test + ./lp-1547640.sh setup + ./lp-1547640.sh test It installs squid3 and sets up dnsmasq to know about 10 ipv6 addresses for a host, and then attempts to use that squid proxy. [Regression Potential] Likely scenarios to cause regression would be for hosts that have several ipv6 addresses. The change has been in squid3 upstream in trunk since 2013-08-21 and for quite a while though. It is released in squids 3.5 branch. [Other Info] After we saw and diagnosed this failure, Canonical's IS team removed one of the ipv6 addresses from security.ubuntu.com and archive.ubuntu.com, so that there are only 9 present now. - $ host archive.ubuntu.com | grep 'has IPv6' - archive.ubuntu.com has IPv6 address 2001:67c:1562::16 - archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::19 - archive.ubuntu.com has IPv6 address 2001:67c:1562::14 - archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::11 - archive.ubuntu.com has IPv6 address 2001:67c:1360:8001::17 - archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::13 - archive.ubuntu.com has IPv6 address 2001:67c:1562::17 - archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::18 - archive.ubuntu.com has IPv6 address 2001:67c:1562::15 + $ host archive.ubuntu.com | grep 'has IPv6' + archive.ubuntu.com has IPv6 address 2001:67c:1562::16 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::19 + archive.ubuntu.com has IPv6 address 2001:67c:1562::14 + archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::11 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8001::17 + archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::13 + archive.ubuntu.com has IPv6 address 2001:67c:1562::17 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::18 + archive.ubuntu.com has IPv6 address 2001:67c:1562::15 There *were* 10 on the day this caused a problem. Canonical will hold off on adding more ipv6 until this change is rolled out widely. + + The fix for this bug will come to xenial through a merge with debian + under bug 1473691. == End SRU Information == Many people run squid (squid-deb-proxy, or maas-proxy) to provide ubuntu archive mirror caching and proxying. MAAS sets this up by default for users with the 'maas-proxy' package. On or about Friday February 19, this setup began to fail for many people. Users would see 'apt-get update' returning 503 errors. For me, I saw 503 on security.ubuntu.com addresses. The reason for the failure was that the DNS records for Ubuntu reacheda threshold of 10 IPv6 entries. The squid proxy host did not have ipv6 connectivity and with a limit of 10 retries the failover does not reach any IPv4 addresses - thus would fail. The fix/workaround is to add the following to your squid config: # http://www.squid-cache.org/Doc/config/forward_max_tries/ forward_max_tries 25 The appropriate squid config file depends on what is running squid. maas-proxy: /usr/share/maas/maas-proxy.conf squid-deb-proxy: /etc/init/squid-deb-proxy.conf I'm not sure how this previously worked, nor what change was made. One change that was made in this time frame was a glibc update (2.19-0ubuntu6.6 to 2.19-0ubuntu6.7) for security (CVE-2013-7423 CVE-2014-9402 CVE-2015-1472 CVE-2015-1473). But it doesn't seem to make sense that that would change squid3 to start looking for records when it did not previously. i can verify that as late as Thu Feb 18 06:36:07 EST 2016 i was seeing entries in my squid
[Bug 1526264] Re: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16)
** Also affects: ntp (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1526264 Title: ntpdate fails with invalid argument when device is set to a date in the future (delta > 2^16) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1526264/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)
** Description changed: Squid's latest upstream version is currently 3.5 and fixes important bugs, such as the inability to fall back to IPv4 if a websites IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid-cache.org /squid-users/11/58389.html), #1213455, #1214379, #1459638, #1448149, #1390132, #1423498 and #1532560. Please update the package from 3.3.8 to the version that Debian already has in its distribution. Question 268037 already asked the same - here's the filed bug. + + Related bug: + * bug 1547640: proxy tries ipv6 and gets 503 when no ipv6 routes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1473691 Title: [FFe] squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
** Description changed: + == Begin SRU Information == + [Impact] + Users of squid3 as a proxy on a host without ipv6 connectivity will see http '503' errors if they attempt to access a url through that proxy that has greater than 9 ipv6 addresses associated with it. + + The failure case is that affected ubuntu users specifically was: + a.) user uses squid from Ubuntu as a proxy + b.) security.ubuntu.com and archive.ubuntu.com had additional IPV6 addresses added to their dns, such that there were 10 ipv6 addresses for each. + c.) the squid system does not have access to the ipv6 addresses. Most likely that woudl be a result of having no routable ipv6 traffic. + + The change as described in the upstream commit is: + | Update forward_max_tries to permit 25 server paths + | + | With cloud sites becoming more popular more CDN servers are producing + | long lists of IPv6 and IPv4 addresses. If there are not enough paths + | selected the IPv4 ones may never be reached. + + + [Test Case] + The attached 'lp-1547640.sh' can be run with: + ./lp-1547640.sh setup + ./lp-1547640.sh test + + It installs squid3 and sets up dnsmasq to know about 10 ipv6 addresses + for a host, and then attempts to use that squid proxy. + + [Regression Potential] + Likely scenarios to cause regression would be for hosts that have several ipv6 addresses. The change has been in squid3 upstream in trunk since 2013-08-21 and for quite a while though. It is released in squids 3.5 branch. + + [Other Info] + After we saw and diagnosed this failure, Canonical's IS team removed one of the ipv6 addresses from security.ubuntu.com and archive.ubuntu.com, so that there are only 9 present now. + $ host archive.ubuntu.com | grep 'has IPv6' + archive.ubuntu.com has IPv6 address 2001:67c:1562::16 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::19 + archive.ubuntu.com has IPv6 address 2001:67c:1562::14 + archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::11 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8001::17 + archive.ubuntu.com has IPv6 address 2001:67c:1560:8001::13 + archive.ubuntu.com has IPv6 address 2001:67c:1562::17 + archive.ubuntu.com has IPv6 address 2001:67c:1360:8c01::18 + archive.ubuntu.com has IPv6 address 2001:67c:1562::15 + + There *were* 10 on the day this caused a problem. Canonical will hold + off on adding more ipv6 until this change is rolled out widely. + + == End SRU Information == + Many people run squid (squid-deb-proxy, or maas-proxy) to provide ubuntu archive mirror caching and proxying. MAAS sets this up by default for users with the 'maas-proxy' package. On or about Friday February 19, this setup began to fail for many people. Users would see 'apt-get update' returning 503 errors. For me, I saw 503 on security.ubuntu.com addresses. The reason for the failure was that the DNS records for Ubuntu reacheda threshold of 10 IPv6 entries. The squid proxy host did not have ipv6 connectivity and with a limit of 10 retries the failover does not reach any IPv4 addresses - thus would fail. The fix/workaround is to add the following to your squid config: # http://www.squid-cache.org/Doc/config/forward_max_tries/ forward_max_tries 25 The appropriate squid config file depends on what is running squid. maas-proxy: /usr/share/maas/maas-proxy.conf squid-deb-proxy: /etc/init/squid-deb-proxy.conf I'm not sure how this previously worked, nor what change was made. One change that was made in this time frame was a glibc update (2.19-0ubuntu6.6 to 2.19-0ubuntu6.7) for security (CVE-2013-7423 CVE-2014-9402 CVE-2015-1472 CVE-2015-1473). But it doesn't seem to make sense that that would change squid3 to start looking for records when it did not previously. i can verify that as late as Thu Feb 18 06:36:07 EST 2016 i was seeing entries in my squid logs with 1455713142.896335 10.7.2.103 TCP_REFRESH_UNMODIFIED/200 82620 GET http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease - HIER_DIRECT/91.189.88.149 - but now i get 1455879482.210 1 10.7.2.103 TCP_REFRESH_FAIL/200 635 GET http://security.ubuntu.com/ubuntu/dists/precise-security/main/i18n/Index - HIER_DIRECT/2001:67c:1562::14 - -- 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/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547147] Re: libnss3-dev adds epoch 2 to the Version in pkg-config's pc file
This bug was fixed in the package nss - 2:3.21-0ubuntu0.12.04.2 --- nss (2:3.21-0ubuntu0.12.04.2) precise-security; urgency=medium * debian/rules: fix versioning since the last update incorrectly added an epoch. (LP: #1547147) -- Marc Deslauriers Mon, 22 Feb 2016 10:10:25 -0500 ** Changed in: nss (Ubuntu Precise) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1547147 Title: libnss3-dev adds epoch 2 to the Version in pkg-config's pc file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1547147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548863] [NEW] PDOException could not find driver
Public bug reported: Hi! I'm upgrade today php7.0 and get this problem. PHP 7.0.3-7+deb.sury.org~wily This version configure without supported pdo_mysql ? ** Affects: php7.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1548863 Title: PDOException could not find driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1548863/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548853] [NEW] 00powersave sleep hook misses claimed patch
Public bug reported: The pm-utils sleep hook installed at /usr/lib/pm- utils/sleep.d/00powersave was supposed to have been patched to prevent it running on ARM architectures. However a new case was added without deleting the preceding existing one (lines 12 on): case $1 in suspend|hibernate) pm-powersave false ;; suspend|hibernate) [ "$ARCH" != "${ARCH#arm}" ] || pm-powersave false ;; resume|thaw) pm-powersave ;; *) exit $NA ;; esac Observed in and affects 14.04.3,4.; seems to be OK in 14.10-15.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions] ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Tue Feb 23 13:51:14 2016 InstallationDate: Installed on 2016-02-21 (1 days ago) InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package-from-proposed trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1548853 Title: 00powersave sleep hook misses claimed patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1548853/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
@paul, I suspect the '25' is 25 ipv6 addresses. Thats based on our debugging and fix we put into place. We started seeing the bug when a 10th ipv6 address was added to archive.ubuntu.com (and security.ubuntu.com). The workaround we put in place was to remove a single ipv6 address, resulting in 9 addresses. So yes, it does just push the issue off, but a fairly large way off. @Amos, Thank you for your assessment. and pointer to the fix. ** Changed in: squid3 (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: squid3 (Ubuntu Wily) Status: Confirmed => Triaged -- 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/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1443249] Re: After kernel-3.13.0-41, wireless script checks wrong sys file.
*** This bug is a duplicate of bug 1544612 *** https://bugs.launchpad.net/bugs/1544612 ** This bug is no longer a duplicate of bug 1414110 Wireless powersave doesn't work (pm-utils) ** This bug has been marked a duplicate of bug 1544612 Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1443249 Title: After kernel-3.13.0-41, wireless script checks wrong sys file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1443249/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1414110] Re: Wireless powersave doesn't work (pm-utils)
*** This bug is a duplicate of bug 1544612 *** https://bugs.launchpad.net/bugs/1544612 Should be fixed along with bug 1544612. Marking as duplicate... ** This bug has been marked a duplicate of bug 1544612 Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1414110 Title: Wireless powersave doesn't work (pm-utils) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1414110/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1481780] ipmitool-1.8.13-1_usb+hpm_fixes-patch.diff
Default Comment by Bridge ** Attachment added: "ipmitool-1.8.13-1_usb+hpm_fixes-patch.diff" https://bugs.launchpad.net/bugs/1481780/+attachment/4579039/+files/ipmitool-1.8.13-1_usb+hpm_fixes-patch.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1481780 Title: ipmitool 1.8.13 needs 2 patches for OpenPower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1481780/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548797] Re: named crashed with SIGABRT in isc_assertion_failed()
*** This bug is a duplicate of bug 1547386 *** https://bugs.launchpad.net/bugs/1547386 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1547386, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1548797/+attachment/4578969/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578971/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578974/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578975/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578976/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578977/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1548797/+attachment/4578979/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1547386 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1548797 Title: named crashed with SIGABRT in isc_assertion_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1548797/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548440] Re: lxc: adt testing failing with 4.4.0-7.22
This bug was fixed in the package lxc - 2.0.0~rc2-0ubuntu2 --- lxc (2.0.0~rc2-0ubuntu2) xenial; urgency=medium * Fix apparmor profile loading order. -- Stéphane Graber Mon, 22 Feb 2016 17:24:44 -0500 ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- 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/1548440 Title: lxc: adt testing failing with 4.4.0-7.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548440/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1534065] Re: Install and configure Cinder controller node in Installation Guide
The issue is that this package did not get installed by default in a dedicated cinder node of Liberty and I had to manually install it. Running 'yum install openstack-cinder python-cinderclient' did not install 'python-oslo-policy'. It was installed manually since it gave the earlier mentioned error. This bug was raised to add this manual installation step to the installation document. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1534065 Title: Install and configure Cinder controller node in Installation Guide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1534065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1523921] Re: cloud-init disk_setup failure: 'list' object has no attribute 'splitlines'
Quick bump - any news on this? Cloud-init is rendered useless due to this bug. -- 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/1523921 Title: cloud-init disk_setup failure: 'list' object has no attribute 'splitlines' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1523921/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548731] [NEW] autostart on boot not working
Public bug reported: Description:Ubuntu 14.04.4 LTS Release:14.04 lxc: Installed: 1.0.8-0ubuntu0.3 Candidate: 1.0.8-0ubuntu0.3 Upstart service /etc/init/lxc.conf should start all LXC containers having set "lxc.start.auto = 1" if /etc/default/lxc got LXC_AUTO="true". This does not work on a "reboot"/"shutdown -r now" but it does work after a reboot using "restart lxc". It fails because of missing network devices (early boot up stage): lxc-start: conf.c: instantiate_veth: 3105 failed to attach 'vethMCUSEO' to the bridge 'lxcfr258': No such device lxc-start: conf.c: lxc_create_network: 3388 failed to create netdev lxc-start: start.c: lxc_spawn: 856 failed to create the network lxc-start: start.c: __lxc_start: 1121 failed to spawn 'xx' lxc-start: lxc_start.c: main: 341 The container failed to start. lxc-start: lxc_start.c: main: 345 Additional information can be obtained by setting the --logfile and --logpriority options. We do use a special veth setup but the lxc upstart service should still cover this case. --- /etc/init/lxc.conf 2015-11-18 20:08:53.0 +0100 +++ /tmp/lxc.conf 2016-02-23 11:30:08.704830042 +0100 @@ -1,7 +1,7 @@ description "lxc" author "Serge Hallyn " -start on runlevel [2345] +start on started networking stop on starting rc RUNLEVEL=[016] env LXC_AUTO="false" ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1548731 Title: autostart on boot not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548731/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1502539] Re: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build
Ставил последнюю. Ошибка осталась! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1502539 Title: open-vm-tools-dkms 2:9.10.2-2822639-1ubuntu3: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1502539/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548685] Re: System hangs, because NTPD drift file is blocked by AppArmor.
** Package changed: apparmor (Ubuntu) => ntp (Ubuntu) ** Description changed: NTPD drift file is not given permission in Apparmor configuration in "/etc/apparmor.d/usr.sbin.ntpd". Proper permission should be given to the drift file. EXPECTED RESULT No NTPD drift error print in syslog and system doesn't hang. ACTUAL RESULT At least on my development PC during heavy compilation whole system freezes and I need to do a forced shutdown. PRINT IN SYSLOG kernel: [ 3613.938660] type=1400 audit(1456152589.274:52): apparmor="DENIED" operation="mknod" profile="/usr/sbin/ntpd" name="/var/lib/ntp.drift.TEMP" pid=1832 comm="ntpd" requested_mask="c" denied_mask="c" fsuid=104 ouid=104 Feb 22 16:49:49 fid655548 ntpd[1832]: frequency file /var/lib/ntp.drift.TEMP: Permission denied FIX ... /etc/ntp.drift rwl, /etc/ntp.drift.TEMP rwl, /etc/ntp/drift* rwl, /var/lib/ntp/*drift rw, /var/lib/ntp/*drift.TEMP rw, /var/lib/ntp.drift.TEMP rw, <-- THIS WAS MISSING ... ~$ lsb_release -rd Description: Ubuntu 14.04.4 LTS Release: 14.04 $ apt-cache policy ntp ntp: Installed: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 Candidate: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 Version table: *** 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 0 - 500 http://mirrors.bit.bittium.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status - 1:4.2.6.p5+dfsg-3ubuntu2.14.04.5 0 - 500 http://mirrors.bit.bittium.com/ubuntu//ubuntu/ trusty-security/main amd64 Packages 1:4.2.6.p5+dfsg-3ubuntu2 0 - 500 http://mirrors.bit.bittium.com/ubuntu/ trusty/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1548685 Title: System hangs, because NTPD drift file is blocked by AppArmor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1548685/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548685] [NEW] System hangs, because NTPD drift file is blocked by AppArmor.
You have been subscribed to a public bug: NTPD drift file is not given permission in Apparmor configuration in "/etc/apparmor.d/usr.sbin.ntpd". Proper permission should be given to the drift file. EXPECTED RESULT No NTPD drift error print in syslog and system doesn't hang. ACTUAL RESULT At least on my development PC during heavy compilation whole system freezes and I need to do a forced shutdown. PRINT IN SYSLOG kernel: [ 3613.938660] type=1400 audit(1456152589.274:52): apparmor="DENIED" operation="mknod" profile="/usr/sbin/ntpd" name="/var/lib/ntp.drift.TEMP" pid=1832 comm="ntpd" requested_mask="c" denied_mask="c" fsuid=104 ouid=104 Feb 22 16:49:49 fid655548 ntpd[1832]: frequency file /var/lib/ntp.drift.TEMP: Permission denied FIX ... /etc/ntp.drift rwl, /etc/ntp.drift.TEMP rwl, /etc/ntp/drift* rwl, /var/lib/ntp/*drift rw, /var/lib/ntp/*drift.TEMP rw, /var/lib/ntp.drift.TEMP rw, <-- THIS WAS MISSING ... ~$ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy ntp ntp: Installed: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 Candidate: 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 Version table: *** 1:4.2.6.p5+dfsg-3ubuntu2.14.04.8 0 500 http://mirrors.bit.bittium.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.6.p5+dfsg-3ubuntu2.14.04.5 0 500 http://mirrors.bit.bittium.com/ubuntu//ubuntu/ trusty-security/main amd64 Packages 1:4.2.6.p5+dfsg-3ubuntu2 0 500 http://mirrors.bit.bittium.com/ubuntu/ trusty/main amd64 Packages ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- System hangs, because NTPD drift file is blocked by AppArmor. https://bugs.launchpad.net/bugs/1548685 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1545821] Re: Regression: spice usbredirect causes windows client to crash
Excellent -- However, ATM I'm away on business and I won't be able to try this until next week. I'll report my findings then. -- 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/1545821 Title: Regression: spice usbredirect causes windows client to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1545821/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs