[Group.of.nepali.translators] [Bug 1814744] Re: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1814744 Title: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814744/+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 1664844] Re: No distinction between link-up and link-down interfaces
** Changed in: nplan (Ubuntu Xenial) 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in nplan package in Ubuntu: In Progress Status in nplan source package in Xenial: Fix Released Status in nplan source package in Zesty: In Progress Status in nplan source package in Artful: In Progress Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1814761] Re: linux-azure-edge: 4.15.0.1039.23 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed ** 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: 1813779 - phase: Ready for Testing - phase-changed: Tuesday, 26. February 2019 14:25 UTC + phase: Ready for Release + phase-changed: Thursday, 28. February 2019 00:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-security: Pending -- ready to copy + promote-to-updates: Pending -- ready to copy -- 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/1814761 Title: linux-azure-edge: 4.15.0.1039.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed 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: 1813779 phase: Ready for Release phase-changed: Thursday, 28. February 2019 00:47 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy promote-to-updates: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814761/+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 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1817038 Title: linux-azure: 4.15.0-1040.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817038/+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 1817949] Re: [SRU] 2.37.4
This bug was fixed in the package snapd - 2.37.4+19.04 --- snapd (2.37.4+19.04) disco; urgency=medium * New upstream release, LP: #1817949 - squashfs: unset SOURCE_DATE_EPOCH in the TestBuildDate test - overlord/ifacestate: fix migration of connections on upgrade from ubuntu-core - tests: fix upgrade-from-2.15 with kernel 4.15 - interfaces/seccomp: increase filter precision - tests: remove snapweb from tests -- Michael Vogt Wed, 27 Feb 2019 19:53:36 +0100 ** Changed in: snapd (Ubuntu) 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/1817949 Title: [SRU] 2.37.4 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: New Status in snapd source package in Xenial: New Status in snapd source package in Bionic: New Status in snapd source package in Cosmic: New Bug description: This is a new bugfix release of snapd - it fixes some corner case regressions we found in the 2.37 release series. The changelog is available here https://github.com/snapcore/snapd/blob/2.37.4/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.37.4 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The travis logs for 2.37.4 can be found here: https://travis- ci.org/snapcore/snapd/branches We currently have no autopkgtest logs before snapd hits -proposed because we got asked to disable our autopkgtest integration as it was using too many resources from the autopkgtest infrastructure. The snappy team released a new release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1817949/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Critical Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Trusty) Status: New => Invalid ** Changed in: systemd (Ubuntu Xenial) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [impact] systems upgraded from pre-Bionic releases to Bionic or later will continue to use ifupdown/resolvconf for network conf and management, but resolvconf has a new systemd service in Bionic and later that pulls systemd-resolved stub-resolv.conf into its local configuration. With the recent addition of edns0 option to the stub resolver conf in systemd to fix bug 1811471, this means resolvconf now sets up the /etc/resolv.conf file to include upstream servers but also use edns. For any systems where the upstream resolver(s) don't support edns, dns lookups will break. [test case] create a xenial system with ifupdown/resolvconf, then upgrade to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf). The system ifupdown config should include an upstream name server. After upgrade, the /etc/resolv.conf will contain both the upstream name server as well as options edns0. [regression potential] this changes how resolvconf handles system dns on bionic and later: 1) networking is managed by ifupdown resolvconf is currently adding the local stub resolver to /etc/resolv.conf, even though in this case it doesn't know about any upstream name servers. This change will remove the local stub resolver from /etc/resolv.conf; it should not be there. 2) networking is managed by systemd-networkd resolvconf is currently setting up /etc/resolv.conf to direct all local dns queries to the local stub resolver, similar to how systemd- resolved itself configures /etc/resolv.conf. This change will instead set up /etc/resolv.conf to bypass the local stub resolver, and send all dns queries to the upstream name server(s). In case #1, this change has little chance for regression; in case #2 however, this change will bypass the local stub resolver and thus create more network dns traffic (since dns queries will not be cached locally). However, this is how pre-Bionic releases worked, and simply removing resolvconf will restore systemd-resolved control of /etc/resolv.conf, causing the system to again use the local stub resolver. Additional regressions due to this change would likely be seen in dns query failures with other system configurations. [other info] This affects only Bionic and later; in Xenial and earlier, resolvconf does not include the 'resolvconf-pull-resolved' service to pull in the systemd-resolved stub config, which is what causes this problem. This also does not affect Debian, as it does not include the 'resolvconf-pull-resolved' service either. original description: -- Mint 19 (Ubuntu 18.04) Following latest mint update done on 24/02/2019, DNS is broken nslookup and dig of certain domain names work as expected, ping does not (ip works but not domain name) After a day of trial and error, testing I found that the problem lies with the presence of "options edns0" in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf) With option present many dns lookups fail with both FF and chrome browswers and thunderbird... This is on a home network, with router set as dns proxy for external wan, not using Netwo
[Group.of.nepali.translators] [Bug 1816106] Re: 4.15.0-1037 does not see all PCI devices on GPU VMs
** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-azure (Ubuntu Bionic) ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/1816106 Title: 4.15.0-1037 does not see all PCI devices on GPU VMs Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure source package in Cosmic: Fix Released Bug description: Host changes have altered how the PCI GUID is presented to the guest and the patches for PCI IDs in 4.15.0-1037 do not properly handle the new condition. Impact: Instances with multiple GPUs are only seeing one. Workaround: 4.15.0-1036 does not have this behavior. Additional info: The commit in 4.15.0-1037 responsible is " - PCI: hv: Make sure the bus domain is really unique" The immediate action requested is to back out this patch on 4.15.0 (azure): https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=master-next&id=b9ae54076a78d01659c4d0f0a558cdb4056f0d13 The same thing on 4.18: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/commit/?h=azure-edge-next&id=29927dfb7f69bcf2ae7fd1cda10997e646a5189c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1816106/+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 1775018] Re: Fix for openssl 1.0.2 backport
** Changed in: ubuntu-z-systems 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/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl1.0 package in Ubuntu: Won't Fix Status in openssl source package in Xenial: Invalid Status in openssl1.0 source package in Xenial: Invalid Status in openssl source package in Bionic: Fix Released Status in openssl1.0 source package in Bionic: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl1.0 source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Status in openssl1.0 source package in Disco: Won't Fix Bug description: [Impact] * Fix hw accelerated performance impact on s390x with non-default openssl1.0. [Test Case] * Test that performance of hw accelerated crypto is improved / i.e. ssl speed test * Test that openssh still works, just in case. [Regression Potential] * This only changes accelerated codepath on s390x, for specific algos when CPACF is enabled on the system cpu, which is usually on. * Same fix is already in use by 1.1.0 default openssl package, and well excercised on bionic and up. [Other Info] * original bug report. This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+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 1817689] Re: [16.04.6 Desktop] Cannot log in after installation with encrypted home enabled
This bug was fixed in the package user-setup - 1.63ubuntu6 --- user-setup (1.63ubuntu6) disco; urgency=medium * Mount /proc before calling adduser --encrypt-home. This calls into ecryptfs, which requires a /proc in order to find out where sysfs is mounted. (LP: #1817689) -- Iain Lane Wed, 27 Feb 2019 16:48:22 + ** Changed in: user-setup (Ubuntu) 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/1817689 Title: [16.04.6 Desktop] Cannot log in after installation with encrypted home enabled Status in ubiquity package in Ubuntu: Confirmed Status in user-setup package in Ubuntu: Fix Released Status in ubiquity source package in Xenial: Fix Released Status in user-setup source package in Xenial: Fix Released Bug description: Ubuntu Desktop 16.04.6 20190222 Test Case Do an entire disk installation and on the 'Who are you' page select "encrypt home", reboot and log in from lightdm Actual Result The log in is rejected. There are permission denied in the logs (journal attached) This is a *regression* in 16.04.6. It works fine on 16.04.5. The following message appears in the logs: user-setup: Error: Your kernel does not support filename encryption user-setup: ERROR: Could not add passphrase to the current keyring user-setup: adduser: `/usr/bin/ecryptfs-setup-private -b -u u' returned error code 1. Exiting. This is with kernel 4.15.0-45-generic 16.04.5 uses kernel 4.15.0-29-generic ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Feb 26 06:10:00 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- apt-setup/restricted=false apt-setup/multiverse=false InstallationDate: Installed on 2019-02-26 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190222) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1817689/+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 1775018] Re: Fix for openssl 1.0.2 backport
This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu6.2 --- openssl1.0 (1.0.2n-1ubuntu6.2) cosmic-security; urgency=medium * SECURITY UPDATE: 0-byte record padding oracle - debian/patches/CVE-2019-1559.patch: go into the error state if a fatal alert is sent or received in ssl/d1_pkt.c, ssl/s3_pkt.c. - CVE-2019-1559 * debian/patches/s390x-fix-aes-gcm-tls.patch: fix typo in backported s390x hw acceleration patch. (LP: #1775018) -- Marc Deslauriers Tue, 26 Feb 2019 14:45:07 -0500 ** Changed in: openssl1.0 (Ubuntu Cosmic) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-1559 ** Changed in: openssl1.0 (Ubuntu Bionic) 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/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Confirmed Status in openssl package in Ubuntu: Fix Released Status in openssl1.0 package in Ubuntu: Won't Fix Status in openssl source package in Xenial: Invalid Status in openssl1.0 source package in Xenial: Invalid Status in openssl source package in Bionic: Fix Released Status in openssl1.0 source package in Bionic: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl1.0 source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Status in openssl1.0 source package in Disco: Won't Fix Bug description: [Impact] * Fix hw accelerated performance impact on s390x with non-default openssl1.0. [Test Case] * Test that performance of hw accelerated crypto is improved / i.e. ssl speed test * Test that openssh still works, just in case. [Regression Potential] * This only changes accelerated codepath on s390x, for specific algos when CPACF is enabled on the system cpu, which is usually on. * Same fix is already in use by 1.1.0 default openssl package, and well excercised on bionic and up. [Other Info] * original bug report. This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+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 1814747] Re: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1814747 Title: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814747/+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 1817918] [NEW] Hard lockups due to unrestricted lapic timer delay
Public bug reported: There is a report of hard lockup induced by a long delay in lapic expiration timer. We'll provide SRU request here for merging the fixes in 4.4 kernel. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Guilherme G. Piccoli (gpiccoli) Status: Fix Released ** Tags: sts ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- 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/1817918 Title: Hard lockups due to unrestricted lapic timer delay Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Released Bug description: There is a report of hard lockup induced by a long delay in lapic expiration timer. We'll provide SRU request here for merging the fixes in 4.4 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817918/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Description changed: + [Impact] + + * Kernel keystroke auditing via pam_tty_audit.so not working + + * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. +It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. + + [Test Case] + + 1. Install libpam-ldap + 2. Add the following to the end of /etc/pam.d/common-sessions + + session required pam_tty_audit.so enable=* open_only + + 3. When logging in with ssh etc., pam_tty_audit will fail and login fails + + [Regression Potential] + + * Low, we are simply including the missing header files and copy the old status as initialization of new. +It's already part of Debian and Disco. + + [Other Info] + + # Upstream fix: + https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee + + # git describe --contains c5f829931a22c65feffee16570efdae036524bee + Linux-PAM-1_2_0~75 + + # rmadision pam + => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source + => pam | 1.1.8-3.2ubuntu2 | xenial | source + => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source + => pam | 1.1.8-3.6ubuntu2 | bionic | source + => pam | 1.1.8-3.6ubuntu2 | cosmic | source + pam | 1.3.1-5ubuntu1 | disco| source + + [Original Description] + Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. ** Also affects: pam (Ubuntu Cosmic) 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam
[Group.of.nepali.translators] [Bug 1786574] Re: remove i2c-i801 from blacklist
** Changed in: hwe-next Status: Fix Released => In Progress -- 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/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: In Progress Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1809439] Re: cpu_hot_plug test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1809439 Title: cpu_hot_plug test in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug' TAP version 13 selftests: cpu-on-off-test.sh pid 18238's current affinity mask: 3 pid 18238's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-1 Cpus in offline state: 2 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 offline to online to offline: cpu 2 ./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such file or directory online_cpu_expect_success 2: unexpected fail not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Dec 21 10:38:05 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809439/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change
Change linux to Fix Released for the same reason. ** Changed in: linux (Ubuntu) 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/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Xenial: Fix Released Status in linux source package in Xenial: Invalid Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change
linux/Cosmic should be Fix Released as the fix is already in 4.18 from upstream. ** Changed in: linux (Ubuntu Cosmic) 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/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Xenial: Fix Released Status in linux source package in Xenial: Invalid Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1817786] Re: tcm_loop.ko: move from modules-extra into main modules-gcp package
** Changed in: linux-gcp (Ubuntu Ee-series) Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Ff-series) Status: New => Invalid ** No longer affects: linux-gcp (Ubuntu Ee-series) ** No longer affects: linux-gcp (Ubuntu Ff-series) -- 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/1817786 Title: tcm_loop.ko: move from modules-extra into main modules-gcp package Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Xenial: In Progress Status in linux-gcp source package in Bionic: In Progress Status in linux-gcp source package in Cosmic: In Progress Status in linux-gcp source package in Disco: In Progress Bug description: Please move the tcm_loop.ko module from the linux-modules-extra-*-gcp to main linux-modules-*-gcp package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1817786/+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 1817038] Re: linux-azure: 4.15.0-1040.44 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress -- 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/1817038 Title: linux-azure: 4.15.0-1040.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed 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: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1817038/+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
