The OEM update fixed the issue, thanks!!!
No more using my dongle, so I'm very pleased with the result.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886247
Title:
Realtek [10
rcu_access_pointer(sk->sk_filter) is basically the same as
sk->sk_filter.
If sk->sk_filter is true, the change makes no difference.
If sk->sk_filter is false, the change also drops a UDP packet with incorrect
UDP checksum by "goto csum_error;". Without the change, the packet is dropped
in udp_re
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[Expired for linux-meta (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-meta (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-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/17797
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 1888715
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Hello Dexuan, wonderful, thanks;
Eric's proposed patch confuses me on one point:
- if (rcu_access_pointer(sk->sk_filter) &&
- udp_lib_checksum_complete(skb))
+ if (udp_lib_checksum_complete(skb))
goto csum_error;
Do you know why the rcu_access_pointer() call
I also encountered this issue, with ubuntu 18.04 and intel AX200NGW
Bluetooth. Would be willing to help provide debugging logs if needed.
--
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/1859
This happened to me as well. Luckily I have an ethernet port on my
laptop and was able to find a drop so I could apply this fix. Guessing
the update blew a bunch of people out of the water. The ppa provided did
fix the issue.
--
You received this bug notification because you are a member of Kerne
Had the exact same error today. Was able to solve it via:
sudo ubuntu-drivers autoinstall
then rebooting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1888617
Title
In some cases this appears to be linked to the use of s2-idle.
If you only see s2-idle when you run cat /sys/power/mem_sleep, then try
these steps:
https://gitlab.freedesktop.org/drm/amd/-/issues/1230#note_580057
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1230
https://gitlab
** Bug watch added: Linux Kernel Bug Tracker #208615
https://bugzilla.kernel.org/show_bug.cgi?id=208615
--
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/1690085
Title:
Ryzen 1800X freez
Have you tried the suggested fixes in this thread? And what changed
between that reinstall and earlier?
On 7/24/20 4:17 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196683
>
> Victor Queiroz (victorcqueir...@gmail.com) changed:
>
> What
I'm also experiencing severe and constant crashes with a Ryzen 5 3600X.
I also had problems with my Ryzen 7 1700 and I was confident that the
problem was never going to have problems again with my Ryzen 5 3600X,
but I was wrong.
First months everything was fine, and after reinstalling the system,
Correction to #19. The kernel is available @
https://people.canonical.com/~alexhung/LP1888570/19357b3b0835/
--
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/1888570
Title:
poweroff not wor
Thanks for reporting this, and your help is needed to identify the patch
that causes this regression.
There are 260 patches between 5.3.0-61 & 5.3.0-62, and it requires some
testing with bisects (see below).
$ git bisect start
$ git bisect good Ubuntu-5.3.0-61.55
$ git bisect bad Ubuntu-5.3.0-62.
** Description changed:
+ SRU Justification
- 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
+
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 from
monotonic-time is no longer tested in the SRU cycles
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Invalid
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
We no longer test with the A1 Instances due to problems like this, A1 is
an extremely minimal, low resource instance. We should not be offlining
cpu and memory in these VMs.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux-signed-azure (Ubuntu)
Status:
As the ecryptfs support has been dropped in
Bionic+(https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798359)
marking bug invalid
** Changed in: ecryptfs
Status: Triaged => Invalid
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
You received this bug notification b
Xenial 4.4.0-187.217
1. 07/22 20:20:47 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t
extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f
btrfs'
2. 07/22 20:21:13 DEBUG| utils:0153| [stdout] extend-file-random pass
3. 07/22 20:21:13 DEBUG| utils:0153|
** Changed in: ecryptfs
Assignee: Tyler Hicks (tyhicks) => (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/1765653
Title:
directory-concurrent.sh.ext4 in ubuntu_ecryptfs
This bug report got stuck with wrong "Fix Released"!
@kmously and @vicamo:
Please could you set the status back to "In Progress"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/186
Marking this as invalid, referenced bugs are all closed and pretty sure
this is not a problem on arm64 any longer.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you a
Same here, appeared today after system update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1888617
Title:
nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidi
I have not seen this occur on the -aws nitro backed arm64 instances.
Giving that mcdivitt is EOL, killing off this bug.
07/09 11:08:48 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64):
PASS
07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race shared
(2M: 64): PAS
** Changed in: systemd (Ubuntu)
Status: Fix Committed => 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/1776654
Title:
systemd upstream sysusers tests fails
Status i
Seemingly related report on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=98321
** Bug watch added: Linux Kernel Bug Tracker #98321
https://bugzilla.kernel.org/show_bug.cgi?id=98321
--
You received this bug notification because you are a member of Kernel
Packages, which is
I don't know how to edit posts but I wanted to add:
I plugged a different m.2 NVMe from a different manufacturer into the
"M2A_32G" port to see if the port is the problem. There are no errors. I
can only replicate the problem with the XPG NVMe in port "M2A_32G".
** Attachment added: "Z370 AORUS G
@colin-king @juliank
It feels to me that the oem flavour should default to
(powersave/ondemand), as it is more-or-less laptop kernel flavour.
I feel like generic kernel flavour should remain on performance.
I feel like we should have a unit, that for chassis=laptop turns on
(powersave/ondemand).
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
I pulled all the hardware from my PC and went through each part one by
one. The device that makes these errors appear is the XPG GAMMIX S5 m.2
when plugged into port "M2A_32G". I moved the m.2 device to port
"M2P_32G" and the errors disa
I updated yesterday and I encounter the same crash. The result is a
login loop problem in my main user and a fixed display resolution
problem. Can you recommend a temporary fix ?
Last part of nvidia-kernel-source-435.0.crash
/nvidia-drm/nvidia-drm-helper.c
/var/lib/dkms/nvidia/435.21/build/nvidi
Verification done on "Disco" (linux-hwe-5.0)
---
# uname -rv
5.0.0-58-generic #62~18.04.1-Ubuntu SMP Tue Jul 14 03:37:30 UTC 2020
For some other reason the kprobes module is not picking up on accept,
only on release. This is unrelated to this patchset.
I used kprobe events instead, which is work
--- Comment From ma...@de.ibm.com 2020-07-24 12:54 EDT---
zfcp regression tested the private build from
https://people.canonical.com/~fheimes/lp1887774/.
(The private build seems to have the same kernelrelease as the latest official
update kernel. I removed the latter after going to the
@Colin: I agree with all of that.
Our kernel-side default is not powersave, but performance, across
generic and oem, at the very least:
$ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.*
/boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.4.0-42-generic:CONFIG_CP
The choice was made from running analysis on a wide range of Intel
machines, old and new. We are trying to select the optimal choice for a
wide range of CPUs for a wide range of use cases. Generally speaking,
the intel-pstate governor has deeper understanding of the processor
features and can acces
Hello,
I think I am experiencing the same issue so I am not opening a new bug
report. Below is the description I also posted a question about:
I have upgraded to Kubuntu 20.04 from 19.10. Session went ok but after
rebooting I noticed one or two times where my screen (external monitor
connected vi
Just commenting to say I have the same problem with Dell XPS 15 2-in-1
9575, BIOS version 1.12.1. The problem was indeed fixed with
blacklisting intel_vbtn. Using Fedora 32.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Done - please note that during the execution of the previous step
"apport-collect 1888703" I used the 5.3.0-62-generic kernel and not the
problematic one 5.4.0-42-generic as the screen is hard to decipher.
Please let me know if you would like me to go through the effort again
using the problematic
The issue still exist on 4.15.0-1092-azure, probably I just verify the
basic nested vm scenario against 4.15.0-1091-azure, will double check.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395590/+files/CurrentDmesg.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
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395597/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395593/+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/1888703
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395600/+files/UdevDb.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/1888703
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395591/+files/IwConfig.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/18
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395599/+files/PulseList.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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395601/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395592/+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/1888703
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395596/+files/ProcEnviron.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/b
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395589/+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/1888703
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395594/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395598/+files/ProcModules.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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1888703/+attachment/5395595/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Tags added: apport-collected
** Description changed:
Everything else works well in the system except for this issue. See
attached picture for details.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus (not installed)
ProcVersionSignature: Ubuntu
Ubuntu 20.04
for me the problem started after upgrading to the kernel version
5.4.0-42-generic,
I noticed it because the boot up failed once.
--
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
--- Comment From s...@de.ibm.com 2020-07-24 10:47 EDT---
I've found the relevant code. It's the flatpak package. For a test on my s390x
machine, I've just changed the check from arg 0 to arg 1:
diff -uNr ./flatpak-1.6.3/common/flatpak-run.orig.c
./flatpak-1.6.3/common/flatpak-run.c
--- .
I've fixed this issue on my Asus UX550VE, Ubuntu 20.04, kernel 5.4.0-42.
I followed Optiman's instructions, which are supposed to "activate
bottom speakers" using jack retasking:
https://askubuntu.com/questions/973690/my-volume-is-either-max-volume-
or-muted-no-middle-ground
--
You received this
For what it is worth, I also have the same enncryption aes256-cts-hmac-
sha1-96 (and same problem). The tickets come from MIT Kerberos on
Ubuntu 18.04; the NFS servers are Ubuntu 18.04 using krb5p security
option.
--
You received this bug notification because you are a member of Kernel
Packages,
Removing nomodeset reverts back to the original screen flickering problem
with almost zero usability. Are there any other solutions to this?
On Thu, Jul 23, 2020 at 9:10 PM Daniel van Vugt <1888...@bugs.launchpad.net>
wrote:
> "nomodeset" will disable all hardware graphics support so it will use
The enctypes according to klist are: Etype (skey, tkt): aes256-cts-hmac-
sha1-96, aes256-cts-hmac-sha1-96. The kerberos tickets come from Active
Directory server and NFS servers are NetApps, if that matters.
--
You received this bug notification because you are a member of Kernel
Packages, which
This also affects Ubuntu Bionic, if linux-generic-hwe-18.04 is
installed. The 4.15.0-112-generic works fine.
--
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/1886277
Title:
Regression on N
--- Comment From jan.hoepp...@de.ibm.com 2020-07-24 06:10 EDT---
(In reply to comment #29)
> I just wanted to try the kernel that I've build yesterday (see comment #6)
> and as a first step I wanted to recreate re-create the described error
> situation on an up to date 20.04 system:
> $ lsb
Checked on the following kernels, this is not failing anymore:
aws 5.4.0-1020.20~18.04.2-aws
aws 5.3.0-1032.34~18.04.1
aws 5.3.0-1032.34
aws 4.15.0-1079.83
aws-fips 4.15.0-2023.23
aws 4.15.0-1079.83~16.04.1
aws 4.4.0-.123
gcp 5.4.0-1021.21~18.04.1
gcp 5.3.0-1032.34~18.04.1
gke 5.3.0-1032.34~18.
** Summary changed:
- RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels
+ rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels
(config not enabled)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This test will need:
CONFIG_DUMMY
CONFIG_NETDEVSIM
To be set to either Y or M.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812194
Title:
RTNETLINK in net from ubuntu_kernel_self
For comment #6, install the module-extra package can solve this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1812978
Title:
rtnetlink.sh in net from ubuntu_kernel_selftest
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 1888703
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: linux-aws (Ubuntu)
Status: New => Triaged
** Changed in: linux-aws (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux-aws (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix Committed
** Changed in
Thanks, reassigning to the linux component since you say it's a kernel
bug
** Package changed: nautilus (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888703
T
You have been subscribed to a public bug:
Everything else works well in the system except for this issue. See
attached picture for details.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux
As Eoan has EOL'ed, I am applying the fix directly to bionic/linux-
raspi2-5.3 and will re-spin it.
** Also affects: linux-raspi2-5.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi2-5.3 (Ubuntu Eoan)
Status: New => Invalid
** Changed in: linux-raspi2-5.3 (
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-raspi - 5.4.0-1015.15
---
linux-raspi (5.4.0-1015.15) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-meta-raspi - 5.4.0.1015.50
---
linux-meta-raspi (5.4.0.1015.50) focal; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] Add transitionals for HWE kernels
linux-meta-raspi (5.4.0.1015.16) focal; urgency=medium
* Bump ABI 5.4.
I just got a fenvi FV-AX3000 card, which at its core uses an Intel
AX200. I was getting the same log from the kernel as above with RT
ucode: -110, until I did some more snooping around.
I originally plugged in the card to one of the x16 slots on my
motherboard (Gigabyte Z77X-UD5H motherboard, CPU
jeremyszu,
That's a crash in gnome-control-center occurring at the same time as a
black screen. It's correlation of two issues, not causation of one by
the other...
Please report the crash in a new bug using these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.
@Marco,
Hi, here is the steps when verifying mutter from focal-proposed:
1. Upgrade all packages to latest version in focal-updates.
2. Enable focal-proposed in source list
3. sudo apt install mutter
4. Configure external screen orientation by selecting "Portrait Right"
5. Screen orientation does
Public bug reported:
zfs-mount --configure fails at upgrade
The error is:
Configurazione di zfsutils-linux (0.8.3-1ubuntu12.2)...
zfs-import-scan.service is a disabled or a static unit, not starting it.
zfs-import-scan.service is a disabled or a static unit, not starting it.
Job for zfs-mount.se
86 matches
Mail list logo
