Marked invalid as packages for a newer upstream release are already
available.
** Changed in: wireless-regdb (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: wireless-regdb (Ubuntu)
Status: In Progress => Invalid
** Changed in: wireless-regdb (Ubuntu Focal)
Stat
*** This bug is a duplicate of bug 1980145 ***
https://bugs.launchpad.net/bugs/1980145
Fixed by LP: #1980145 which updated to the 2022.06.06 release. Marking
as a duplicate of that bug.
** This bug has been marked a duplicate of bug 1980145
New upstream release 2022.06.06
--
You received
** Changed in: wireless-regdb (Ubuntu Impish)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1980145
Title:
New upstream release 2022.06.
I tested the jammy, focal, and bionic patches as described in the test
case from the description. The kernel was able to load the database, and
I was able to successfully query and change the regulatory domain.
Marking verification as done.
** Tags removed: verification-needed verification-needed-
The autopkgtest failure for linux-oracle is a timeout during the rebuild
test. Clearly this isn't caused by the wireless-regdb update, so the
test should be retried or hinted (I can do neither).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I can see how that's a bit confusing; possibly I should be handling the
backport changelogs differently. But yes, I did not remove the Suggests:
crda in the backports except in jammy where the crda package had also
been removed.
--
You received this bug notification because you are a member of Ke
nable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth For
** Changed in: linux-firmware (Ubuntu)
Assignee: Seth Forshee (sforshee) => (unassigned)
--
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/1928393
Title:
linux-firmware 1.
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.08.28-0ubuntu1~18.04.1
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.08.28-0ubuntu1~20.04.1
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.08.28-0ubuntu1~21.04.1
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
New packages in
https://launchpad.net/~sforshee/+archive/ubuntu/wireless-regdb.
** Changed in: wireless-regdb (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: wireless-regdb (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: wireless-regdb (Ubuntu Bionic
nable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.
** Affects: wireless-regdb (Ubuntu)
Importance: Undecided
Assignee: Seth For
What about the trusty/xenial packages?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1936255
Title:
New upstream release 2021.07.14
Status in wireless-regdb package in Ubuntu:
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~21.04.1
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~20.04.1
$ iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
nable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth For
. A serious
problem in the test case might cause passing test cases to fail or
prevent subsequent test cases from running. Any such issues should be
caught during testing in -proposed before releasing kernels to users.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee
Was linux-firmware the only package upgraded, or were other packages
also upgraded at the same time? Have you confirmed that reverting back
to linux-firmware 1.197 fixes the issue?
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becau
Looks like you are probably out of space in /boot, in which case you
will need to remove some old kernels.
--
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/1931798
Title:
installed initram
ld
be excluded. Some instances of this occurred while developing these
changes and have been fixed. Future updates to upstream or to the
packaging could cause additional issues.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
On Fri, May 14, 2021 at 06:01:50PM -, Thiago Jung Bauermann wrote:
> Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/
> amdgpu/ with the files from the latest commit of the upstream linux-
> firmware git repo you mention below. It's been only a little over 2 hours,
>
us: New => Incomplete
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
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/192839
A synchronous exception is a direct result of the executing software --
illegal memory access, invalid instruction, etc. So this looks different
than the IRQ exception, which are interrupts from devices external to
the CPU. However since this is a VM guest context the exceptions are
presumably all
I couldn't find anywhere in the kernel that might be printing this
message so I went searching, looks like it is probably coming from the
firmware:
https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/PrePeiCore/AArch64/ArchPrePeiCore.c#L29
--
You received this bug notification because y
I honestly don't know much about how these dual-GPU systems work. I
suspect there must be some firmware interfaces for enabling/disabling
the discrete GPU, I have no idea whether those are standardized or
platform-specific. Assuming the kernel supports the interfaces for your
platform, I also don't
The reason you don't see any Intel graphics drivers in the "Addditional
Drivers" tab is that none are needed. The Intel graphics driver (i915)
is open source and already included in the kernel, and from your logs it
has been loaded.
There's nothing I'm seeing currently which indicates a kernel iss
It is odd that you have so many marked manually installed. Unless you
actually installed those packages manually, they should be marked as
automatically installed. We do keep a few kernels installed, so that
it's possible to boot back to a previous kernel if an update causes
problems, but it should
Do you have a separate /boot partition? If so, check whether or not it's
full. You may need to remove some old kernel packages you are no longer
using.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.
Disabling AUFS was a choice, we planned to update the test accordingly
but just didn't get to it. The only remaining software which used AUFS
in the archive was docker, and even there support is deprecated in favor
of overlayfs. In hirsute a migration strategy was put in place for
docker, so AUFS w
Oh, there was also fsprotect which used aufs. But it looked to be
abandoned upstream, and other packages provided duplicate functionality
using overlayfs, so it has been removed from the archive in hirsute.
--
You received this bug notification because you are a member of Kernel
Packages, which i
I just confirmed that Ubuntu 21.04 has no kernel patches for btrfs that
are not from upstream stable releases, so I have doubts that this is
Ubuntu-specific. We do produce testing builds of unpatched upstream
kernel releases though, so you could try out 5.11 and 5.12 builds to
check whether this is
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ Hot removal of disks under kvm on s390 does not result in the kernel
+ removing the block device, which can lead to hung tasks and other
+ issues.
+
+ [Test Plan]
+
+ See steps to reproduce the bug in the original description below.
The condition for css_sch_device_unregister(sch) also caught my eye,
calling it unconditionally is probably closer to right because it was
called in the !cdev case before, and in the attached patch it would no
longer be called in this case. However I think in the short term the
revert is the safest
The commit reverts cleanly. We need to confirm that reverting the commit
does fix the issue. I put a test build here, please test.
https://people.canonical.com/~sforshee/lp1925211/
I doubt we can get a new kernel into the release. If it's extremely
urgent we can consider a day 0 SRU kernel for hi
*** This bug is a duplicate of bug 1922403 ***
https://bugs.launchpad.net/bugs/1922403
** This bug has been marked a duplicate of bug 1922403
hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI
--
You received this bug notification because you are a member of Kerne
** Attachment added: "install.log"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487811/+files/install.log
** Description changed:
- evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream
- updates for 5.11 proved problematic, and a working set of
** Attachment added: "build.log"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487810/+files/build.log
--
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/1923638
The project does not maintain a changelog, so instead attaching the git
commit history between the v1.7.0 and v1.9.1 tags.
** Attachment added: "changelog.txt"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487808/+files/changelog.txt
--
You received this bug notifi
** Summary changed:
- [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
+ [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Description changed:
- This is a scripted bug report about ADT failures while running evdi
- tests for linux/5.11.0-14.15 on hirsute. Whether thi
** Summary changed:
- evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15
+ [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Public bug reported:
This is a scripted bug report about ADT failures while running evdi
tests for linux/5.11.0-14.15 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Testing failed on:
** Affects: evdi (Ubuntu)
Importance: Un
These commits are already included in hirsute, closing the development
task.
** Changed in: linux (Ubuntu)
Status: Confirmed => 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.ne
** Changed in: linux-firmware (Ubuntu)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Bug watch added: Linux Kernel Bug Tracker #212371
https://bugzilla.kernel.org/show_bug.cgi?id=212371
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=212371
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Also affects: linux (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/1922406
Title:
Intel AX210 Wi-Fi card does not work since updat
It looks like the package may have downloaded incorrectly. If you are
still seeing this issue, try running 'sudo apt-get clean' in a terminal
and then try upgrading again.
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you ar
I came across this bug when looking through open linux-firmware bugs.
Sorry that it didn't attract any attention before.
If this is still a problem, I think the right solution is to pursue a
solution upstream. Once one is found we can accept these fixes into
Ubuntu. Unfortunately, changing our con
I don't see a reason this was filed against the kernel. Changing to
gnome-system-monitor.
** Package changed: linux (Ubuntu) => gnome-system-monitor (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Changed in: linux (Ubuntu Hirsute)
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/1922600
Title:
Hirsute update: v5.11.10 upstream stable r
** Changed in: linux (Ubuntu Hirsute)
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/1922601
Title:
Hirsute update: v5.11.11 upstream stable r
hen ipg clock is disabled
net: stmmac: fix dma physical address of descriptor when display ring
mt76: mt7915: only modify tx buffer list after allocating tx token id
mt76: fix tx skb error handling in mt76_dma_tx_queue_skb
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Seth
** Changed in: linux (Ubuntu Hirsute)
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/1915717
Title:
[FEATURE] Hirsute: support TLS device offl
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1922372
Title:
i915 doesn't support some high pixel clock 4k * 60H
Warn on pinning without holding a reference"
Revert "drm/ttm: make ttm_bo_unpin more defensive"
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
--
You received this bug not
Sorry, I wasn't seeing emails for this bug despite being subscribed. Not
sure what's going on with that.
If the key is self-signed, shouldn't having the key in
.builtin_trusted_keys allow for loading it into the IMA keyring? Or is
that insufficient for some reason?
--
You received this bug notif
On Thu, Mar 18, 2021 at 01:36:55AM -, SaveTheRbtz wrote:
> Is it possible (pun intended) to compromise on
> `CONFIG_SQUASHFS_DECOMP_MULTI` (which uses num_online_cpus) instead of
> `CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU` (which uses `num_possible_cpus`)?
It's better, but still not that great of
@SaveTheRbtz I did get to the cause, and added a lot of notes about it
in the comments for this bug. I even wrote some code to provide a more
balanced compromise between memory usage and performance, but once the
memory issues were alleviated it seems no one cared about it enough to
even try out th
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
-
- SRU Justification
-
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originat
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
I should have mentioned, the kernel in comment #11 is not signed with
the archive signing key since it's in a personal ppa, but the cert which
is built into the kernel is for the archive key.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Here's a test build with public cert for the opal signing key built into
.builtin_trusted_keys:
https://launchpad.net/~sforshee/+archive/ubuntu/lp1903288
I'm still working out exactly how we want to distribute the key in the
filesystem, but if you can try that out and let me know whether that
wor
Sorry for the delayed response here, it's taken me a while to get some
of the needed information.
In general this should be fine. One thing to note is that the key is
self-signed, so we will need to add the signing key itself into
.builtin_trusted_keys. This should still allow loading the key into
*** This bug is a duplicate of bug 1911836 ***
https://bugs.launchpad.net/bugs/1911836
Marking as a duplicate of bug 1911836 based on comment #2.
** This bug has been marked a duplicate of bug 1911836
package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade:
run-parts: /
** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)
--
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/1912947
Title:
bluetooth: hci0: failed to restart LE scan: status 31
Status
: Low
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1912499
Title:
Reset upload number to 1 for derivative ABI bumps
@Tim I do not think you have the same problem. I see some errors which
look like debconf is attempting to prompt you about something but
failing to find a frontend to use for the prompt. Possibly this is the
cause, but I'm not sure. You can try running the upgrade like this:
# DEBIAN_FRONTEND=noni
Have you tried to install any firmware, either manually or via third-
party packages? Are you running any antivirus tools?
What is the output from running the following commands in a terminal?
ls -ld /lib/firmware/brcm
ls -l /lib/firmware/brcm
** Changed in: linux-firmware (Ubuntu)
Status
The problem appears to be a failed sync when regenerating the initrd.
Looking through the attached dmesg I see a lot of disk-related errors.
This could indicate a kernel bug or potentially a hardware problem. This
is not directly a problem in linux-firmware, reassigning to linux.
Have you noticed
Seems like it might be the same as this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=210695
If so this is the fix, which is already queued up for the next 5.10
stable update:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39b4d43e6003cee51cd119596d3c33d0449eb44
Confirmed that the attached test script reproduces the problem with
5.8.0-36-generic from groovy-updates. ith 5.8.0-37-generic from groovy-
proposed the problem is fixed.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification bec
On Mon, Jan 11, 2021 at 11:12:35AM -, Philipp Wendler wrote:
> I tested it on a Focal machine and the -proposed kernel works. However,
> I don't have a Groovy machine here, is it necessary for me to test this?
I can verify the fix in groovy.
> I noticed that in the list of affected packages i
I think I've got a good idea of what you're after here. Let me look into
this, and I'll try to get back to you soon.
--
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/1903288
Title:
Power g
@Kai-Heng please add some information about how you verified this.
--
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/1909705
Title:
Fix Realtek 8821c bluetooth fails reconnect BLE
** 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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ The backports to fix CVE-2020-16120 introduced a regression for overlay
+ mounts within user namespaces. Files with ownership outside of the user
+ namespace can no longer be accessed, even if allowed by both DAC and
+ MAC.
+
+ This i
gt; In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy
Apologies for the delay on this bug. There is a fix upstream in
5.11-rc1, I've backported the fix to the test kernel located here:
https://people.canonical.com/~sforshee/lp1900141/linux-5.4.0-59.65+lp1900141v202101061102/
I'm also attaching a script which reproduces the bug. In my testing the
pro
I confirmed that that correct new firmware files have been added, and
that the contents of those files match what is expected. I also
confirmed that the nic-firmware udeb updates are as expected, and that
there are no changes to the contents of the scsi-firmware udeb.
** Tags added: verification-d
That's not the sort of config we usually turn on, as it's more of a
developer feature than something end users are interested in. So I don't
see any need to turn the option back on. We can go ahead and grab the
patch though.
In any case I'd like to get some secure boot testing with the current
bui
The 5.10.0-7.8 with CONFIG_RCU_SCALE_TEST disabled has completed and is
available in https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/bootstrap as before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
encounter issues when
upgrading.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Assignee: Seth Forshee (sforshee)
Status: Invalid
** Affects: linux-firmware (Ubuntu Focal)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
Our latest 5.10 update is building with CONFIG_RCU_SCALE_TEST disabled,
I will update once the build is complete.
--
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/1904906
Title:
5.10 kerne
ntu Precise)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Trusty)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Precise)
Assignee: (unassigned) =&g
** Description changed:
- New upstream version, bringing in updated regulatory rules for various
- jurisdictions.
+ [Impact]
+
+ New upstream release. This is a database of wireless regulations, and
+ should updated in all releases to ensure users have the most up-to-date
+ regulatory information
Public bug reported:
New upstream version, bringing in updated regulatory rules for various
jurisdictions.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: wireless-regdb (Ubuntu Xenial)
Importance
That config shouldn't be on at all, it's just a performance test that
isn't likely to be of interest to users. I agree it's weird though -- it
shouldn't cause boot problems, as it shouldn't be loaded automatically
(the module doesn't even have any modaliases). Regardless, I will
disable the option.
Added lilo as an affected package.
--
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/1905195
Title:
package linux-firmware 1.187.4 failed to install/upgrade: installed
linux-firm
>From the dpkg terminal log:
update-initramfs: Generating /boot/initrd.img-4.15.0-125-generic
Fatal: raid_setup: stat("/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_Z9K8SF7NS")
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
dpkg: error processing package linux-firmware (--confi
*** This bug is a duplicate of bug 1905195 ***
https://bugs.launchpad.net/bugs/1905195
** This bug has been marked a duplicate of bug 1905195
package linux-firmware 1.187.4 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned error exit
*** This bug is a duplicate of bug 1905195 ***
https://bugs.launchpad.net/bugs/1905195
** This bug has been marked a duplicate of bug 1905195
package linux-firmware 1.187.4 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned error exit
I also note that you are testing with 5.10.0-0, which was based on
5.10-rc1. We have 5.10.0-4 in the ppa now based on -rc4, it is built for
hirsute and not groovy though. I'd recommend trying that version to see
if there was an upstream bug which has already been fixed.
--
You received this bug n
I've attached our configs for the Ubuntu 5.8 and 5.10 kernels along with
a diff between these configs. I didn't see anything in the diff which
looked like an obvious candidate for causing the boot problems. Please
let me know if you see something there which should be changed.
--
You received thi
** Patch added: "Diff between Ubuntu 5.8 and 5.10 ppc64el kernel configs"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436111/+files/ppc64el-config.flavour.generic.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Attachment added: "Ubuntu ppc64el kernel config for 5.10"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436110/+files/ppc64el-config.flavour.generic-5.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Attachment added: "Ubuntu ppc64el kernel config for 5.8"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436109/+files/ppc64el-config.flavour.generic-5.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** Changed in: linux-restricted-modules (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-signed (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in
restricted-modules (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: linux-signed (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Also affects: linux-restricted-modul
1 - 100 of 3474 matches
Mail list logo
