[Group.of.nepali.translators] [Bug 1736804] Re: No tcp_keepalive_time in LXD container
The reporter states in the linuxcontainers.org discussion and in this bug description that he's not using an Ubuntu kernel. This is fixed in Ubuntu 18.04 and will soon be available in Ubuntu 16.04 via the hardware enablement kernel. I'm marking this Xenial task as Won't Fix in regards to its 4.4 kernel. ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1736804 Title: No tcp_keepalive_time in LXD container Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Bug description: Using LXD v2.20 on Ubuntu 16.04 host, with kernel Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I get the following # cat /proc/sys/net/ipv4/tcp_keepalive_time cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory I'm informed from linuxcontainers.org, that this is a kernel bug. https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891 I happen to be trying to run Kolab.org in a container, and some of their python code errors as this is parameter is not found. Clearly someone has found this in Kolab before as there's a patch https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch But the problem is in other places too. It could be argued that Kolab should code round this issue. But on the other hand, with out it, and in general, other applications would not run in containers, which perhaps is a undesirable limitation. Thus it's why I'm reporting here. And there may be other parameters not appearing in the container too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736804/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1736804] Re: No tcp_keepalive_time in LXD container
The commit mentioned in comment #4 has been upstream since kernel v4.5. Marking the main linux task as fix released. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1736804 Title: No tcp_keepalive_time in LXD container Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Incomplete Bug description: Using LXD v2.20 on Ubuntu 16.04 host, with kernel Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I get the following # cat /proc/sys/net/ipv4/tcp_keepalive_time cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory I'm informed from linuxcontainers.org, that this is a kernel bug. https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891 I happen to be trying to run Kolab.org in a container, and some of their python code errors as this is parameter is not found. Clearly someone has found this in Kolab before as there's a patch https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch But the problem is in other places too. It could be argued that Kolab should code round this issue. But on the other hand, with out it, and in general, other applications would not run in containers, which perhaps is a undesirable limitation. Thus it's why I'm reporting here. And there may be other parameters not appearing in the container too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736804/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779963] Re: create pull-ppa-* functionality
@mapreri I'll see if I can get around to it one of these days, the delta certainly is getting big between my fork and the 'official' git. As you know, after over a year of bugging/begging people to review/merge my changes, I gave up and forked so I could actually keep adding functionality and fixing bugs in ubuntu-dev-tools. Meanwhile, pull-ppa-* now auto-detects the 'latest' release/series that a package is built for (in a PPA) so it doesn't always assume all PPAs have builds for the latest devel release. https://launchpad.net/~ddstreet/+archive/ubuntu/ubuntu-dev-tools ** Changed in: ubuntu-dev-tools (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: ubuntu-dev-tools (Ubuntu Cosmic) Status: In Progress => Fix Released ** Changed in: ubuntu-dev-tools (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1779963 Title: create pull-ppa-* functionality Status in ubuntu-dev-tools package in Ubuntu: Fix Released Status in ubuntu-dev-tools source package in Trusty: Won't Fix Status in ubuntu-dev-tools source package in Xenial: Fix Released Status in ubuntu-dev-tools source package in Artful: Won't Fix Status in ubuntu-dev-tools source package in Bionic: Fix Released Status in ubuntu-dev-tools source package in Cosmic: Fix Released Bug description: the pull-[lp|debian|uca]-[source|debs|ddebs|udebs] allows pulling from the 3 major archives, but not PPAs. Functionality is needed to be able to pull from specific PPAs. See ppa:ddstreet/ubuntu-dev-tools for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1779963/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Tags added: kernel-da-key xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1783385] Re: intel-microcode: update to 20180703 drop
This was fixed in cosmic in https://launchpad.net/ubuntu/+source/intel- microcode/3.20180703.2ubuntu1 ; pacakge for trusty, xenial, and bionic are available for testing in the ubuntu-security-proposed ppa: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ . Please note that packages in this ppa are for testing only and have not been widely tested, and thus should not be used in production. Thanks. ** Changed in: intel-microcode (Ubuntu) Status: New => Fix Released ** Changed in: intel-microcode (Ubuntu Trusty) Status: New => In Progress ** Changed in: intel-microcode (Ubuntu Xenial) Status: New => In Progress ** Changed in: intel-microcode (Ubuntu Bionic) Status: New => In Progress ** Changed in: intel-microcode (Ubuntu Bionic) Assignee: (unassigned) => Steve Beattie (sbeattie) ** Changed in: intel-microcode (Ubuntu Xenial) Assignee: (unassigned) => Steve Beattie (sbeattie) ** Changed in: intel-microcode (Ubuntu Trusty) Assignee: (unassigned) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1783385 Title: intel-microcode: update to 20180703 drop Status in intel-microcode package in Ubuntu: Fix Released Status in intel-microcode source package in Trusty: In Progress Status in intel-microcode source package in Xenial: In Progress Status in intel-microcode source package in Bionic: In Progress Bug description: Intel has released a new version of their microcode, that starts to address Rogue System Register Read (RSRE, aka Spectre Variant 3a, CVE-2018-3640) and Speculative Store Bypass (SSB, aka Spectre Variant 4, CVE-2018-3639). Reference: https://downloadcenter.intel.com/download/27945/Linux- Processor-Microcode-Data-File To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1783385/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1777600] Re: chzdev can't find modprobe
** No longer affects: s390-tools (Ubuntu Artful) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: New Status in s390-tools source package in Bionic: New Status in s390-tools source package in Cosmic: Fix Released Bug description: Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1777600] Re: chzdev can't find modprobe
This bug was fixed in the package s390-tools - 2.5.0-0ubuntu1 --- s390-tools (2.5.0-0ubuntu1) cosmic; urgency=medium * New upstream release LP: #1776907 LP: #1775627 LP: #1775632 * Drop udevadm patch, no longer needed * Refresh patches * Import upstream patches since v2.5.0 LP: #1777600 -- Dimitri John Ledkov Tue, 24 Jul 2018 17:00:03 +0100 ** Changed in: s390-tools (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1777600 Title: chzdev can't find modprobe Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Invalid Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: New Status in s390-tools source package in Artful: New Status in s390-tools source package in Bionic: New Status in s390-tools source package in Cosmic: Fix Released Bug description: Description: only when trying to change some attributes chzdev fails because it cant find modprobe under Ubuntu 18.04 root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5 sh: 1: /usr/sbin/modprobe: not found zfcp device type configure failed Error: Command failed (exit code 127): /usr/sbin/modprobe -r zfcp root@m83lp09:~# whereis modprobe modprobe: /sbin/modprobe /etc/modprobe.d /lib/modprobe.d /usr/share/man/man8/modprobe.8.gz Potential solution ? : adding a symlink is a workaround, is this path hardcoded? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1777600/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
Per discussion above: - Closing the kernel tasks - Raising priority on apparmor tasks to Critical (to match what kernel had) - Assigning to jjohansen as the AppArmor maintainer As we care about xenial, bionic and cosmic, we need point releases (or cherry-pick) for: - AppArmor 2.10 (2.10.95 in xenial) - AppArmor 2.12 (2.12 in bionic and cosmic) John: Any ETA for those two point releases or pointer to a commit which we could SRU on its own? For now our focus is obviously on getting this resolved in Ubuntu as soon as possible, since it's breaking a number of systemd services that are now (18.04) shipping with more confinement than in the past. The same issue is also currently preventing us from starting newer Fedora and Arch containers on Ubuntu. Our standard response so far has been to tell users to turn off AppArmor for those containers, but it's obviously not an answer we like to give (I'm sure you'll agree). ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: apparmor (Ubuntu) Status: New => Triaged ** Changed in: apparmor (Ubuntu Xenial) Status: New => Triaged ** Changed in: apparmor (Ubuntu Bionic) Status: New => Triaged ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Critical => Undecided ** Changed in: linux (Ubuntu Xenial) Importance: High => Undecided ** Changed in: linux (Ubuntu Bionic) Importance: High => Undecided ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: apparmor (Ubuntu Xenial) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: apparmor (Ubuntu Bionic) Assignee: (unassigned) => John Johansen (jjohansen) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Changed in: linux (Ubuntu) Importance: High => Critical ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1701222] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Won't Fix Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1698919] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux-raspi2 (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1698919 Title: CVE-2017-1000364 Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-joule package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Trusty: New Status in linux-aws source package in Trusty: Invalid Status in linux-azure source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-gke source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-hwe source package in Trusty: Invalid Status in linux-hwe-edge source package in Trusty: Invalid Status in linux-joule source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-flo source package in Xenial: Invalid Status in linux-gke source package in Xenial: New Status in linux-goldfish source package in Xenial: New Status in linux-hwe source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-joule source package in Xenial: New Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Invalid Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: New Status in linux-snapdragon source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-aws source package in Yakkety: Invalid Status in linux-azure source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Invalid Status in linux-gke source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: New Status in linux-hwe source package in Yakkety: Invalid Status in linux-hwe-edge source package in Yakkety: Invalid Status in linux-joule source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Invalid Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: New Status in linux-snapdragon source package in Yakkety: New Status in linux-ti-omap4 source package in Yakkety: Invalid Status in linux source package in Zesty: New Status in linux-aws source package in Zesty: Invalid Status in linux-azure source package in Zesty: Invalid Status in linux-flo source package in Zesty: Invalid Status in linux-gke source package in Zesty: Invalid Status in linux-goldfish source package in Zesty: New Status in linux-hwe source package in Zesty:
[Group.of.nepali.translators] [Bug 1698919] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1698919 Title: CVE-2017-1000364 Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-joule package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Trusty: New Status in linux-aws source package in Trusty: Invalid Status in linux-azure source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-gke source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-hwe source package in Trusty: Invalid Status in linux-hwe-edge source package in Trusty: Invalid Status in linux-joule source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-flo source package in Xenial: Invalid Status in linux-gke source package in Xenial: New Status in linux-goldfish source package in Xenial: New Status in linux-hwe source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-joule source package in Xenial: New Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Invalid Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: New Status in linux-snapdragon source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-aws source package in Yakkety: Invalid Status in linux-azure source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Invalid Status in linux-gke source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: New Status in linux-hwe source package in Yakkety: Invalid Status in linux-hwe-edge source package in Yakkety: Invalid Status in linux-joule source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Invalid Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: New Status in linux-snapdragon source package in Yakkety: New Status in linux-ti-omap4 source package in Yakkety: Invalid Status in linux source package in Zesty: New Status in linux-aws source package in Zesty: Invalid Status in linux-azure source package in Zesty: Invalid Status in linux-flo source package in Zesty: Invalid Status in linux-gke source package in Zesty: Invalid Status in linux-goldfish source package in Zesty: New Status in linux-hwe source package in Zesty:
[Group.of.nepali.translators] [Bug 1699772] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Incomplete Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1711407] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1715271] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1715271 Title: Middle button of trackpoint doesn't work Status in HWE Next: Opinion Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Middle button doesn't work on several Thinkpad laptops like E570, E475, E470, E575 and X1Carbon. When middle button fails to work, logs show: psmouse serio2: trackpoint: failed to get extended button data It fails to read out ext button info via PS2 command. Almost all the Thinkpad have 3 buttons, so set it to 3 button when it fails to read button info. And on Lenovo X1, there is a new version of trackpoint, add this ID for this new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1715271/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1545542] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1545542 Title: Enable arm64 emulation of removed ARMv7 instructions Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: New Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: Linux now supports emulation of three deprecated ARMv7 features that were removed from ARMv8: SWP(B), CP15ISB/DSB/DMB, and SETEND. At least CP15DMB is used by some armhf archive binaries (notably pandoc), so we need emulation enabled on the kernels that scalingstack uses. I haven't checked which version added which, but they appeared some time between 3.13 and 4.2, and I only care about 4.2 onwards. So please enable ARMV8_DEPRECATED, SWP_EMULATION, CP15_BARRIER_EMULATION and SETEND_EMULATION in arm64 kernels for wily onwards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545542/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1713884] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1713884 Title: [CIFS] Fix maximum SMB2 header size Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Currently the maximum size of SMB2/3 header is set incorrectly which leads to hanging of directory listing operations on encrypted SMB3 connections. Fix this by setting the maximum size to 170 bytes that is calculated as RFC1002 length field size (4) + transform header size (52) + SMB2 header size (64) + create response size (56). https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de This applies across the board 3.16, 4.4, 4.10, artful, and azure. Microsoft would be happy to help test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1721842] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1721842 Title: CVE-2017-1000255 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux-hwe source package in Zesty: Invalid Status in linux source package in Artful: Won't Fix Status in linux-hwe source package in Artful: Invalid Bug description: CRD: 2017-10-09 CVE: CVE-2017-1000255 Affected series: zesty and the corresponding xenial/linux-hwe, Power8 PPC hardware only, so derived kernels (arm + clouds) are not affected. Patches: sent by email To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721842/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1724044] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie
artful. The bug task representing the artful nomination is being closed
as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1724044
Title:
autopkgtest regression due to only building single FLAVOUR
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Trusty:
Triaged
Status in linux source package in Xenial:
Triaged
Status in linux source package in Zesty:
Triaged
Status in linux source package in Artful:
Won't Fix
Status in linux source package in Bionic:
Triaged
Bug description:
commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel)
changed autopkgtest to only build the first 'flavour'. However, this
causes failure on armhf because the 'lpae' flavour is still expected,
e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz
Debug: do-binary-udebs
dh_testdir
dh_testroot
# unpack the kernels into a temporary directory
mkdir -p debian/d-i-armhf
imagelist=$(cat
/tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions |
grep ^armhf | gawk '{print $4}') && \
for i in $imagelist; do \
dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \
debian/d-i-armhf; \
if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \
dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \
debian/d-i-armhf; \
fi; \
/sbin/depmod -b debian/d-i-armhf $i; \
done
ls: cannot access
../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file
or directory
dpkg-deb: error: --extract needs a target directory.
Either this should be reverted to build all flavours, or the
build/autopkgtest needs to updated also to not expect the lpae flavour (or
other than base flavour).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714859] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1714859 Title: oops in 4.4.0-62-generic (ppc64le) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Won't Fix Bug description: Sep 1 14:23:30 p87 kernel: [17274563.423972] device vnet2 entered promiscuous mode Sep 1 14:23:30 p87 kernel: [17274563.436101] br0: port 4(vnet2) entered forwarding state Sep 1 14:23:30 p87 kernel: [17274563.436113] br0: port 4(vnet2) entered forwarding state Sep 1 14:23:31 p87 kernel: [17274564.005034] audit: type=1400 audit(1504239811.140:793): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=18952 comm="apparmor_parser" Sep 1 14:23:31 p87 kernel: [17274564.019911] audit: type=1400 audit(1504239811.156:794): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=18952 comm="apparmor_parser" Sep 1 14:23:31 p87 kernel: [17274564.324291] KVM guest htab at c079a100 (order 29), LPID 3 Sep 1 14:23:45 p87 kernel: [17274578.483572] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:53 p87 kernel: [17274766.572284] br0: port 4(vnet2) entered disabled state Sep 1 14:26:53 p87 kernel: [17274766.579930] device vnet2 left promiscuous mode Sep 1 14:26:53 p87 kernel: [17274766.579932] br0: port 4(vnet2) entered disabled state Sep 1 14:26:54 p87 kernel: [17274767.303109] audit: type=1400 audit(1504240014.441:795): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22668 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.917394] audit: type=1400 audit(1504240016.053:796): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22672 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.917673] audit: type=1400 audit(1504240016.053:797): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=22672 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274768.982783] device vnet2 entered promiscuous mode Sep 1 14:26:56 p87 kernel: [17274768.994891] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:56 p87 kernel: [17274768.994902] br0: port 4(vnet2) entered forwarding state Sep 1 14:26:56 p87 kernel: [17274769.535982] audit: type=1400 audit(1504240016.673:798): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5" pid=22702 comm="apparmor_parser" Sep 1 14:26:56 p87 kernel: [17274769.546719] audit: type=1400 audit(1504240016.685:799): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-435e8619-e460-4c31-98b9-01dc8eab0cc5//qemu_bridge_helper" pid=22702 comm="apparmor_parser" Sep 1 14:26:57 p87 kernel: [17274769.861666] KVM guest htab at c079a100 (order 29), LPID 3 Sep 1 14:27:11 p87 kernel: [17274784.050382] br0: port 4(vnet2) entered forwarding state Sep 1 14:28:30 p87 kernel: [17274863.605174] Unable to handle kernel paging request for data at address 0x0008 Sep 1 14:28:30 p87 kernel: [17274863.605188] Faulting instruction address: 0xc044edcc Sep 1 14:28:30 p87 kernel: [17274863.605195] Oops: Kernel access of bad area, sig: 11 [#1] Sep 1 14:28:30 p87 kernel: [17274863.605199] SMP NR_CPUS=2048 NUMA PowerNV Sep 1 14:28:30 p87 kernel: [17274863.605206] Modules linked in: tcp_diag inet_diag ebtable_filter ebtables binfmt_misc veth xfrm_user xfrm_algo vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter overlay bridge stp llc kvm_hv uio_pdrv_genirq powernv_rng ibmpowernv vmx_crypto leds_powernv uio ipmi_powernv ipmi_msghandler kvm_pr kvm autofs4 xfs btrfs raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 ses enclosure mlx4_en be2net lpfc mlx4_core vxlan ip6_udp_tunnel
[Group.of.nepali.translators] [Bug 1729256] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1729256 Title: Invalid btree pointer causes the kernel NULL pointer dereference Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: [Impact] The frequent kernel errors can be seen inside the XFS based OSD processes and it causes to crash and restart. BUG: unable to handle kernel NULL pointer dereference at 00a0 IP: [] xfs_da3_node_read+0x30/0xb0 [xfs] CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016 task: 880620f38e00 ti: 880678228000 task.ti: 880678228000 RIP: 0010:[] [] xfs_da3_node_read+0x30/0xb0 [xfs] RSP: 0018:88067822bd00 EFLAGS: 00010286 RAX: RBX: 88078abff3f0 RCX: 0001 RDX: RSI: RDI: 88067822bcb0 RBP: 88067822bd20 R08: 0001 R09: fffe R10: ea001e2aff80 R11: 0001 R12: 88067822bd50 R13: 8805a37f R14: 0001 R15: 8d180e3e FS: 7f7573c01700() GS:88103fa0()knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Stack: c03cfb50 c03b0ecc 88067822bde0 0001 88067822bd98 c038c8b3 00020008 88081cb06040 0002d8723bf8 880fc142ae80 Call Trace: [] ? xfs_trans_roll+0x2c/0x50 [xfs] [] xfs_attr3_node_inactive+0x183/0x220 [xfs] [] xfs_attr3_root_inactive+0xac/0x100 [xfs] [] xfs_attr_inactive+0x14c/0x1a0 [xfs] [] xfs_inactive+0x85/0x120 [xfs] [] xfs_fs_evict_inode+0xa5/0x100 [xfs] [] evict+0xbe/0x190 [] iput+0x1c1/0x240 [] do_unlinkat+0x199/0x2d0 [] SyS_unlink+0x16/0x20 [] entry_SYSCALL_64_fastpath+0x16/0x71 [Fix] commit e678a63e6c95f140befe6fcd81b49075ecb3c701 Author: Brian Foster Date: Mon Oct 9 11:38:56 2017 -0700 xfs: reinit btree pointer on attr tree inactivation walk xfs_attr3_root_inactive() walks the attr fork tree to invalidate the associated blocks. xfs_attr3_node_inactive() recursively descends from internal blocks to leaf blocks, caching block address values along the way to revisit parent blocks, locate the next entry and descend down that branch of the tree. The code that attempts to reread the parent block is unsafe because it assumes that the local xfs_da_node_entry pointer remains valid after an xfs_trans_brelse() and re-read of the parent buffer. Under heavy memory pressure, it is possible that the buffer has been reclaimed and reallocated by the time the parent block is reread. This means that 'btree' can point to an invalid memory address, lead to a random/garbage value for child_fsb and cause the subsequent read of the attr fork to go off the rails and return a NULL buffer for an attr fork offset that is most likely not allocated. Note that this problem can be manufactured by setting XFS_ATTR_BTREE_REF to 0 to prevent LRU caching of attr buffers, creating a file with a multi-level attr fork and removing it to trigger inactivation. To address this problem, reinit the node/btree pointers to the parent buffer after it has been re-read. This ensures btree points to a valid record and allows the walk to proceed. [Test] The patch has been tested on the production system. [Regression Risk] Clean cherry-pick queued for stable, so we'll be picking it up anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729256/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1673498] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1673498 Title: move aufs.ko from -extra to linux-image package Status in linux package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Committed Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-gke source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Docker is ordinarily configured to use aufs, but the aufs kernel module is only available after installing the linux-image-extra package. Please promote aufs.ko from the linux-image-extra package to the main linux-image package for all supported Ubuntu kernels and derivatives, so as to remove Docker's dependence on linux-image-extra. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673498/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1698919] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux-snapdragon (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1698919 Title: CVE-2017-1000364 Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-joule package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Trusty: New Status in linux-aws source package in Trusty: Invalid Status in linux-azure source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-gke source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-hwe source package in Trusty: Invalid Status in linux-hwe-edge source package in Trusty: Invalid Status in linux-joule source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-flo source package in Xenial: Invalid Status in linux-gke source package in Xenial: New Status in linux-goldfish source package in Xenial: New Status in linux-hwe source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-joule source package in Xenial: New Status in linux-lts-utopic source package in Xenial: Invalid Status in linux-lts-vivid source package in Xenial: Invalid Status in linux-lts-wily source package in Xenial: Invalid Status in linux-lts-xenial source package in Xenial: Invalid Status in linux-mako source package in Xenial: Invalid Status in linux-manta source package in Xenial: Invalid Status in linux-raspi2 source package in Xenial: New Status in linux-snapdragon source package in Xenial: New Status in linux-ti-omap4 source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Status in linux-aws source package in Yakkety: Invalid Status in linux-azure source package in Yakkety: Invalid Status in linux-flo source package in Yakkety: Invalid Status in linux-gke source package in Yakkety: Invalid Status in linux-goldfish source package in Yakkety: New Status in linux-hwe source package in Yakkety: Invalid Status in linux-hwe-edge source package in Yakkety: Invalid Status in linux-joule source package in Yakkety: Invalid Status in linux-lts-utopic source package in Yakkety: Invalid Status in linux-lts-vivid source package in Yakkety: Invalid Status in linux-lts-wily source package in Yakkety: Invalid Status in linux-lts-xenial source package in Yakkety: Invalid Status in linux-mako source package in Yakkety: Invalid Status in linux-manta source package in Yakkety: Invalid Status in linux-raspi2 source package in Yakkety: New Status in linux-snapdragon source package in Yakkety: New Status in linux-ti-omap4 source package in Yakkety: Invalid Status in linux source package in Zesty: New Status in linux-aws source package in Zesty: Invalid Status in linux-azure source package in Zesty: Invalid Status in linux-flo source package in Zesty: Invalid Status in linux-gke source package in Zesty: Invalid Status in linux-goldfish source package in Zesty: New Status in linux-hwe source package in
[Group.of.nepali.translators] [Bug 1747134] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1747134/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1729337] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie
artful. The bug task representing the artful nomination is being closed
as Won't Fix.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1729337
Title:
CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
In Progress
Status in linux source package in Artful:
Won't Fix
Bug description:
== SRU Justification ==
The bug reporter stated they have a cluster of servers that applied Xenial
updates
and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 do not hit the regression. It was found that the
regression is fixed by mainline commit:
4587eee04e2a ("SMB3: Validate negotiate request must always be signed").
This fix is required in all Ubuntu supported releases. Commit 4587eee04e2a
landed in mailine as of 4.14-rc7. It was also cc'd to upstream stable,
but it has not landed in any stable releases yet, which is the reason for
this SRU.
== Fix ==
commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
Author: Steve French
Date: Wed Oct 25 15:58:31 2017 -0500
SMB3: Validate negotiate request must always be signed
== Regression Potential ==
This patch is to fix a regression. It was also cc'd to upstream stable, so
it received addition review upstream.
We have a cluster of servers that applied a security update overnight
and were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 were fine the night before, and are fine
after downgrading. The only error message CIFS would report, even on
verbose, was:
[ 257.089876] CIFS VFS: validate protocol negotiate failed: -11
[ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5
Rebooting did not help. Nor did attempting to mount the share
manually using mount -t cifs.
Here's the offending line from our /etc/fstab (with hostnames
sanitized):
//server/share /mnt/share cifs
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
,exec,soft,noserverino,vers=3.0 0 0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 1 07:56 seq
crw-rw 1 root audio 116, 33 Nov 1 07:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Nov 1 08:49:47 2017
HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
InstallationDate: Installed on 2016-12-16 (319 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic
root=/dev/mapper/ubuntu--template--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-98-generic N/A
linux-backports-modules-4.4.0-98-generic N/A
linux-firmware1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions
___
[Group.of.nepali.translators] [Bug 1749961] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux package in Debian: New Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1752692] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1752692 Title: Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-hwe source package in Xenial: Confirmed Status in linux source package in Artful: Won't Fix Status in linux-hwe source package in Artful: Invalid Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 There are 4 cards each with 4 devices on http://www.hauppauge.co.uk/site/products/data_quadhd.html Installed tvheadend. Lspci shows all the 4 cards. But only 2 cards in /dev/dvb/ since 2 cards makes 8 adapters. Whitch is the limit in kernel at the moment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 1 19:57:25 2018 InstallationDate: Installed on 2018-02-14 (15 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm-256color PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752692/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1755118] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1755118 Title: Unable to create KVM with uvtool on A/X/X-hwe ppc64le system Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Won't Fix Bug description: When trying to create a KVM instance with uvtool on Artful ppc64le, it always report that the created instance was not running. Steps: sudo su apt-get install qemu-kvm uvtool -y ssh-keygen -t rsa -N '' uvt-simplestreams-libvirt sync release=artful arch=ppc64el uvt-kvm create kvm-test release=artful arch=ppc64el uvt-kvm wait kvm-test --insecure Result: uvt-kvm: error: libvirt domain 'kvm-test' is not running. This issue might be related to bug 1452016 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 12 08:03 seq crw-rw 1 root audio 116, 33 Mar 12 08:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 12 08:40:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 9.65 5.79 4.46 1/1853 109388 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.13.0-37-generic (buildd@bos02-ppc64el-004) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:12:30 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.695 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.695 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755118/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1757422] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: New Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1755268] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and mlx4_en driver (when bonding and sriov enabled) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Bug description: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -machine pc-i440fx-xenial,accel=kvm,usb=off -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] mlx4_en: eno1d1: Fail to bond device [74390.750758] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 [74391.152326] general protection fault: [#1] SMP PTI [74391.410424] cache_from_obj: Wrong slab cache. kmalloc-256 but object is from kmalloc-192 kernel trace log in attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Mar 12 19:59:16 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Group.of.nepali.translators] [Bug 1760099] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1760099 Title: Additional spectre and meltdown patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-03-29 08:53:56 == Hi Canonical, There are some additional patches for Spectre and Meltdown that is required on ppc64el. We would need to have them included on all Ubuntu kernels. This is the patch series: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown http://patchwork.ozlabs.org/project/linuxppc- dev/list/?series=36012=* == Comment: #1 - Breno Leitao - 2018-03-29 08:55:48 == This is a better formatted patch series list: [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1() [v2,08/10] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus() [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown() [v2,05/10] powerpc/64s: Move cpu_show_meltdown() [v2,04/10] powerpc/powernv: Set or clear security feature flags [v2,03/10] powerpc/pseries: Set or clear security feature flags [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1760099/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775784] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775784 Title: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Bug description: <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24~16.04.1 ProcVersionSignature: User Name 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 08:08:27 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775784/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1777029] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1777029 Title: fscache: Fix hanging wait on page discarded by writeback Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == [Impact] Under heavy NFS + FSCache load, a user sometimes observes a hang in __fscache_wait_on_page_write+0x5f/0xa0. Example traces: [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache] [] __fscache_uncache_all_inode_pages+0xba/0x120 [fscache] [] nfs_fscache_open_file+0x4e/0xc0 [nfs] [] __fscache_wait_on_page_write+0x5f/0xa0 [fscache] [] __nfs_fscache_invalidate_page+0x2c/0x80 [nfs] [] nfs_invalidate_page+0x63/0x90 [nfs] [] truncate_inode_page+0x80/0x90 [Fix] Cherry-pick 2c98425720233ae3e135add0c7e869b32913502f from upstream, which is a patch from the FSCache maintainer. [Testcase] The user has run a NFS stress-test with a similar home-grown patch, and will run a stress test on the proposed kernel. [Regression Potential] Patch is limited to FSCache, so regression potential is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777029/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
Verified with Xenial Azure cloud, it works as expected. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial ** No longer affects: lttng-modules -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: In Progress Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: Fix Released Bug description: SRU Request: [Impact] After bionic/linux-azure commit 4fbb658dd8ce96384852ceae18b0b09034de7b36 (UBUNTU: [Config] azure: CONFIG_HOTPLUG_CPU=n) the lttng_tracer module cannot find some symbols and cannot be loaded. kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) This is caused by lttng-modules incorrectly handling the case when CONFIG_HOTPLUG_CPU is not enabled. [Test Case] Install linux-azure >= 4.15.0-1014, install lttng-modules-dkms and run the autotest ubuntu_lttng_smoke_test testcase (or just 'sudo lttng list --kernel'). [Fix] commit 894ce5dc825733d1ccab25b1aede9ce0be2a7c4e (Fix: do not use CONFIG_HOTPLUG_CPU for the new hotplug API) commit 1ee63d8d1b0aaf30564d3879d8e9282d0ddfef1b (Cleanup: comment about CONFIG_HOTPLUG_CPU ifdef) [Regression Potential] Very low. The two patches can be cleanly cherry-picked from the upstream commits. The first one that really fixed the issue just changes a single #ifdef to compile a piece of code when CONFIG_HOTPLUG_CPU is not defined. The second one just updates some comments on the code to make them consistent with the changes. [Original Description] This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key kernel: [ 639.753366] lttng_tracer: Unknown symbol
[Group.of.nepali.translators] [Bug 1762491] Re: [SRU] No graphics after update, caused by virtualbox
This bug was fixed in the package virtualbox-guest-additions-iso - 5.1.38-0ubuntu1.16.04.1 --- virtualbox-guest-additions-iso (5.1.38-0ubuntu1.16.04.1) xenial; urgency=medium * New upstream version 5.1.38 - LP: #1762491 * Update copyright file -- Gianfranco Costamagna Tue, 10 Jul 2018 13:04:33 +0200 ** Changed in: virtualbox-hwe (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762491 Title: [SRU] No graphics after update, caused by virtualbox Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-ext-pack package in Ubuntu: Fix Released Status in virtualbox-guest-additions-iso package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in virtualbox source package in Xenial: Fix Released Status in virtualbox-ext-pack source package in Xenial: Fix Released Status in virtualbox-guest-additions-iso source package in Xenial: Fix Released Status in virtualbox-hwe source package in Xenial: Fix Released Bug description: [Impact] * ubuntu when used as a guest inside a Virtualbox VM machine [Test Case] * Install Ubuntu and mate or other DM, experience a black screen * Install vbox on xenial with guest and host. Test if everything works and starts with 3d enabled and disabled, as well as different Desktop Managers. [ autopkgtests ] * this package has a really huge autopkgtest suite performed by upstream on each release, and this is the reason for me using the new release as-is instead of patching old versions. [Regression Potential] * This is part of virtualbox on Debian and Ubuntu since bionic and 3 months Author: Gianfranco Costamagna Date: Tue Apr 24 00:15:39 2018 +0200 basically, I now detect at runtime the --check3d switch, and enable the mesa override only for desktop and not for applications, the same as the official guest-additions packages do. this is the code: + if /usr/bin/VBoxClient --check3d 2>/dev/null; then + if test -e /usr/lib/virtualbox/additions/00vboxvideo.conf; then + cp -f /usr/lib/virtualbox/additions/00vboxvideo.conf /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi + fi + if test -e /etc/ld.so.conf.d/00vboxvideo.conf; then + rm -f /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi the update-alternatives switch can't work when 3d is not enabled, and with user applications using mesa-specific features. [ upstream changes ] Version 5.1.38 (2018-05-09) Linux hosts: support Linux 4.17 changes. Thank you Larry Finger Linux guests: support Linux 4.16 and EL 7.5 kernels (bugs #17676 and #17678) Linux guests: 3D fixes for recent guests (bug #17623) Version 5.1.36 (2018-04-17) VMM: Fixed missing NULL pointer check in MMIO code. Network: fixed VERR_INTNET_FLT_IF_NOT_FOUND when bridging to some adapters on Windows hosts (possibly related bugs #15294, #15060, #13481) [Other info] After performing an "apt-get update && apt-get upgrade" on a Ubuntu 16.04.4 box, graphics fails to start. I use my laptop with text boot, then I log in and issue "startx", with "/usr/lib/gnome-flashback/gnome-flashback-metacity" in my ~/.xinitrc file. After update, "startx" (Xorg) returns me to character prompt. Same with KDE, and while WMaker seemed to start, I still couldn't run apps like Firefox or Konsole. Tinkering with my system for about two hours I managed to figure out that this behaviour is caused by some Virtualbox package. After issuing "apt-get purge virtualbox*", the normal behaviour returned. Fortunately I don't use Virtualbox, it was installed 'just in case', so I could remove it without affecting everyday usage. But it seems that something in Virtualbox is seriously broken. A cut from apt's history.log after upgrade and before package removal: virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-additions-iso:amd64 (5.0.40-0ubuntu1.16.04.1, 5.1.34-0ubuntu1.16.04.2) virtualbox-guest-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-utils:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-x11:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-qt:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1762491/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 1762491] Re: [SRU] No graphics after update, caused by virtualbox
This bug was fixed in the package virtualbox - 5.1.38-dfsg- 0ubuntu1.16.04.1 --- virtualbox (5.1.38-dfsg-0ubuntu1.16.04.1) xenial; urgency=medium * New upstream version 5.1.38-dfsg - fixes for kernel 3.16 and 3.17 - fixes for opengl libraries - automatically detect if 3d is enabled or not LP: #1762491 -- Gianfranco Costamagna Tue, 10 Jul 2018 12:40:22 +0200 ** Changed in: virtualbox (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: virtualbox-ext-pack (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762491 Title: [SRU] No graphics after update, caused by virtualbox Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-ext-pack package in Ubuntu: Fix Released Status in virtualbox-guest-additions-iso package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in virtualbox source package in Xenial: Fix Released Status in virtualbox-ext-pack source package in Xenial: Fix Released Status in virtualbox-guest-additions-iso source package in Xenial: Fix Released Status in virtualbox-hwe source package in Xenial: Fix Released Bug description: [Impact] * ubuntu when used as a guest inside a Virtualbox VM machine [Test Case] * Install Ubuntu and mate or other DM, experience a black screen * Install vbox on xenial with guest and host. Test if everything works and starts with 3d enabled and disabled, as well as different Desktop Managers. [ autopkgtests ] * this package has a really huge autopkgtest suite performed by upstream on each release, and this is the reason for me using the new release as-is instead of patching old versions. [Regression Potential] * This is part of virtualbox on Debian and Ubuntu since bionic and 3 months Author: Gianfranco Costamagna Date: Tue Apr 24 00:15:39 2018 +0200 basically, I now detect at runtime the --check3d switch, and enable the mesa override only for desktop and not for applications, the same as the official guest-additions packages do. this is the code: + if /usr/bin/VBoxClient --check3d 2>/dev/null; then + if test -e /usr/lib/virtualbox/additions/00vboxvideo.conf; then + cp -f /usr/lib/virtualbox/additions/00vboxvideo.conf /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi + fi + if test -e /etc/ld.so.conf.d/00vboxvideo.conf; then + rm -f /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi the update-alternatives switch can't work when 3d is not enabled, and with user applications using mesa-specific features. [ upstream changes ] Version 5.1.38 (2018-05-09) Linux hosts: support Linux 4.17 changes. Thank you Larry Finger Linux guests: support Linux 4.16 and EL 7.5 kernels (bugs #17676 and #17678) Linux guests: 3D fixes for recent guests (bug #17623) Version 5.1.36 (2018-04-17) VMM: Fixed missing NULL pointer check in MMIO code. Network: fixed VERR_INTNET_FLT_IF_NOT_FOUND when bridging to some adapters on Windows hosts (possibly related bugs #15294, #15060, #13481) [Other info] After performing an "apt-get update && apt-get upgrade" on a Ubuntu 16.04.4 box, graphics fails to start. I use my laptop with text boot, then I log in and issue "startx", with "/usr/lib/gnome-flashback/gnome-flashback-metacity" in my ~/.xinitrc file. After update, "startx" (Xorg) returns me to character prompt. Same with KDE, and while WMaker seemed to start, I still couldn't run apps like Firefox or Konsole. Tinkering with my system for about two hours I managed to figure out that this behaviour is caused by some Virtualbox package. After issuing "apt-get purge virtualbox*", the normal behaviour returned. Fortunately I don't use Virtualbox, it was installed 'just in case', so I could remove it without affecting everyday usage. But it seems that something in Virtualbox is seriously broken. A cut from apt's history.log after upgrade and before package removal: virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-additions-iso:amd64 (5.0.40-0ubuntu1.16.04.1, 5.1.34-0ubuntu1.16.04.2) virtualbox-guest-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-utils:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-x11:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-qt:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) To manage notifications about this bug go to:
[Group.of.nepali.translators] [Bug 1762491] Re: [SRU] No graphics after update, caused by virtualbox
This bug was fixed in the package virtualbox-ext-pack - 5.1.38-0ubuntu1.16.04.1 --- virtualbox-ext-pack (5.1.38-0ubuntu1.16.04.1) xenial; urgency=medium * New upstream version 5.1.38 (LP: #1762491) * New upstream release, update rules, postinst file * Update copyright file * Update watch file * Automatically generate postinst version -- Gianfranco Costamagna Tue, 10 Jul 2018 12:49:47 +0200 ** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762491 Title: [SRU] No graphics after update, caused by virtualbox Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-ext-pack package in Ubuntu: Fix Released Status in virtualbox-guest-additions-iso package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in virtualbox source package in Xenial: Fix Released Status in virtualbox-ext-pack source package in Xenial: Fix Released Status in virtualbox-guest-additions-iso source package in Xenial: Fix Released Status in virtualbox-hwe source package in Xenial: Fix Released Bug description: [Impact] * ubuntu when used as a guest inside a Virtualbox VM machine [Test Case] * Install Ubuntu and mate or other DM, experience a black screen * Install vbox on xenial with guest and host. Test if everything works and starts with 3d enabled and disabled, as well as different Desktop Managers. [ autopkgtests ] * this package has a really huge autopkgtest suite performed by upstream on each release, and this is the reason for me using the new release as-is instead of patching old versions. [Regression Potential] * This is part of virtualbox on Debian and Ubuntu since bionic and 3 months Author: Gianfranco Costamagna Date: Tue Apr 24 00:15:39 2018 +0200 basically, I now detect at runtime the --check3d switch, and enable the mesa override only for desktop and not for applications, the same as the official guest-additions packages do. this is the code: + if /usr/bin/VBoxClient --check3d 2>/dev/null; then + if test -e /usr/lib/virtualbox/additions/00vboxvideo.conf; then + cp -f /usr/lib/virtualbox/additions/00vboxvideo.conf /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi + fi + if test -e /etc/ld.so.conf.d/00vboxvideo.conf; then + rm -f /etc/ld.so.conf.d/00vboxvideo.conf + ldconfig + fi the update-alternatives switch can't work when 3d is not enabled, and with user applications using mesa-specific features. [ upstream changes ] Version 5.1.38 (2018-05-09) Linux hosts: support Linux 4.17 changes. Thank you Larry Finger Linux guests: support Linux 4.16 and EL 7.5 kernels (bugs #17676 and #17678) Linux guests: 3D fixes for recent guests (bug #17623) Version 5.1.36 (2018-04-17) VMM: Fixed missing NULL pointer check in MMIO code. Network: fixed VERR_INTNET_FLT_IF_NOT_FOUND when bridging to some adapters on Windows hosts (possibly related bugs #15294, #15060, #13481) [Other info] After performing an "apt-get update && apt-get upgrade" on a Ubuntu 16.04.4 box, graphics fails to start. I use my laptop with text boot, then I log in and issue "startx", with "/usr/lib/gnome-flashback/gnome-flashback-metacity" in my ~/.xinitrc file. After update, "startx" (Xorg) returns me to character prompt. Same with KDE, and while WMaker seemed to start, I still couldn't run apps like Firefox or Konsole. Tinkering with my system for about two hours I managed to figure out that this behaviour is caused by some Virtualbox package. After issuing "apt-get purge virtualbox*", the normal behaviour returned. Fortunately I don't use Virtualbox, it was installed 'just in case', so I could remove it without affecting everyday usage. But it seems that something in Virtualbox is seriously broken. A cut from apt's history.log after upgrade and before package removal: virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-additions-iso:amd64 (5.0.40-0ubuntu1.16.04.1, 5.1.34-0ubuntu1.16.04.2) virtualbox-guest-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-utils:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-guest-x11:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) virtualbox-qt:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2) To manage notifications about this bug go to:
[Group.of.nepali.translators] [Bug 1779383] Re: linux-snapdragon: 4.4.0-1096.101 -proposed tracker
Snap verification completed, no regressions found. ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1779383 Title: linux-snapdragon: 4.4.0-1096.101 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1779376 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779383/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779383] Re: linux-snapdragon: 4.4.0-1096.101 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1779376 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Tuesday, 24. July 2018 07:22 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1779376 - phase: Promoted to updates + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Tuesday, 24. July 2018 07:22 UTC - kernel-stable-phase:Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1779383 Title: linux-snapdragon: 4.4.0-1096.101 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1779376 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1779383/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779403] Re: [SRU] 2.34.2
This bug was fixed in the package snapd - 2.34.2+18.04
---
snapd (2.34.2+18.04) bionic; urgency=medium
* New upstream release, LP: #1779403
- packaging: fix bogus date in fedora snapd.spec
- tests: fix tests expecting old email address
snapd (2.34.1) xenial; urgency=medium
* New upstream release, LP: #1779403
- tests: cherry-pick test fixes from master for 2.34
- coreconfig: add support for `snap set system network.disable-
ipv6`
- debian: do not ship snapd.apparmor.service on ubuntu
- overlord/snapstate: dedupe default content providers
- interfaces/builtin: create can-bus interface
snapd (2.34) xenial; urgency=medium
* New upstream release, LP: #1779403
- store, daemon, client, cmd/snap: expose "scope", default to wide*
- tests: fix arch tests
- snapstate: make sure all *link-*snap tasks carry a snap type and
further hints
- snapstate: allow setting "refresh.timer=managed"
- cmd/snap: display a link to data privacy notice for interactive
snap login
- devicestate: fix race when refreshing a snap with snapd-control
- tests: skip interfaces-framebuffer when no /dev/fb0 is found
- tests: run interfaces-contacts-service only where test-snapd-eds
is available
- many: expose publisher's validation throughout the API
- many: use extra "releases" information on store "revision-not-
found" errors to produce better errors
- dirs: improve distro detection for Antegros
- Revert "dirs: improve identification of Arch Linux like systems"
- devicestate: fix panic in firstboot code when no snaps are seeded
- i18n: use xgettext-go --files-from to avoid running into cmdline
size limits
- interfaces: move ValidateName helper to utils
- snapstate,ifstate: wait for pending restarts before auto-
connecting
- snap: account for parallel installs in wrappers, place info and
tests
- configcore: fix incorrect handling of keys with numbers (like
gpu_mem_512)
- tests: fix tests when no keyboard input detected
- overlord/configstate: add watchdog options
- snap-mgmt: fix for non-existent dbus system policy dir,
shellchecks
- tests/main/snapd-notify: use systemd's service properties rater
than the journal
- snapstate: allow removal of snap.TypeOS when using a model with a
base
- interfaces: make findSnapdPath smarter
- tests: run "arp" tests only if arp is available
- spread: increase the number of auto retries for package downloads
in opensuse
- cmd/snap-confine: fix nvidia support under lxd
- corecfg: added experimental.hotplug feature flag
- image: block installation of parallel snap instances
- interfaces: moved normalize method to interfaces/utils and made it
public
- api/snapctl: allow -h and --help for regular users.
- interfaces/udisks2: also implement implicit classic slot
- cmd/snap-confine: include CUDA runtime libraries
- tests: disable auto-refresh test on core18
- many: switch to account validation: unproven|verified
- overlord/ifacestate: get/set connection state only via helpers
- tests: adding extra check to validate journalctl is showing
current test data
- data: add systemd environment configuration
- i18n: handle write errors in xgettext-go
- snap: helper for validating snap instance names
- snap{/snaptest}: set instance key based on snap name
- userd: fix running unit tests on KDE
- tests/main/econnreset: limit ingress traffic to 512kB/s
- snap: introduce a struct Channel to represent store channels, and
helpers to work with it
- tests: add fedora to distro_clean_package_cache function
- many: rename snap.Info.StoreName() to snap.Info.SnapName()
- tests: add spread test to ensure snapd/core18 are not removable
- tests: tweaks for running the main tests on core18
- overlord/{config,snap}state: introduce experimental.parallel-
instances feature flag
- strutil: support iteration over almost clean paths
- strutil: add PathIterator.Rewind
- tests: update interfaces-timeserver-control to core18
- tests: add halt-timeout to google backend
- tests: skip security-udev-input-subsystem without /dev/input/by-
path
- snap: introduce the instance key field
- packaging/opensuse: remaining packaging updates for 2.33.1
- overlord/snapstate: disallow installing snapd on baseless models
- tests: disable core tests on all core systems (16 and 18)
- dirs: improve identification of Arch Linux like systems
- many: expose full publisher info over the snapd API
- tests: disable core tests on all core systems (16 and 18)
- tests/main/xdg-open: restore or clean up xdg-open
- tests/main/interfaces-firewall-control: shellcheck fix
- snapstate: sort "snapd" first
- systemd: require snapd.socket in snapd.seeded.service; make sure
[Group.of.nepali.translators] [Bug 1772024] Re: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-smoke-test)
This bug was fixed in the package nbd - 1:3.16.2-1ubuntu0.1 --- nbd (1:3.16.2-1ubuntu0.1) bionic; urgency=medium * Fix bugs causing nbd-smoke-test to fail (LP: #1772024) - Fix segfault when exporting only from a file on the command line. + https://github.com/NetworkBlockDevice/nbd/commit/4c924b7b64fb1b6cb9be8e8f508d459c0ed05a60 - Fix fd leaks when fork fails. + https://github.com/NetworkBlockDevice/nbd/commit/0e094066a2676149e511f41a5eee1062de73e198 - debian/control: change Maintainer -- Thadeu Lima de Souza Cascardo Wed, 30 May 2018 15:10:02 -0300 ** Changed in: nbd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1772024 Title: linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd- smoke-test) Status in linux package in Ubuntu: In Progress Status in nbd package in Ubuntu: Fix Released Status in linux source package in Trusty: New Status in nbd source package in Trusty: Invalid Status in linux source package in Xenial: New Status in nbd source package in Xenial: Invalid Status in linux source package in Artful: New Status in nbd source package in Artful: Incomplete Status in linux source package in Bionic: New Status in nbd source package in Bionic: Fix Released Status in linux source package in Cosmic: In Progress Status in nbd source package in Cosmic: Fix Released Bug description: [Impact] nbd-server will crash when a client connects to it, if it was started without a server name. It may also leak fds if fork fails. [Test Case] Running the server with an empty config file and an image on the command line, and then starting a local client will crash the server. After the fix, it doesn't crash anymore, and a filesystem may be created and used after that. [Regression Potential] The fix also implies a small package change, to use quilt. It has built just fine and many tests have been run on top of those packages and no failure seemed to be the result of those userspace changes, but known failures in the kernel driver. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772024/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
