** Also affects: mesa (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/1878670
Title:
Reproduceable i915 gpu hang Intel Iris Plus
Hi guys, more than months is passed, but Bug is still present even in the
latest Ubuntu 20.04
The same thing
BUG: kernel NULL pointer dereference, address: 0080
In redhat bug tracker text about the patch, eliminating this bug
(probably)
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/1880076
Title:
ubuntu 20.4 - retransmitts
Public bug reported:
Hi,
i run some network-tests (iperf3) and noticed massive retransmitts in
ubuntu 20.4 with kernel 5.4.0-29. I'm using module r8169 for network-
adapter
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
[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.
*** This bug is a duplicate of bug 1879893 ***
https://bugs.launchpad.net/bugs/1879893
Please use bug 1787338 / bug 1787332 / bug 1421808 / bug 1879893
It's unclear which this one is.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1879893 ***
https://bugs.launchpad.net/bugs/1879893
Looks closest to bug 1879893 so let's use that for now.
** This bug has been marked a duplicate of bug 1879893
GNOME crashed when resuming from sleep in NVIDIA performance mode with
disconnecting
(EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
(EE) NVIDIA(0): Failing initialization of X screen
...
(II) UnloadModule: "nvidia"
...
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
(EE) no screens found(EE)
** Tags added: hwe-graphics
--
You
hdajackretask did not help. Going to remove it now. Any other things i
should try ? This wasnt a problem in 18.04 but in 20.04 it is
irritating.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Marcos,
I think it would be a wonderful experience if you already hold the
chance to submit a patch to Ubuntu kernel yourself.
You may try following steps to send your patch:
1. `git clone -o focal https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal`
2. `git checkout
The current version is pulseaudio 1:13.99.1-1ubuntu3.2.
There is a fix/patch (Version: pulseaudio 1:13.99.1-1ubuntu3.2lp1869819)
in this PPA that you can use it for now until the next update/release:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819
Voila.
--
You received this
I confirm - still broken in 101. Hopefully the patch is reverted in the
next version :-)
--
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/1875916
Title:
upgrading to 4.15.0-99-generic
There are three patches in the aforementioned patchset 289291 in comment
#8:
* rtw88: coex: 8723d: set antanna control owner
* rtw88: coex: 8723d: handle BT inquiry cases
* rtw88: fix EAPOL 4-way failure by finish IQK earlier
However, the last one conflicts with the solutions for 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 1879287
and then change the status of the bug to 'Confirmed'.
If, due to the
** Summary changed:
- System sometimes starts with a black screen with Nvidia PRIME setup on
Ryzen+Nvidia system
+ [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME
setup on Ryzen+Nvidia system
** Tags added: amdgpu
** Summary changed:
- [nvidia+amdgpu] System
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/1880049
Title:
Using Lakka with Intel GVT-g
Public bug reported:
I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel
GVT-g and, when the graphics should start loading, the system freezes.
The command line used was:
The command line I used to start QEMU was:
sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none
Hi Steve, Julian, Łukasz, everyone,
Sorry that I didn't test the package on time – my life circumstances
have significantly changed since I reported this bug, nowadays I don't
have enough free time to do as much testing as I did back in the day.
I've been using the workaround ever since then,
version 1.4.6 of conntrack-tools now has passing autopkgtests again, but
it's still a concern if older versions of this package in LTS releases
are broken by newer versions of the kernel that are available as the hwe
kernel in those series.
--
You received this bug notification because you are a
Public bug reported:
Microsoft would like to request commits to enable VM hibernation in the
Azure 5.4 kernels for 18.04 and 20.04.
Some of the commits needed to enable VM hibernation were included in
mainline 5.4 and older. However, 24 commits were added in 5.5 and
later, which are required in
This was greatly debugged by LP user WGH in https://bugs.launchpad.net
/cloud-images/+bug/1573095/comments/46 - it's really a flaw on
initramfs, I managed to workaround the issue with "quiet" parameter
(system boots normally ,even with the wrong serial console).
Investigation continues... I guess
** Changed in: linux-aws (Ubuntu)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherme
@Ike: it looks like that patch depends on this other patch set, which is
currently in linux-next:
https://www.spinics.net/lists/linux-crypto/msg46951.html
To avoid backporting that, perhaps you could drop the qm_list
assignment.
That said, I don't see a valid SRU justification for any of
** Package changed: nvidia-prime (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/1879287
Title:
System sometimes starts with a black screen with Nvidia PRIME
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/1880012
Title:
ASUS UX533F overheating and
You have been subscribed to a public bug:
I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first issue
that this kind of setup gives on a fresh install is that that PRIME
render offloading doesn't work, I presume
** Summary changed:
- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1876196
Title:
apt info does not show the Supported: information for
** Package changed: 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/1880012
Title:
ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS
Status in linux
You have been subscribed to a public bug:
After installing Ubuntu 20.04 LTS, my laptop's temperature goes fairly
high without intensive CPU activity. The fan(s) remain **off** under
heavy CPU load and the temperature goes very high.
I don't suspect a material failure since I didn't notice such
Sound and microphone both fixed on my Dell Inspiron 7590 after doing
"sudo ln -s /lib/firmware/intel/sof/sof-cnl.ri /lib/firmware/intel/sof
/sof-cfl.ri". Thx!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Related public bugs found here and there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
https://github.com/systemd/systemd/issues/15783
https://github.com/systemd/systemd/issues/15656
** Bug watch added: Debian Bug tracker #960355
Not a kernel issue, moving to invalid for 'linux'.
** 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/1862028
Title:
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
Thanks for the tip. I have set my IntelliJ and GoLand settings properly
:)
--
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/1878670
Title:
Reproduceable i915 gpu hang Intel Iris Plus
It also affects Bionic HWE kernel 5.3.0-53
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1880004
Title:
can't boot from samsung sm961 nvme drive on 4.0.15-101
Status in
/var/log/audit.log on Suse logs the same:
type=AVC msg=audit(1590086639.489:8595): apparmor="DENIED"
operation="open" profile="snap.docker.dockerd" name="/entrypoint.sh"
pid=5656 comm="entrypoint.sh" requested_mask="r" denied_mask="r" fsuid=0
ouid=0
--
You received this bug notification
To confirm that this isn't shiftfs related and that we were just causing
the issue to be hidden, I've run the same test on OpenSuse tumbleweed.
I chose that distro because it's apparmor-enabled, has snapd and a 5.4
kernel.
```
localhost:~ # snap install docker
docker 18.09.9 from Canonical*
I can confirm that the workaround:
$ gsettings set org.gnome.settings-daemon.plugins.xsettings antialiasing
'grayscale'
followed by logout+login.
does stop the crashes.
Note:
To stop Intellij IDEA / Android Studio from crashing the system, it necessary
to set Antialiasing to Greyscale in
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 1880005
and then change the status of the bug to 'Confirmed'.
If, due to the
I'm Sorry, the kernel version written in the title is wrong, the kernel
version that fails is number 5.3.0-53.
--
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/1880005
Title:
Public bug reported:
I have installed Linux Mint Mate 19.3 (Tricia, 64-bits).
When I upgraded the Kernel to version 5.3.0-53, the on / off function
failed, the screen is off but the laptop is still working, the light of
manual shutdown button is still lit.
There is no problem with the previous
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1880004/+attachment/5375306/+files/screenshot.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Public bug reported:
Hang on /scripts/local-premount with timeout, completition polled.(see
attached "screenshot")
Reproduced on 2 systems using the same NVMe drive, I can boot using
older kernel. I was thinking it may be an initramfs issue so I rebuilt
the image for my older kernel but it still
Thanks @vicamo
I had a look at those documents.
If I understand correctly I’d need to either:
1. Ask for a cherry pick by commit hash
2. Provide the patch as a git diff myself - on the basis it’s been accepted
upstream.
I’ve also heard that lots of fixes are backported anyway to the various
This indeed disables Thunderbolt as described.
--
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/1836176
Title:
Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th
Status in
And, "console=ttyS0" on it's own is particularly bad because it seems to
default to a baud rate of 9600 (at least, setting it to 115200 on my NUC
improved things considerably, but the boot is still slower than without
the serial console option). Add that to the fact that the kernel is
quite noisy
I don't know yet if related, but I also observed the following:
syslog:May 21 17:25:27 ubuntu kernel: [0.00] random: get_random_bytes
called from start_kernel+0x99/0x4fd with crng_init=0
syslog:May 21 17:25:27 ubuntu kernel: [1.902484] random: lvm: uninitialized
urandom read (4
I observed the random kernel spew on my reproducer but I also want to
add that it was also noticed on my VMware impacted contact who brought
this up to my attention at the first place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
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 1879997
and then change the status of the bug to 'Confirmed'.
If, due to the
I have done the gsettings to grayscale
And my Xorg dying on me seems gone when I now try to reproduce the crashes :)
--
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/1878670
Title:
from dmesg (took from virsh dump)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=ttyS4
..
[1.053683] Warning: unable to open an initial console.
--
You received this bug notification because you are a member of
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+attachment/5375294/+files/journal.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel
5.3.0-53 update
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
*meant to say, whether receiver is on or off.
--
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/1879401
Title:
[XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI] sound
rarely
By the way, the TV I'm connecting to is an LG C9 running firmware
04.71.25 (current as of this writing) which is further connected to a
Sony STR-DH750 via HDMI ARC. I connect the laptop via the TV, not the
receiver, and problem persists whether TV is on or off.
--
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 1861941
and then change the status of the bug to 'Confirmed'.
If, due to the
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
Tested version_signature Ubuntu 5.3.0-53.47-generic 5.3.18.
Unfortunately the problem persists.
--
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/1879401
Title:
[XPS 13 7390 2-in-1, Intel
Digging deeper and walking through this in a focal vm, I'm seeing some
strange things.
Starting with a clean disk, and just creating the backing device like
so:
make-bcache -B /dev/vdb
We see /dev/bcache0 get created with vdb as the backing device. Now,
after this, I see:
/dev/bcache/by-uuid/
@Balint
I do not thing the fix you're released is correct, can you upload a new
version without the scripts?
Also, we should fix make-bcache -B to ensure that cset.uuid is not
initialized; that may be why the kernel thinks it should emit the
CACHED_UUID if the suerpblock of the device has a
** Tags removed: rls-gg-incoming
** Also affects: grub2 (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
I think the answer here is to stop passing "console=ttyS0". This is
something that is typically only done for debugging.
dmesg shows a 14 second delay between the "console [tty1] enabled" and
"console [ttyS0] enabled" messages. I suspect that because console=ttyS0
is passed the kernel is going to
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/1879989
Title:
"Failed to play sound: No
For reference, the other commit that fixed this is:
e4a58cdd069e6 ("clocksource/drivers/hyper-v: Untangle stimers and timesync from
clocksources")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
I see the fix is already included in Focal, from a different commit.
This bug can be closed.
--
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/bugs/1877647
Title:
Make sched clock return
Public bug reported:
my speakers- built in audio produces terrible sound
I tested the speakers via settings/sound and there was no sound
I checked gnome logs and found "Failed to play sound: No such driver"
I checked online and it seams to be a problem that affects many users
ProblemType: Bug
** Attachment added: "console_issue.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879987/+attachment/5375272/+files/console_issue.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Medium => 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/1879987
Title:
kernel get stuck at boot if specified 'console=ttyS* ' doesn't
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
I've managed to reproduce in 4.4, 4.15, 5.4 (all from Ubuntu releases)
and 5.7-rc4-next; also, I think bare-metal usually doesn't reproduce.
Seems like a live-lock situation, I'll attach some calltraces I gathered using
sysrqs.
Cheers,
Guilherme
--
You received this bug notification because
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
- Removing the non-existent
Public bug reported:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent 'console=ttyS*'
SRU request for the reverts:
https://lists.ubuntu.com/archives/kernel-team/2020-May/110122.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/1879690
Title:
Docker registry doesn't
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/1879981
Title:
touchpad does't work properly
Can you please test the 5.3 kernel, which is used in 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/1879401
Title:
[XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out, HDMI]
Public bug reported:
Ubuntu is installed on the Dell latitude 7480. This model has laptop with two
rows of buttons.
Lower row doesn't work at all since I installed ubuntu. Before this, with
Windows installed there was no problems.
Upper row works for some time after waking up, then it stops
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1877151
Title:
root unable to write to file in directory with sticky bit
I tested the PPA. It doesn't help. If anything, it might make things a
bit worse.
Also, I can now confirm that I spoke a bit too soon in comment #19 when
I said "linux-image-5.4.0-32-generic after removing kernel command line
pcie_aspm.policy=powersupersave --> seems better so far". That
I finally managed to install a beta image on a Thinkcentre m920 (by
removing the tpm module in grub before booting). Console output appears
at the 32s mark, see full dmesg below. Some interesting console-related
excerpts:
[0.049211] printk: console [tty1] enabled
[ 14.088918] printk:
Okay, pretty sure have found the right upstream bug, and have what looks
like a good workaround.
$ gsettings set org.gnome.settings-daemon.plugins.xsettings antialiasing
'grayscale'
https://gitlab.freedesktop.org/mesa/mesa/issues/2183
The steps to reproduce does kill the session with a gpu hang
I'm having trouble coming up with a pin to get the PPA to install with
apt update && apt upgrade. Why doesn't this work?
nbryant@atlantis:/etc/apt/preferences.d$ cat fix
Package: *
Pin: release o=LP-PPA-kaihengfeng-fix-lp1869819
Pin-Priority: 999
--
You received this bug notification because
Sorry, I got it! Priority needs to be 1000 or more for a "downgrade"
--
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/1879401
Title:
[XPS 13 7390 2-in-1, Intel Icelake HDMI, Digital Out,
This bug was fixed in the package linux-azure - 5.3.0-1022.23
---
linux-azure (5.3.0-1022.23) eoan; urgency=medium
* eoan/linux-azure: 5.3.0-1022.23 -proposed tracker (LP: #1877945)
[ Ubuntu: 5.3.0-53.47 ]
* eoan/linux: 5.3.0-53.47 -proposed tracker (LP: #1877257)
*
This bug was fixed in the package linux-raspi - 5.4.0-1011.11
---
linux-raspi (5.4.0-1011.11) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1011.11 -proposed tracker (LP: #1877517)
[ Ubuntu: 5.4.0-31.35 ]
* focal/linux: 5.4.0-31.35 -proposed tracker (LP: #1877253)
*
This bug was fixed in the package linux-raspi - 5.4.0-1011.11
---
linux-raspi (5.4.0-1011.11) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1011.11 -proposed tracker (LP: #1877517)
[ Ubuntu: 5.4.0-31.35 ]
* focal/linux: 5.4.0-31.35 -proposed tracker (LP: #1877253)
*
No that's gone now. Anywhere in the logs they would be written?
--
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/1879613
Title:
Computer hung when resuming from suspend
Status in linux
A photo, maybe?
--
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/1879613
Title:
Computer hung when resuming from suspend
Status in linux package in Ubuntu:
Incomplete
Bug description:
Could you attach your system journal of last boot?
1. Reboot to the problematic kernel
2. When it still fails to let you login, reboot to a working kernel,
3. Dump system journal:
$ journalctl -b -1 > journal.log
Attach that "journal.log" file here.
** Changed in: linux
** 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.
https://bugs.launchpad.net/bugs/1879690
Title:
Docker registry doesn't stay up and keeps
Where would they be?
--
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/1879613
Title:
Computer hung when resuming from suspend
Status in linux package in Ubuntu:
Incomplete
Bug
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/1879949
Title:
Can not log in
Status in
@Marcos, awesome!
If you're interested, Ubuntu SRU process is documented at:
https://wiki.ubuntu.com/StableReleaseUpdates
For kernel SRU patch format:
https://wiki.ubuntu.com/Kernel/Dev/KernelPatches
https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
We're also more than happy to help here if
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
Captured one, context from journalctl:
May 21 14:13:51 xps2020 kernel: [drm] GPU HANG: ecode 11:0:0x85db, in Xorg
[1985], reason: hang on rcs0, action: reset
May 21 14:13:51 xps2020 kernel: i915 :00:02.0: Resetting rcs0 for hang on
rcs0
May 21 14:13:54 xps2020 kernel: Asynchronous wait
Public bug reported:
I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to
5.4.0-31-generic I could not log in anymore. I was stuck in the display
manager. Then I rebooted into the old kernel and sent these reports. I'm
not sure if this is related but I can't put my display onto the
Can you please test this PPA:
https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819
--
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/1879401
Title:
[XPS 13 7390 2-in-1, Intel
@marcos-scriven thanks for going through the process of putting together
an upstream patch. I'm still manually applying the patch and building a
kernel from Ubuntu (git) sources each time a new kernel becomes
available. So hopefully this makes is into Ubuntu's 5.4 kernel (and
potentially kernels
1 - 100 of 168 matches
Mail list logo
