*** 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
Added lilo as an affected package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905195
Title:
package linux-firmware 1.187.4 failed to install/upgrade: installed
linux-firmware package post-inst
>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
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.
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
** 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
** Changed in: openrazer (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916905
Title:
openrazer 2.9.0+dfsg-1 build failure with linux 5.10* on s3
** Changed in: oss4 (Ubuntu)
Importance: Undecided => Medium
** Changed in: oss4 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916872
Title:
oss4-dk
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
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931798
Title:
installed initramfs-tools pack
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
. 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
Public bug reported:
Ubuntu carries a patch for gdb, ptrace-error-verbosity.patch, to print
some extra information about why attaching to a process might have
failed. This inserts a fprintf_unfiltered() call between the ptrace()
and the corresponding perror(). Recently something has changed which
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
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
us: New => Incomplete
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928393
Title:
linux-firmw
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,
>
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
** 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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923638
Title:
[FF
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
** 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
*** 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 Ubunt
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
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
** 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.
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
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 Ubuntu
Bugs, which is su
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
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
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
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
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
Make this a wildcard, "debian.master*", which
will allow us to build linux-libc-dev for hirsute forward-port kernels.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
You received this bug notification because you are a m
Here are the error messages from the log files:
Setting up linux-firmware (1.157.23) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-170-generic
E: amd64-microcode: unsupported kernel version!
E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
update-initramfs: faile
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
Started getting this error after upgrading from 1:2.6.16-1 to 1:2.7.2-1.
Gives the following stacktrace:
$ /usr/bin/imapfilter -c ~/.imapfilter/mail.lua
imapfilter: /usr/share/imapfilter/regex.lua:10: bad argument #1 to 'compile'
(string expected, got nil)
stack traceback:
I filed a bug upstream, the issue is fixed in v2.7.4.
https://github.com/lefcha/imapfilter/issues/218
Here's the fix:
https://github.com/lefcha/imapfilter/commit/987ea442fa0aa3dc5f5d59ec89c9a3d818cd48d3
** Bug watch added: github.com/lefcha/imapfilter/issues #218
https://github.com/lefcha/im
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu
** 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 Ubuntu
Bugs, which is subscri
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904906
Title:
5.10 kernel fails to bo
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
Testing failed on:
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz
--
FAIL: misc/tst-sigcontext-get_pc
ori
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/amd64/l/lxc/20201208_183047_03358@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonic
lxc-test-api-reboot fails. The container fails to start, I see lots of
errors in the logs related to mounting things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907307
Title:
lxc 1:4.0.4-0ubuntu
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
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
It's understandably difficult to use apport-collect when you don't have
a network connection. If possible use a wired connection, otherwise at
least collect dmesg and attach it to this bug. Please be sure that any
logs are collected while running the 4.15 kernel.
--
You received this bug notifica
Also note that the patch you linked to was included in a stable update
from upstream and has been in the bionic kernel since 4.15.0-11.12, and
the CONFIG_SSB_PCIHOST_POSSIBLE is being enbled. So that should not be
the issue causing your problem in linux-hwe-edge 4.15.0-13.
--
You received this bu
Applied fe9a552e715.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730829
Title:
[Feature]Crystal Ridge:add support for the platform capabilities NFIT
sub-table in ACPI 6.2A
To manage notificati
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759279
Title:
[Intel Ubuntu 18.04 Bug] Null pointer dereference, when
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758206
Title:
Ubuntu 18.04 [ WSP DD2.2 with stop4 and stop5 enabled ]:
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759312
Title:
AT_BASE_PLATFORM in AUXV is absent on kernels available
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758662
Title:
[Bionic] mlx4 ETH - mlnx_qos failed when set some TC to
The pci ids for your device should be handled by the bcma module, but
that module is not loaded. Can you confirm that you have the
corresponding linux-image-extra package installed? If so, please run:
modprobe --show-depends
pci:v14E4d4331sv14E4sd4331bc02sc80i00
and provide the
Okay, so you've installed the bcmwl-kernel-source package and that's the
driver being used with 4.13 (and likely it did blacklist bcma). I
suspect that when you install hwe-edge or the 4.16 kernel you got some
messages about the dkms build for the driver failing, but perhaps you
didn't notice them.
nel-team) => Seth Forshee
(sforshee)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
--
You recei
Bionic should have been fixed for a while now, updating the status.
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757497
Title:
Ubuntu 18.04 - IO Hang on some namespaces when running H
Applied the backport to bionic/master-next, thanks!
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758910
Title:
Impor
It looks like we've already applied
ff6781fd1bb404d8a551c02c35c70cec1da17ff1 and
e4b79900222b8cccd4da4a7a89581f0e1b764ed2 from other bugs. So now we're
only missing the backport of a5d4b5891c2f1f865a2def1eb0030f534e77ff86.
--
You received this bug notification because you are a member of Ubuntu
B
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
/dev/bcache/by-uuid links not created after reboot
To m
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876
** This bug is no longer a duplicate of bug 1760973
virtualbox-dkms 5.2.8-dfsg-5: virtualbox kernel module failed to build
[Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install
libelf-dev
*** This bug is a duplicate of bug 1760876 ***
https://bugs.launchpad.net/bugs/1760876
"Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev,
libelf-devel or elfutils-libelf-devel" is only a warning, it is not
causing the build to fail. We do want CONFIG_STACK_VALIDATION=y.
The rea
As for the UNCLAIMED issue, I think maybe you're confusing the output of
lspci and lshw? Because the part in the description which says UNCLAIMED
looks like lshw output and not lspci output.
The bcmwl-kernel-source driver does need updates for 4.15. This will be
done before 4.15 becomes the hwe ke
It's not possible to turn around a kernel that quickly. I intend to get
a kernel with the fix uploaded bionic-proposed today, but it takes a few
days at minimum to get it built, tested, and promoted to the -release
pocket.
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
Imp
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
Imp
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-stable-maste
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
backports: bug 1761184 (linux-hwe-edge)
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: linux-hwe-edge (Ubuntu)
Status: New => Invalid
** Changed in: linux-hwe-edge (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761165
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
** Changed in: kernel-sru-workflow
Status: In Progress => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/prepare-package-me
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-stable-maste
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the 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
-- swm properties --
kernel-master-bug:
1 - 100 of 5860 matches
Mail list logo
