I tried with 2 new images
initrd.img-5.4.10-050410-generic
initrd.img-5.5.0-050500rc5-generic
Problem not solved for both. Touchpad is not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Note that I've found dozens of posts on the web that describe the same
symptom, and a subset of those arrive at the same conclusion of this
bug. I do agree that the license that the github repo holds indicates
that the files are made available for personal use, but perhaps we can
address that.
For my laptop, which is an x230 model 2325KZ5, I have:
Bus 001 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0
[ThinkPad]
The file which I needed to use was brcm/BCM20702A1-0a5c-21e6.hcd as
noted above. That is the only file needed to fix my issue.
The post I linked to is for
Similar defiled experience on ASUS Zenbook 14 UM431D with Ubuntu 19.10.
--
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/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I understand this situation.
I want to update next release.
** Changed in: linux (Ubuntu)
Status: Expired => 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/1842173
I understand this situation.
** Changed in: linux (Ubuntu)
Status: Expired => 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/1848964
Title:
ubuntu-18.04.3 iso boot
** 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 --
They are running Intel Xeon Gold 5120 CPU so will recommend that as
well, thanks.
--
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/1859099
Title:
BUG: unable to handle kernel paging
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319169/+files/ProcEnviron.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319175/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319170/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319165/+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/1859102
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319173/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319174/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected staging tricia
** Description changed:
Laptop does not power off when issue a shutdown request. This problem
actually began for me with kernel 4.15.0.72.74 but 4.15.0.74.76 did not
fix it. I can provide whatever debug/log information
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319168/+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/1859102/+attachment/5319162/+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/1859102
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319172/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319163/+files/CurrentDmesg.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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319166/+files/Lsusb.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/1859102
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319164/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319167/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1859102/+attachment/5319171/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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 --
** Summary changed:
- disco/linux-gcp: -proposed tracker
+ disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Summary changed:
- disco/linux-oracle: -proposed tracker
+ disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Summary changed:
- disco/linux-aws: -proposed tracker
+ disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** 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 --
The intel-microcode package [1] had an update in mid November 2019
(version "3.20191115"ish) with an entry apparently related to the
symptoms seen in the kernel log you provided:
'Unexpected Page Faults in Guest Virtualization Environment (SKL-188,
KBL-144, CFL-136 errata)'
If you're running on
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
** 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 --
** Summary changed:
- disco/linux-raspi2: -proposed tracker
+ disco/linux-raspi2: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/verification-testing
Status: New => Confirmed
** 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 --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
I agree with what Richard said above in comment #14, especially:
> The installer should prompt (with a checkbox) for whether the user
wants encryption. It should default to off. If the user selects the
checkbox, prompt them for a passphrase. Setup encryption using that
passphrase.
--
You
This appears to fix it for me:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commitdiff;h=8cd0e5e93145699736a370b271ff03f3f41670b0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
> It is not appropriate to require the user to type a password on every
> boot by default; this must be opt-in.
Agreed.
The installer should prompt (with a checkbox) for whether the user wants
encryption. It should default to off. If the user selects the checkbox,
prompt them for a passphrase.
> I would recommend setting encryption=aes256-gcm instead of
> encryption=on (which is aes256-ccm).
I think the right way to handle this is to change the behavior of zfs-
linux so that encryption=on defaults to the recommended algorithm -
rather than hard-coding the algorithm selection in
> I believe it would be rather trivial to have Ubiquity collect
> a password from the user, use "-O keylocation=prompt" and to
> expect the user to provide the password every reboot.
It is not appropriate to require the user to type a password on every
boot by default; this must be opt-in.
The
** 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 --
@You-Sheng Yang
Is this bug a duplicate/related to these?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858077
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I'll take a look, but usually firmware like this has been extracted from
drivers for Windows and does not have a license which allows us to
redistribute the files. I'll try to find out what the license is for the
files you linked to.
I'm not sure we'd do a wholesale import of everything you've
** 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 --
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1858941
Title:
eoan/linux-raspi2:
** Changed in: kernel-sru-workflow/security-signoff
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/1858943
Title:
eoan/linux: 5.3.0-27.29
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Hi, I have the same problem I think (2.1 speakers and sounds only the
left, if i remove the two little ones (L & R), the subwoofer can sound)
I run "sudo lshw" so the text is long:
descripción: Equipo de escritorio
producto: System Product Name (ASUS_MB_CNL)
fabricante: System
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** 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:
** 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: crash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1859226
Title:
crash reports Illegal instruction w/ newer
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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
Public bug reported:
Hello there, it's my third or fourth session spending hours trying to
debug why a Bluetooth headset would not work in HSP/HFP mode on my x230.
The failure more is super obscure because at the time of error the only
thing you notice is that no audio comes through in either
Yes, this works again
--
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/1858844
Title:
[Dell XPS 15 9575] Screen brightness stopped working with linux-
image-5.4.0-9-generic
Status 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 --
** 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 --
BuildBox 3.0 Crack incl Serial Key {Updated} Windows (x86/x64)
BuildBox Crack is a delightful software which is used to generate games. More ,
deprived of programming and physical coding, you will be able to create as well
as design a game. Add more, BuildBox is a very unpretentious tool for the
http://crackingkeys.com/buildbox-crack-keygen/
--
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/1239459
Title:
1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
== "mwifiex crash on idle/using"
I heard this issue only from Surface 3 and SP5 owners.
It can be fixed by disabling ASPM L1 state. I think this is the hardest issue
to fix. So, I hope at least we could fix the mwifiex reset feature (see below).
== "mwifiex reset feature broken"
I think this
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: High => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
** Changed in: makedumpfile
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: makedumpfile (Ubuntu Disco)
Importance: Low => Undecided
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned)
--
You received this bug
*if someone knows devices
--
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/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Status in Linux:
Confirmed
Status in linux package in
Also, ff someone knows devices (other than Surface) that use the same
88W8897 chip (or at least similar PCIe chip like 88W8997), let me know.
I want to get the device as a reference.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thank you for looking into this issue. Reporting current status.
== "mwifiex crash after suspend"
This issue might be the Surface devices specific problem? Not sure.
I know some ways to prevent at least mwifiex crashing:
1. Disabling d3cold for wifi device (even doable on mainline kernels):
** Bug watch added: github.com/jakeday/linux-surface/issues #420
https://github.com/jakeday/linux-surface/issues/420
--
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/1730924
Title:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
Hi Guilherme, Thadeu,
The re-spinned packages have been uploaded to Bionic and Eoan.
Xenial didn't change, and is still in the upload queue (which
I'll go check about on next week.)
Disco didn't change, and has been removed from the upload queue.
(After discussions with other people, it turns
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
** 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:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
** 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 --
packages:
** Summary changed:
- bionic/linux: -proposed tracker
+ bionic/linux: 4.15.0-75.85 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** 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 --
** Summary changed:
- disco/linux-kvm: -proposed tracker
+ disco/linux-kvm: 5.0.0-1025.27 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
1 - 100 of 165 matches
Mail list logo
