Hello Leo, or anyone else affected,
Accepted firmware-sof into plucky-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2025.01-1ubuntu1~25.04.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Hello Leo, or anyone else affected,
Accepted firmware-sof into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2023.12.1-1ubuntu1.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I’m also running Ubuntu 24.04 with kernel 6.11 on an ASUS ROG Zephyrus
G16 GU605MI laptop RTX4070
Same problem, I was able to resolve this issue with some grub parameters
GRUB_CMD_LINE_LINUX=quiet splash nvidia-drm.modeset=1
i915.enable_dpcd_backlight=1 nvidia.NVreg_EnableBacklightHandler=0
nvidi
I think these kinds of things are normally handled in the alsa-ucm-conf
package, so adding a task there.
** Also affects: alsa-ucm-conf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to a
The test plan should have noted this actually, but the way to test
upgrades using ubuntu-release-upgrader is:
$ do-release-upgrade --proposed
--
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
Hello Benjamin, or anyone else affected,
Accepted ubuntu-release-upgrader into plucky-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:25.04.17
in a few hours, and then in the -proposed repository.
Please help us by testing th
I think the reasoning for avoiding and upload to questing right now is
fair, and I think the plucky SRU should not be blocked by that.
** Changed in: ubuntu-release-upgrader (Ubuntu Plucky)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-plucky
Hello Bin, or anyone else affected,
Accepted alsa-ucm-conf into plucky-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.12-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Chris, or anyone else affected,
Accepted alsa-ucm-conf into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu5.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Bin, or anyone else affected,
Accepted alsa-ucm-conf into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu5.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello AaronMa, or anyone else affected,
Accepted alsa-ucm-conf into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu5.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Hello AaronMa, or anyone else affected,
Accepted alsa-ucm-conf into plucky-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.12-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Hello Chris, or anyone else affected,
Accepted alsa-ucm-conf into oracular-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu6.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Hello Chris, or anyone else affected,
Accepted alsa-ucm-conf into plucky-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.12-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Bin, or anyone else affected,
Accepted alsa-ucm-conf into oracular-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.10-1ubuntu6.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
I tested with plymouth 24.004.60-2ubuntu8 and systemd 257.6-1ubuntu1
(still in questing-proposed at the time of writing), and I still saw the
"/dev/x clean ..." message before the splash.
But then it occurred to me that systemd-fsck-root.service was skipped
because we have the following drop-in co
Given the fact that upstream systemd intentionally dropped MS_NOEXEC
from the /dev mount flags[1], and Debian did something similar[2], I am
marking this "Won't Fix" for systemd.
I don't see enough of a reason for Ubuntu to deviate here (at least in
src:systemd).
If anyone wants to push the case
Okay, thanks.
I am going to close the issue for now then. If it comes up again, please
open a new bug report.
** 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 U
Is this an issue on newer releases? From a first read it sounds like a
CLOCK_MONOTONIC vs CLOCK_BOOTTIME issue or something.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Package changed: ubuntu-release-upgrader (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/2109478
Title:
upgrade to 25.04 (plucky) finished, but boot failed
** 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/2107491
Title:
systemd-creds encryption/decryption doesn't work in a 24.04 co
** Package changed: ubuntu-release-upgrader (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/2101223
Title:
ubuntu 24.04.2 wireless does not work with RealTek wi
emd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
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/21022
** Changed in: systemd (Ubuntu)
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/2102236
Title:
plucky/s390x does not come up after kernel updat
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
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/2102236
Title:
plucky/s390x does not come up after kernel update + re
What are the contents of those rules? The names are very cryptic and
give me no indication of whether they are relevant here or not.
Maybe a red herring, but...
This is reminding me about
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2044104. Are
those rules generated/managed/whatever
Well if the boot fails because the root device is not found, then you're
getting stuck in the initrd, right?
Which means systemd has not been started - it's not in our initrd,
unless you're experimenting with dracut? And, udev (nor the rules I
mentioned above) is not responsible for *creating* the
Since this is quite an old bug, if we are going to target it to systemd,
can someone who is affected please open a fresh bug report?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
So /usr/lib/udev/rules.d/60-persistent-storage-dm.rules is responsible
for creating the /dev/disk/by-id/dm-uuid-* symlinks:
root@plucky:~# grep -rn "disk/by-id/dm-uuid" /usr/lib/udev/rules.d/
/usr/lib/udev/rules.d/60-persistent-storage-dm.rules:18:ENV{DM_UUID}=="?*",
SYMLINK+="disk/by-id/dm-uuid
** 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/2037667
Title:
Regression on Jammy's kernel 5.15 when cre
I re-verified the fix using systemd 249.11-0ubuntu3.15 from jammy-
proposed:
First, I confirmed that the bug was present without systemd from jammy-
proposed:
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15
19:18:46 UTC 2 x86_64 x86_64 x8
This test passes now:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/s/systemd/20250228_041633_efb81@/log.gz
In particular, we see:
467s autopkgtest [03:25:44]: test networkd-test.py:
[---
...SNIP...
600s test_resolved_domain_restricted_dns (__main__.D
** Tags removed: rls-pp-incoming
--
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/2099864
Title:
[p-m] depwait on riscv64 due to missing linux-bpf-dev in Ubuntu
Status in linux package in
already done
--
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/2099864
Title:
[p-m] depwait on riscv64 due to missing linux-bpf-dev in Ubuntu
Status in linux package in Ubuntu:
Invalid
S
My above comment is wrong. I (1) misunderstood how the riscv64 kernel is
built, and (2) missed the fact that we previously had a fallback for the
Build-Depends: linux-bpf-dev that was taking effect on riscv64.
So, this is a bug in systemd packaging only.
** Changed in: linux (Ubuntu)
Statu
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/2099864
Title:
[p-m] depwait on riscv64 due to missing linux-bpf-de
Something looks odd with the riscv64 linux builds[1]. This linux-bpf-dev
was previously available on riscv64. I see this in the log[2]:
Debug: binary-arch
dpkg-genbuildinfo --build=any -O../linux_6.12.0-15.15_riscv64.buildinfo
dpkg-genchanges --build=any -mLaunchpad Build Daemon
-O../linux_6.1
** Package changed: systemd (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/2098900
Title:
Ubuntu 24.10 Fails to Resume from Suspend on Lenovo Legion Y545
(NV
Updated the ubuntu-release-upgrader bug tasks to reflect that this is
something that will be fixed in jammy.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Jammy)
Importance: Undecided
Status: New
** Ch
Hi Masahiro. Thank you for following up. I want to let you and Aaron
know that I also tried 6.8.0-39-generic just today, and suspend works.
I wanted to rule out the chance that the issue was caused by my machine
having any defect in updating the kernel as 6.8.0-38 was so far the only
one that wo
** Tags removed: foundations-todo
--
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/2027847
Title:
Bump minimum /boot size in ubuntu-release-upgrader
Status in apt package in Ubun
I see a line in the kernel changelog under 6.8.0-40-generic.
- e1000e: change usleep_range to udelay in PHY mdic access
I think this may have to do with the following errors:
sudo dmesg | grep -i suspend
[1.106374] Low-power S0 idle used by default for system suspend
[1.502944] nvme
I want to add that I think it is an issue with the Ethernet interface
and Wake-on-LAN. After a lot of back and forth with ChatGPT, I was able
to (at least temporarily) get the device to suspend on 6.8.0-52.
$ sudo ethtool enp0s31f6 | grep "Wake-on"
Supports Wake-on: pumbg
Wake-on:
kernel I upgrade to has this
issue with the computer not suspending.
Below is the output of 'journalctl -u systemd-suspend.service' and 'inxi
-Fxxxz'
-- Boot c56d4ed7deaa466e96959bdee19f1a08 --
Jan 28 23:33:09 nick-ThinkPad-E14-Gen-6 systemd[1]: Starting
systemd-suspend.serv
Public bug reported:
`lsb_release -rd`
Output:
`No LSB modules are available.
Description:Linux Mint 22.1
Release:22.1`
Expected behavior:
That computer will suspend when clicking 'Suspend'.
What happens:
Screen goes black for a split second then immediately the computer wakes and
g
Can you please be more verbose with the test plan?
How do you confirm that the system is FIPS-enabled? Is this something I
should be able to test myself in a VM? If so, how do I enable "fips-
updates?" What is the failure mode I should see before testing your
proposed version of ubuntu-release-upg
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
+ [Impact]
+
systemd autopkgtests are failing in kinetic, and they are not considered
regressions. The failing test is one within networkd-test.py:
==
ERROR: test_resolved_domain_restricted_dns
Public bug reported:
got error messages during an "apt -y upgrade"
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-50-generic 6.8.0-50.51
ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12
Uname: Linux 6.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset
** Tags added: rls-jj-incoming
** Also affects: ubuntu-release-upgrader (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/2055825
Title:
Based on the many stack traces in dmesg, I think this is more likely a
kernel bug.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Adding a jammy task for systemd because I see the error there now. At
the very least I want to just skip the test in jammy to get a green
baseline again.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undeci
Public bug reported:
Under Software and Updates -> Additional Drivers, I have enabled the IPU6
Driver for the webcam
Now at least this seems to install without a crash
However, no application can detect a camera (Skype, Cheese, Gnome Camera)
If I query the devices, this is the output.
$ v4l2-ct
I verified the fix using systemd 249.11-0ubuntu3.13 in jammy-proposed.
First, I confirmed that my systemd and kernel combination is affected by
this bug:
$ uname -a
Linux clean-jammy-amd64 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/
The output of:
$ apt policy linux-image-generic
should show you where the kernel is installed from (e.g. jammy vs.
jammy-updates). However, based on the version numbers seen in $(uname
-r), it appears you are running 22.04 (jammy) on one machine, and 24.04
(noble) on another? Or, at least, the ke
*** This bug is a duplicate of bug 2085835 ***
https://bugs.launchpad.net/bugs/2085835
I believe this is a duplicate of bug 2085835.
** This bug has been marked a duplicate of bug 2085835
"Predictable Network Interface Naming" suddenly changed the name from
enp96s0f0 to enp96s0f0np0 causi
This probably belongs in ubuntu-raspi-settings, but one could construct
a /usr/lib/systemd/network/70-raspi-nic-default.link that matches based
on the available keys[1].
Then either set Name= or NamePolicy= as appropriate.
I don't think there is anything for systemd to do here, but if there is
so
** Package changed: systemd (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/2085732
Title:
Install media (from Startup Disk Creator) does not reboot
Status in
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Jammy)
Importance: High => 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/bu
** Description changed:
+ [Impact]
+
+ We noticed that some of Netplan's integration tests started to fail on
+ Jammy. These tests will try to create ip6gre and vti6 virtual interfaces
+ and systemd-networkd is failing to create them starting on kernel
+ 5.15.0-83.92. As far as I can tell, kernel
** Package changed: systemd (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/2077257
Title:
dev-tpmrm0.device failed -> slow boot
Status in linux package in Ubu
Re-adding a Linux task to see if anyone can confirm whether kernel
interface naming was changed between these two kernel versions.
--
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/2077159
Ti
By default, the NamePolicy=[1] (as configured in
/usr/lib/systemd/network/99-default.link) is:
[Link]
NamePolicy=keep kernel database onboard slot path
This means that if the kernel claims to assign a predictable name, then
that will take precedence over other policies, including the "onboard"
po
** Tags added: rls-nn-incoming
--
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/2078720
Title:
Upgrading from jammy to noble results in a linux-headers package being
in a broken stat
This does not sound like a systemd bug, but more like kernel or the
nouveau driver. From the attached CurrentDmesg.txt:
[ 248.207134] nouveau :01:00.0: Enabling HDA controller
[ 248.310486] [ cut here ]
[ 248.310488] WARNING: CPU: 0 PID: 1530 at kernel/workqueue.c:17
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Fix Committed
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_rang
itical
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags removed: systemd-sru-next
--
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/20581
** Tags added: rls-nn-incoming
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for
Fix for systemd to work around this:
https://github.com/systemd/systemd/pull/32341.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** T
Thank you! oem-6.5.0-1014 works
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058808
Title:
iwlwifi disconnect and crash - intel wifi7
Status in HWE Next:
In Progress
Status
Having this same issue now. Running Jammy kernel 6.5.0-1019-OEM. How
can I fix it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058808
Title:
iwlwifi disconnect and crash -
** Package changed: ubuntu-release-upgrader (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/2056784
Title:
I am facing this problem since last update
Status in
** 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/2017846
Title:
System kept waking up after pressing power button
Stat
*** This bug is a duplicate of bug 2037667 ***
https://bugs.launchpad.net/bugs/2037667
This sounds like a duplicate of 2037667, which is planned to be fixed
sometime soon-ish.
** This bug has been marked a duplicate of bug 2037667
Regression on Jammy's kernel 5.15 when creating ip6gre and
Closing bug report as the issue was fixed in the drivers included in
kernel 6.5.0-17.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https:
Integrated laptop screen is now detected and functions since upgrading
to kernel and hwe 6.5.0-17.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2050103
Title:
Integrated Laptop
AFAIK, the systemd-fsckd patch is still required, but we have vague
plans to get rid of it by making plymouth learn this functionality (i.e.
reading /run/systemd/fsck.progress directly). I have no idea about the
re-ordering, but it would be easy to test with a drop-in config.
** Changed in: system
Public bug reported:
i don't know why
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Arch
Integrated laptop screen not detected on kernel 6.5.0-15
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2050103
Title:
Integrated Laptop screen not detected on 6.5 hwe - Intel UH
** Attachment added: "Output from journalctl on kernel 6.5.0-15"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5742242/+files/journalctl_6.5.0-15
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
** Tags added: systemd-sru-next
--
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/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
tunnels
Status in linux p
** Attachment added: "Output from journalctl for boot to shutdown from kernel
6.5.0-14"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741576/+files/journalctl_6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is s
There is this gem in the journalctl from 6.5.0-14:-
journalctl_6.5:Jan 23 12:18:00 hybris kernel: i915 :00:02.0: [drm]
[ENCODER:94:DDI A/PHY A] HPD is down, disabling eDP
May explain why eDP is not enabled.
--
You received this bug notification because you are a member of Kernel
Packages, w
** Attachment added: "Output from journalctl for boot to shutdown from kernel
6.5.0-14"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741577/+files/journalctl_6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is s
** Attachment added: "Output from journalctl from boot to shutdown from kernel
6.2.0-39"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741578/+files/journalctl_6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is
Added Package
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2050103
Title:
Integrated Laptop screen not detected on 6.5 hwe
I'm back...same computer, but running Jammy this time, fresh install.
Everything works as expected!
For anyone else wondering, you will have to make sure you're using oem
kernel 6.5 and also have the jammy proposed linux-firmware package
installed.
sudo apt install linux-oem-22.04d
sudo apt ins
Fresh installed 23.10 Mantic on an HP Z2 Mini G9, I manually upgraded
the wifi card to the Intel BE200 a few weeks ago...no wifi detected at
all by default, although bluetooth was working ok.
Looked in dmesg and I saw it was complaining that there was no valid
firmware image for my wifi adapter.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-release-upgrader (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/2045407
T
** Package changed: ubuntu-release-upgrader (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/2042929
Title:
kernel ring buffer prints UBSAN: array-index-out-of-b
** Tags added: foundations-todo
--
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/1837227
Title:
systemd mount units fail during boot, while file system is correctly
mounted
Status in sy
** Also 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 Ubuntu.
https://bugs.launchpad.net/bugs/2038433
Title:
systemd autopkgtest regression on arm64 and s390
** Tags removed: rls-mm-incoming
** Tags added: foundations-todo
** Tags added: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) =
** Package changed: ubuntu-release-upgrader (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/2037068
Title:
Last several kernel upgrades all lead to unbootable k
** Package changed: ubuntu-release-upgrader (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/2034106
Title:
Bluetooth is scanning for devices but it does not fin
The deprecation of systemd-udev-settle.service has been in place since
at least v243[1], and upstream OpenZFS has been tracking this for a few
years[2].
I don't think anything should change in systemd WRT the deprecation
notice.
[1]
https://github.com/systemd/systemd/commit/1662732768d4846805bb0
** Package changed: systemd (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/2034068
Title:
Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers
Since I switched it back to AHCI mode in the BIOS, it has really
improved. In RAID mode, the drain is very noticable. I'll be interested
to know how you get on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Re-assigning since it sounds like this is not a systemd issue.
** Package changed: systemd (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/1988023
Title:
Could
** Changed in: systemd (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/2023401
Title:
[Dell XPS 17 9700] Upon shutdown, shutdown process doesn't com
1 - 100 of 534 matches
Mail list logo
