[Group.of.nepali.translators] [Bug 1770019] Re: linux-kvm: 4.4.0-1024.29 -proposed tracker
4.4.0-1024.29 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kvm_smoke_test - CONFIG_AUDITSYSCALL needs to be enabled (bug 1770245) ubuntu_qrt_kernel_security - test_072_config_debug_rodata (bug 1760643) test_072_config_debug_set_module_ronx (bug 1760646) test_074_config_security_default_mmap_min_addr (bug 1760650) test_076_config_security_acl_ext4 (bug 1760652) test_077_config_security_ipsec (bug 1760653) test_151_sysctl_disables_bpf_unpriv_userns (bug 1760656) test_160_setattr_CVE_2015_1350 (bug 1760657) ubuntu_zram_smoke_test - zram module not found (bug 1766823) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1770019 Title: linux-kvm: 4.4.0-1024.29 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770019/+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 1769182] Re: ./configure --enable-arm needed for ARM events
cosmic got this ** Changed in: rasdaemon (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: rasdaemon (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1769182 Title: ./configure --enable-arm needed for ARM events Status in rasdaemon package in Ubuntu: Fix Released Status in rasdaemon source package in Xenial: In Progress Status in rasdaemon source package in Artful: In Progress Status in rasdaemon source package in Bionic: Fix Committed Status in rasdaemon package in Debian: Fix Released Bug description: [Impact] The UEFI 2.6 spec added support for ARM processor errors and errors that have unrecognized CPER section types. rasdaemon needs to support ARM kernel trace events. To enable arm events we need to configure rasdaemon package with --enable-arm [Test] debian/rules needs --enable-arm to enable arm events. I have a test build of the rasdaemon package in ppa:centriq-team/lp1741978-rasdaemon. I tested this on an a QDF2400 system. Here are the results for bionic, artful and xenial. --- bionic --- ubuntu@awrep3:~$ sudo service rasdaemon status ● rasdaemon.service - RAS daemon to log the RAS events Loaded: loaded (/lib/systemd/system/rasdaemon.service; enabled; vendor preset Active: active (running) since Mon 2018-04-23 15:25:18 UTC; 17s ago Main PID: 3369 (rasdaemon) Tasks: 1 (limit: 7065) CGroup: /system.slice/rasdaemon.service └─3369 /usr/sbin/rasdaemon -f -r Apr 23 15:25:18 awrep3 rasdaemon[3369]: ras:arm_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: Enabled event ras:arm_event Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't parse /proc/cpuinfo: missing [vend Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't register mce handler Apr 23 15:25:18 awrep3 rasdaemon[3369]: Can't get traces from ras:aer_event Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mc_event events Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording aer_event events Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording extlog_event events Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Recording mce_record events Apr 23 15:25:19 awrep3 rasdaemon[3369]: rasdaemon: Recording arm_event events ubuntu@awrep3:~$ grep rasdaemon /var/log/syslog Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled Apr 23 15:25:18 awrep3 rasdaemon: ras:mc_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:mc_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:mc_event Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:aer_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:aer_event Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:mc_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:aer_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: Can't write to set_event Apr 23 15:25:18 awrep3 rasdaemon[3370]: rasdaemon: ras:arm_event event enabled Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:mc_event Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: ras:arm_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Enabled event ras:arm_event Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags] Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't register mce handler Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get ras:extlog_mem_event traces. Perhaps this feature is not supported on your system. Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Can't get traces from ras:aer_event Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled Apr 23 15:25:18 awrep3 rasdaemon[3369]: rasdaemon: Listening to events for cpus 0 to 45 Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event Apr 23 15:25:18 awrep3 rasdaemon: ras:aer_event event enabled Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:aer_event Apr 23 15:25:18 awrep3 rasdaemon: Can't write to set_event Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled Apr 23 15:25:18 awrep3 rasdaemon: ras:arm_event event enabled Apr 23 15:25:18 awrep3 rasdaemon: Enabled event ras:arm_event Apr 23 15:25:18 awrep3 rasdaemon: Can't parse /proc/cpuinfo: missing [vendor_id] [cpu family] [model] [cpu MHz] [flags] Apr 23 15:25:18 awrep3 rasdaemon: Can't register mce handler Apr 23 15:25:18 awrep3 rasdaemon: Can't get traces from ras:aer_event Apr 23 15:25:18 awrep3 rasda
[Group.of.nepali.translators] [Bug 1758037] Re: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown".
** Changed in: ubuntu-power-systems Status: Fix Released => 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/1758037 Title: LTC Test- Ubuntu18.04: Starting the guest with network filter defined will fail with "cause is unknown". Status in libvirt: Unknown Status in The Ubuntu-power-systems project: Fix Committed Status in libvirt package in Ubuntu: Fix Released Status in libvirt source package in Xenial: Fix Committed Status in libvirt source package in Artful: Fix Committed Status in libvirt source package in Bionic: Fix Committed Bug description: [Impact] * nwfilters were not usable if configured to use dhcp based learning * Fix by backporting upstream bug [Test Case] * Add the following to the interface section of a guest description in libvirt: Then start the guest. Bad case: error: Failed to start domain VM1 error: An error occurred, but the cause is unknown Fixed: Guest starts and works. [Regression Potential] * I thought a while on this. On first sight one might say there is a regression risk due to increasing the size of the buffer. This risk would arise on hyperscale environments where the memory consumption per guest would increase by 2*128Kb*#guest-interfaces (not much, but can sum up on MANY guests). But then I realized that this is only true for the use case using dhcpsnoop which is a) clearly not the most common case b) failing to work at all before this fix So there can't be anyone today with a working setup that then runs OOM, due to the setup either not using the feature (=no change) or failing missing this fix. So I actually think this mem consumption increase is not an issue in terms of SRU considerations. Due to that the only remaining regression would be users that had a self-built libpcap without TPACKET_V3 to drive a workload like the above, and even then only the rather small size bump is what changes. [Other Info] * I have added this case and a few deeper checks on the created rules for iptables to the regression tests --- == Comment: #2 - Mallesh N. Koti - 2018-02-28 05:02:49 == Guest Xml === ISSUE === Defining a network filter and Starting a VM with this nwfiter in VM's xml is failing with "cause is unknown". == Recreation Steps == 1. Define a network filter as: virsh nwfilter-define filter.xml 2. Add nwfilter in guest xml and start guest. virsh start VM1 It fails with : # virsh start VM1 error: Failed to start domain VM1 error: An error occurred, but the cause is unknown XML used for defining network filter: ``` -b071-6127-b4ec- ``` will be attaching the guest xml The issue happens with Ubuntu 18.04 host - where not able to start the guest with network defined with value dhcp. . Found following commit is not there in 18.04 Ubuntu source. There could be some dependent commit too. we are facing some build issue and hence not able to verify it. . https://github.com/libvirt/libvirt/commit/e62cb4a9b78c7f4499a206635fb4f06e6ac627e5 . To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1758037/+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 1770565] Re: [i915_bpo] Fix flickering issue after panel change
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (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/1770565 Title: [i915_bpo] Fix flickering issue after panel change Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Triaged Bug description: [Impact] A certain OEM laptop changed the panel type/vendor, and the change regressed the driver causing a flickering image. The ODM has tools to measure various values of the driver/panel combination, and determined that some voltage levels were way too low to pass the spec. The process to bisect the commits took weeks, so while it's technically possible that this issue was fixed by a single commit (drm/i915: Ignore OpRegion panel type except on select machines), we've also kept another 10 commits which upstream thought should help (and did, they improved the measured values but not enough). So, this backport carries all 11 commits from 4.8/4.9 that the ODM verified to pass the tests. [Test case] Needs to be tested with the ODM tools to be sure. [Regression potential] There is some, but apart from the necessary refactoring the rest are bugfixes to match the HW specs, so this should in fact fix a lot more than just this certain machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770565/+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 1770018] Re: linux-euclid: 4.4.0-9028.30 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 11. May 2018 10:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 11. May 2018 10:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1770018 Title: linux-euclid: 4.4.0-9028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-euclid package in Ubuntu: Invalid Status in linux-euclid source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1770011 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770018/+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 1770002] Re: linux-gcp: 4.13.0-1016.20 -proposed tracker
4.13.0-1016.20 - gcp Regression test CMPL. Issue to note in gcp: libhugetlbfs - 1 failed , 1 killed by signal, 3 bad config ubuntu_kvm_unit_tests - test disabled ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) Skipped / blacklisted: * ubuntu_ltp * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1770002 Title: linux-gcp: 4.13.0-1016.20 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770002/+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 1750038] Re: user space process hung in 'D' state waiting for disk io to complete
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1750038
Title:
user space process hung in 'D' state waiting for disk io to complete
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Bug description:
== SRU Justification ==
[Impact]
Occasionally an application gets stuck in "D" state on NFS reads/sync and
close system calls. All the subsequent operations on the NFS mounts are stuck
and reboot is required to rectify the situation.
[Fix]
Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is
upstream in:
ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback")
[Testcase]
See Test scenario in previous description.
A test kernel with this patch was tested heavily (>100hrs of test
suite) without issue.
[Regression Potential]
This changes memory allocation in NFS to use a different policy. This could
potentially affect NFS.
However, the patch is already in Artful and Bionic without issue.
The patch does not apply to Trusty.
== Previous Description ==
Using Ubuntu Xenial user reports processes hang in D state waiting for
disk io.
Ocassionally one of the applications gets into "D" state on NFS
reads/sync and close system calls. based on the kernel backtraces
seems to be stuck in kmalloc allocation during cleanup of dirty NFS
pages.
All the subsequent operations on the NFS mounts are stuck and reboot
is required to rectify the situation.
[Test scenario]
1) Applications running in Docker environment
2) Application have cgroup limits --cpu-shares --memory -shm-limit
3) python and C++ based applications (torch and caffe)
4) Applications read big lmdb files and write results to NFS shares
5) use NFS v3 , hard and fscache is enabled
6) now swap space is configured
This prevents all other I/O activity on that mount to hang.
we are running into this issue more frequently and identified few
applications causing this problem.
As updated in the description, the problem seems to be happening when
exercising the stack
try_to_free_mem_cgroup_pages+0xba/0x1a0
we see this with docker containers with cgroup option --memory
.
whenever there is a deadlock, we see that the process that is hung has
reached the maximum cgroup limit, multiple times and typically cleans
up dirty data and caches to bring the usage under the limit.
This reclaim path happens many times and finally we hit probably a
race get into deadlock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+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 1769996] Re: linux-oem: 4.13.0-1027.30 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 11. May 2018 15:00 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 11. May 2018 15:00 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1769996 Title: linux-oem: 4.13.0-1027.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1769993 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769996/+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 1766401] Re: full config file wiped after apt-upgrade issued
This bug was fixed in the package cloud-init - 18.2-41-g3b712fce- 0ubuntu1 --- cloud-init (18.2-41-g3b712fce-0ubuntu1) cosmic; urgency=medium * debian/new-upstream-snapshot: Remove script, now maintained elsewhere. * New upstream snapshot. - tests: do not rely on host /proc/cmdline in test_net.py [Lars Kellogg-Stedman] (LP: #1769952) - ds-identify: Remove dupe call to is_ds_enabled, improve debug message. - SmartOS: fix get_interfaces for nics that do not have addr_assign_type. - tests: fix package and ca_cert cloud_tests on bionic (LP: #1769985) - ds-identify: make shellcheck 0.4.6 happy with ds-identify. - pycodestyle: Fix deprecated string literals, move away from flake8. - azure: Add reported ready marker file. [Joshua Chan] (LP: #1765214) - tools: Support adding a release suffix through packages/bddeb. - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt. [Harm Weites] (LP: #1404745) - tools: Re-use the orig tarball in packages/bddeb if it is around. - netinfo: fix netdev_pformat when a nic does not have an address assigned. (LP: #1766302) - collect-logs: add -v flag, write to stderr, limit journal to single boot. (LP: #1766335) - IBMCloud: Disable config-drive and nocloud only if IBMCloud is enabled. (LP: #1766401) - Add reporting events and log_time around early source of blocking time -- Scott Moser Fri, 11 May 2018 16:37:02 -0400 ** Changed in: cloud-init (Ubuntu Cosmic) 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/1766401 Title: full config file wiped after apt-upgrade issued Status in cloud-images: New Status in cloud-init: Fix Committed 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 Artful: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Fix Released Bug description: === Begin SRU Template === [Impact] Upgrades of cloud-init on official Ubuntu 16.04 and 17.10 images running on IBM public cloud will be unreachable after a reboot. This is because cloud-init incorrectly recognizes the newly added 'IBMCloud' as the datasource to use and skips use of the previously used ConfigDrive or NoCloud datasource. This is because a.) Official 16.04 and 17.10 images of Ubuntu have seeded data in their /var/lib/cloud/seed/ directory that was used on first boot and should be continued to be used. b.) IBMCloud's datasource in some scenarios appears looks similar to that of Config Drive. The version of cloud-init in xenial and artful checks to disable config-drive in order to identify the IBMCloud datasource. That should not happen unless the IBMCloud datasource is enabled, which is configured off in those images. The fix is to continue using the existing datasource on those images. [Test Case] * Launch an image on IBM public cloud. * add -proposed * apt-get update && apt-get install cloud-init * reboot * ssh back in If you are able to ssh back in, then this bug has been fixed. [Regression Potential] This specific fix is tightly contained down the path involved in IBM cloud. The most likely failure scenario would be failure in 18.04 images which do not have the additional datasources built into the images. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11172924 === End SRU Template === file: 50-cloud-init.cfg wiped of it's initial (working) configuration after a standard apt-upgrade was issued. Cloud provider is SoftLayer. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1766401/+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 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** Changed in: inkscape 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/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Released Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in terminator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in terminator source package in Xenial: Confirmed Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1756587] Re: mii-mon should have a consistent unit schema
This bug was fixed in the package netplan.io - 0.37.1 --- netplan.io (0.37.1) cosmic; urgency=medium * tests/integration.py: fix autopkgtests to be less flaky, especially given changes in systemd-networkd's behavior regarding Router Advertisements. -- Mathieu Trudel-Lapierre Fri, 11 May 2018 09:58:19 -0400 ** Changed in: netplan.io (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/1756587 Title: mii-mon should have a consistent unit schema Status in netplan: Fix Committed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Committed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Committed Status in netplan.io source package in Bionic: Fix Committed Status in nplan source package in Bionic: Invalid Bug description: [Impact] Documentation is confusing to users wishing to tune bond and bridge parameters. This potentially affects all users of netplan. [Test case] 1) Update the netplan.io package. 2) Run 'man netplan' 3) Verify that the documentation under "parameters" for bridges and bonds is clear that time-based parameters are in milliseconds unless otherwise specified by the individual parameter: For example, in the bonds section: - learn-packet-interval is in seconds - mii-monitor-interval, up-delay, down-delay, arp-interval are in milliseconds [Regression potential] Change is limited to the manpage; there is no risk of regression there, except for a garbled manpage or missing file. Any new bugs in netplan behavior found after this SRU that can't be reproduced with the immediately previous version should be investigated as potential toolchain / build issues introduced by the new build required for the SRU. --- The docs say "Using the NetworkManager renderer, parameter values for intervals should be expressed in milliseconds; for the systemd renderer, they should be in seconds unless otherwise specified." This however fails to encapsulate the description of the network in a form abstracted from the renderer. We should have a scheme which is clear, has one and only one explicit form, and works with all renderers. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1756587/+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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
This bug was fixed in the package netplan.io - 0.37.1 --- netplan.io (0.37.1) cosmic; urgency=medium * tests/integration.py: fix autopkgtests to be less flaky, especially given changes in systemd-networkd's behavior regarding Router Advertisements. -- Mathieu Trudel-Lapierre Fri, 11 May 2018 09:58:19 -0400 ** Changed in: netplan.io (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/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: New Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: New Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Committed Status in initramfs-tools source package in Artful: New Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Committed Status in initramfs-tools source package in Bionic: New Status in netplan.io source package in Bionic: Fix Committed Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+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
