[Group.of.nepali.translators] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
This bug was fixed in the package klibc - 2.0.4-8ubuntu3 --- klibc (2.0.4-8ubuntu3) yakkety; urgency=medium * debian/patches/broadcast_dhcp_send.patch: the patch sets the wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000. (LP: #1624014) -- Dan Streetman Fri, 16 Sep 2016 20:20:58 -0400 ** Changed in: klibc (Ubuntu Yakkety) 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/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: In Progress Status in klibc source package in Xenial: In Progress Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
** Also affects: klibc (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: klibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: klibc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: klibc (Ubuntu Trusty) Status: New => In Progress ** Changed in: klibc (Ubuntu Yakkety) Status: New => In Progress ** Changed in: klibc (Ubuntu Xenial) Status: New => In Progress ** Changed in: klibc (Ubuntu Yakkety) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Trusty) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Trusty) Importance: Undecided => High ** Changed in: klibc (Ubuntu Xenial) Importance: Undecided => High ** Changed in: klibc (Ubuntu Yakkety) Importance: Undecided => High -- 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/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: In Progress Status in klibc source package in Trusty: In Progress Status in klibc source package in Xenial: In Progress Status in klibc source package in Yakkety: In Progress Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1624569] [NEW] thunder: chip errata w/ multiple CQEs for a TSO packet
Public bug reported: [Impact] With small segment sizes, it is possible for the driver to free an SKB before transmitting it, potentially resulting in a crash. [Test Case] The test case for this is to use a small MTU (200) and mount an NFS exported directory. Create several (~4) 1M files w/ dd, then copy them locally. However, I have not been able to trigger the crash myself. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. ** Affects: linux (Ubuntu) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Summary changed: - thunder: + thunder: chip errata w/ multiple CQEs for a TSO packet ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => dann frazier (dannf) -- 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/1624569 Title: thunder: chip errata w/ multiple CQEs for a TSO packet Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: [Impact] With small segment sizes, it is possible for the driver to free an SKB before transmitting it, potentially resulting in a crash. [Test Case] The test case for this is to use a small MTU (200) and mount an NFS exported directory. Create several (~4) 1M files w/ dd, then copy them locally. However, I have not been able to trigger the crash myself. [Regression Risk] Fix is upstream, so regressions will have upstream support. Fix is limited to a driver that is only applicable to the Cavium Thunder-X SoC, so risk is negligible to other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624569/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
** No longer affects: light-locker (Ubuntu) ** No longer affects: light-locker (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1588479] Re: dkms_packages.py supported kernel check is not working
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu14 --- dkms (2.2.0.3-2ubuntu14) yakkety; urgency=medium * apport_name_in_valueerror.diff: (LP: #1588479) - Check the ValueError from apport for the package name too, this prevents reporting of dkms crashes about unsupported kernels. -- Brian Murray Thu, 15 Sep 2016 13:46:49 -0700 ** Changed in: dkms (Ubuntu Yakkety) 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/1588479 Title: dkms_packages.py supported kernel check is not working Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Trusty: In Progress Status in dkms source package in Xenial: In Progress Status in dkms source package in Yakkety: Fix Released Bug description: Test Case - 1) Look for some dkms package in /usr/src e.g. bbswitch-0.8 2) Run python3 /usr/share/apport/package-hooks/dkms_packages.py -m bbswitch -v 0.8 -k 4.6.1-01234-lowlatency 3) Observe a crash report dialog from apport for bbswitch With the version of apport from -proposed you will instead receive: ERROR (dkms apport): kernel package linux- headers-4.6.1-01234-lowlatency is not supported The apport package hook for dkms packages seems to have an error in its supported kernel check. If the kernel is an unsupported one, the hook should exit with a return code of 1. However, in the Ubuntu Error Tracker we can see some crashes with unsupported kernel versions e.g.: https://errors.ubuntu.com/oops/2733d742-284e-11e6-a745-fa163e839e11 DKMSKernelVersion: 4.6.1-040601-lowlatency https://errors.ubuntu.com/oops/0a1afefc-253c-11e6-9082-fa163e192766 DKMSKernelVersion: 4.6.0-040600-lowlatency If the intent really is to block creation of these reports, then let's do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1588479/+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 1623187] Re: initramfs includes qle driver, but not firmware
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Fix Committed ** Changed in: linux (Ubuntu Yakkety) 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/1623187 Title: initramfs includes qle driver, but not firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: [Impact] The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't find devices. This is because the driver, by default, is loaded by the initramfs, and the initramfs does not contain the required firmware blob. The root cause is that the driver does not use implement the MODULE_FIRMWARE macro(), which is required for initramfs-tools to find and pre-load the required firmware. [Test Case] Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On failure, dmesg will show: [ 5.934190] qede 0009:90:00.0: Direct firmware load for qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2 [ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - /lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin [ 5.934280] qede: probe of 0009:90:00.0 failed with error -2 [ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002) [ 5.935115] qede 0009:90:00.1: Direct firmware load for qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2 [ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - /lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin [ 5.935236] qede: probe of 0009:90:00.1 failed with error -2 [Regression Risk] Fix is upstream and the macro usage is well defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623187/+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 1610756] Re: upgrade to 16.04 failed to calculate due to backuppc
** Also affects: ubuntu-release-upgrader (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ubuntu-release-upgrader (Ubuntu Xenial) Status: New => Triaged -- 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/1610756 Title: upgrade to 16.04 failed to calculate due to backuppc Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in ubuntu-release-upgrader source package in Xenial: Triaged Bug description: Workaround -- Install libcgi-pm-perl before trying to upgrade Original Description Am current with all updates to 14.04 LTS ProblemType: BugDistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CrashDB: ubuntu Date: Sun Aug 7 19:00:42 2016 InstallationDate: Installed on 2015-12-09 (242 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2016-08-07 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1610756/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
** Also affects: bridge-utils (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Confirmed ** Also affects: bridge-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** No longer affects: linux (Ubuntu Yakkety) -- 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/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in bridge-utils source package in Xenial: New Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: New Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_de
[Group.of.nepali.translators] [Bug 1622469] Re: New device ID for Kabypoint
** Changed in: linux (Ubuntu Yakkety) 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/1622469 Title: New device ID for Kabypoint Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: Intel has some new Kaby Lake platforms come with new Kaybpoint PCH, and need to backport the support to Xenial release. Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs following two patches: https://lkml.org/lkml/2016/7/4/403 http://marc.info/?l=linux-i2c&m=146945783426903&w=2 These patches only add some pid specific codes and it won't cause any regression in my opinion, so I think it's ok to backport them in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1622469/+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 1622469] Re: New device ID for Kabypoint
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Assignee: Phidias (phidias-chiang) Status: Incomplete ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Phidias (phidias-chiang) -- 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/1622469 Title: New device ID for Kabypoint Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: Intel has some new Kaby Lake platforms come with new Kaybpoint PCH, and need to backport the support to Xenial release. Besides 704d2b0 and 7a1a47c which are already in Xenial, we still needs following two patches: https://lkml.org/lkml/2016/7/4/403 http://marc.info/?l=linux-i2c&m=146945783426903&w=2 These patches only add some pid specific codes and it won't cause any regression in my opinion, so I think it's ok to backport them in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1622469/+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 1624450] [NEW] linux: 4.4.0-39.58 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-39.58 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 ** Affects: kernel-sru-workflow Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importanc
[Group.of.nepali.translators] [Bug 1622763] Re: Sennheiser Officerunner - cannot get freq at ep 0x83
** No longer affects: linux (Ubuntu Trusty) -- 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/1622763 Title: Sennheiser Officerunner - cannot get freq at ep 0x83 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: This USB headset doesn't seem to support sample rate polling, similar to this issue: https://bugzilla.kernel.org/show_bug.cgi?id=95961 == The problem == Every time something goes to interact with the device (playing a sound file, opening the sound panel, opening web audio/video), a 10 second pause is encountered, where dmesg prints out two messages: usb 2-1.2: 2:1: cannot get freq at ep 0x83 usb 2-1.2: 2:1: cannot get freq at ep 0x83 Once the sound is playing, everything is fine. These sample rate polls don't seem to keep happening. After waiting for maybe 30 seconds after sound is playing, future interactions will again trigger the pause. This 10 second pause can introduce other subtle problems. For instance, google hangouts will sometimes timeout waiting for the sound device to respond, and the browser tab will crash or not fully load as a result. The sound panel often also will not display the device in the list of choices, and you will have to close it out. Sometimes restart pulse audio to get it to recognize the headset again. == The solution == It is simple, add this USB ID to the sound/usb/quirks.c:snd_usb_get_sample_rate_quirk function. case USB_ID(0x1395, 0x740a): /* Sennheiser Officerunner */ version signature: Ubuntu 4.4.0-36.55-generic 4.4.16 # lsusb |grep Senn Bus 002 Device 004: ID 1395:740a Sennheiser Communications # zcat /var/log/kern.log.2.gz | grep 'cannot get' | tail -4 Sep 2 11:26:56 helo kernel: [908040.937098] usb 2-1.2: 2:1: cannot get freq at ep 0x4 Sep 2 11:27:01 helo kernel: [908045.941168] usb 2-1.2: 2:1: cannot get freq at ep 0x4 Sep 2 12:18:44 helo kernel: [911149.006318] usb 2-1.2: 3:1: cannot get freq at ep 0x83 Sep 2 12:18:49 helo kernel: [911154.010268] usb 2-1.2: 3:1: cannot get freq at ep 0x83 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dpb 12893 F pulseaudio /dev/snd/controlC2: dpb 12893 F pulseaudio /dev/snd/controlC1: dpb 12893 F pulseaudio /dev/snd/controlC0: dpb 12893 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a9a39ff3-c97d-471e-a0b3-518b4db8685c InstallationDate: Installed on 2015-03-18 (544 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) MachineType: Hewlett-Packard HP Z620 Workstation NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/vgroot-lvroot ro console=tty0 console=ttyS4,115200 nosplash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-16 (210 days ago) UserGroups: adm cdrom dip docker libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/27/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.88 dmi.board.asset.tag: 2UA41528ZC dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: 2UA41528ZC dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/+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 1621269] Re: not possible to build yakkety packages because of gpg changes
** Also affects: sbuild (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: sbuild (Ubuntu Trusty) Status: New => Triaged ** Changed in: sbuild (Ubuntu Trusty) Importance: Undecided => High -- 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/1621269 Title: not possible to build yakkety packages because of gpg changes Status in sbuild package in Ubuntu: Invalid Status in sbuild source package in Trusty: Triaged Status in sbuild source package in Xenial: Triaged Status in sbuild package in Debian: Fix Released Bug description: I was trying to build update-manager in a yakkety sbuild chroot from a xenial system and encountered the following error: Local sources - update-manager_16.10.5.dsc exists in .; copying to chroot Check architectures --- Check dependencies -- Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<>/resolver-9lYerC/apt_archive/sbuild-build-depends-core-dummy.deb'. gpg: /<>/resolver-9lYerC/gpg/trustdb.gpg: trustdb created gpg: Warning: not using 'Sbuild Signer' as default key: No secret key gpg: all values passed to '--default-key' ignored gpg: no default secret key: No secret key gpg: signing failed: No secret key Failed to sign dummy archive Release file. I worked around the issue by installing the yakkety version of sbuild on my xenial system, but the fix should be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1621269/+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 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1619766 Title: Backport E3 Skylake Support in ie31200_edac to Xenial Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Skylake E3 Support was added to ie31200_edac with the following commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797 Could we get this support backported to Xenial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619766/+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 1623579] Re: [SRU] 2.15
** Also affects: snapd (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/1623579 Title: [SRU] 2.15 Status in snapd package in Ubuntu: New Status in snapd source package in Xenial: New Bug description: This is a new version of snapd. The changelog for 2.15 is available here https://github.com/snapcore/snapd/blob/2.15/debian/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.15 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new 2.15 micro release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. The following automatic tests are run: - travis unit tests https://travis-ci.org/snapcore/snapd/branches (check for 2.15 here) - travis/spread based integration/system tests: https://travis-ci.org/snapcore/snapd/branches (check for 2.15 here under "spread") The following additional tests were performed: """ - adt-buildvm-ubuntu-cloud - customize the resulting image: "sudo apt install snapd && sudo snap install hello-world && hello-world.env && sudo snap remove hello-world" (ensures the base image has the old debs and the daemon has some state) - adt-run --source snapd_2.15.dsc --- adt-virt-qemu adt-xenial-amd64-cloud.img: PASS """ This included the upgrade from 2.0.14.2 as part of the autopkgtest run. There are also various snaps installed/removed (including installing and running ubuntu-calculator-app in xvfb) and run as part of the auto pkg test, including reboots to ensure that the system keeps working over reboots. After installing the new snapd it was ensured that apt is unaffected by doing: """ - sudo apt install -y hello && sudo apt remove -y hello """ After installing the new snapd gnome-software was used: """ - install "http" (snap) and remove it again """ All worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1623579/+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