[Group.of.nepali.translators] [Bug 1742090] Re: Redpine: Wifi/BT not functioning after s3 resume
** Changed in: hwe-next 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/1742090 Title: Redpine: Wifi/BT not functioning after s3 resume Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Bug description: System cannot be waked by wowlan, but sometimes works. When the wowlan not works and system waked by other wakeup sources, after resume the wifi and BT would not functioning until reload driver. The driver/FW info: [ 395.217187] ven_rsi_91x: RSI Version Info == [ 395.217188] ven_rsi_91x: [ 395.217192] ven_rsi_91x: FW Version : 1.5.4 [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2 [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL] [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps [ 395.217202] ven_rsi_91x: Kernel version: 4.4.0-98-generic Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58 BIOS version: 01.00.05 (Also tested with 01.00.03) Tested SKU: T, Media, GPA The reproduce steps: 1. Enable Wowlan and Wol in BIOS 2. Boot up Ubuntu core 3. Connect to Wifi AP $ nmcli d wifi connect password 4. Enable wowlan $ sudo iw phy phy0 wowlan enable magic-packet 5. Enter suspend or hibernate $ sudo systemctl suspend or $ sudo systemctl hibernate 6. Send wake signal from another machine # wakeonlan or # sudo etherwake 7. If system not waked, try to wol or other wake source # wakeonlan 8. After resume, check the wifi/BT function, but not functioning. $ nmcli dev DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi disconnected -- eth1 ethernet unavailable -- cdc-wdm0 gsm unavailable -- lo loopback unmanaged -- $ nmcli dev wifi rescan $ nmcli dev wfii list No wifi APs found $ sudo bluetoothctl [NEW] Controller 00:23:A7:EA:65:64 0225399 [default] [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed The not functioning issue can be fixed by reload driver. Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still functioning which could be the FW is reloaded by driver. This bug is only for tracking purporse, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1742090/+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 1782721] Re: DEBUG_WX is not set in Bionic KVM kernel
** Changed in: ubuntu-kernel-tests 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/1782721 Title: DEBUG_WX is not set in Bionic KVM kernel Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Bug description: == Justification == In the Bionic KVM kernel, the CONFIG_DEBUG_WX was not set, which is needed to meet the security team's requirement. == Test == Before enabling the config, test_330_config_debug_wx will fail in the kernel security testsuite for the kernel SRU regression test. It will pass with this patche applied, tested on a KVM node. == Fix == UBUNTU: [Config]: enable CONFIG_DEBUG_WX == Regression Potential == Minimal. No code changes, just a config changes without disabling any other configs. -- The kernel security test require this config to be enabled. FAIL: test_330_config_debug_wx (__main__.KernelSecurityConfigTest) Ensure DEBUG_WX is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2537, in test_330_config_debug_wx self.assertKernelConfig('DEBUG_WX', expected) File "./test-kernel-security.py", line 207, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 194, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: DEBUG_WX option was expected to be set in the kernel config ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Jul 20 07:56:06 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash 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/1782721/+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 1739591] Re: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial
** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: lttng-modules 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/1739591 Title: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial Status in lttng-modules: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in lttng-modules package in Ubuntu: Fix Released Status in lttng-modules source package in Xenial: Fix Released Status in lttng-modules source package in Artful: Fix Released Bug description: SRU request, Xenial, Artful [Impact] lttng dkms modules fail to build against newer HWE kernels because of missing 4.14 compat fixes that allow it to build against newer 4.14 kernels. [Fix] Upstream lttng 4.14 compat fixes. [Testcase] Without the fix, running the kernel team autotest lttng regression test suite fails because the module does not build and install. With the fix the lttng smoke tests pass. To run the test: sudo autotest/client/autotest-local autotest/client/tests/ubuntu_lttng_smoke_test/control using git://kernel.ubuntu.com/ubuntu/autotest and git://kernel.ubuntu.com/ubuntu/autotest-client-tests [Regression Potential] lttng fails to build and work against older kernels. As the new code is #if'def'd compat code the 4.14 specific changes are not built into the older kernels, so this risk is small. -- [stdout] Setting up lttng-modules-dkms (2.8.0-1ubuntu1~16.04.3) ... [stdout] Loading new lttng-modules-2.8.0 DKMS files... [stdout] First Installation: checking all kernels... [stdout] Building only for 4.14.0-1002-azure-edge [stdout] Building initial module for 4.14.0-1002-azure-edge [stdout] Error! Bad return status for module build on kernel: 4.14.0-1002-azure-edge (x86_64) [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/lttng-modules/+bug/1739591/+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 1781036] Re: bionic amd64 netboot.tar.gz - bad permission on uncompressed file
This bug was fixed in the package debian-installer - 20101020ubuntu451.25 --- debian-installer (20101020ubuntu451.25) xenial; urgency=medium * Bump FLOPPY_SIZE on amd64, i386 and powerpc for linux-firmware growth. debian-installer (20101020ubuntu451.24) xenial; urgency=medium [ Łukasz 'sil2100' Zemczak ] * Move master kernels to 4.4.0-131. * Move hwe kernels to 4.15.0-29. * Rebuild against new systemd for SCSI sync (LP: #1779815) * build/config/amd64/hwe-*.cfg, build/config/ppc64el/hwe-*.cfg: - Strip off .efi.signed for signed hwe kernels. [ Adam Conrad ] * Fix permissions on the netboot.tar kernel (LP: #1781036) -- Łukasz 'sil2100' Zemczak Fri, 27 Jul 2018 10:38:40 +0200 ** Changed in: debian-installer (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/1781036 Title: bionic amd64 netboot.tar.gz - bad permission on uncompressed file Status in debian-installer package in Ubuntu: Fix Released Status in debian-installer source package in Xenial: Fix Released Status in debian-installer source package in Bionic: Fix Released Bug description: I find that the permission on a file is not correct. Unpacking the tarball http://be.archive.ubuntu.com/ubuntu/dists/bionic/main/installer- amd64/current/images/netboot/netboot.tar.gz to prepare my TFTP server, I found that the permission on the file .../ubuntu- installer/amd64/linux is 600 instead of 644. This prevents the process to perform a PXE installation. FYI: TZ=utc ls -n ./netboot.tar.gz -rw-r--r-- 1 xxx xxx 54820328 avr 25 21:23 ./netboot.tar.gz sha256sum ./netboot.tar.gz 5fe1e599ed7266abb39364b21c07870866b37f655d603c3b2191394a3e85ff39 ./netboot.tar.gz TZ=utc ls -n ./ubuntu-installer/amd64/linux -rw--- 1 xxx xxx 8249080 avr 25 20:10 ./ubuntu-installer/amd64/linux sha256sum ./linux beeab595bb361fa38f9eadac4bedff6082c2f7f06cb97507103a4316a291c0f5 ./linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1781036/+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 1760796] Re: kernel 4.15 breaks xl2tpd
This bug was fixed in the package xl2tpd - 1.3.6+dfsg-4ubuntu0.16.04.2 --- xl2tpd (1.3.6+dfsg-4ubuntu0.16.04.2) xenial; urgency=medium * Fix ENODEV errors with linux kernel 4.15 (LP: #1760796) - d/p/fix-for-enodev.patch: cherry-pick patch from upstream to no longer attempt to obtain IP_PKTINFO by default. -- Billy Olsen Sat, 21 Jul 2018 07:29:54 -0700 ** Changed in: xl2tpd (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/1760796 Title: kernel 4.15 breaks xl2tpd Status in xl2tpd package in Ubuntu: Fix Released Status in xl2tpd source package in Xenial: Fix Released Status in xl2tpd source package in Artful: Won't Fix Status in xl2tpd source package in Bionic: Fix Committed Status in xl2tpd package in Debian: Fix Released Status in xl2tpd package in Fedora: Fix Released Bug description: [Impact] Kernel 4.15 breaks xl2tpd, please see following upstream issue for more details : https://github.com/xelerance/xl2tpd/issues/147 The following commit/patch fixes the issue: https://github.com/xelerance/xl2tpd/commit/9c2cd4933478a83075df5b10f24af7589e90abc3.patch As Ubuntu 18.04 (Bionic Beaver) is no longer accepting Debian packages, I'm guessing then that the patch would need to be added and applied to the existing xl2tpd-1.3.10-1 package. The linux-image kernel package on Ubuntu 18.04 is currently linux- image-4.15.0-13 [Test Case] * apt install network-manager-l2tp-gnome * Add new VPN connection via network manager * establish vpn connection [Regression Potential] * For Bionic, there is none. The xl2tpd daemon does not work without the patch on the standard bionic kernel. * For Xenial w/ the 4.15 HWE kernel there is no risk. * For Xenial w/ the stock 4.4 kernel there is minimal risk as the code is pulling values that are not valid on the 4.4 kernel by default. Note that a test pkg (Pre-SRU) has been tested for both Bionic and Xenial by a user affected by this problem and the package has been proven to work as expected on the different supported Ubuntu kernel series (v4.4, v4.13, v4.15). For more details, please have a look at comment #17 and #23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1760796/+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 1716999] Re: installer creates rather small /boot partition
This bug was fixed in the package ubiquity - 2.21.63.7 --- ubiquity (2.21.63.7) xenial; urgency=medium * Automatic update of included source packages: console-setup 1.108ubuntu15.4, debian-installer-utils 1.113ubuntu1.16.04.1, hw- detect 1.117ubuntu2.3, partman-auto 134ubuntu1.3, partman- partitioning 110ubuntu4.2, preseed 1.71ubuntu1.2. (LP: #1716999) -- Mathieu Trudel-Lapierre Thu, 12 Jul 2018 17:34:32 -0400 ** Changed in: ubiquity (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/1716999 Title: installer creates rather small /boot partition Status in partman-auto package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in partman-auto source package in Xenial: Fix Released Status in ubiquity source package in Xenial: Fix Released Bug description: [Impact] All new installs of 16.04. [Test case] 1) Install Ubuntu 16.04 on a system 2) Validate that the size of the /boot partition is greater than or equal to 512MB; should be somewhere between 512MB and 1GB, close to 768MB. [Regression potential] This may adversely affect installs on tiny disks, by taking up more space for the /boot partition than was previously taken, at the cost of / or /home. As such, failures to install due to insufficient space on a partition, or failure to partition a disk that was previously working should be investigated as possible regressions. This is a corner case in general since there is no requirement to allocate a separate partition for /boot in the default configuration, and if you are using a non-default configuration where /boot must be a separate partition, you probably also don't have a disk so small that an additional 256MB of disk usage is a problem. --- The installer (in 16.04 and 17.10) creates a separate /boot partition, when required, of only 487M. This ends up being rather small when you using the following equation to estimate a minimal size allowing for reasonable room for further growth. (2*(3*kernel + 4*plymouth-carrying initrd + bootloader)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1716999/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
This bug was fixed in the package systemd - 229-4ubuntu21.3 --- systemd (229-4ubuntu21.3) xenial; urgency=medium [ Dimitri John Ledkov ] * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i. [ Adam Conrad ] * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to the kernel (we previously only set it in modprobe.d) LP: #1779815 -- Adam Conrad Thu, 26 Jul 2018 04:00:09 -0600 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: debian-installer (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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-i
[Group.of.nepali.translators] [Bug 1729754] Re: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad
This bug was fixed in the package python-wadllib - 1.3.2-3ubuntu0.16.04.1 --- python-wadllib (1.3.2-3ubuntu0.16.04.1) xenial; urgency=medium * Fix MIME encoding of binary parts (LP: #1729754). -- Colin Watson Fri, 20 Jul 2018 18:09:05 +0100 ** Changed in: python-wadllib (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/1729754 Title: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad Status in wadllib: Fix Released Status in python-wadllib package in Ubuntu: Fix Released Status in python-wadllib source package in Xenial: Fix Released Status in python-wadllib source package in Bionic: Fix Committed Bug description: Tested on 16.04 and 17.10 python-launchpadlib (1.10.5-1 on 17.10) python3-launchpadlib (1.10.5-1 on 17.10) While working on porting a utility using launchpadlib from Python2 to Python3, I noticed the binary attachments were becoming unreadable. I've tried uploading .jpg files, .tgz files, .tar.xz files, they all fail to open properly. P.S.: When a fix is available, can it be ported to Xenial? We need this for our tools running on devices using Xenial. [Test Case] I wrote a little proof of concept that uploads a given binary attachment to a launchpad issue (see attachment). To use it on staging launchpad: APPORT_STAGING=1 ./poc.py When using the exact same script with python2 (basically, replacing `python3` with `python` in the shebang line), the binary file is properly attached. That's why I think it's a bug with python3-launchpadlib. [Regression Potential] The only sensible way to fix this bug was to rewrite how wadllib does MIME-encoding of its form uploads, so it'll be important to test both text and binary uploads. Launchpad only defines a few methods that use multipart/form-data, so the regression potential is confined to those: bug.addAttachment, distro_arch_series.setChroot, and project_release.add_file. To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/1729754/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778642] Re: ubuntu_lttng_smoke_test failed on Azure 4.15
This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.7 --- lttng-modules (2.8.0-1ubuntu1~16.04.7) xenial; urgency=medium * ubuntu_lttng_smoke_test failed on Azure 4.15 (LP: #1778642) - debian/patches/0041-Fix-do-not-use-CONFIG_HOTPLUG_CPU-for-the-new-hotplu.patch - debian/patches/0042-Cleanup-comment-about-CONFIG_HOTPLUG_CPU-ifdef.patch -- Kleber Sacilotto de Souza Thu, 19 Jul 2018 17:47:16 +0200 ** Changed in: lttng-modules (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/1778642 Title: ubuntu_lttng_smoke_test failed on Azure 4.15 Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Invalid Status in lttng-modules source package in Xenial: Fix Released Status in linux-azure source package in Bionic: Invalid Status in lttng-modules source package in Bionic: In Progress Status in linux-azure source package in Cosmic: Invalid Status in lttng-modules source package in Cosmic: Fix Released Bug description: SRU Request: [Impact] After bionic/linux-azure commit 4fbb658dd8ce96384852ceae18b0b09034de7b36 (UBUNTU: [Config] azure: CONFIG_HOTPLUG_CPU=n) the lttng_tracer module cannot find some symbols and cannot be loaded. kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) This is caused by lttng-modules incorrectly handling the case when CONFIG_HOTPLUG_CPU is not enabled. [Test Case] Install linux-azure >= 4.15.0-1014, install lttng-modules-dkms and run the autotest ubuntu_lttng_smoke_test testcase (or just 'sudo lttng list --kernel'). [Fix] commit 894ce5dc825733d1ccab25b1aede9ce0be2a7c4e (Fix: do not use CONFIG_HOTPLUG_CPU for the new hotplug API) commit 1ee63d8d1b0aaf30564d3879d8e9282d0ddfef1b (Cleanup: comment about CONFIG_HOTPLUG_CPU ifdef) [Regression Potential] Very low. The two patches can be cleanly cherry-picked from the upstream commits. The first one that really fixed the issue just changes a single #ifdef to compile a piece of code when CONFIG_HOTPLUG_CPU is not defined. The second one just updates some comments on the code to make them consistent with the changes. [Original Description] This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed. It looks like the kernel module can be installed, but four tests have failed: == lttng smoke test of session create/destroy == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) == lttng smoke test trace open/close system calls == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-14716-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 4 passed, 4 failed http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure- azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke- test.DEBUG.html Error message from /var/log/syslog: kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0) lttng-sessiond[1097]: Error: Unable to load required module lttng-ring-buffer-client-discard lttng-sessiond[1097]: Warning: No kernel tracer available kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0) kernel: [ 639.680886] lttng_tracer: Unknown symb
[Group.of.nepali.translators] [Bug 1777682] Re: lttng-modules 2.8.0-1ubuntu1~16.04.5 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.7 --- lttng-modules (2.8.0-1ubuntu1~16.04.7) xenial; urgency=medium * ubuntu_lttng_smoke_test failed on Azure 4.15 (LP: #1778642) - debian/patches/0041-Fix-do-not-use-CONFIG_HOTPLUG_CPU-for-the-new-hotplu.patch - debian/patches/0042-Cleanup-comment-about-CONFIG_HOTPLUG_CPU-ifdef.patch -- Kleber Sacilotto de Souza Thu, 19 Jul 2018 17:47:16 +0200 ** Changed in: lttng-modules (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/1777682 Title: lttng-modules 2.8.0-1ubuntu1~16.04.5 ADT test failure with linux-hwe- edge 4.15.0-23.25~16.04.1 Status in lttng-modules package in Ubuntu: In Progress Status in lttng-modules source package in Xenial: Fix Released Bug description: SRU Request: [Impact] Currently the DKMS package fails to install on supported custom kernels that are based on 4.15. That includes the current 4.15 hwe-edge and some of the custom and cloud kernels as well. [Test Case] Install the broadcom-sta package with the 4.15 hwe-edge kernel. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that, the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.13 - linux-hwe-edge 4.15 - linux-azure 4.15 [Original Description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lttng-modules/20180528_193635_39048@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lttng-modules/20180528_195032_39048@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/lttng-modules/20180528_194139_39048@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lttng-modules/20180528_194024_39048@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lttng-modules/20180528_194343_39048@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lttng-modules/20180528_193734_39048@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1777682/+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 1782557] Re: linux-gcp: add a signed kernel
** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Xenial) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-gcp (Ubuntu Bionic) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1782557 Title: linux-gcp: add a signed kernel Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Xenial: In Progress Status in linux-gcp source package in Bionic: In Progress Bug description: We need the kernel binaries to be signed. Switch this on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1782557/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Changed in: ubuntu-power-systems 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not exist,
[Group.of.nepali.translators] [Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Cosmic) Importance: Medium Assignee: Dariusz Gadomski (dgadomski) Status: In Progress ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts Status in gdm3 package in Ubuntu: In Progress Status in gdm3 source package in Xenial: New Status in gdm3 source package in Bionic: New Status in gdm3 source package in Cosmic: In Progress Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/399 [Impact] GDM blocks SIGUSR1 for it's processes, since this is used in communication with X. This signal is later unblocked, however it happens after PAM interaction, so if PAM depends on this signal in any way it will get blocked. The issue has been fixed upstream. [Test Case] 1. Prepare a setup described in Other Info using the attached scripts. 2. Log in. 3. Check logs /tmp/auth.log. Expected result: SIGUSR1 has been received. Actual result: SIGUSR1 never reaches the process. [Regression Potential] If there were components depending on SIGUSR1 their behavior may change - features that were inactive before may be triggered. [Other Info] Original bug description: In case of the following scenario: 1. PAM configured to run auth and session with pam_exec scripts synchronizing via SIGUSR1 2. Using GDM as the login manager causes SIGUSR1 never reaches the target scripts. Workaround: a) Use SIGUSR2 in the scripts. b) Comment out block_sigusr1() call in daemon/main.c. To reproduce add the following entries: /etc/pam.d/common-auth: auth optionalpam_exec.so log=/tmp/auth.log expose_authtok quiet /usr/local/bin/auth.py /etc/pam.d/common-session: session optional pam_exec.so log=/tmp/session.log /usr/local/bin/session.py Attaching example scripts. When using SIGUSR1 - sigusr1_handler is never called, with SIGUSR2 it is called without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+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 1784401] [NEW] [SRU] ceph 10.2.11
Public bug reported: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: * ceph 10.2.11 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. ** Affects: cloud-archive Importance: Undecided Status: Invalid ** Affects: cloud-archive/mitaka Importance: Medium Status: Triaged ** Affects: ceph (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ceph (Ubuntu Xenial) Importance: Medium Status: Triaged ** Also affects: ceph (Ubuntu) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu) Status: New => Invalid ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Changed in: cloud-archive Status: New => Invalid ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: ceph (Ubuntu Xenial) Status: New => Triaged ** Changed in: ceph (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-archive/mitaka Importance: Undecided => Medium ** Description changed: - TBC + [Impact] + This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. + + The update contains the following package updates: + +* ceph 10.2.11 + + [Test Case] + The following SRU process was followed: + + https://wiki.ubuntu.com/OpenStackUpdates + + In order to avoid regression of existing consumers, the OpenStack team + will run their continuous integration test against the packages that are + in -proposed. A successful run of all available tests will be required + before the proposed packages can be let into -updates. + + The OpenStack team will be in charge of attaching the output summary of + the executed tests. The OpenStack team members will not mark + ‘verification-done’ until this has happened. + + [Regression Potential] + In order to mitigate the regression potential, the results of the + aforementioned tests are attached to this bug. -- 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/1784401 Title: [SRU] ceph 10.2.11 Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Triaged Status in ceph package in Ubuntu: Invalid Status in ceph source package in Xenial: Triaged Bug description: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements. The update contains the following package updates: * ceph 10.2.11 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1784401/+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 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
** Also affects: glib2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Xenial: In Progress Bug description: Package failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jul 27 18:31:08 2018 DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu3 Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): triggers ci file contains unknown directive `interest-await' ErrorMessage: triggers ci file contains unknown directive `interest-await' InstallationDate: Installed on 2015-03-31 (1213 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+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 1778738] Re: Default to early instead of auto when MODULES=most
This bug was fixed in the package intel-microcode - 3.20180425.1~ubuntu0.18.04.2 --- intel-microcode (3.20180425.1~ubuntu0.18.04.2) bionic; urgency=medium * Default to early instead of auto, and install all of the microcode, not just the one matching the current CPU, if MODULES=most is set in the initramfs-tools config (LP: #1778738) -- Julian Andres Klode Tue, 26 Jun 2018 16:31:30 +0200 ** Changed in: intel-microcode (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: amd64-microcode (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/1778738 Title: Default to early instead of auto when MODULES=most Status in amd64-microcode package in Ubuntu: Fix Released Status in intel-microcode package in Ubuntu: Fix Released Status in amd64-microcode source package in Trusty: Triaged Status in intel-microcode source package in Trusty: Fix Committed Status in amd64-microcode source package in Xenial: Fix Released Status in intel-microcode source package in Xenial: Fix Released Status in amd64-microcode source package in Artful: Won't Fix Status in intel-microcode source package in Artful: Won't Fix Status in amd64-microcode source package in Bionic: Fix Released Status in intel-microcode source package in Bionic: Fix Released Bug description: [Impact] Initramfs for MODULES=most should build with all microcodes installed [Test case] Have both amd64-microcode and intel-microcode installed, and MODULES=most set. Test generated initramfs in both amd64 and intel machines and make sure the microcodes load. If that's not feasible, we should at least run update-initramfs with -v and ensure that it says the right things: I: amd64-microcode: installing AMD64 microcode into the early initramfs... intel-microcode: adding microcode for either all or selected Intel processor models [long list of microcodes] [Regression potential] Some tools will fail to understand the initramfs, as it now has two cpio archives prepended (e.g. lsinitramfs skips intel microcode archive, as seen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886424) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1778738/+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 1780996] Re: Convert triggers to noawait
This bug was fixed in the package fusiondirectory - 1.0.19-1ubuntu0.18.04.1 --- fusiondirectory (1.0.19-1ubuntu0.18.04.1) bionic; urgency=medium * debian/fusiondirectory.triggers: Be specific about using interest-noawait for the triggers -- there's no need to block in awaiting the triggers for locale, plugins updates. (LP: #1780996) -- Mathieu Trudel-Lapierre Thu, 12 Jul 2018 16:55:25 -0400 ** Changed in: fusiondirectory (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: guile-2.2 (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/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in doche
[Group.of.nepali.translators] [Bug 1744062] Re: [SRU] L3 HA: multiple agents are active at the same time
This bug was fixed in the package keepalived - 1:1.3.9-1ubuntu0.18.04.1 --- keepalived (1:1.3.9-1ubuntu0.18.04.1) bionic; urgency=medium * d/p/fix-removing-left-over-addresses-if-keepalived-abort.patch: Cherry-picked from upstream to ensure left-over VIPs and eVIPs are properly removed on restart if keepalived terminates abonormally. This fix is from the upstream 1.4.0 release (LP: #1744062). -- Corey Bryant Tue, 03 Jul 2018 10:40:59 -0400 ** Changed in: keepalived (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/1744062 Title: [SRU] L3 HA: multiple agents are active at the same time Status in Ubuntu Cloud Archive: Triaged Status in Ubuntu Cloud Archive mitaka series: Triaged Status in Ubuntu Cloud Archive queens series: Fix Committed Status in neutron: New Status in keepalived package in Ubuntu: Fix Released Status in neutron package in Ubuntu: Invalid Status in keepalived source package in Xenial: Triaged Status in neutron source package in Xenial: Invalid Status in keepalived source package in Bionic: Fix Released Status in neutron source package in Bionic: Invalid Bug description: [Impact] This is the same issue reported in https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked as 'Fix Released' and the issue is still occurring and I can't change back to 'New' so it seems best to just open a new bug. It seems as if this bug surfaces due to load issues. While the fix provided by Venkata in https://bugs.launchpad.net/neutron/+bug/1731595 (https://review.openstack.org/#/c/522641/) should help clean things up at the time of l3 agent restart, issues seem to come back later down the line in some circumstances. xavpaice mentioned he saw multiple routers active at the same time when they had 464 routers configured on 3 neutron gateway hosts using L3HA, and each router was scheduled to all 3 hosts. However, jhebden mentions that things seem stable at the 400 L3HA router mark, and it's worth noting this is the same deployment that xavpaice was referring to. keepalived has a patch upstream in 1.4.0 that provides a fix for removing left-over addresses if keepalived aborts. That patch will be cherry-picked to Ubuntu keepalived packages. [Test Case] The following SRU process will be followed: https://wiki.ubuntu.com/OpenStackUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] The regression potential is lowered as the fix is cherry-picked without change from upstream. In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1744062/+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 1729754] Re: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad
This bug was fixed in the package python-wadllib - 1.3.2-3ubuntu0.18.04.1 --- python-wadllib (1.3.2-3ubuntu0.18.04.1) bionic; urgency=medium * Fix MIME encoding of binary parts (LP: #1729754). -- Colin Watson Fri, 20 Jul 2018 18:09:05 +0100 ** Changed in: python-wadllib (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/1729754 Title: Python3 version of launchpadlib doesn't properly upload binary attachments to Launchpad Status in wadllib: Fix Released Status in python-wadllib package in Ubuntu: Fix Released Status in python-wadllib source package in Xenial: Fix Released Status in python-wadllib source package in Bionic: Fix Released Bug description: Tested on 16.04 and 17.10 python-launchpadlib (1.10.5-1 on 17.10) python3-launchpadlib (1.10.5-1 on 17.10) While working on porting a utility using launchpadlib from Python2 to Python3, I noticed the binary attachments were becoming unreadable. I've tried uploading .jpg files, .tgz files, .tar.xz files, they all fail to open properly. P.S.: When a fix is available, can it be ported to Xenial? We need this for our tools running on devices using Xenial. [Test Case] I wrote a little proof of concept that uploads a given binary attachment to a launchpad issue (see attachment). To use it on staging launchpad: APPORT_STAGING=1 ./poc.py When using the exact same script with python2 (basically, replacing `python3` with `python` in the shebang line), the binary file is properly attached. That's why I think it's a bug with python3-launchpadlib. [Regression Potential] The only sensible way to fix this bug was to rewrite how wadllib does MIME-encoding of its form uploads, so it'll be important to test both text and binary uploads. Launchpad only defines a few methods that use multipart/form-data, so the regression potential is confined to those: bug.addAttachment, distro_arch_series.setChroot, and project_release.add_file. To manage notifications about this bug go to: https://bugs.launchpad.net/wadllib/+bug/1729754/+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 1760796] Re: kernel 4.15 breaks xl2tpd
This bug was fixed in the package xl2tpd - 1.3.10-1ubuntu1 --- xl2tpd (1.3.10-1ubuntu1) bionic; urgency=medium * Fix ENODEV errors with linux kernel 4.15 (LP: #1760796) - d/p/fix-for-enodev.patch: cherry-pick patch from upstream to no longer attempt to obtain IP_PKTINFO by default. -- Billy Olsen Thu, 12 Jul 2018 12:07:29 -0700 ** Changed in: xl2tpd (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/1760796 Title: kernel 4.15 breaks xl2tpd Status in xl2tpd package in Ubuntu: Fix Released Status in xl2tpd source package in Xenial: Fix Released Status in xl2tpd source package in Artful: Won't Fix Status in xl2tpd source package in Bionic: Fix Released Status in xl2tpd package in Debian: Fix Released Status in xl2tpd package in Fedora: Fix Released Bug description: [Impact] Kernel 4.15 breaks xl2tpd, please see following upstream issue for more details : https://github.com/xelerance/xl2tpd/issues/147 The following commit/patch fixes the issue: https://github.com/xelerance/xl2tpd/commit/9c2cd4933478a83075df5b10f24af7589e90abc3.patch As Ubuntu 18.04 (Bionic Beaver) is no longer accepting Debian packages, I'm guessing then that the patch would need to be added and applied to the existing xl2tpd-1.3.10-1 package. The linux-image kernel package on Ubuntu 18.04 is currently linux- image-4.15.0-13 [Test Case] * apt install network-manager-l2tp-gnome * Add new VPN connection via network manager * establish vpn connection [Regression Potential] * For Bionic, there is none. The xl2tpd daemon does not work without the patch on the standard bionic kernel. * For Xenial w/ the 4.15 HWE kernel there is no risk. * For Xenial w/ the stock 4.4 kernel there is minimal risk as the code is pulling values that are not valid on the 4.4 kernel by default. Note that a test pkg (Pre-SRU) has been tested for both Bionic and Xenial by a user affected by this problem and the package has been proven to work as expected on the different supported Ubuntu kernel series (v4.4, v4.13, v4.15). For more details, please have a look at comment #17 and #23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1760796/+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 1780996] Re: Convert triggers to noawait
This bug was fixed in the package wokkel - 0.7.1-1ubuntu0.18.04.1 --- wokkel (0.7.1-1ubuntu0.18.04.1) bionic; urgency=medium * Convert trigger to noawait (LP: #1780996) -- Brian Murray Wed, 11 Jul 2018 13:59:50 -0700 ** Changed in: wokkel (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nevow (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/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: Fix Released Status in gdk-pixbuf source
[Group.of.nepali.translators] [Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package nevow - 0.14.2-1ubuntu2 --- nevow (0.14.2-1ubuntu2) bionic; urgency=medium * use pybuild --print build_dir instead of hadrcoding pybuild's internal paths, fixes FTBFS. nevow (0.14.2-1ubuntu1) bionic; urgency=medium * Convert trigger to noawait (LP: #1780996) -- Brian Murray Tue, 17 Jul 2018 09:15:21 -0700 ** Changed in: guile-2.0 (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/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: Fix Released Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: Won't Fix Status in guile-2.0 package in Ubuntu: Fix Released Status in guile-2.2 package in Ubuntu: Fix Released Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: Triaged Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: Fix Released Status in neurodebian package in Ubuntu: Fix Released Status in nevow package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: Won't Fix Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: Fix Released Status in bumblebee source package in Xenial: Fix Released Status in clutter-imcontext source package in Xenial: Won't Fix Status in django-countries source package in Xenial: Fix Released Status in dochelp source package in Xenial: Fix Released Status in dovecot source package in Xenial: Fix Released Status in fusiondirectory source package in Xenial: Fix Released Status in gdk-pixbuf source package in Xenial: Fix Released Status in glib2.0 source package in Xenial: Fix Released Status in gosa source package in Xenial: Won't Fix Status in guile-2.0 source package in Xenial: Fix Released Status in hicolor-icon-theme source package in Xenial: Fix Released Status in libomxil-bellagio source package in Xenial: Triaged Status in libreoffice source package in Xenial: Triaged Status in ltsp source package in Xenial: Fix Released Status in mate-icon-theme source package in Xenial: Fix Released Status in maxima source package in Xenial: Fix Committed Status in neurodebian source package in Xenial: Fix Released Status in nevow source package in Xenial: Fix Released Status in octave source package in Xenial: Fix Released Status in packagekit source package in Xenial: Fix Released Status in pike7.8 source package in Xenial: Fix Released Status in pike8.0 source package in Xenial: Fix Released Status in postgresql-common source package in Xenial: Fix Released Status in qgis source package in Xenial: Fix Released Status in reconf-inetd source package in Xenial: Won't Fix Status in shared-mime-info source package in Xenial: Fix Released Status in sphinx source package in Xenial: Fix Released Status in syslog-ng-incubator source package in Xenial: Fix Released Status in tex-common source package in Xenial: Fix Released Status in wokkel source package in Xenial: Fix Released Status in xpdf source package in Xenial: Fix Released Status in yorick source package in Xenial: Fix Released Status in appstream source package in Bionic: Fix Released Status in bumblebee source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in django-countries source package in Bionic: Fix Released Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in
[Group.of.nepali.translators] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** No longer affects: ubuntu-z-systems -- 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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Committed Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
This bug was fixed in the package systemd - 229-4ubuntu21.4 --- systemd (229-4ubuntu21.4) xenial; urgency=medium * debian/extra/start-udev: test that sync parameters file is writable, before writing to it. On old kernels (e.g. v4.4) the file is available but is read-only, thus writing to it causes init to fail and thus raise a kernel panic. As an extra caution ignore failures to write into that file anyway, since synchronous scsi probing is not critical enough to prevent starting d-i. LP: #1784454 -- Dimitri John Ledkov Mon, 30 Jul 2018 19:58:15 +0100 ** Changed in: systemd (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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
This bug was fixed in the package debian-installer - 20101020ubuntu451.26 --- debian-installer (20101020ubuntu451.26) xenial; urgency=medium * Rebuild against new systemd for the 4.4 kernel regression fix (LP: #1784454) -- Łukasz 'sil2100' Zemczak Mon, 30 Jul 2018 22:26:39 +0200 ** Changed in: debian-installer (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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+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 1784382] Re: Xenial update to 4.4.139 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu) 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/1784382 Title: Xenial update to 4.4.139 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.139 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.139 stable release shall be applied: * xfrm6: avoid potential infinite loop in _decode_session6() * netfilter: ebtables: handle string from userspace with care * ipvs: fix buffer overflow with sync daemon and service * atm: zatm: fix memcmp casting * net: qmi_wwan: Add Netgear Aircard 779S * net/sonic: Use dma_mapping_error() * Revert "Btrfs: fix scrub to repair raid6 corruption" * tcp: do not overshoot window_clamp in tcp_rcv_space_adjust() * Btrfs: make raid6 rebuild retry more * usb: musb: fix remote wakeup racing with suspend * bonding: re-evaluate force_primary when the primary slave name changes * tcp: verify the checksum of the first data segment in a new connection * ext4: update mtime in ext4_punch_hole even if no blocks are released * ext4: fix fencepost error in check for inode count overflow during resize * driver core: Don't ignore class_dir_create_and_add() failure. * btrfs: scrub: Don't use inode pages for device replace * ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream() * ALSA: hda: add dock and led support for HP EliteBook 830 G5 * ALSA: hda: add dock and led support for HP ProBook 640 G4 * cpufreq: Fix new policy initialization during limits updates via sysfs * libata: zpodd: make arrays cdb static, reduces object code size * libata: zpodd: small read overflow in eject_tray() * libata: Drop SanDisk SD7UB3Q*G1001 NOLPM quirk * w1: mxc_w1: Enable clock before calling clk_get_rate() on it * fs/binfmt_misc.c: do not allow offset overflow * x86/spectre_v1: Disable compiler optimizations over array_index_mask_nospec() * m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap() * serial: sh-sci: Use spin_{try}lock_irqsave instead of open coding version * signal/xtensa: Consistenly use SIGBUS in do_unaligned_user * usb: do not reset if a low-speed or full-speed device timed out * 1wire: family module autoload fails because of upper/lower case mismatch. * ASoC: dapm: delete dapm_kcontrol_data paths list before freeing it * ASoC: cirrus: i2s: Fix LRCLK configuration * ASoC: cirrus: i2s: Fix {TX|RX}LinCtrlData setup * lib/vsprintf: Remove atomic-unsafe support for %pCr * mips: ftrace: fix static function graph tracing * branch-check: fix long->int truncation when profiling branches * ipmi:bt: Set the timeout before doing a capabilities check * Bluetooth: hci_qca: Avoid missing rampatch failure with userspace fw loader * fuse: atomic_o_trunc should truncate pagecache * fuse: don't keep dead fuse_conn at fuse_fill_super(). * fuse: fix control dir setup and teardown * powerpc/mm/hash: Add missing isync prior to kernel stack SLB switch * powerpc/ptrace: Fix setting 512B aligned breakpoints with PTRACE_SET_DEBUGREG * powerpc/ptrace: Fix enforcement of DAWR constraints * cpuidle: powernv: Fix promotion from snooze if next state disabled * powerpc/fadump: Unregister fadump on kexec down path. * ARM: 8764/1: kgdb: fix NUMREGBYTES so that gdb_regs[] is the correct size * of: unittest: for strings, account for trailing \0 in property length field * IB/qib: Fix DMA api warning with debug kernel * RDMA/mlx4: Discard unknown SQP work requests * mtd: cfi_cmdset_0002: Change write buffer to check correct value * mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock() * mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips * mtd: cfi_cmdset_0002: Fix unlocking requests crossing a chip boudary * mtd: cfi_cmdset_0002: Avoid walking all chips when unlocking. * MIPS: BCM47XX: Enable 74K Core ExternalSync for PCIe erratu
[Group.of.nepali.translators] [Bug 1784409] Re: Xenial update to 4.4.140 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: linux (Ubuntu) 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/1784409 Title: Xenial update to 4.4.140 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.140 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.140 stable release shall be applied: * usb: cdc_acm: Add quirk for Uniden UBC125 scanner * USB: serial: cp210x: add CESINEL device ids * USB: serial: cp210x: add Silicon Labs IDs for Windows Update * n_tty: Fix stall at n_tty_receive_char_special(). * staging: android: ion: Return an ERR_PTR in ion_map_kernel * n_tty: Access echo_* variables carefully. * x86/boot: Fix early command-line parsing when matching at end * ath10k: fix rfc1042 header retrieval in QCA4019 with eth decap mode * i2c: rcar: fix resume by always initializing registers before transfer * ipv4: Fix error return value in fib_convert_metrics() * kprobes/x86: Do not modify singlestep buffer while resuming * nvme-pci: initialize queue memory before interrupts * netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain() * ARM: dts: imx6q: Use correct SDMA script for SPI5 core * ubi: fastmap: Correctly handle interrupted erasures in EBA * mm: hugetlb: yield when prepping struct pages * tracing: Fix missing return symbol in function_graph output * scsi: sg: mitigate read/write abuse * s390: Correct register corruption in critical section cleanup * drbd: fix access after free * cifs: Fix infinite loop when using hard mount option * jbd2: don't mark block as modified if the handle is out of credits * ext4: make sure bitmaps and the inode table don't overlap with bg descriptors * ext4: always check block group bounds in ext4_init_block_bitmap() * ext4: only look at the bg_flags field if it is valid * ext4: verify the depth of extent tree in ext4_find_extent() * ext4: include the illegal physical block in the bad map ext4_error msg * ext4: clear i_data in ext4_inode_info when removing inline data * ext4: add more inode number paranoia checks * ext4: add more mount time checks of the superblock * ext4: check superblock mapped prior to committing * HID: i2c-hid: Fix "incomplete report" noise * HID: hiddev: fix potential Spectre v1 * HID: debug: check length before copy_to_user() * x86/mce: Detect local MCEs properly * x86/mce: Fix incorrect "Machine check from unknown source" message * media: cx25840: Use subdev host data for PLL override * mm, page_alloc: do not break __GFP_THISNODE by zonelist reset * dm bufio: avoid sleeping while holding the dm_bufio lock * dm bufio: drop the lock when doing GFP_NOIO allocation * mtd: rawnand: mxc: set spare area size register explicitly * dm bufio: don't take the lock in dm_bufio_shrink_count * mtd: cfi_cmdset_0002: Change definition naming to retry write operation * mtd: cfi_cmdset_0002: Change erase functions to retry for error * mtd: cfi_cmdset_0002: Change erase functions to check chip good only * netfilter: nf_log: don't hold nf_log_mutex during user access * staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write() * Linux 4.4.140 Note: The following patch needed some context adjustment to be applied: * nvme-pci: initialize queue memory before interrupts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784409/+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