All autopkgtests for the newly accepted linux-meta-lowlatency (6.2.0.1005.5)
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64)
linux-lowlatency/6.2.0-1005.5 (amd64, arm64)
@John, could you switch to another router for verification?
--
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/2022826
Title:
Ethernet hangs
Status in linux-firmware package in
All autopkgtests for the newly accepted linux-meta-azure (6.2.0.1005.5) for
lunar have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/252.5-2ubuntu3 (amd64, arm64)
Please visit the excuses page listed below and investigate 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
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
All autopkgtests for the newly accepted linux-meta-aws (6.2.0.1005.6) for lunar
have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64)
systemd/252.5-2ubuntu3 (amd64, arm64)
Please visit the
All autopkgtests for the newly accepted linux-meta-gke-5.15
(5.15.0.1036.41~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gke-5.15/5.15.0-1036.41~20.04.1 (arm64)
systemd/245.4-4ubuntu3.21 (arm64)
Please visit the
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2016908
Title:
udev fails to make prctl() syscall with
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
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 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-jammy' to
'verification-done-jammy'. If the problem
Upon further investigation, this is an issue that the package "xserver-
xorg-video-vmware" causes to start happening, as on a perfectly fine
working Kubuntu 22.04 installing that package only, and restarting,
causes the issue to be immediately reproducible, versus non-reproducible
without that
A friend of mine also just reproduced the same issue just now on Kubuntu
22.04.2 LTS (a fresh Ubuntu 22.04.2 installation with kubuntu-desktop
installed onto it, more-so) using VMWare 16.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Can reproduce the exact same issue on Feren OS 2023.07 Alpha 2, with the
exact same kernel version causing the issue and the exact same last
working kernel version as the OP states.
For Feren OS, it triggers upon a window spawning in KDE Plasma.
--
You received this bug notification because you
** Changed in: linux-kvm (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Changed in: linux-kvm (Ubuntu)
Status: New => Fix Committed
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a
> I filed a bug about this with the MySQL project back in April. They
closed it as 'not a bug'.
> https://bugs.mysql.com/bug.php?id=110752=2=67
FWIW we got MySQL to at least acknowledge/verify the issue. So they may
end up fixing this themselves.
--
You received this bug notification because
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
Interesting, maybe something is triggering a controlled shutdown for some
reason then? For context, here's what I'm seeing:
https://drive.google.com/file/d/1OlPV7akUgekD9-rl1gsMes_zhO68aius/view?usp=sharing
My gnome shell is now crashing while trying to upload the crash file for
the gnome crash,
All autopkgtests for the newly accepted linux-meta-kvm (6.2.0.1006.6) for lunar
have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64)
lttng-modules/2.13.8-1 (amd64)
Hi Jon we recently identified regressions in our kernels that breaks
WiFi, which very well could be what you are experiencing here.
We should have a new Jammy-hwe kernel 5.19.0-45.46~22.04.1 in ~proposed
on Monday which should fix this issue.
- Luke
--
You received this bug notification
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2021830
Title:
GVE: Performance improvement for
I do see the behavior you are describing in those logs:
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:35:45
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2019240
Title:
Pull-request to address a
** Package changed: ubuntu => linux-firmware (Ubuntu)
--
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/2023396
Title:
After an Ubuntu Update, the WiFi was not working. When
This bug is awaiting verification that the linux-gke/5.15.0-1036.41
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-gke/5.15.0-1036.41
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-
gke-5.15/5.15.0-1036.41~20.04.1 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
This bug is stale, and it remains unclear if there is a systemd bug, so
marking invalid.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: systemd (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/1979352
Title:
system frozen after sleep
Status in Ubuntu MATE:
All autopkgtests for the newly accepted glibc (2.35-0ubuntu3.2) for jammy have
finished running.
The following regressions have been reported in tests triggered by the package:
adsys/0.9.2~22.04.1 (armhf)
bbmap/38.95+dfsg-1 (armhf)
boost1.74/1.74.0-14ubuntu3 (armhf)
breezy/3.2.1+bzr7585-1build1
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in
Ubuntu.
https://bugs.launchpad.net/bugs/2023394
Title:
package linux-modules-nvidia-530-5.19.0-44-generic
Public bug reported:
the version reported that there is a new update so when i tried to
install this new update it gave me this error mentioned in the summary .
am using DellG15 5520 RTX3050 there is a lot of bugs related to the
NVIDIA drivers which is affecting the performance of the laptop so
kprobe_events are not available (seems related to CONFIG_KALLSYMS disabled) and
this test `tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc`
doesn't seems to works well in this case as it fails quickly:
```
+ echo e:egroup/eevent syscalls/sys_enter_openat
Public bug reported:
Summary:
LOC, IWI, RES and CAL interrupts are observed on isolated cores on which
low-latency benchmark is performed. Interrupts are caused by simple Go
application (printing "Hello world" every 1 second) which runs on different,
non-isolated cores. Similar Python
Archive contained all files/scripts/results mentioned
** Attachment added: "Archive contained and files/scripts/results mentioned"
https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2023391/+attachment/5678810/+files/files.zip
--
You received this bug notification because you
** No longer affects: u-boot-nezha (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-allwinner in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in linux-allwinner package in Ubuntu:
** Changed in: u-boot-nezha (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1975592
Title:
Enable Nezha board
Status in
> The build at
https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.33-0ubuntu2 passed
for armhf and MTR/CI did not fail. Why is it failing for users then?
The tests are disabled on armhf:
ifneq (,$(filter $(ARCH), amd64 i386))
TESTSUITE_FAIL_CMD:=exit 1
else
TESTSUITE_FAIL_CMD:=true
endif
@juergh
Tech Support Realtek told me to disable Secure Boot which I have done. I was
then able to compile & install r8125, r8128 & r8128 modules obtained from
Realtek website. 'lsmod | grep r81' showed all 3 modules. ifconfig showed the
ethernet interface Ok (as enp3s0). However, ethernet still
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy
** Tags added: verification-done verification-done-jammy
verification-needed-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
linux-raspi 5.4 in Focal is the first kernel that supports Pi 4B which
requires LPAE to be enabled for armhf. Since we currently don't support
board-specific kernels but follow a one-kernel-fits-all strategy, the
LPAE kernel is also used on Pi 3 and 2 boards. Back then,
55 matches
Mail list logo
