Verified that the behavior is the same when the laptop is used stand-
alone, unconnected to a docking station.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981727
Title:
For whatever reason I don't have crashdb.conf ...
kordosky@miketop5:~$ apport-collect 1981727
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 596, in
app = GTKUserInterface()
File "/usr/share/apport/apport-gtk", line 56, in __init__
Perhaps this comment from the changes log is relevant:
amd/display: set backlight only if required
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981727
Title:
kernel
Public bug reported:
After upgrading the kernel from 5.13.0-48 to 5.15.0-41, my external
monitor connected via HDMI wasn't detected. According to xrandr the
HDMI-1 output is "disconnected".
If I select the 5.13.0-52 kernel from the boot menu, then the HDMI
monitor works fine. Unfortunately, I am
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.13 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
Public bug reported:
It always happens to me when I open a program like "Mp3 Direct Cut" with
wine. (https://mpesch3.de/)
EDITION="Xfce"
DESCRIPTION="Linux Mint 20.3 Una"
System:Kernel: 5.13.0-52-generic x86_64 bits: 64 compiler: N/A Desktop:
Xfce 4.16.0
Distro: Linux Mint
Even I am also getting the same error log
[ 834.879658] [ cut here ]
[ 834.884279] NETDEV WATCHDOG: enx00249b305673 (ax88179_178a): transmit queue
0 timed out
[ 834.892287] WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:529
dev_watchdog+0x1fb/0x210
[ 834.900550]
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 1981723
and then change the status of the bug to 'Confirmed'.
If, due to the
For reference purposes, I'm attaching a dmesg log with debugging boot
options to:
- print initcalls entry/return
- print calls to __request_module() while the FIPS DRBG is uninitialized
Method / boot options:
fips=1
random.fips_urandom_drbg_crypto_noload=0
This commit appeared now in v5.15.46, which will be handled in the next
weeks by the kernel team.
But I change the title to 22.04, since 21.10 is EOL as of today, and this patch
is not in jammy.
It got upstream accepted with v5.19-rc1 hence no need to patch kinetic, since
kinetic's target
I have tried further boot cycles with the 5.15.0-40 kernel, abutnd have
not been able to achieve successful boot consistently. The problem is
the same for 5.15.0-41.
I may have been too hasty to conclude the problem is resolved in the
more recent kernel versions (patch levels).
--
You received
Thanks. If you can identify the exact revision 5.15.x or 5.16.y that
fixed it then that would be most helpful. But if you don't have time
then that's fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I had another look at my hibernation settings and realised my resume
offset was wrong in my /etc/default/grub. After updating this with the
value from command (found on
https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate):
~$ sudo filefrag -v /swapfile | awk '$1=="0:" {print
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1981727
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
A recent update to 5.15.0-41 results in my laptop screen (Dell Precision
7520) being unable to come up to full brightness. I have verified that I
can revert to 5.13.0-52 and the problem is not there. I looked at
/sys/class/backlight/nv_backlight/max_brightness which lists
@waveform thanks for this.
Separately will need to evaluate impact on small cloud instances. They
may have multiple cpu cores, x86, low memory, and many snap revisions.
I.e. 4-5 snaps, with 2-3 revisions of each.
I wonder if it will make sense to set multi_percpu on
x86/arm64/s390x/ppc64el
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 1981699
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package linux-lowlatency-hwe-5.15 -
5.15.0-42.45~20.04.1
---
linux-lowlatency-hwe-5.15 (5.15.0-42.45~20.04.1) focal; urgency=medium
* focal/linux-lowlatency-hwe-5.15: 5.15.0-42.45~20.04.1 -proposed tracker
(LP: #1981210)
*
** Summary changed:
- hwclock failed on 5.13 Oracle ARM64 bare-metal BM.Standard.A1.160
+ hwclock failed on 5.4 Oracle ARM64 bare-metal BM.Standard.A1.160
** Summary changed:
- hwclock failed on 5.4 Oracle ARM64 bare-metal BM.Standard.A1.160
+ hwclock failed on B-5.4 / F-5.4 Oracle ARM64
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Got it, thank you. It sounds like testing encrypted zfs performance
could perhaps be added to the validation suite for kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969482
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
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/1981699
Title:
ubuntu_ltp.mm:thp02 times out on
Actually we have 5.19 on the way in Ubuntu 22.10 so you don't need to do
anything more. We can declare it fix committed already.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
All autopkgtests for the newly accepted linux-meta (5.4.0.123.124) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/unknown (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding
FYI
There was a request on IRC to also promote firmware-sof
Moving that here to have an auditable trail why things were changed - also I
guess we'd want to have an explicit ack by the kernel team that this is the
very same case.
>From #ubuntu-release
[11:53] ubuntu-archive: Please move the
The dependency change is already done: linux-firmware recommends
firmware-sof-signed, that is built by the firmware-sof source package.
Please promote the firmware-sof source package (currently in restricted)
to main.
--
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.
Me too.
After the upgrade to:
linux-image-5.14.0-1044-oem
and continuing with
linux-image-5.14.0-1045-oem
the one VirtualBox VM (Windows 10) that I run has started throwing various
BSODs.
I tried a fresh Windows 10 install in a new VM (several times) under
linux-image-5.14.0-1045-oem.
problem reappeared on Ubuntu 5.15.0-41.44-generic 5.15.39 (upgraded to
that)
suspend does not resume, just a blank screen on displayport or HDMI.
system is a z390i Motherboard with i3-8350 (onboard graphics.) 32GB.
fresh install of 22.04 jammy (jellyfish Ubuntu 5.15.0-25.25-generic
5.15.30)
- I have installed GUI and checked the default display resolution was
1280*1024@75Hz---> While booting and
afterbooting external display not showing anything.
- Changed to display resolution 1152*864@75Hz ---> while booting not able to
see content on display but
Afterboot able to see
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-oem-5.14 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu.
Independent confirmation from me, with the same symptoms:
updated from kernel 5.13 to 5.15 today. After rebooting the system hangs
at "Loading ramdisk". I reverted to 5.13 and it started properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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 1981773
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1952385
Title:
Fix missing external headset after resume problem for
Public bug reported:
[Impact]
cm32181 ambient light sensor stops working after system suspend.
[Fix]
Add PM support for cm32181 so it can work after system suspend.
[Test]
The sysfs in_illuminance_input continues to change after system suspend.
[Where problems could occur]
This changeset is
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
While experimenting with FreeDOS and Windows PE, I discovered that
disabling UEFI mode (switching to Legacy mode) means I can now boot into
kernel 5.15. Certainly not a solution, but at least a workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which
Solved with Kernel upgrade to 5.15.0.41
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
Boot Failure - linux-image-5.13.0-28-generic | regression
Status in
All solved 5.15.0.41
--
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/1956467
Title:
powerlight stays on after shutdown
Status in linux package in Ubuntu:
Confirmed
Bug description:
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939886
Title:
Network connection can't come
Public bug reported:
Sometime in sleep mode it is giving some error messages.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1045-oem 5.14.0-1045.51
ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21
Uname: Linux 5.14.0-1045-oem x86_64
NonfreeKernelModules:
** Tags removed: impish
--
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/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not
autoconnecting on power-on on 22.04
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thanks for replying to my issue.
I tried the workaround you specified but it didn't work for me.
--
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/1976473
Title:
Unable to change screen
Public bug reported:
With kernel linux-image-5.14.0-1042-oem VirtualBox VM runs stable
With kernel linux-image-5.14.0-1044-oem VirtualBox VM crashed constantly
Wiht kernel linux-image-5.14.0-1045-oem VirtualBox VM crash multiple times a day
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
** Changed in: libinput (Ubuntu)
Status: New => 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/1950471
Title:
Touchpad on HP Spectre x360 gets into unusable state
Status
I have tried both kernels and can happily say the issue does not exist!
It's so snappy now, much faster than Windows 11.
Sorry for wasting your time, I should've tried newer kernels before
opening a bug report. I'm not sure how to close the bug report.
--
You received this bug notification
It is actually Intel-signed SOF firmware.
** Changed in: firmware-sof (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/1956104
Title:
No problem - this bug is still open and still valid. If you have time
then please try to figure out which kernel version fixed it between 5.15
and 5.18.11 ...
https://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member of Kernel
Packages, which
5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
Jul 14 10:35:45 pluton kernel: [22004.577865] [ cut here
]
Jul 14 10:35:45 pluton kernel: [22004.577873] Invalid rxb from HW 0
Jul 14 10:35:45 pluton kernel: [22004.578011]
Mark as incomplete as per requests in comment #6
Also note that 21.10 will reach its End-Of-Life this month. It's better
to give newer release a try.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
This test can pass with 5.15.0-1013.17~20.04.1 on this very same node.
** Tags added: sru-20220620
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1971215
Title:
hwclock failed
I have tried 5.17 and 5.16. The issue is not there. It's not fixed on
5.15.54 too. So it's fixed somewhere between 5.15 and 5.16.
--
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/1981559
56 matches
Mail list logo
