[Group.of.nepali.translators] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == SRU Justification == This bug was reported against a Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both drivers currently provide a single rfkill trigger, so the led could just be assigned to one. This was resolved by mainline commit 9b8e34e211, which added a "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. Commit 9b8e34e211b1 is in mainline as of 4.11-rc1. == Fix == commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger == Regression Potential == Medium. This commit affects all arches, but it has been in mainline since 4.11-rc1 with no reported issues. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+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 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
This bug was fixed in the package linux - 4.4.0-119.143 --- linux (4.4.0-119.143) xenial; urgency=medium * linux: 4.4.0-119.143 -proposed tracker (LP: #1760327) * Dell XPS 13 9360 bluetooth scan can not detect any device (LP: #1759821) - Revert "Bluetooth: btusb: fix QCA Rome suspend/resume" linux (4.4.0-118.142) xenial; urgency=medium * linux: 4.4.0-118.142 -proposed tracker (LP: #1759607) * Kernel panic with AWS 4.4.0-1053 / 4.4.0-1015 (Trusty) (LP: #1758869) - x86/microcode/AMD: Do not load when running on a hypervisor * CVE-2018-8043 - net: phy: mdio-bcm-unimac: fix potential NULL dereference in unimac_mdio_probe() linux (4.4.0-117.141) xenial; urgency=medium * linux: 4.4.0-117.141 -proposed tracker (LP: #1755208) * Xenial update to 4.4.114 stable release (LP: #1754592) - x86/asm/32: Make sync_core() handle missing CPUID on all 32-bit kernels - usbip: prevent vhci_hcd driver from leaking a socket pointer address - usbip: Fix implicit fallthrough warning - usbip: Fix potential format overflow in userspace tools - x86/microcode/intel: Fix BDW late-loading revision check - x86/retpoline: Fill RSB on context switch for affected CPUs - sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks - can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once - can: af_can: canfd_rcv(): replace WARN_ONCE by pr_warn_once - PM / sleep: declare __tracedata symbols as char[] rather than char - time: Avoid undefined behaviour in ktime_add_safe() - timers: Plug locking race vs. timer migration - Prevent timer value 0 for MWAITX - drivers: base: cacheinfo: fix x86 with CONFIG_OF enabled - drivers: base: cacheinfo: fix boot error message when acpi is enabled - PCI: layerscape: Add "fsl,ls2085a-pcie" compatible ID - PCI: layerscape: Fix MSG TLP drop setting - mmc: sdhci-of-esdhc: add/remove some quirks according to vendor version - fs/select: add vmalloc fallback for select(2) - hwpoison, memcg: forcibly uncharge LRU pages - cma: fix calculation of aligned offset - mm, page_alloc: fix potential false positive in __zone_watermark_ok - ipc: msg, make msgrcv work with LONG_MIN - x86/ioapic: Fix incorrect pointers in ioapic_setup_resources() - ACPI / processor: Avoid reserving IO regions too early - ACPI / scan: Prefer devices without _HID/_CID for _ADR matching - ACPICA: Namespace: fix operand cache leak - netfilter: x_tables: speed up jump target validation - netfilter: arp_tables: fix invoking 32bit "iptable -P INPUT ACCEPT" failed in 64bit kernel - netfilter: nf_dup_ipv6: set again FLOWI_FLAG_KNOWN_NH at flowi6_flags - netfilter: nf_ct_expect: remove the redundant slash when policy name is empty - netfilter: nfnetlink_queue: reject verdict request from different portid - netfilter: restart search if moved to other chain - netfilter: nf_conntrack_sip: extend request line validation - netfilter: use fwmark_reflect in nf_send_reset - ext2: Don't clear SGID when inheriting ACLs - reiserfs: fix race in prealloc discard - reiserfs: don't preallocate blocks for extended attributes - reiserfs: Don't clear SGID when inheriting ACLs - fs/fcntl: f_setown, avoid undefined behaviour - scsi: libiscsi: fix shifting of DID_REQUEUE host byte - Input: trackpoint - force 3 buttons if 0 button is reported - usb: usbip: Fix possible deadlocks reported by lockdep - usbip: fix stub_rx: get_pipe() to validate endpoint number - usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input - usbip: prevent leaking socket pointer address in messages - um: link vmlinux with -no-pie - vsyscall: Fix permissions for emulate mode with KAISER/PTI - eventpoll.h: add missing epoll event masks - x86/microcode/intel: Extend BDW late-loading further with LLC size check - hrtimer: Reset hrtimer cpu base proper on CPU hotplug - dccp: don't restart ccid2_hc_tx_rto_expire() if sk in closed state - ipv6: Fix getsockopt() for sockets with default IPV6_AUTOFLOWLABEL - ipv6: fix udpv6 sendmsg crash caused by too small MTU - ipv6: ip6_make_skb() needs to clear cork.base.dst - lan78xx: Fix failure in USB Full Speed - net: igmp: fix source address check for IGMPv3 reports - tcp: __tcp_hdrlen() helper - net: qdisc_pkt_len_init() should be more robust - pppoe: take ->needed_headroom of lower device into account on xmit - r8169: fix memory corruption on retrieval of hardware statistics. - sctp: do not allow the v4 socket to bind a v4mapped v6 address - sctp: return error if the asoc has been peeled off in sctp_wait_for_sndbuf - vmxnet3: repair memory leak - net: Allow neigh contructor functions ability to modify the primary_key - ipv4: Make neigh lookup keys for loopback/point-to-point devices be INADDR_ANY
[Group.of.nepali.translators] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
SRU Request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-February/089892.html ** No longer affects: linux (Ubuntu Trusty) ** Description changed: + == SRU Justification == + This bug was reported against a Fujitsu u7x7 laptop series based on Skylake hardware. + It has a single rfkill button and a single LED for wlan and bluetooth. Both + drivers currently provide a single rfkill trigger, so the led could + just be assigned to one. This was resolved by mainline commit 9b8e34e211, which added a + "rfkill-any" led trigger to correctly handle the led with multiple + rfkill devices. That was added by one of the fujitsu-laptop maintainers and + the driver sets it as the default trigger. + + Commit 9b8e34e211b1 is in mainline as of 4.11-rc1. + + == Fix == + commit 9b8e34e211b15af429b72388a8f2b3b1823d172e + Author: Michał Kępień + Date: Fri Jan 6 07:07:47 2017 +0100 + + rfkill: Add rfkill-any LED trigger + + == Regression Potential == + Medium. This commit affects all arches, but it has been in mainline since + 4.11-rc1 with no reported issues. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + == Original Bug Description == I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 - rfkill: Add rfkill-any LED trigger + rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: == SRU Justification == This bug was reported against a Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both drivers currently provide a single rfkill trigger, so the led could just be assigned to one. This was resolved by mainline commit 9b8e34e211, which added a "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. Commit 9b8e34e211b1 is in mainline as of 4.11-rc1. == Fix == commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger == Regression Potential == Medium. This commit affects all arches, but it has been in mainline since 4.11-rc1 with no reported issues. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigg
[Group.of.nepali.translators] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) 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/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Bug description: I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+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 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
** Also affects: linux-lts-xenial (Ubuntu Xenial) Importance: Undecided Status: New ** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+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
