Activity log for bug #1745130

Date Who What changed Old value New value Message
2018-01-24 10:31:42 Jan-Marek Glogowski bug added bug
2018-01-24 10:31:42 Jan-Marek Glogowski attachment added Add rfkill-any as led trigger https://bugs.launchpad.net/bugs/1745130/+attachment/5042221/+files/rfkill-any-4.4.patch
2018-01-24 12:28:54 Ubuntu Foundations Team Bug Bot tags apport-bug i386 third-party-packages trusty apport-bug i386 patch third-party-packages trusty
2018-01-24 12:28:55 Ubuntu Foundations Team Bug Bot bug added subscriber Joseph Salisbury
2018-01-24 16:39:44 Joseph Salisbury nominated for series Ubuntu Xenial
2018-01-24 16:39:44 Joseph Salisbury bug task added linux-lts-xenial (Ubuntu Xenial)
2018-01-24 16:40:09 Joseph Salisbury affects linux-lts-xenial (Ubuntu) linux (Ubuntu)
2018-01-24 16:40:20 Joseph Salisbury linux (Ubuntu): status New Triaged
2018-01-24 16:40:23 Joseph Salisbury linux (Ubuntu Xenial): status New Triaged
2018-01-24 16:40:26 Joseph Salisbury linux (Ubuntu): importance Undecided Medium
2018-01-24 16:40:28 Joseph Salisbury linux (Ubuntu Xenial): importance Undecided Medium
2018-01-24 17:54:18 Joseph Salisbury linux (Ubuntu): assignee Joseph Salisbury (jsalisbury)
2018-01-24 17:54:22 Joseph Salisbury linux (Ubuntu Xenial): assignee Joseph Salisbury (jsalisbury)
2018-01-24 17:54:25 Joseph Salisbury linux (Ubuntu Xenial): status Triaged In Progress
2018-01-24 17:54:28 Joseph Salisbury linux (Ubuntu): status Triaged In Progress
2018-02-01 20:26:00 Joseph Salisbury nominated for series Ubuntu Trusty
2018-02-01 20:26:00 Joseph Salisbury bug task added linux (Ubuntu Trusty)
2018-02-01 20:26:12 Joseph Salisbury linux (Ubuntu Trusty): status New In Progress
2018-02-01 20:26:15 Joseph Salisbury linux (Ubuntu Trusty): importance Undecided Medium
2018-02-01 20:26:19 Joseph Salisbury linux (Ubuntu Trusty): assignee Joseph Salisbury (jsalisbury)
2018-02-02 14:23:49 Joseph Salisbury bug task deleted linux (Ubuntu Trusty)
2018-02-02 14:25:33 Joseph Salisbury 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ń <kernel@kempniu.pl> 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) == 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ń <kernel@kempniu.pl> 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ń <kernel@kempniu.pl> 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)
2018-03-12 14:31:59 Stefan Bader linux (Ubuntu Xenial): status In Progress Fix Committed
2018-03-19 10:55:23 Stefan Bader tags apport-bug i386 patch third-party-packages trusty apport-bug i386 patch third-party-packages trusty verification-needed-xenial
2018-03-19 13:22:22 Jan-Marek Glogowski tags apport-bug i386 patch third-party-packages trusty verification-needed-xenial apport-bug i386 patch third-party-packages trusty verification-done-xenial
2018-04-04 09:27:25 Launchpad Janitor linux (Ubuntu Xenial): status Fix Committed Fix Released
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-15129
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-16995
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-17448
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-17450
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-17741
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-17862
2018-04-04 09:27:25 Launchpad Janitor cve linked 2017-5753
2018-04-04 09:27:25 Launchpad Janitor cve linked 2018-1000026
2018-04-04 09:27:25 Launchpad Janitor cve linked 2018-5333
2018-04-04 09:27:25 Launchpad Janitor cve linked 2018-5344
2018-04-04 09:27:25 Launchpad Janitor cve linked 2018-8043
2019-01-23 01:11:30 Joseph Salisbury linux (Ubuntu): status In Progress Fix Released