** Changed in: linux (Ubuntu Eoan)
Status: Fix Released => 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/1870320
Title:
[UBUNTU 18.04] zpcictl --reset - contribution for
John,
Unfortunately the chip is unmarked except for the letters "V3" and a dot to
mark a corner. It's QFP88 package of some kind.
On Wed, May 6, 2020, 11:55 AM John Jackson <1749...@bugs.launchpad.net>
wrote:
> Thanks Lior, and Aki. I fear the Razer core X chroma may require
> extensive setup
I've uploaded some test kernel packages that address this issue. Do you
mind testing these to see if it resolves the issue and let me know so I
can get this fix into the next kernel release.
https://kernel.ubuntu.com/~cking/lp-1876856/
--
You received this bug notification because you are a
having same issue in 18.04 with HWE kernel:
Linux hostname 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31
04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Model name: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
$ cat /etc/issue
Ubuntu 18.04.4 LTS \n \l
** Attachment added: "1915.error"
I feel like this is a lot better on Ubuntu 20.04. Anyone else have the
same experience?
--
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/1208993
Title:
Ubuntu slows down and hangs while
TEST-21 did not fail for any arch for autopkgtests on bionic and eoan.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan
--
You received this bug notification because you
This was fixed in Debian at version 244.2-1, which is earlier than the
version in focal, so this is fix released for focal.
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
Thanks Lior, and Aki. I fear the Razer core X chroma may require
extensive setup and a graphics card that I do not have handy or am
prepared to take on right now. And I cannot get the IMX291 CMOS Camera
overnight. Aki, do you mind looking at the Camera and trying decipher
which device side usb
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => David (chicolion)
--
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/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic,
** Changed in: linux (Ubuntu)
Assignee: David (chicolion) => (unassigned)
--
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/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic,
You have been subscribed to a public bug:
Black screen after grub menu, selected kernel 5.4.0-29-generic and can't
login, have to shut down laptop by pressing power button, or Alt + SysRq
+ REISUB(O), and when those dont work a hard power off.
I have installed linux-signed-oem-5.6 and
@stgraber sorry I should have clarified that I'm referring to Eoan specifically.
In Eoan, EFI_STUB is still not enabled. Is it needed there?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
Public bug reported:
I've Ubuntu 20 EOAN installed on a Toshiba Satellite laptop. I have connected
an external monitor screen connected to the laptop through the HDMI laptop's
output. The external monitor only works when I go into the BIOS and select
HDMI. However the laptop monitor does not
** Tags added: hwe-networking-wifi
--
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/1876963
Title:
Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04
Status in linux
Public bug reported:
Wifi is enabled with kernel 5.4.0-29, kernel -26 is correct.
The information was generated with kernel -26.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux
This feels related to
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665 which was
filed by amd64 users.
--
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/1876697
Title:
** Summary changed:
- fanotify09 case 3 from ubuntu_ltp_syscalls failed on Focal
+ fanotify09 case 3 from ubuntu_ltp_syscalls failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: 5.3 eoan
--
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/1876684
Title:
fanotify09 case 3 from ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-tests:
New
Status in
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/1877218
Title:
wifi disabled
Status in
** Summary changed:
- black screen before login on 5.4 kernel
+ [amdgpu] black screen before login on 5.4 kernel
** Tags added: amdgpu
** Summary changed:
- [amdgpu] black screen before login on 5.4 kernel
+ [amdgpu] black screen before login on 5.4 kernel, but iommu=soft fixes it
** Package
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/1877207
Title:
HDMI monitor
Status in linux
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You
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 1876835
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
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.
** Tags added: regression-release
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1875252
Title:
Ubuntu 20.04 LTS update
Probably a good idea to attach full dmesg here...
--
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/1876963
Title:
Broadcom [14e4:4320] BCM4306 (rev 03) Slow Wifi on Ubuntu Server 20.04
Yes, it is a bug.
I have a long time spent to are run Linux on this PC and no results.
It doesn't detect the second display in power saver mode in Nvidia options.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- [nvidia] Can't detect the second screen
+ [nvidia] External displays are only detected when in performance mode
** Description changed:
- Hi, I just reinstalled ubuntu.
- I did change from nvidia 440 driver to 435, since 440 didn't detect second
screen.
- There is
Hi,
Thank you all for your testing. We will investigate further the issues
reported by @benjamin-gemmill, but it seems to be a improvement already.
Regarding the issues with docker, it seems to be the same root cause as
the issue reported on bug 1876645. We are investigating it and we will
That patch was submitted as a fix for bug 1857257, which was applied for
Focal as well. Therefore this bug might affect Focal too, we are waiting
for some test results to confirm it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This issue could be found on 5.0 kernel as well.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Anyone knows who maintains the grub package shipped in the cloud-images?
Should we report a bug at https://bugs.launchpad.net/ubuntu/+source/grub2 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Could you take a screenshot of the notification?
--
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/1798166
Title:
“Mouse battery low” notification can't be disabled
Status in
>Can you share a bit more details about how you have yours setup?
Sure!
Partitions:
root@eu1 ~ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 9.1T 0 disk
├─sda1 8:10 9.1T 0 part
└─sda9 8:90 8M 0 part
sdb 8:16
I think commen #6 is correct: it looks the 2018 patch introduced the
issue for us, but the patch is originally for "initrd-less boot
capabilities." and here we do need the initramfs file.
I guess the patch "ubuntu-add-initrd-less-boot-fallback.patch" is not
included into the grub shipped in the
Updated: https://lists.ubuntu.com/archives/kernel-
team/2020-May/thread.html#109615
--
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/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow
On Tue, May 05, 2020 at 06:04:28PM -, Billy Olsen wrote:
> @bjornt Are you going to copy it over to the MAAS discourse feature set
> then?
We would prefer that one of the stakeholders actually would add it to
discourse. That will ensure that the stakeholders are still in the loop,
if there
The fix for this bug seems to be causing bug 1876645.
--
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/1857257
Title:
linux-image-5.0.0-35-generic breaks checkpointing of container
@pcworld @rhardy @benjamin-gemmill thank you very much for the feedback!
We will keep investigating about this bug.
--
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/1872001
Title:
Fix here:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109617.html
--
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/1857257
Title:
linux-image-5.0.0-35-generic breaks
verified on focal in machine bios ID 09FB thermald actived well.
kernel: 5.6.0-1010-oem
BIOS: 0.1.11
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Fix here:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109617.html
--
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/1876645
Title:
Unable to handle kernel pointer dereference in
** Also affects: linux (Ubuntu Focal)
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/1876645
Title:
Unable to handle kernel pointer
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Christian Brauner
I can reproduce this issue on Focal (5.4.0-30-generic) AMD64 KVM as well
with the ubuntu_docker_smoke_test:
4331.987024] general protection fault: [#1] SMP PTI
[ 4331.989188] CPU: 0 PID: 34912 Comm: dockerd Not tainted 5.4.0-30-generic
#34-Ubuntu
[ 4331.992158] Hardware name: QEMU Standard
You have been subscribed to a public bug:
Hi,
I am am experiencing slow wifi for a Linksys WMP54GS v1.0 wireless PCI
card with Ubuntu Server 20.04 installed, e.g. apt-get has taken 18
minutes 41 seconds to fetch 459Kb.
Following the advice from
https://ubuntuforums.org/showthread.php?t=2214110,
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/1877077
Title:
Bluetooth Not Working
Status
Public bug reported:
Earlier i was using window 10 on this system but as when i switch to
Ubuntu it doesn't show bluetooth device , as under my system setting
bluetooth On/Off button is greyed.And i'm not able to On/Off my system
bluetooth Please help
ProblemType: Bug
DistroRelease: Ubuntu
Public bug reported:
I would like to ask to backport following patch into ubuntu kernels:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=933db73351d359f74b14f4af095808260aff11f9
This bug silently corrupts memory in kmalloc-192 objects.
we observed several such
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 1877070
and then change the status of the bug to 'Confirmed'.
If, due to the
Receiving messaging from b43 module/driver:
"[ 164.945040] b43-pci-bridge :04:07.0: swiotlb buffer is full (sz:
55 bytes), total 0 (slots), used 0 (slots) (repeated 3 times)"
Wifi is very slow.
** Package changed: ubuntu => b43-fwcutter (Ubuntu)
--
You received this bug notification
https://bugzilla.kernel.org/attachment.cgi?id=288935=diff Works for me.
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1876707
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
When testing development kernels I usually rely on the installkernel
script either through the "make install" target of the Kernel source
or manually. This used to work great on Ubuntu on Z.
On Ubuntu 20.04 (freshly installed up to date) this fails
You have been subscribed to a public bug:
I installed Ubuntu 20.04 on IBM z15 with secure=1 in zipl conf.
System can be secure booted, /sys/firmware/ipl/secure shows "1".
I prepared zfcp dump disk as described in LTC bug 185713.
Stopped the system and performed a SCSI dump with "Enable Secure
@vmc, I've noticed the same with nvme, or at least not slower. It slowed
after the last update for 20.04 and updating the kernel to 5.40.0-29
however. it was almost 5 seconds faster with version -28
--
You received this bug notification because you are a member of Kernel
Packages, which is
@seppel Can you try if the patch https://lore.kernel.org/linux-
gpio/20200424091201.568-1-caizhaop...@uniontech.com/ fixes an issue?
--
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/1784152
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
According to the bug title this all should still land in 20.04?
Please notice that 20.04 got already released, hence the development is over
and the window to add new features is largely closed.
Requesting changes to an already released Ubuntu version is now strictly
regulated by the Stable
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
Verified linux-5.7=5.7.0-2.3+lp1876707 and linux-
oem-5.6=5.6.0-1010.10+lp1876707 in my ppa.
--
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/1876707
Title:
NULL pointer dereference in
@magean, I believe you are having a different issue here, so please
create a separate bug report, and, as you reproduced this with Linux 5.4
(also try https://kernel.ubuntu.com/~kernel-ppa/), contact linux-
p...@vger.kernel.org and the PCI subsystem maintainers directly, and
attach `dmesg` to your
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Add apport-collect 1876963 saved as a file attachment to bug report
** 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.
apport-collect 1876963 saved to file - unable to send wifi too slow
** Attachment added: "apport-collect 1876963 saved to file - unable to send
wifi too slow"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876963/+attachment/5367397/+files/apport.linux.7id7fsgb.apport
--
You
Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-May/thread.html#109623
Changing status to 'In Progress'.
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * An issue with the endianess handling in the Mellanox mlx5 driver was
+
So, although `pci=nommconf` gets rid of the error flood, it does
apparently make some collateral damage. After a few days under this
kernel parameter, the person who uses the laptop on a daily basis
reported a decrease in responsiveness and stability, with occasional
stutters if I understood
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
** Summary changed:
- installkernel script does not symlink /boot/initrd.img which is required with
the default zipl.conf
+ [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which
is required with the default zipl.conf
--
You received this bug notification because you are
Public bug reported:
When testing development kernels I usually rely on the installkernel
script either through the "make install" target of the Kernel source
or manually. This used to work great on Ubuntu on Z.
On Ubuntu 20.04 (freshly installed up to date) this fails however because
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug
Public bug reported:
I installed Ubuntu 20.04 on IBM z15 with secure=1 in zipl conf.
System can be secure booted, /sys/firmware/ipl/secure shows "1".
I prepared zfcp dump disk as described in LTC bug 185713.
Stopped the system and performed a SCSI dump with "Enable Secure Boot for
Linux"
We can either revert the path change in s390-tools or rebuild the
zfcpdump kernel flavour with the new name.
** Also affects: zfcpdump-kernel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
thanks for the feedback Zed, i will give this a shot.
It's so sad to see how laggy canonical is in fixing such a serious bugs, but
also how careless in introducing regressions such as this one.
I believe these wireless cards are extremely widespread, so i wonder how it's
possible not to catch
** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1859387
Title:
intel/sof: update the intel sof firmware to
** Package changed: linux (Ubuntu) => linux-base (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1877088
Title:
[UBUNTU 20.04] installkernel script does not symlink
After reading https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
filed the bug under linux package instead of b43-fwcutter since suspect
the issue is with the b43 driverand not the firmware installer
** Package changed: b43-fwcutter (Ubuntu) => linux (Ubuntu)
--
You received this bug
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 1876963
and then change the status of the bug to 'Confirmed'.
If, due to the
With the fixup patch applied, I could not reproduce the issue anymore on
both Eoan and Focal running ubuntu_fan_smoke_test and
ubuntu_docker_smoke_test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
--- Comment From thorsten.di...@de.ibm.com 2020-05-06 08:35 EDT---
>From LTC bug 185720 - LP1877089:
> We can either revert the path change in s390-tools or rebuild the zfcpdump
> kernel flavour with the new name.
This should IMO be decided by the s390tools maintainer! (I personally
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
--
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/1875254
Title:
Intermittent display blackouts on event
Status in
--- Comment From niklas.schne...@ibm.com 2020-05-06 08:06 EDT---
To add, I'm pretty sure this broke in a very recent change as we were using
the installkernel script extensively just last week.
Also I believe there is something in the usual kernel upgrade process that
hides this issue as
On Wed, May 06, 2020 at 10:32:19AM -, Kleber Sacilotto de Souza wrote:
> With the fixup patch applied, I could not reproduce the issue anymore on
> both Eoan and Focal running ubuntu_fan_smoke_test and
> ubuntu_docker_smoke_test.
Sweet, thank you and sorry for the rebase mess-up with Andrei's
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a
1 - 100 of 129 matches
Mail list logo
