Public bug reported:
I am using Raspberry Pi 4B (4GB) and want to make use of the OTG
functionality (g_ether). I cross checked with Raspbian to make sure it
is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with
latest updates applied as of Jan 26th, 2020 via "apt-get update" and
I tried the patch https://forum.manjaro.org/t/alc294-analog-audio-card-
detected-but-no-sound-internaly-or-headphones/54089/29 for kernel 5.4,
but the sound is not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
Could be. Bug 1860178's write-up seems similar to 1860483.
I have been able to use "Settings" in the sda1 install, and switched the
background to "black", at which point the raster type corruption in the
desktop went away. Now there's occasionally an odd speckled background
in the top tool
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1861063
Title:
Dualshock4 controller doesn't
** Changed in: kernel-sru-workflow/promote-to-security
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:
It sounds like this might be the problem:
Bluetooth: Dropping L2CAP data: receive buffer overflow
in which case that would be a kernel bug. So this has been assigned to
the kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1511855
Title:
Some Sony Dualshock 4 controllers do not work in
** Changed in: linux (Ubuntu Eoan)
Status: Triaged => 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/1860535
Title:
Disable ECKD Thin Provisioning to prevent data
If I try to connect the controller with the usb cable it gets recognized
as pulse audio source.
The controller model is: CUH-ZCT2U
This is the output of the dmesg:
[ 1882.762621] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[ 1882.913951] usb 1-1: New USB device found,
Public bug reported:
Pairing the Dualshock4 controller works somehow, after several attempts.
I expected this to work out of the box but it does not work well at all.
Once the pairing is completed, if I try to connect it it doesn't stay
connected.
I have checked the dmesg and apparently there
** Description changed:
This config option causes the following message to be displayed in the
kernel log:
[0.568713] *
[0.570549] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE**
[0.570640] **
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Cosmic)
** No longer affects: linux (Ubuntu Disco)
--
You received this bug notification because you are a member of Kernel
[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.
** No longer affects: kexec-tools (Ubuntu)
** No longer affects: kexec-tools (Ubuntu Cosmic)
** No longer affects: kexec-tools (Ubuntu Disco)
** No longer affects: kexec-tools (Ubuntu Eoan)
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Disco)
** No longer affects:
This change was made by a bot.
** Changed in: linux (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/1860925
Title:
Xorg freeze / nouveau driver
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 1861057
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
This config option causes the following message to be displayed in the
kernel log:
[0.568713] *
[0.570549] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE**
[0.570640] **
** Tags added: nvidia
** Summary changed:
- second monitor is not waking up automaticall after boot and sleep
+ [nvidia] second monitor is not waking up automatically after boot and sleep
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-435
(Ubuntu)
--
You received this bug
Reply #5:
No, the change is not in the 1.2.1 and will not apply to 1.2.1. these
confs are ucm1 version, they are only for eoan and bionic. For alsa-lib
1.2.1, the upstream is writing ucm2 confs and it is not finished yet. So
let's SRU the ucm confs for eoan and bionic first. And in future the
You have been subscribed to a public bug:
primary screen : laptop screen
secondary screen: Samsung Monitor
secondary monitor is connected to laptop via HDMI port.
secondary monitor won't wake up after a normal boot.
secondary monitor will wake up after boot if switch to ctl+alt+f7 and then back
This looks like a nouveau kernel problem, but can you describe the
problem you are experiencing?
** Tags added: nouveau
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change was made by a bot.
** Changed in: linux (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/1860754
Title:
ASUS T100HAN boots to a blank
You have been subscribed to a public bug:
june@june-pc:~$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
(Note: upgrade today from 19.04, which also froze randomly)
june@june-pc:~$ apt-cache dump | grep nouveau | grep
Please:
1. Reproduce the freeze again, then reboot and run:
journalctl -b-1 > preboot.txt
and attach the file here.
2. Try uninstalling the Nvidia driver if you can and tell us if the
problem still happens with the default built-in driver.
** Tags added: nvidia
** Summary changed:
-
** Changed in: kernel-sru-workflow/promote-to-security
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:
You have been subscribed to a public bug:
I have problem with graphic cards. After work, when I reboot system then
system feeze and I can't work. I must change to the recovery mode and
next work.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature:
See also bug 1860754.
** Summary changed:
- 3D Application cannot run anymore
+ 3D Application cannot run anymore [i965: Failed to submit batchbuffer:
Input/output error]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
See also bug 1838181.
** Summary changed:
- ASUS T100HAN boots to a blank screen with a cursor
+ ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit
batchbuffer: Input/output error]
** Package changed: ubuntu => mesa (Ubuntu)
** Also affects: linux (Ubuntu)
This change was made by a bot.
** Changed in: linux (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/1860178
Title:
[nouveau] Desktop wallpaper
If that driver version solves the problem, yes. If you are willing to
risk trying pre-release drivers then please do.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
Possibly related to bug 1860178.
** Also affects: mutter (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/1860483
Title:
[nouveau,
Possibly related to bug 1860483.
** Summary changed:
- [nouveau] Graphic environment bug
+ [nouveau] Desktop wallpaper is corrupt noise
** Package changed: ubuntu => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Also affects: gnome-shell (Ubuntu)
You have been subscribed to a public bug:
Graphic environment unstable, desktop background degraded. Seems
consequently to last system upgrade (2020.jan.17)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic
> Considering nvidia's market share (80% according to the steam hardware
survey, which will be skewed towards people with discrete GPUs, but
still), I think giving this issue a priority of low is wrong.
That might be true for gaming machines but I don't think that's an
accurate figure for
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Fix Released
** No longer affects: linux (Ubuntu)
** No longer affects: linux-hwe (Ubuntu)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux-hwe (Ubuntu Bionic)
--
You received this bug
Re comment #39, can someone with the privileges please click retry? It
won't let me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1845046
Title:
Bluetooth headphones default to low
You should probably log a new bug for the 2540p.
---
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and
Wait, did the problem appear in a daily update or do you mean it
appeared after upgrading from 18.10 to 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/1860764
Title:
Line out
Thanks for the bug report. Can you please try the latest kernel and tell
us if that has the same bug?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/
** Summary changed:
- problem after pulseaudio updating
+ Line out audio device is missing after resume-from-suspend
** Tags added: resume
Please also try an older kernel like version 5.0, since you say the
regression appeared in an update.
--
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/1860764
Title:
Line out audio device
Upstream PR: https://github.com/systemd/systemd/pull/14681
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux (Ubuntu Cosmic)
Status: Expired => Invalid
** Changed in: linux (Ubuntu Eoan)
Status: New => Invalid
** Changed in: linux (Ubuntu
Just add that PPA and update its series to bionic and run apt update
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1860940
Title:
Cannot read
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: Expired
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Eoan)
** 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.
https://bugs.launchpad.net/bugs/1861053
Title:
no fatrace output in focal
Status in fatrace package
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1861053/+attachment/5323432/+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
** Tags added: apport-collected
** Description changed:
Hello, fatrace in focal doesn't seem to work for me in focal.
Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
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 1861053
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Hello, fatrace in focal doesn't seem to work for me in focal.
Start fatrace in one terminal, and perform file operations in another
terminal: man man, echo hi > hi, echo hi > /run/user/1000/hi, etc.
sarnold@millbarge:~$ sudo fatrace
[sudo] password for sarnold:
I added the linux package too, because the strace doesn't seem too
unusual.
** Attachment added: "strace.out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861053/+attachment/5323430/+files/strace.out
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Changed in: kernel-sru-workflow/promote-to-security
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:
** Tags added: regression-testing-passed
--
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/1858625
Title:
trusty/linux: 3.13.0-176.227 -proposed tracker
Status in Kernel SRU Workflow:
** Changed in: kernel-sru-workflow/regression-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 workflow
** Changed in: dmidecode (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1858615
Title:
dmidecode triggers system reboot on Inforce
Notice in the log in comment #6 that the unexpected error we are seeing
for "unhappy-2" is the expected error for "unhappy-1".
I wonder if there's a race here:
# tests for error conditions
for f in unhappy-*.input; do
echo "*** Running test $f"
rm
thanks for following up on this
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1859592
Title:
Bluetooth unavailable
Another instance:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/s/systemd/20200127_181441_fb524@/log.gz
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
This bug was fixed in the package linux-aws - 5.3.0-1010.11
---
linux-aws (5.3.0-1010.11) eoan; urgency=medium
* eoan/linux-aws: 5.3.0-1010.11 -proposed tracker (LP: #1859817)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: Port EFA 1.4.0
- SAUCE: linux/efa: Fix
This bug was fixed in the package linux-raspi2 - 5.3.0-1017.19
---
linux-raspi2 (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker (LP: #1859692)
[ Ubuntu: 5.3.0-28.30 ]
* eoan/linux: 5.3.0-28.30 -proposed tracker (LP: #1859694)
*
*** This bug is a duplicate of bug 1859692 ***
https://bugs.launchpad.net/bugs/1859692
This bug was fixed in the package linux-raspi2 - 5.3.0-1017.19
---
linux-raspi2 (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker (LP: #1859692)
[
This bug was fixed in the package linux-raspi2 - 5.3.0-1017.19
---
linux-raspi2 (5.3.0-1017.19) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker (LP: #1859692)
[ Ubuntu: 5.3.0-28.30 ]
* eoan/linux: 5.3.0-28.30 -proposed tracker (LP: #1859694)
*
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 1861044
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package linux-aws - 5.3.0-1010.11
---
linux-aws (5.3.0-1010.11) eoan; urgency=medium
* eoan/linux-aws: 5.3.0-1010.11 -proposed tracker (LP: #1859817)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: Port EFA 1.4.0
- SAUCE: linux/efa: Fix
Public bug reported:
[What happens]
When system goes sleep it takes a while to resume, and does it freezing for
some minutes.
[System info]
Logs begin at Thu 2020-01-02 18:38:22 -03, end at Mon 2020-01-27 20:02:00 -03.
--
jan 02 18:38:22 d4rkl41n kernel: microcode: microcode updated early to
This bug affected the previous generation of Zenbooks but was apparently
fixed. I am hoping someone figures out how to apply the same patches.
Downloading and patching 5.4.10 kernel wont let me boot into it but I
will try again with 4.20 next weekend
--
You received this bug notification because
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
One should adapt the /usr/sbin/dkms script to be more informative when
error logging. You can change the line 527 (or similar on your system):
[[ -r $read_conf_file ]] || die 4 $"Could not locate dkms.conf file." \
to something like
[[ -r $read_conf_file ]] || die 4 $"Could not locate
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'm in the same train as colingelling96. Very similar computer and same
problem. It really sucks because I got this computer from work to work
on something that requires Linux, and now this thing is useless since I
can't attend meetings.
I guess I will keep it for a couple weeks to see if this
** Changed in: kernel-sru-workflow/promote-to-updates
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 workflow
** 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 --
This bug was fixed in the package linux-oem - 4.15.0-1067.77
---
linux-oem (4.15.0-1067.77) bionic; urgency=medium
* bionic/linux-oem: 4.15.0-1067.77 -proposed tracker (LP: #1859702)
[ Ubuntu: 4.15.0-75.85 ]
* bionic/linux: 4.15.0-75.85 -proposed tracker (LP: #1859705)
*
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
** 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/1859261
Title:
[hns3-0111]sync mainline kernel 5.5rc6 hns3
** Changed in: kernel-sru-workflow/promote-to-updates
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 workflow
** 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
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1859702
Title:
bionic/linux-oem: 4.15.0-1067.77 -proposed tracker
Status in Kernel SRU
I'm not sure exactly what has changed, but a new kernel did install
today and suspend/resume is working much better.
`systemctl suspend` is working as expected. However, closing the laptop
lid is not quite working yet. When I close the lid, the power stays on,
but when I open the lid, it
** Changed in: kernel-sru-workflow/promote-to-updates
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 workflow
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
** Description changed:
This bug will
** 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-updates
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 workflow
** 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/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a
This bug was fixed in the package linux-aws - 4.15.0-1058.60
---
linux-aws (4.15.0-1058.60) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1058.60 -proposed tracker (LP: #1859795)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: linux/efa: Fix incorrect error print
This bug was fixed in the package linux-aws - 4.15.0-1058.60
---
linux-aws (4.15.0-1058.60) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1058.60 -proposed tracker (LP: #1859795)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: linux/efa: Fix incorrect error print
Folks, Just as an update, this is affecting anyone that wants to use
VirtualBox with kernel 5.4 and 5.5, when it is just downloaded from the
kernel repository.
You can see more activity at
https://forums.virtualbox.org/viewtopic.php?f=7=96297. Virtualbox
maintainers have also confirmed the above
This bug was fixed in the package linux-aws - 4.15.0-1058.60
---
linux-aws (4.15.0-1058.60) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1058.60 -proposed tracker (LP: #1859795)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: linux/efa: Fix incorrect error print
This bug was fixed in the package linux-aws - 4.15.0-1058.60
---
linux-aws (4.15.0-1058.60) bionic; urgency=medium
* bionic/linux-aws: 4.15.0-1058.60 -proposed tracker (LP: #1859795)
* Update EFA driver to 1.5.0 (LP: #1850195)
- SAUCE: linux/efa: Fix incorrect error print
** Changed in: linux (Ubuntu)
Assignee: Tim Gardner (timg-tpi) => Petro (petrolerouxubuntu)
--
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/1566221
Title:
linux: Enforce signed
1 - 100 of 379 matches
Mail list logo
