[Group.of.nepali.translators] [Bug 1809699] Re: cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial
** Changed in: ubuntu-kernel-tests 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/1809699 Title: cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: == SRU Justification == This cpu-hotplug test will always return PASSED even if there are some failures there: $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in cpu-hotplug; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' for TARGET in cpu-hotplug; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' pid 25001's current affinity mask: 3 pid 25001'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 78: /sys/devices/system/cpu/cpu2/online: No such file or directory online_cpu_expect_success 2: unexpected fail ./cpu-on-off-test.sh: line 83: /sys/devices/system/cpu/cpu2/online: No such file or directory offline_cpu_expect_success 2: unexpected fail selftests: cpu-on-off-test.sh [PASS] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' == Fixes == 8fe6e53a8ed5f0 (selftests/cpu-hotplug: exit with failure when test occured unexpected behaviors) For newer releases, they already have this patch. For Trusty and older release, they will need more work to get this patch. == Regression Potential == None, fix for testing tools. For Trusty, it's missing another 20 commits to reach 8fe6e53: 4813d2e736 (tools: memory-hotplug fix unexpected operator error) da9bc4 (tools: selftests - create a separate hotplug target for full range test) a88cc108f6 (lib: Export interval_tree) 93e9ef83f4 (test: add minimal module for verification testing) 3e2a4c183a (test: check copy_to/from_user boundary validation) 64a8946b44 (net: filter: BPF testsuite) 7069a97a14 (selftests/net: move test out of Makefile into a shell script) 3c25fa14f0 (selftests/user: move test out of Makefile into a shell script) 24fe831c17 (tools/testing/selftests/sysctl: validate sysctl_writes_strict) 0a8adf5847 (test: add firmware_class loader test) 6e68e6c5e4 (ftracetest: Initial commit for ftracetest) 4f5ce5e8d7 (selftests: add memfd_create() + sealing tests) c9b26b81af (syscalls: add selftest for execveat(2)) 3ce51050fa (selftest: size: Add size test for Linux kernel) backport with context arrangement 87b2d44026 (selftests: add memfd/sealing page-pinning tests) 498b473af9 (tools: selftests: fix build issue with make kselftests target) ce6a144a0d (selftests/memfd: Run test on all architectures) 5e29a9105b (selftests: Introduce minimal shared logic for running tests) cc16782169 (selftests: change cpu on-off-test.sh name to be unique) 8c749ce93e (selftests: create test-specific kconfig fragments) 8fe6e53a8e (selftests/cpu-hotplug: exit with failure when test occured unexpected behaviors) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl 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' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Mon Dec 24 04:08:18 2018 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or director
[Group.of.nepali.translators] [Bug 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt
** Also affects: libxfont (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libxfont (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/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt Status in libxfont package in Ubuntu: Fix Released Status in libxfont source package in Xenial: New Status in libxfont package in Nexenta Operating System: Unknown Bug description: Compiling the xorg Test Suite called XTS (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on this Bug, - /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf BDF Error on line 32: character 'ascii001' has out of range width, -8 /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt Makefile:767: recipe for target 'xtfont4.pcf' failed --- Which seems to be fixed upstream, See RedHat Bugzilla 1241939 (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream fix here (https://lists.x.org/archives/xorg- devel/2015-July/046914.html) I hope, I can get this fixed/backported soon on Ubuntu Xenial. Operating System Details: Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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
** Changed in: ubiquity (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: Fix Released 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 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt
btw, libxfont2 is backported to xenial, so you should be able to build XTS with libxfont-dev, not libxfont1-dev ** Changed in: libxfont (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt Status in libxfont package in Ubuntu: Fix Released Status in libxfont source package in Xenial: Won't Fix Status in libxfont package in Nexenta Operating System: Unknown Bug description: Compiling the xorg Test Suite called XTS (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on this Bug, - /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf BDF Error on line 32: character 'ascii001' has out of range width, -8 /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt Makefile:767: recipe for target 'xtfont4.pcf' failed --- Which seems to be fixed upstream, See RedHat Bugzilla 1241939 (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream fix here (https://lists.x.org/archives/xorg- devel/2015-July/046914.html) I hope, I can get this fixed/backported soon on Ubuntu Xenial. Operating System Details: Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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 1778811] Re: live-build doesn't work with multi-part initrds
** Also affects: live-build (Ubuntu Trusty) 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/1778811 Title: live-build doesn't work with multi-part initrds Status in live-build package in Ubuntu: Fix Released Status in live-build source package in Trusty: New Status in live-build source package in Xenial: Fix Released Status in live-build source package in Bionic: Fix Released Bug description: [Impact] Due to attempts to treat initrds as single compressed files (both for recompression, and in the lesser-used codepath for hunting through the initrd to find a file), multi-part initrds cause live-build to fail. Proposed fix is to let initramfs-tools do the heavy lifting, by setting COMPRESS for generating initrds, and by using unmkinitramfs to unpack them and look around for stuff. [Test Case] A livefs build of a -proposed bionic image should generate a working initrd. To test this a new bionic build on cdimage should be started. The build should succeed and generate a working image. [Regression Potential] The initrds are empty right now so it can't get any worse than this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1778811/+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 1749283] Re: configured stats_temp_directory does not get created after reboot
@Mario / @Eric - just to check in whoms curt the ball is right now - Is Mario or someone else in your Org still/again working on this? If not who do we need to bother to re-assign properly? ** Changed in: resource-agents (Ubuntu Artful) Status: New => 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/1749283 Title: configured stats_temp_directory does not get created after reboot Status in postgresql-common package in Ubuntu: Won't Fix Status in resource-agents package in Ubuntu: In Progress Status in postgresql-common source package in Xenial: Won't Fix Status in resource-agents source package in Xenial: New Status in postgresql-common source package in Artful: Won't Fix Status in resource-agents source package in Artful: Invalid Status in postgresql-common source package in Bionic: Won't Fix Status in resource-agents source package in Bionic: New Status in postgresql-common package in Debian: Fix Released Bug description: Default postgres installation in Ubuntu (and Debian) configures stats_temp_directory inside /var/run/postgresql: $ grep stats_temp /etc/postgresql/10/main/postgresql.conf stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp' However, this directory is not created after reboot. In most cases this is not a problem as systemd starts postgres via pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and pg_ctlcluster will create missing directories before starting postgres. But in cases where systemd is not starting postgres this is a problem. Specifically, when postgres is controlled by pacemaker (using postgres resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl won't create missing directories and therefore postgres fails to start. The simplest solution for this issue is to have systemd recreate missing directories via /usr/lib/tmpfiles.d/postgresql.conf file. Currently only /var/run/postgresql and /var/log/postgresql are created using systemd-tmpfiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+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 1818201] Re: /usr/lib/packagekit/packagekitd:11:__memmove_avx_unaligned_erms:std::char_traits:std::__cxx11::basic_string:std::__cxx11::basic_string:std::__cxx11::bas
SRUs uploaded for bionic and cosmic. Since we do not use packagekit in gnome-software in xenial, not fixing it there. Also not fixing it in trusty, as it's close to EOL. ** Changed in: packagekit (Ubuntu Cosmic) Status: New => In Progress ** Changed in: packagekit (Ubuntu Bionic) Status: New => In Progress ** Changed in: packagekit (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1818201 Title: /usr/lib/packagekit/packagekitd:11:__memmove_avx_unaligned_erms:std::char_traits:std::__cxx11::basic_string:std::__cxx11::basic_string:std::__cxx11::basic_string Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Won't Fix Status in packagekit source package in Bionic: In Progress Status in packagekit source package in Cosmic: In Progress Status in packagekit source package in Disco: Fix Released Bug description: [Impact] packagekit (sometimes) crashes when there are errors. [Test case] Check that there are no further cases on the error tracker with the proposed version. [Regression potential] Given that this just changes the return type of a function only used in calls, and the code compiles, there should be no possibility for a regression. Of course, if there were, it'd be segfaults or stuff. [Original info] The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.12-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1818201/+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 1805920] Re: iPXE ignores vlan 0 traffic
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d- 0ubuntu4.1 --- ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu4.1) cosmic; urgency=medium * d/p/0005-strip-802.1Q-VLAN-0-priority-tags.patch: Strip 802.1Q VLAN 0 priority tags; Fixes PXE when VLAN tag is 0. (LP: #1805920) -- Andres Rodriguez Mon, 10 Dec 2018 16:26:42 -0500 ** Changed in: ipxe (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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Fix Committed Status in ipxe source package in Cosmic: Fix Released Status in ipxe source package in Disco: Fix Released Bug description: [Impact] * VLAN 0 is special (for QoS actually, not a real VLAN) * Some components in the stack accidentally strip it, so does ipxe in this case. * Fix by porting a fix that is carried by other distributions as upstream didn't follow the suggestion but it is needed for the use case affected by the bug here (Thanks Andres) [Test Case] * Comment #42 contains a virtual test setup to understand the case but it does NOT trigger the isse. That requires special switch HW that adds VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a customer site with such hardware being affected by this issue. [Regression Potential] * The only reference to VLAN tags on iPXE boot that we found was on iBFT boot for SCSI, we tested that in comment #34 and it still worked fine. * We didn't see such cases on review, but there might be use cases that made some unexpected use of the headers which are now stripped. But that seems wrong. [Other Info] * n/a --- I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1685885] Re: Extreme RAM and SWAP usage
This bug was fixed in the package landscape-client - 18.01-0ubuntu4.2 --- landscape-client (18.01-0ubuntu4.2) cosmic; urgency=medium * debian/patches/mem-usage-1685885.patch: Reduce memory usage by unused twisted logs. (LP: #1685885) -- Simon Poirier Fri, 08 Feb 2019 12:02:17 -0500 ** Changed in: landscape-client (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: landscape-client (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/1685885 Title: Extreme RAM and SWAP usage Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Bug description: [Impact] * Memory usage of landscape processes abnormally grows, over time, even for processes which are generally idle and have no reason to grow. * Most of that memory leak is due to uninitialized python-twisted logging facilities buffering logs and their context. This fix Initializes logging with a null handler to have those unused log entries discarded. * Upstream twisted has mitigated part of the issue in recent releases by reducing the default buffer size. Because of that, the impact of this bug is greater on xenial. [Test Case] * register a landscape client and log the memory growth over a day * the effect is most noticeable on /usr/bin/landscape-client and less on the other processes * the memory difference on recent releases (bionic and up) is expected to be smaller (~10mb on bionic instead of 200mb on xenial) [Regression Potential] * The fix initializes twisted logging, which is unused by landscape so it is unlikely to have an impact. * The fix comes from recommendations on the upstream bug: https://twistedmatrix.com/trac/ticket/8164 [Original description] This has been noticed on several systems of mine, all 16.04. Landscape Client takes up, over time, an *extreme* amount of system resources. On a 1024MB RAM system, within 3 days to a month, Landscape Client and it's python scripts (possibly cached data?) are consuming massive quantities of memory - in the realm of 512MB RAM and over 400MB of the Swap on the system. This is repeatably shown in other systems of mine as well. Is there a memory leak or something in landscape-client that would contribute to this issue? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: landscape-client 16.03-0ubuntu2.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_vcdevice talpa_core talpa_linux talpa_syscallhook talpa_pedevice ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Apr 24 14:42:37 2017 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Package: landscape-client 16.03-0ubuntu2.16.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Tags: third-party-packages xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1685885/+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 1778811] Re: live-build doesn't work with multi-part initrds
This bug was fixed in the package live-build - 3.0~a57-1ubuntu11.5 --- live-build (3.0~a57-1ubuntu11.5) trusty; urgency=medium * Backport Adam's ubuntu-initramfs-handling.patch patch from xenial: Use initramfs-tools to work with initrds, instead of trying to naively repack and unpack them blindly (LP: #1778811) -- Łukasz 'sil2100' Zemczak Mon, 04 Mar 2019 13:27:25 +0100 ** Changed in: live-build (Ubuntu Trusty) 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/1778811 Title: live-build doesn't work with multi-part initrds Status in live-build package in Ubuntu: Fix Released Status in live-build source package in Trusty: Fix Released Status in live-build source package in Xenial: Fix Released Status in live-build source package in Bionic: Fix Released Bug description: [Impact] Due to attempts to treat initrds as single compressed files (both for recompression, and in the lesser-used codepath for hunting through the initrd to find a file), multi-part initrds cause live-build to fail. Proposed fix is to let initramfs-tools do the heavy lifting, by setting COMPRESS for generating initrds, and by using unmkinitramfs to unpack them and look around for stuff. [Test Case] A livefs build of a -proposed bionic image should generate a working initrd. To test this a new bionic build on cdimage should be started. The build should succeed and generate a working image. [Regression Potential] The initrds are empty right now so it can't get any worse than this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1778811/+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 1815251] Re: Build buildd images
This bug was fixed in the package livecd-rootfs - 2.408.44 --- livecd-rootfs (2.408.44) xenial; urgency=medium * Make sure buildd images have a /usr/sbin/policy-rc.d symlink (LP: #1815251). -- Colin Watson Mon, 18 Feb 2019 16:05:32 + ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: livecd-rootfs (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/1815251 Title: Build buildd images Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Bug description: I've been working for some time on having livecd-rootfs be able to build buildd chroots. This has a few immediate advantages: it makes the process of building those chroots more transparent and reproducible, reduces the pressure on the single person currently responsible for managing chroots across all architectures, and allows for a less frustrating chroot update process since I added a facility to Launchpad last year for updating chroots from a livefs build which will be a fast API operation rather than something requiring uploading several hundred megabytes to Launchpad and frequently timing out. I expect that in the future it can also allow us to have separate chroots for e.g. -updates at relatively low cost, which will make builds for stable series substantially faster as they won't need to apply a large and growing set of upgrades at the start of nearly every build. We also have a more recent requirement to build LXD images in order that we can converge with the images used by snapcraft, and so that we can use them directly in Launchpad livefs and snap builds rather than having to convert chroots on the fly. Fortunately it's quite easy to convert buildd chroots into images usable by LXD, and for now I've simply translated the approach currently used in launchpad-buildd to do the conversion on the fly. Particularly in order to assist with snapcraft convergence but also so that we can improve build performance for the heavily-used LTS series, I'd like to backport this support to xenial and bionic. Most of it has been in disco for a while now, with some recent tweaks. [Test Case] We'll want to run livefs builds in Launchpad with appropriate configuration, similar to https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/disco/buildd, and probably then test on dogfood or similar before unleashing them on production. [Regression Potential] The patch is substantially just adding another subproject type so I'm not too concerned, but of course we should check that a couple of other build types still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1815251/+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 1685885] Re: Extreme RAM and SWAP usage
This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.6 --- landscape-client (16.03-0ubuntu2.16.04.6) xenial; urgency=medium * debian/patches/mem-usage-1685885.patch: Reduce memory usage by unused twisted logs. (LP: #1685885) -- Simon Poirier Fri, 08 Feb 2019 12:02:17 -0500 ** Changed in: landscape-client (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/1685885 Title: Extreme RAM and SWAP usage Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Bug description: [Impact] * Memory usage of landscape processes abnormally grows, over time, even for processes which are generally idle and have no reason to grow. * Most of that memory leak is due to uninitialized python-twisted logging facilities buffering logs and their context. This fix Initializes logging with a null handler to have those unused log entries discarded. * Upstream twisted has mitigated part of the issue in recent releases by reducing the default buffer size. Because of that, the impact of this bug is greater on xenial. [Test Case] * register a landscape client and log the memory growth over a day * the effect is most noticeable on /usr/bin/landscape-client and less on the other processes * the memory difference on recent releases (bionic and up) is expected to be smaller (~10mb on bionic instead of 200mb on xenial) [Regression Potential] * The fix initializes twisted logging, which is unused by landscape so it is unlikely to have an impact. * The fix comes from recommendations on the upstream bug: https://twistedmatrix.com/trac/ticket/8164 [Original description] This has been noticed on several systems of mine, all 16.04. Landscape Client takes up, over time, an *extreme* amount of system resources. On a 1024MB RAM system, within 3 days to a month, Landscape Client and it's python scripts (possibly cached data?) are consuming massive quantities of memory - in the realm of 512MB RAM and over 400MB of the Swap on the system. This is repeatably shown in other systems of mine as well. Is there a memory leak or something in landscape-client that would contribute to this issue? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: landscape-client 16.03-0ubuntu2.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_vcdevice talpa_core talpa_linux talpa_syscallhook talpa_pedevice ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Apr 24 14:42:37 2017 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-02 (21 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) Package: landscape-client 16.03-0ubuntu2.16.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Tags: third-party-packages xenial Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1685885/+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 1805920] Re: iPXE ignores vlan 0 traffic
This bug was fixed in the package ipxe - 1.0.0+git-20180124.fbe8c52d- 0ubuntu2.2 --- ipxe (1.0.0+git-20180124.fbe8c52d-0ubuntu2.2) bionic; urgency=medium * d/p/0005-strip-802.1Q-VLAN-0-priority-tags.patch: Strip 802.1Q VLAN 0 priority tags; Fixes PXE when VLAN tag is 0. (LP: #1805920) -- Andres Rodriguez Mon, 10 Dec 2018 16:26:42 -0500 ** Changed in: ipxe (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/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Fix Released Status in ipxe source package in Cosmic: Fix Released Status in ipxe source package in Disco: Fix Released Bug description: [Impact] * VLAN 0 is special (for QoS actually, not a real VLAN) * Some components in the stack accidentally strip it, so does ipxe in this case. * Fix by porting a fix that is carried by other distributions as upstream didn't follow the suggestion but it is needed for the use case affected by the bug here (Thanks Andres) [Test Case] * Comment #42 contains a virtual test setup to understand the case but it does NOT trigger the isse. That requires special switch HW that adds VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a customer site with such hardware being affected by this issue. [Regression Potential] * The only reference to VLAN tags on iPXE boot that we found was on iBFT boot for SCSI, we tested that in comment #34 and it still worked fine. * We didn't see such cases on review, but there might be use cases that made some unexpected use of the headers which are now stripped. But that seems wrong. [Other Info] * n/a --- I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority of packets. This is separate from vlan, it just happens to use that ethertype to do the priority tagging. Someone confirmed to me that, in the iPXE source, it drops all packets if they are vlan tagged. The customer is unable to figure out why the packets between blades is getting vlan tagged so we either need to figure out how to allow iPXE to accept vlan 0 or the customer will need to use different equipment for the MAAS nodes. I found a conversation on the ipxe-devel mailing list that suggested a commit was submitted and signed off but that was from 2016 so I'm not sure what became of it. Notable messages in the thread: http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html Would it be possible to install a local patch as part of the FCE deployment? I suspect the patch(es) mentioned in the above thread would require some modification to apply properly. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1805920/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.7 --- initramfs-tools (0.130ubuntu3.7) bionic; urgency=medium [ Steve Langasek ] * hooks/resume: cherry-pick patch from upstream git to fix auto-configuration of resume devices that are on LVM; always refer to them by name, never by UUID. LP: #1768230. [ Thadeu Lima de Souza Cascardo ] * Do not include graphical drivers when FRAMEBUFFER is not set. (LP: #1561643) -- Brian Murray Thu, 17 Jan 2019 12:26:22 -0800 ** Changed in: initramfs-tools (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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: Fix Released Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1812198] Re: user_copy in user from ubuntu_kernel_selftests failed on KVM kernel
** Changed in: linux-kvm (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-kvm (Ubuntu) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- 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/1812198 Title: user_copy in user from ubuntu_kernel_selftests failed on KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: Fix Committed Status in linux-kvm source package in Cosmic: Fix Released Bug description: == Justification == This user_copy test has failed while attempting to insert the test_user_copy module, but this module does not exist in the Bionic KVM kernel as the CONFIG_TEST_USER_COPY was not enabled. # modprobe test_user_copy modprobe: FATAL: Module test_user_copy not found in directory /lib/modules/4.15.0-1028-kvm == Fix == d7d5311 (selftests: user: return Kselftest Skip code for skipped tests) 3c07aae (selftests: kselftest: change KSFT_SKIP=4 instead of KSFT_PASS) c31d02d (selftests: kselftest: Remove outdated comment) This fix will make the test return a skipped retun code if the test_user_copy module does not exist. This patch set can be cherry-picked into Bionic, and we already have it in Cosmic / Disco. For Xenial, it already got d7d5311 and does not need the other two. == Test == With this patch, the test will return "skipped" as expected: $ sudo ./test_user_copy.sh user: module test_user_copy is not found [SKIP] $ echo $? 4 Note that the test framework will need another fix to treat the SKIP return code properly. (bug 1812352) == Regression potential == None, this patch just change the code for the testing tool. -- This test_user_copy module will need the CONFIG_TEST_USER_COPY to be enabled https://cateee.net/lkddb/web-lkddb/TEST_USER_COPY.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:57:57 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812198/+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 1818595] [NEW] Update to 1.46
Public bug reported: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + https://wiki.ubuntu.com/SnapdGlibUpdates + Overview of changes in snapd-glib 1.46 - * New API: - - snapd_channel_get_released_at - - SNAPD_ERROR_DNS_FAILURE - * Fix tests breaking due to undefined order of results + * New API: + - snapd_channel_get_released_at + - SNAPD_ERROR_DNS_FAILURE + * Fix tests breaking due to undefined order of results -- 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/1818595 Title: Update to 1.46 Status in snapd-glib package in Ubuntu: New Status in snapd-glib source package in Xenial: New Status in snapd-glib source package in Bionic: New Status in snapd-glib source package in Cosmic: New Status in snapd-glib source package in Disco: New Bug description: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+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
