This should be solved by later kernel release. Does this issue still
occur?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809316
Title:
HDMI Audio failing after resuming from sleep
Failed on B-AWS-5.3 bare-metal instance i3.metal
PASS: x2apic - writing 0x78 to 0x080: x2APIC write; got 0x78, want 0x78
Unhandled exception 13 #GP at ip 004071a3
error_code= rflags=00010006 cs=0008
rax=0078 rcx=0809 rdx=
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850486
Title:
eoan/linux: 5.3.0-21.22
Thanks for the testing. There are two new commits that should fix this issue:
commit 09f3dbe474735df13dd8a66d3d1231048d9b373f
Author: Hans de Goede
Date: Mon Oct 7 20:56:26 2019 +0200
HID: i2c-hid: add Trekstor Primebook C11B to descriptor override
The Primebook C11B uses the
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850986
Title:
many problems:
Status in apport package in
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc6/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849276
Title:
alfa-AWUS036ACH wifi usb
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851347
Title:
libmbim-proxy using 100% CPU on a Dell
4.15.0-1062.71 - oem
Regression test CMPL, RTB.
57 / 60 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4,
ubuntu_xfstests_xfs
Issue to note in amd64:
ubuntu_bpf - test_maps failed (bug 1837386)
ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Do we have actually somebody assigned to this report? I've been playing with
the module parameters but nothing seem to be helping.
I added the debug parameter today, because none of the i915.enable_hangcheck=1
i915.error_capture=1 i915.verbose_state_checks=1 were helpful.
Should I fill a bug
Well, apparently Nvidia driver doesn't do that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1840592
Title:
systemd-backlight does not save and restore brightness for nvidia
Sorry, it should be `sudo dkms install -m bcmwl -v 6.30.223.271+bdcom -k
5.3.0-19-generic`.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851014
Title:
WiFi (inbuilt) and Bluetooth
The backlight device only gets registered after it's opened by graphical
session.
And the backlight gets unregistered when graphical session stops, hence
when systemd-backight@.service's "Conflicts=shutdown.target" triggers,
the backlight is already gone so the brightness wasn't saved.
Since
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.15.0-1067.74/snapdragon-4.15-proposed-
published.html
** Tags added: certification-testing-passed
**
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1125.134/raspi2-4.4-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.15.0-1050.54/raspi2-4.15-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1129.137/snapdragon-4.4-proposed-published.html
** Tags added: certification-testing-passed
** Changed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
I've filed a follow-up bug of neutron-openvswitch on kernel upgrade:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1851764
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: thermald (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1763144
Title:
Significantly lower power and thermal
The described behavior with CPU thermal throtteling was confirmed by
Lenovo. The limits are higher as in Windows "DPTF" works by driver
support and enables the "desk mode". In Linux the "desk mode" is never
reached due to the lack of sensor information and the system operates in
the "lap mode"
This patch is not needed for Focal as it got the existed patch from
upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Thanks to the sponsor,
the patched dkms for eoan is on the queue:
https://launchpad.net/ubuntu/eoan/+queue?queue_state=1
version : 2.7.1-4ubuntu2.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Changed in: linux-firmware (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1850738
Title:
Intel Bluetooth AX201
This has been reverted in bug 1850739 in Ubuntu-1.173.12.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1847250
Title:
update firmware for sound sof driver to fix the hang
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303665/+files/UdevDb.txt
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303666/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303662/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303664/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303663/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303661/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303660/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303655/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851749
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303654/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303659/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303657/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303658/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851749
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1851749/+attachment/5303656/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above
threshold, cpu clock throttled (total events = 50300)
I think we need to drop this from proposed and move forward! it blocks
some other firmware update like LP: #1850738 which we have schedule to
catch.
** Tags added: oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status:
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
** Tags
On Thu, 7 Nov 2019 at 20:05, Scott Moser wrote:
>
> > > So that means we have this sequence of events:
> > > a.) growpart change partition table
> > > b.) growpart call partx
> > > c.) udev created and events being processed
>
> > That is not true. whilst sfdisk is deleting, creating,
On Thu, 7 Nov 2019 at 17:50, Ryan Harper <1834...@bugs.launchpad.net> wrote:
>
> @ddstreet
>
> Yes, settle does not help.
>
> Re-triggering udevadm trigger --action=add /sys/class/block/sda
>
> Would re-run all of them after the partition change has occurred, which
> is what I'm currently
Hi Frank,
Just giving you an update on the status of these bugs. The kernel team
has reviewed the patches I submitted, and each set of patches have
received two acks each, meaning they will be built into the next kernel
update.
Bug 1842037:
@jjohansen, I see that you've included the fix in most of the kernels
currently in -proposed, thanks for that! Although, I'm not seeing those
for 4.4 and 4.15 and I'd like to make sure they don't fall through the
cracks ;)
--
You received this bug notification because you are a member of Kernel
> We can't know how many devices are in the system. It maybe nearly zero,
> it could be minutes.
I'm not suggesting you trigger uevents for all devices, just the one
you're repartitioning...
> The cold plug is required (initramfs may or maynot
> have ran
> scripts/udevd etc but kernel events
Peter, Pedro, thanks for the extra detail. After reading
https://github.com/kubernetes/kubernetes/issues/58927, I agree that we
won't be able to fix this in Charmed Kubernetes directly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
On Thu, Nov 7, 2019 at 2:41 PM Dan Streetman
wrote:
> > Issuing a second
> > trigger will repeat this.
> > IMO, that's a non-zero amount of time that slows the boot down, so I'd
> like
> > to avoid that.
>
> systemd-udev-trigger.serivce retriggers *everything* at boot (except in
>
an
> Issuing a second
> trigger will repeat this.
> IMO, that's a non-zero amount of time that slows the boot down, so I'd like
> to avoid that.
systemd-udev-trigger.serivce retriggers *everything* at boot (except in
an unprivileged container where it can't), so I'm not sure how much
added time
On Thu, Nov 7, 2019 at 11:30 AM Dimitri John Ledkov
wrote:
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
>
> That is not true. whilst sfdisk is deleting, creating,
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Hi Tim, I don't think patching kubernetes-master will resolve this
issue. Mainly because the issue happens on kubernetes-workers.
We were seeing PVCs failing with: "No VM found". When we look into the
logs, actually kubernetes was trying to learn about its kubernetes-
workers through SystemUUID.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
That's not enough information. At this point you should report a new
bug, please.
Notice the linked bug #1760450 includes a crash trace. (Not saying for
sure you'd be able to do the same). The fatal signal is SIGBUS, as
opposed to the usual SIGSEGV or abort. If you've got a SIGSEGV or an
What we're seeing is a failed provisioning error when adding volumes, we
hit this closed issue:
https://github.com/kubernetes/kubernetes/issues/58927 Kubernetes
behaviour changed to fix this issue by switching to the */product_serial
file as the source of truth.
But for our case the
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing
> partition table (a) and partx is called (b), udev events
Thanks Mr. Kernel Bot but I really do not think that this bug misses
logs :)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Thu, Nov 7, 2019 at 1:30 PM Dan Streetman
wrote:
> > Yes, settle does not help.
>
> Well, I didn't suggest just to settle ;-)
>
Sorry; long bug thread.
> > I'm currently suggesting as a heavy-handed workaround.
>
> I don't really see why you think this is heavy-handed, but I must be
>
Attaching all-in-one test case for testing patched kernels.
** Attachment added: "lp1850994.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850994/+attachment/5303560/+files/lp1850994.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1851709
and then change the status of the bug to 'Confirmed'.
If, due to the
> Yes, settle does not help.
Well, I didn't suggest just to settle ;-)
> I'm currently suggesting as a heavy-handed workaround.
I don't really see why you think this is heavy-handed, but I must be
missing something.
> I would like to understand *why* the udevd/kernel pair exhibits this racy
>
Public bug reported:
Mostly the same info as on a related kernel.org bugzilla entr[0].
[0]: https://bugzilla.kernel.org/show_bug.cgi?id=205441
We got issues reported with old Intel CPUs and Linux guest run with
QEMU/KVM after a recent kernel update which is based on
Ubuntu-5.0.0-33.35.
I
We could potentially patch Charmed Kubernetes against this by not
reading /sys/class/dmi/id/product_uuid (https://github.com/charmed-
kubernetes/charm-kubernetes-
master/blob/master/reactive/kubernetes_master.py#L2244), but instead
using the workaround published by vmware at
Hi Peter, can you elaborate on this part please: "manifests itself by
breaking provisioning in Kubernetes."
Can you describe the behavior you're seeing?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
Just a clarification, the description says "hpre patchset have merged
into mainline 5.4rc3 kernel", however it has not:
$ git log --pretty=oneline --abbrev-commit v5.3..v5.4-rc6 --grep
"crypto: hisilicon - add HiSilicon HPRE accelerator"
But it is in linux-next:
$ git log --pretty=oneline
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848534
** Description changed:
Hi,
- On VMWare when decoding /sys/class/dmi/id/product_serial dmidecode
- produces an output whereby the first 16 characters have been reversed in
- comparison to /sys/class/dmi/id/product_uuid.
+ On VMWare 6.5 and higher (HW version 13 and higher) when decoding
+
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-disco
** Branch linked: lp:~gpiccoli/britney/hints-ubuntu-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1851663
Title:
** Also affects: atlas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837525
Title:
[20.04 FEAT] Set Architecture Level (ALS) to
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
@ddstreet
Yes, settle does not help.
Re-triggering udevadm trigger --action=add /sys/class/block/sda
Would re-run all of them after the partition change has occurred, which
is what I'm currently suggesting as a heavy-handed workaround.
I would like to understand *why* the udevd/kernel pair
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851677
Title:
s_iflags overlap prevents unprivileged overlayfs
Just curious, did anyone actually test with my suggestion from comment
40? That is, just make your partition table change (and update the
kernel with partx or whatever, of course), and after it's done trigger
--settle udev for the device. Be interesting to know if that actually
fixes it or not.
** Description changed:
+ SRU Justification
+
+ Impact: SB_I_NOSUID was added by a sauce patch, and over time it has
+ come to occpy the same bit in s_iflags as SB_I_USERNS_VISIBLE without
+ being noticed. overlayfs will set SB_I_NOSUID when any lower mount is
+ nosuid. When this happens for a
> So that means we have this sequence of events:
> a.) growpart change partition table
> b.) growpart call partx
> c.) udev created and events being processed
That is not true. whilst sfdisk is deleting, creating, finishing
partition table (a) and partx is called (b), udev events are already
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
All Eoan issues verified
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850486
Title:
@anomaly256: Could you please give a link to the bug report you filled?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1520874
Title:
[MacBook8,1] keyboard does not work
Status in
I really think you are all *way* over thinking this.
a. growpart made a change to the partition table (using sfdisk)
b. growpart called partx --update --nr 3 /dev/sda
c. growpart exited
With a and b growpart created udev events. If you create udev events,
you really need to wait for those
Attaching test script to reproduce the bug, adapted from the reproducer
for bug 1850994. Requires the bindfs package.
** Description changed:
As reported by Jann Horn on bug 1850994, unprivileged overlayfs mounting
- fails in disco/eoan due to SB_I_NOSUID and SB_I_USERNS_VISIBLE.
+ can fail in
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 206 matches
Mail list logo
