[Group.of.nepali.translators] [Bug 1820157] [NEW] CONFIG_CIFS_POSIX=y needs to added to xenial/kvm kernel config
Public bug reported: For xenial/kvm, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: Fix Committed ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu) ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => Fix Committed -- 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/1820157 Title: CONFIG_CIFS_POSIX=y needs to added to xenial/kvm kernel config Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: Fix Committed Bug description: For xenial/kvm, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1820157/+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 1820152] Re: CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config
** Also affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu) ** No longer affects: linux-raspi2 (Ubuntu Xenial) ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: New => Fix Committed -- 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/1820152 Title: CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config Status in linux-snapdragon package in Ubuntu: New Status in linux-snapdragon source package in Xenial: Fix Committed Bug description: For xenial/snapdragon, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1820152/+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 1820152] [NEW] CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config
Public bug reported: For xenial/snapdragon, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: Fix Committed ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Fix Committed -- 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/1820152 Title: CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Xenial: Fix Committed Bug description: For xenial/snapdragon, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1820152/+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 1820151] Re: CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config
** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Fix Committed -- 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/1820151 Title: CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Xenial: Fix Committed Bug description: For xenial/raspi2, we need a commit equivalent to d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1820151/+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 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
** Changed in: linux (Ubuntu Trusty) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Invalid => 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/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 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 Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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 1550950] Re: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also
** Changed in: hundredpapercuts 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/1550950 Title: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b107-0ubuntu1 Status in One Hundred Papercuts: Fix Released Status in openjdk-9 package in Ubuntu: Fix Released Status in openjdk-9 source package in Xenial: Fix Released Bug description: Ubuntu Xenial Xerus (development branch) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openjdk-9-jdk 9~b102-1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sun Feb 28 16:44:30 2016 ErrorMessage: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b107-0ubuntu1 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: openjdk-9 Title: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b107-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1550950/+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 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance
This bug was fixed in the package cloud-init - 18.5-45-g3554ffe8-0ubuntu1 --- cloud-init (18.5-45-g3554ffe8-0ubuntu1) disco; urgency=medium * New upstream snapshot. - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) -- Daniel Watkins Fri, 08 Mar 2019 17:42:34 -0500 ** Changed in: cloud-init (Ubuntu) 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/1802073 Title: No network in AWS (EC-Classic) after stopping and starting instance Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Confirmed Bug description: I don't know is this cloud-init or netplan or what, but this is not good. Background: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy cloud-init cloud-init: Installed: 18.4-0ubuntu1~18.04.1 Candidate: 18.4-0ubuntu1~18.04.1 Version table: *** 18.4-0ubuntu1~18.04.1 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.2-14-g6d48d265-0ubuntu1 500 500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1. Get newest image to use $ aws --region eu-west-1 ec2 describe-images --owners 099720109477 --filters Name=root-device-type,Values=ebs Name=architecture,Values=x86_64 Name=name,Values='*hvm-ssd/ubuntu- bionic-18.04*' --query 'sort_by(Images, )[-1].ImageId' "ami-08596fdd2d5b64915" 2. Start instance to EC2-Classic with that image. 3. Try to SSH. Everything is ok. # cat /var/log/cloud-init-output.log Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Wed, 07 Nov 2018 08:12:16 +. Up 10.51 seconds. Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init' at Wed, 07 Nov 2018 08:12:21 +. Up 15.50 seconds. ci-info: +++Net device info ci-info: ++--+-+-++---+ ci-info: | Device | Up | Address | Mask | Scope | Hw-Address| ci-info: ++--+-+-++---+ ci-info: | eth0 | True | 10.74.200.25| 255.255.255.192 | global | 22:00:0a:4a:c8:19 | ci-info: | eth0 | True | fe80::2000:aff:fe4a:c819/64 |.| link | 22:00:0a:4a:c8:19 | ci-info: | lo | True | 127.0.0.1 |255.0.0.0| host | . | ci-info: | lo | True | ::1/128 |.| host | . | ci-info: ++--+-+-++---+ ... Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'modules:config' at Wed, 07 Nov 2018 08:12:41 +. Up 35.63 seconds. Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'modules:final' at Wed, 07 Nov 2018 08:12:44 +. Up 38.98 seconds. Cloud-init v. 18.4-0ubuntu1~18.04.1 finished at Wed, 07 Nov 2018 08:12:45 +. Datasource DataSourceEc2Local. Up 39.38 seconds 4. Stop the instance. 5. Start the instance. 6. Try to SSH. Expected to happen: Instance has network and is working. What happens: Instance has no working network Getting instance log we can see: [ 11.342357] cloud-init[412]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Wed, 07 Nov 2018 08:21:07 +. Up 10.77 seconds. [ OK ] Started Initial cloud-init job (pre-networking). [ OK ] Reached target Network (Pre). Starting Network Service... [ OK ] Started Network Service. Starting Network Name Resolution... Starting Wait for Network to be Configured... [ OK ] Started Wait for Network to be Configured. Starting Initial cloud-init job (metadata service crawler)... [ OK ] Started Network Name Resolution. [ OK ] Reached target Host and Network Name Lookups. [ OK ] Reached target Network. [ 13.036207] cloud-init[637]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init' at Wed, 07 Nov 2018 08:21:08 +. Up 12.55 seconds. [ 13.052849] cloud-init[637]: ci-info: +++Net device info [ 13.100325] cloud-init[637]: ci-info: ++---+---+---+---+---+ [ 13.121790] cloud-init[637]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address| [ 13.129189] cloud-init[637]: ci-info:
[Group.of.nepali.translators] [Bug 1815051] Re: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries
This bug was fixed in the package cloud-init - 18.5-45-g3554ffe8-0ubuntu1 --- cloud-init (18.5-45-g3554ffe8-0ubuntu1) disco; urgency=medium * New upstream snapshot. - cloud-init-per: POSIX sh does not support string subst, use sed (LP: #1819222) -- Daniel Watkins Fri, 08 Mar 2019 17:42:34 -0500 ** Changed in: cloud-init (Ubuntu) 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/1815051 Title: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Confirmed Bug description: The netplan configuration redeclares the nameservers anchor for every single section (vlans, bonds), and use the same id for similar entries (id001). In this specific case the network configuration in maas have a bond0 with two vlans, bond0.3502 and bond0.3503, and an untagged bond1 without vlans. The rendered 50-cloud-init.yaml looks like this: network: version: 2 ethernets: ... bonds: ... bond1: ... nameservers: <- anchor declaration here addresses: - 255.255.255.1 - 255.255.255.2 - 255.255.255.3 - 255.255.255.5 search: - customer.domain - maas ... bondM: ... nameservers: *id001 vlans: bond0.3502: ... nameservers: <- anchor redeclaration here addresses: - 255.255.255.1 - 255.255.255.2 - 255.255.255.3 - 255.255.255.5 search: - customer.domain - maas bond0.3503: ... nameservers: *id001 As the cloudinit renders an invalid yaml file, the netplan apply produces the following error: (due to the anchor redeclaration in the vlans section): Invalid YAML at /etc/netplan/50-cloud-init.yaml line 118 column 25: second occurence This render bug prevents us using the untagged bond and the bond with the vlans in the same configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1815051/+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
** Changed in: resolvconf (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: resolvconf (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: resolvconf (Ubuntu Disco) 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/1817903 Title: systemd-resolve appends "options edns0" to resolv.conf Status in resolvconf package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in resolvconf source package in Trusty: Invalid Status in systemd source package in Trusty: Invalid Status in resolvconf source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in resolvconf source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Status in resolvconf source package in Cosmic: In Progress Status in systemd source package in Cosmic: Invalid Status in resolvconf source package in Disco: In Progress Status in systemd source package in Disco: Invalid 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] == upgrade from pre-bionic (e.g. xenial) to bionic or later == 1) create a xenial system with ifupdown/resolvconf. The ifupdown config needs to include an upstream name server (must be static). At this point, once the network is configured and up, the resolvconf should have put the upstream name server(s) and search domain into the /etc/resolv.conf. As is usual for pre-systemd releases, there should be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should not be included) at this point. 2) upgrade the system to bionic (alternately it should be possible to install bionic, then remove netplan and install/configure ifupdown and resolvconf, but I have not specifically tested this). The upgrade will retain the ifupdown/resolvconf configuration, and will not change to netplan/systemd-networkd. After upgrade is finished, the /etc/resolv.conf will contain: a) the upstream name server(s) b) options edns0 c) the local stub resolver (127.0.0.53) d) search domain the fixed resolvconf will remove (b) and (c), and restore /etc/resolv.conf to what it contained in Xenial release, before the upgrade to Bionic. As mentioned, this case also should cover the situation of a native Bionic install, where netplan is removed and ifupdown/resolvconf is manually installed. == bionic or later install == with a bionic install, ifupdown is not installed, instead netplan /systemd-networkd handle networking. In this case, systemd-networkd manages the /etc/resolv.conf, and symlinks it to networkd's stub- resolv.conf which always contains only the local stub resolver (127.0.0.53) and (recently) options edns0, and local search domain. If resolvconf is installed while systemd-networkd is managing the network, then currently the resolv.conf contents will remain completely unchanged, still pointing to the local stub resolver. This resolvconf change will alter that, to revert the /etc/resolv.conf to Xenial's contents; specifically, the upstream name server(s) and search domain. It will no longer include the local stub resolver nor edns0. [regression potential] Regressions due to this change would likely be seen in dns query failures with other system configurations. Additionally, for the case where systemd-networkd is actually managing the network, this change will stop sending dns traffic to the local stub resolver, and instead send it to the upstream name server(s). This will increase outgoing dns traffic (since it's no longer cached locally), but will matches the behavior from Xenial. Additionally, resolvconf should not be needed when systemd-networkd is managing the network (and thus systemd-resolved is managing dns), and resolvconf can simply be uninstalled from the system to move back to normal use of the local stub resolver. [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
[Group.of.nepali.translators] [Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: cloud-init Status: Fix Released => Confirmed -- 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/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment Status in cloud-init: Confirmed Status in MAAS: Incomplete Status in cloud-init package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Zesty: Fix Released Bug description: According to https://bugs.launchpad.net/maas/+bug/1604962/comments/12, these logs are needed to debug curtin/cloud-init issues but aren't collected automatically by MAAS: - /var/log/cloud-init* - /run/cloud-init* - /var/log/cloud - /tmp/install.log We need these to be automatically collected by MAAS so we can automatically collect them as artifacts in the case of failures in OIL. curtin/cloud-init issues can be race conditions that are difficult to reproduce manually, so we need to grab the logs required to debug the first time it happens. http://pad.lv/1607345 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1607345 === Begin SRU Template === [Impact] ubuntu-bug cloud-init now collects cloud-init-related information for a bug-report [Test Case] # Launch instance under test $ for release in xenial zesty; do ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc launch $ref $name; sleep 10; lxc exec $name ubuntu-bug cloud-init # And follow the prompts to report a bogus bug done [Regression Potential] Worst case scenario is the apport wrapper doesn't work and the developer has to file a bug manually instead. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=ca2730e2ac86b05f7e6 === End SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+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 1816753] Re: do-release-upgrade on WSL failed horribly due to grub and others
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) 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/1816753 Title: do-release-upgrade on WSL failed horribly due to grub and others Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: New Bug description: Upon reading an Ubuntu page that said it was possible to upgrade my Ubuntu-under-Windows 10 install (WSL) from 16.04 LTS just by running do-release-upgrade, I excitedly went to my terminal and ran the command. First it refused to run because system was not fully updated. Fine, I ran: sudo apt update sudo apt dist-upgrade This process completed without any errors. I then ran do-release- upgrade again. This time it started okay and got through most of the process. But then at some point it decided to run grub even though I am running Ubuntu under WSL, so presumably grub should not be used. It did apparently detect that it wasn't needed, because it asked me if I was sure I didn't want to install it on the boot device. I answered yes. Then the install proceeded to LXD but soon after came an error related to grub. After that it went downhill fast with at least 2 other errors. Additionally, when the system attempted to roll back the upgrade I got an error from a kernel package. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: friendly-recovery 0.2.38ubuntu1 ProcVersionSignature: Microsoft 4.4.0-17763.253-Microsoft 4.4.35 Uname: Linux 4.4.0-17763-Microsoft x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Feb 19 23:50:44 2019 Dmesg: [0.017808] Microsoft 4.4.0-17763.253-Microsoft 4.4.35 ErrorMessage: installed friendly-recovery package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.8 SourcePackage: grub2 Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-02-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1816753/+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 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment
** Changed in: maas Milestone: 2.5.x => 2.6.0 ** No longer affects: maas/2.4 -- 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/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment Status in cloud-init: Fix Released Status in MAAS: Incomplete Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Zesty: Fix Released Bug description: According to https://bugs.launchpad.net/maas/+bug/1604962/comments/12, these logs are needed to debug curtin/cloud-init issues but aren't collected automatically by MAAS: - /var/log/cloud-init* - /run/cloud-init* - /var/log/cloud - /tmp/install.log We need these to be automatically collected by MAAS so we can automatically collect them as artifacts in the case of failures in OIL. curtin/cloud-init issues can be race conditions that are difficult to reproduce manually, so we need to grab the logs required to debug the first time it happens. http://pad.lv/1607345 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1607345 === Begin SRU Template === [Impact] ubuntu-bug cloud-init now collects cloud-init-related information for a bug-report [Test Case] # Launch instance under test $ for release in xenial zesty; do ref=$release-proposed; lxc-proposed-snapshot --proposed --publish $release $ref; lxc launch $ref $name; sleep 10; lxc exec $name ubuntu-bug cloud-init # And follow the prompts to report a bogus bug done [Regression Potential] Worst case scenario is the apport wrapper doesn't work and the developer has to file a bug manually instead. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=ca2730e2ac86b05f7e6 === End SRU Template === To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1607345/+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 1808383] Re: Java 9+ multi-release jars are not supported in ant tasks
This bug was fixed in the package ant - 1.10.5-2ubuntu1 --- ant (1.10.5-2ubuntu1) disco; urgency=medium * Enable multi release jar support. (LP: #1808383) - debian/patches/0016-multirelease-jar-support.patch: apply 2 upstream patches to provide mrjar support. -- Tiago Stürmer Daitx Thu, 14 Mar 2019 14:52:44 + ** Changed in: ant (Ubuntu Disco) 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/1808383 Title: Java 9+ multi-release jars are not supported in ant tasks Status in ant package in Ubuntu: Fix Released Status in ant source package in Xenial: New Status in ant source package in Bionic: New Status in ant source package in Cosmic: New Status in ant source package in Disco: Fix Released Bug description: Reproduced in release: Ubuntu 18.04.1 LTS Version of ant used: 1.10.3-1ubuntu0.1 Having a multi-release jar with different .class files for Java 8 and Java 9, when using this jar in a custom ant task and running in Java 9+, the Java 8 class file will be loaded instead of the Java 9 one. This may lead to errors when the older class uses a deprecated/removed API. This can be easily reproduced using the code pushed to this repository: https://github.com/katanagari7c1/ant-mrjar-support-test This issue have already been reported in the ant bug tracker: https://bz.apache.org/bugzilla/show_bug.cgi?id=62952 It has already been fixed and will be introduced in next release 1.10.6: https://github.com/apache/ant/commit/593aff2d2ea52a025cfe7da32155216719029a7d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ant/+bug/1808383/+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 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Marking certification-testing Invalid per previous comment. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Invalid -- 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/1814647 Title: linux: 4.4.0-143.169 -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: Fix Released 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: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- FAILED certification-testing: Ongoing -- status In Progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+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 1616497] Re: uwsgi-plugin-python3 failed to install
Pressed enter too soon. I meant to add it's fixed in debian since 2.0.12-6 ** Changed in: uwsgi (Ubuntu) Status: Incomplete => Triaged ** Changed in: uwsgi (Ubuntu) Importance: Undecided => Medium ** Also affects: uwsgi (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: uwsgi (Ubuntu Xenial) Status: New => Triaged ** Changed in: uwsgi (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: uwsgi (Ubuntu) Status: Triaged => Fix Released ** Tags added: server-next ** Tags added: bite-size -- 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/1616497 Title: uwsgi-plugin-python3 failed to install Status in uwsgi package in Ubuntu: Fix Released Status in uwsgi source package in Xenial: Triaged Status in uwsgi package in Debian: Unknown Bug description: I expected the package uwsgi-plugin-python3 will be installed with apt-get install. But instead it failed with error "/var/lib/dpkg/info /uwsgi-plugin-python3.postinst: 61: [: Illegal number:". # apt-get install uwsgi-plugin-python3 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: python3-uwsgidecorators The following NEW packages will be installed uwsgi-plugin-python3 0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/73.7 kB of archives. After this operation, 259 kB of additional disk space will be used. Selecting previously unselected package uwsgi-plugin-python3. (Reading database ... 101126 files and directories currently installed.) Preparing to unpack .../uwsgi-plugin-python3_2.0.12-5ubuntu3_amd64.deb ... Unpacking uwsgi-plugin-python3 (2.0.12-5ubuntu3) ... Processing triggers for man-db (2.7.5-1) ... Setting up uwsgi-plugin-python3 (2.0.12-5ubuntu3) ... /var/lib/dpkg/info/uwsgi-plugin-python3.postinst: 61: [: Illegal number: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy uwsgi-plugin-python3 uwsgi-plugin-python3: Installed: 2.0.12-5ubuntu3 Candidate: 2.0.12-5ubuntu3 Version table: *** 2.0.12-5ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1616497/+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 1819713] Re: linux-azure: 4.15.0-1041.45 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Ready for Packaging - phase-changed: Wednesday, 13. March 2019 11:04 UTC + phase: Packaging + phase-changed: Thursday, 14. March 2019 14:03 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- 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/1819713 Title: linux-azure: 4.15.0-1041.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819711 (trusty/linux-azure) derivatives: bug 1819710 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Thursday, 14. March 2019 14:03 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819713/+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 1819660] Re: linux: 4.4.0-144.170 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 (linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon) -- swm properties -- - phase: Packaging - phase-changed: Thursday, 14. March 2019 09:07 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 14. March 2019 12:34 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1819660 Title: linux: 4.4.0-144.170 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819653 (linux-aws), bug 1819654 (linux-euclid), bug 1819655 (linux-kvm), bug 1819656 (linux-raspi2), bug 1819657 (linux-snapdragon) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Thursday, 14. March 2019 12:34 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819660/+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 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompa
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Tags added: verification-done-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/1819077 Title: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible- pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] nvidia-340 (from xenial-proposed) breaks compatibility with linux-generic-hwe-16.04. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update simply re-enables a patch that had been disabled in 340.107-0ubuntu0.16.04.1 _ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev:
[Group.of.nepali.translators] [Bug 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
This bug was fixed in the package virtualbox - 5.1.38-dfsg- 0ubuntu1.16.04.3 --- virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) xenial; urgency=medium * debian/patches/fix-compile-for-xenial-kernel.patch - Fix for LP: #1818049 (virtualbox dkms modules fail to build with linux 4.4.0-143.169) -- Kleber Sacilotto de Souza Thu, 28 Feb 2019 12:52:28 +0100 ** Changed in: virtualbox (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/1818049 Title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in virtualbox source package in Trusty: Won't Fix Status in virtualbox-lts-xenial source package in Trusty: Fix Committed Status in virtualbox source package in Xenial: Fix Released Status in virtualbox-hwe source package in Xenial: Fix Released Bug description: [Impact] virtualbox dkms modules fail to build after Ubuntu kernel 4.4 backported the following fix from upstream stable, which is included on xenial kernel 4.4.0-143.169 that's currently in -proposed. mm: replace get_user_pages() write/force parameters with gup_flags https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-next=9c72ad08f1510332e9314046e6a2adba5064f39a Excerpt from ./virtualbox/5.1.38/build/make.log: /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1112:18: error: too many arguments to function ‘get_user_pages’ rc = get_user_pages(pTask, /* Task for fault accounting. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0, from /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ [Test case] Install virtualbox dkms packages (virtualbox-dkms and virtualbox-guest-dkms) with Ubuntu linux 4.4.0-143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+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 1795590] Re: [SRU] 2.36
This bug was fixed in the package snapd - 2.37.4 --- snapd (2.37.4) xenial; 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 Xenial) 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/1795590 Title: [SRU] 2.36 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Status in snapd source package in Cosmic: New Bug description: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.36/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.36 (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.36 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/1795590/+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 1786438] Re: [SRU] 2.35
This bug was fixed in the package snapd - 2.37.4 --- snapd (2.37.4) xenial; 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 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/1786438 Title: [SRU] 2.35 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: Fix Committed Status in snapd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Bug description: This is a new version of snapd. The changelog is available here https://github.com/snapcore/snapd/blob/2.35/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.35 (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.35 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. Related bugs: * bug 1797218: snap confine fails on top of overlayroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1786438/+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 --- snapd (2.37.4) xenial; 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 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/1817949 Title: [SRU] 2.37.4 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: Fix Committed Status in snapd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released 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. = PACKAGING CHANGES = 1. debian/rules: Fix the apparmor loading order, this change ensures that the new apparmor profiles are loaded *before* snapd is restarted. The old behaviour was buggy and when jumping from a very old version of snapd the old behaviour would cause snap services to fail to start. 2. debian/rules: Disable /usr/lib/systemd/system-environment-generators/snapd-env-generator on 18.04 because the systemd environment generator is not working correctly in 18.04 (this triggered LP: #1811233). 3. debian/postinst: Remove leftover /etc/apparmor.d/usr.lib.snapd.snap-confine - without this change apparmor loads the wrong profile for snap-confine which will lead to service restart failures and failure to run snaps on upgrades from older versions of snapd = TEST CASE = 1. This is tested in tests/main/upgrade-from-2.15 - without this change the go-example-webserver will fail to (re)start when snapd is upgraded. 2. This is tested in tests/main/snap-system-env which will ensure that PATH still has .*/local/.* 3. This is tested in tests/main/upgrade-from-2.15 - without that the snap apptest-snapd-tools.echo would not work after the upgrade of snapd. = REGRESSION POTENTIAL = 1. low regression potential, the order of the snippets is changed only, no new code or removed code in postinst 2. low regression risk, worst case is that the chmod does not work and we break PATH again - we have an automated test for this 3. low regression potential: removing the snap-confine file has the risk that someone who downgrades the deb from 2.37 to 2.15 has a missing conffile now and snap-confine does not run properly anymore. 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 1811233] Re: [SRU] 2.37.1 and 2.37.3
This bug was fixed in the package snapd - 2.37.4 --- snapd (2.37.4) xenial; 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 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/1811233 Title: [SRU] 2.37.1 and 2.37.3 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: Fix Committed Status in snapd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released Bug description: This is a new version of snapd. This bug tracks both 2.37.1 which got released to bionic and cosmic. It also tracks 2.37.3 which will be released to trusty,xenial,bionic,cosmic. The debian changes and the rational for it can be found here: https://github.com/snapcore/snapd/pull/6508 The changelog is available here https://github.com/snapcore/snapd/blob/2.37/packaging/ubuntu-16.04/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.36 (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 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/1811233/+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 1818049] Re: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
This bug was fixed in the package virtualbox-hwe - 5.1.38-dfsg- 0ubuntu1.16.04.2 --- virtualbox-hwe (5.1.38-dfsg-0ubuntu1.16.04.2) xenial; urgency=medium * debian/patches/fix-compile-for-xenial-kernel.patch - Fix for LP: #1818049 (virtualbox dkms modules fail to build with linux 4.4.0-143.169) -- Kleber Sacilotto de Souza Thu, 28 Feb 2019 16:06:20 +0100 ** 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/1818049 Title: virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in virtualbox source package in Trusty: Won't Fix Status in virtualbox-lts-xenial source package in Trusty: Fix Committed Status in virtualbox source package in Xenial: Fix Committed Status in virtualbox-hwe source package in Xenial: Fix Released Bug description: [Impact] virtualbox dkms modules fail to build after Ubuntu kernel 4.4 backported the following fix from upstream stable, which is included on xenial kernel 4.4.0-143.169 that's currently in -proposed. mm: replace get_user_pages() write/force parameters with gup_flags https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-next=9c72ad08f1510332e9314046e6a2adba5064f39a Excerpt from ./virtualbox/5.1.38/build/make.log: /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1112:18: error: too many arguments to function ‘get_user_pages’ rc = get_user_pages(pTask, /* Task for fault accounting. */ ^ In file included from /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0, from /var/lib/dkms/virtualbox/5.1.38/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ [Test case] Install virtualbox dkms packages (virtualbox-dkms and virtualbox-guest-dkms) with Ubuntu linux 4.4.0-143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1818049/+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+18.04 --- snapd (2.37.4+18.04) bionic; 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 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/1817949 Title: [SRU] 2.37.4 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: Fix Committed Status in snapd source package in Xenial: Fix Committed Status in snapd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released 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. = PACKAGING CHANGES = 1. debian/rules: Fix the apparmor loading order, this change ensures that the new apparmor profiles are loaded *before* snapd is restarted. The old behaviour was buggy and when jumping from a very old version of snapd the old behaviour would cause snap services to fail to start. 2. debian/rules: Disable /usr/lib/systemd/system-environment-generators/snapd-env-generator on 18.04 because the systemd environment generator is not working correctly in 18.04 (this triggered LP: #1811233). 3. debian/postinst: Remove leftover /etc/apparmor.d/usr.lib.snapd.snap-confine - without this change apparmor loads the wrong profile for snap-confine which will lead to service restart failures and failure to run snaps on upgrades from older versions of snapd = TEST CASE = 1. This is tested in tests/main/upgrade-from-2.15 - without this change the go-example-webserver will fail to (re)start when snapd is upgraded. 2. This is tested in tests/main/snap-system-env which will ensure that PATH still has .*/local/.* 3. This is tested in tests/main/upgrade-from-2.15 - without that the snap apptest-snapd-tools.echo would not work after the upgrade of snapd. = REGRESSION POTENTIAL = 1. low regression potential, the order of the snippets is changed only, no new code or removed code in postinst 2. low regression risk, worst case is that the chmod does not work and we break PATH again - we have an automated test for this 3. low regression potential: removing the snap-confine file has the risk that someone who downgrades the deb from 2.37 to 2.15 has a missing conffile now and snap-confine does not run properly anymore. 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 1817949] Re: [SRU] 2.37.4
This bug was fixed in the package snapd - 2.37.4+18.10 --- snapd (2.37.4+18.10) cosmic; 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 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/1817949 Title: [SRU] 2.37.4 Status in snapd package in Ubuntu: Fix Released Status in snapd source package in Trusty: Fix Committed Status in snapd source package in Xenial: Fix Committed Status in snapd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released 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. = PACKAGING CHANGES = 1. debian/rules: Fix the apparmor loading order, this change ensures that the new apparmor profiles are loaded *before* snapd is restarted. The old behaviour was buggy and when jumping from a very old version of snapd the old behaviour would cause snap services to fail to start. 2. debian/rules: Disable /usr/lib/systemd/system-environment-generators/snapd-env-generator on 18.04 because the systemd environment generator is not working correctly in 18.04 (this triggered LP: #1811233). 3. debian/postinst: Remove leftover /etc/apparmor.d/usr.lib.snapd.snap-confine - without this change apparmor loads the wrong profile for snap-confine which will lead to service restart failures and failure to run snaps on upgrades from older versions of snapd = TEST CASE = 1. This is tested in tests/main/upgrade-from-2.15 - without this change the go-example-webserver will fail to (re)start when snapd is upgraded. 2. This is tested in tests/main/snap-system-env which will ensure that PATH still has .*/local/.* 3. This is tested in tests/main/upgrade-from-2.15 - without that the snap apptest-snapd-tools.echo would not work after the upgrade of snapd. = REGRESSION POTENTIAL = 1. low regression potential, the order of the snippets is changed only, no new code or removed code in postinst 2. low regression risk, worst case is that the chmod does not work and we break PATH again - we have an automated test for this 3. low regression potential: removing the snap-confine file has the risk that someone who downgrades the deb from 2.37 to 2.15 has a missing conffile now and snap-confine does not run properly anymore. 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 1798921] Re: sky2 ethernet card don't work after returning from suspension
** 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+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 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
Test kernel for Disco with this config enabled: http://people.canonical.com/~phlin/kernel/lp-1819881-font/D/ I will just patch this for D, for T/X/B/C, it looks like the FONT_TER16x32 support (ac8b6f14) can be cherry-picked as well, please let me know if we want this for older releases. ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Invalid -- 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/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Cosmic: Invalid Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
Oops, mis-understand this. Patch available in Disco, but the config needs to be enabled. ** Changed in: linux (Ubuntu) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 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 Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819881/+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
