Hello Brad, or anyone else affected,
Accepted kdump-tools into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/kdump-
tools/1:1.6.10ubuntu2.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Brad, or anyone else affected,
Accepted kdump-tools into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/kdump-
tools/1:1.8.1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
@Juerg,
Hi, since it takes an additional commit (fw rev 36 -> 37) to fix it, I
have resubmitted SRU pull request to Mantic with only one commit atop of
currecnt Mantic HEAD. For Jammy, four commits resubmitted.
SRU:
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/11 (jammy)
*
You have an unsupported DKMS module (virtualbox) installed that breaks
the kernel headers installation. Please remove it:
$ dkms remove virtualbox
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
Building module:
Cleaning build area...
make -j8 KERNELRELEASE=6.6.0-14-generic -C /lib/modules/6.6.0-14-generic/build
M=/var/lib/dkms/virtualbox/6.1.38/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.6.0-14-generic (x86_64)
Consult
> It is expected to be released in 2 weeks
Thanks! Is there anywhere we can get access to a proposed/pre-release
package with the fix inside to verify that it fixes the issue in our CI?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Mantic)
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/2045233
Title:
[SRU][22.04.04]: mpi3mr driver update
MAntic is fixed with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027
Title:
The display becomes frozen
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
It is expected to be released in 2 weeks
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
The way it is currently done, I don't think valid CPU frequency listing
via "scaling_cur_freq", or /proc/cpuinfo, is expected to work. Why not?
Because the required code is never executed, on purpose. Here is an
excerpt from a commit (see the bit about NOHZ full)
commit
CPU frequency scaling driver: intel_pstate
CPU frequency scaling governor: powersave
HWP: disabled.
Purpose to verify that the driver is working correctly, regardless of CPU
frequencies reported.
A single threaded load was applied to CPU 5 at 347 hertz sleep/work frequency.
The load was
** Tags added: originate-from-2000353
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2051199
Title:
Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
The blanking from GRUB_TIMEOUT>0 will be made much worse by
CONFIG_FB_EFI=n because usually in Ubuntu it's the efifb that restores
the logo after Grub has wiped it. I think not having CONFIG_FB_EFI at
the same time as using GRUB_TIMEOUT>0 explains your previous "really
long time of a black
Okay, I'll try to see what the tools say, but so far it happens only
when the computer is left at the login for a while. This is the page
where various users can login, so technically only background processes
are running.
I've tried multiple times to catch it in the act, but never successful.
Public bug reported:
[Impact]
Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified.
[Fix]
Validate max connection interval to pass test case
"GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid
Parameters Central Responder'"
[Test]
Run the test suite. With the
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: New => Invalid
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing
a modeset for some reason.
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.
Here's various artifacts if you want
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black
screen.
Moving that to zero certainly helps. It's a lot better; but still not perfect.
Let me get things back to as close as possible to stock and capture logs and a
videos to compare with Ubuntu and Fedora with this exact
Installed the proposed kernel (1014) to some lenovo/dell/hp machines,
the audio worked as well as before. verification done.
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a
The slow login is unrelated to this bug. Please open a new bug for that.
--
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/2051450
Title:
Nouveau kernel errors prevent reaching the
GRUB_TIMEOUT > 0 also causes the vendor logo to be replaced by a black
screen, but that seems to be Grub's fault. Default Ubuntu won't have
that problem since it ships GRUB_TIMEOUT=0. And if you want a nonzero
timeout without the blackness then GRUB_TERMINAL=console is a
workaround.
--
You
This bug has been closed for over 14 years so if you have any current
issues then please open new bugs for each of them.
--
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/241000
Title:
I think that's a different bug. I believe it's when plymouthd is
starting and is the handover (mode set?) from efifb to DRM. It doesn't
happen at all if you add "nomodeset" (please try that).
"Really long time" might be subjective though? How long?
VT switches (or more accurately virtual console
** Changed in: libpcap (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: libpcap (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.
Hello, I suspect this is more likely a program on your computer acting
poorly.
I suggest trying a few different tools from the bpfcc-tools package:
- opensnoop-bpfcc
- filelife-bpfcc
- dirtop-bpfcc
- filetop-bpfcc
Thanks
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/2049768
Title:
my computer doesnt start
Status in linux package in Ubuntu:
Thanks Daniel Letzesien that worked
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-* FTBS with linux 6.5
Status in
I tested it on Noble with a hand built kernel and it at least does what
you planned (don't see any console messages), but also I'm not seeing
the OEM vendor logo stick all the way through. There's a really long
time of a black screen. Not sure if this is because it was an upstream
kernel and
Public bug reported:
If left at the login screen, after a day or so, /tmp seems to fill up on
its own. It will show an X window message upon login regarding /tmp,
then any applications, like LibreOffice, won't run. The files don't
shows up using du, likely because it's a tmpfs type.
ProblemType:
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2051457
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (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/2051457
Flash-kernel contains a database matching device-tree machine values
with devicetree names.
There is no necessity to remove entries for architectures that are not
supported in Ubuntu. We should try to minimize the differences to
Debian. So setting this to won't fix for flash-kernel.
** Changed
We ran into a similar issue since Ubuntu 22.04.3 moved from linux-6.2.y to
6.5.y for linux-generic-hwe-22.04.
The corresponding dkms package rtl8821ce-dkms-5.5.2.1-0ubuntu11~0.22.04.1
unsurprisingly no longer compiles due to quite a number of kernel API changes.
Btw, we're currently considering
For what it's worth, we've been running a file server for several weeks
with the 2.1.14 .ko files in 22.04 with no problem. I didn't try to
cherry pick the one fix as I'd prefer to have the whole 2.1.14.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Reviewed zfs-linux on mantic/jammy/focal-unapproved for acceptance.
They all look good to me (notes below, in addition to usual checks),
but I'll ask for another reviewer to provide input too, as it's ZFS.
(But I did want to provide some assistance in this long-running SRU.)
Thanks,
Mauricio
I went into the recovery with "nomodeset" option. I installed the up-to-
date driver "nvidia-driver-545". I rebooted, the bootup process was
quick and it went straight to the login screen without a problem. The
only thing I noticed is that after I entered my credentials and hit the
enter key it
** Description changed:
Phone name is displayed properly. After click turning circle icons appears.
info appears: cannot open device MTP "001,026"
Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
+ Mounting Samsung-Android works as intended.
Please hint me what info
I can confirm this issue exists on both Ubuntu 22.04.3 and 24.04.beta
(2024-01-25) with Linux 6.5x.
Both the Logitech (Bluetooth) M535 mouse and Microsoft Surface (Pro 7)
Type Cover were problematic with Linux 6.5x to the point where they were
unusable (timeouts or non-responsive for the mouse
** Description changed:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone
Public bug reported:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix
** Changed in: libpcap (Ubuntu)
Status: Incomplete => Triaged
--
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/2006557
Title:
Enable rdma-sniffer for libpcap
Status in libpcap
Public bug reported:
Phone name is displayed properly. After click turning circle icons appears.
info appears: cannot open device MTP "001,026"
Mounting via Nautilus works on Debian and it doesn't work on Ubuntu
Please hint me what info should I provide.
Ubuntu 22.04.3 LTS
sudo mtp-detect
** Description changed:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport
Hey Chris,
> ... the primary way that users get zfs in Ubuntu is via the module built with
> the *kernel* image.
> ... fixing that requires a zfs-linux upload and then a further kernel upload
> to pull in the new zfs.
Yes, fixing the zfs modules shipped with the kernel packages require
** Also affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-nvidia-tegra (Ubuntu)
** No longer affects: linux-nvidia-tegra (Ubuntu Jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Provide raspi-realtime kernel package/flavor (arm64 only) for Pi 4 and
5.
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Affects: flash-kernel (Ubuntu
** Description changed:
- Noble and newer doesn't support armhf for Pi anymore.
+ Noble and newer doesn't support armhf for Pi anymore. As a result of
+ that, the raspi-nolpae package/flavor will disappear since that is armhf
+ only.
** Tags added: kern-9084
** Description changed:
- Noble and
** Changed in: zfs-linux (Ubuntu Lunar)
Importance: Medium => Undecided
--
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/2044657
Title:
Multiple data corruption issues in zfs
Any update on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048945
Title:
scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status in linux:
Confirmed
** Tags removed: server-triage-discuss
--
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/2006557
Title:
Enable rdma-sniffer for libpcap
Status in libpcap package in Ubuntu:
Incomplete
I did a screening of the traces, but couldn't really find suspicious entries.
I'm now looking for a someone else's view and opinion...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
i try to restore my grub
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
@andysem yes that is also another possibility. The idea is to do a lot
of tests and if we find that there's a remote possibility to introduce
significant performance regressions in certain cases we can still keep
HZ=250, but definitely go with the other options.
--
You received this bug
@arighi: Did you consider applying lowlatency settings to generic kernel
but keeping CONFIG_HZ=250?
I suspect, the majority of desktop usage issues (i.e. responsiveness)
would be solved by `preempt=full rcu_nocbs=all` being the default (or
whatever the equivalent boot options are). While keeping
** Summary changed:
- change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
+ [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status:
** Description changed:
[Impact]
When plugin the headset jack, only speaker is identified.
[Fix]
Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
[Test]
Vendor tested on hardware, headset mic works fine.
[Where problems could occur]
It may break audio.
** Tags removed: originate-from-2046105
** Tags added: originate-from-2049464
--
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/2051947
Title:
Sound: Add rtl quirk of M70-Gen5
** Changed in: linux-oracle (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2046184
Title:
[arm64] Increase max CPU count
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Description changed:
[Impact]
When plugin the headset jack, only speaker is identified.
[Fix]
Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.
[Test]
Vendor tested on hardware, headset mic
** Description changed:
[Impact]
When plugin the headset jack, only speaker is identified.
[Fix]
Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
[Test]
Vendor tested on hardware, headset mic works fine.
[Where problems could occur]
It may break audio.
Thanks @vicamo, but what we want to ensure is much simpler than that
whole release process.
We just want to be sure that the firmware-sof from proposed, and the
updated kernel from proposed (and updates, i.e., currently available
outside proposed) were tested together according to the test plan.
Public bug reported:
[Impact]
When plugin the headset jack, only speaker is identified.
[Fix]
Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.
[Test]
Vendor tested on hardware, headset mic works fine.
[Where problems could occur]
It may break audio.
** Affects: hwe-next
** Summary changed:
- Sync iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
+ Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable
(main)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Description changed:
- Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
- /etc/kernel/postinst.d/dkms:
- * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
-...done.
- /etc/kernel/postinst.d/initramfs-tools:
- update-initramfs: Generating
Since upgrading to the 6.5.0 Ubuntu HWE kernel a few weeks ago, I have
not experienced this issue; so it looks like it is specific to the 6.2.0
Ubuntu kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: kdump-tools (Ubuntu Noble)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Also affects: linux-nvidia (Ubuntu Mantic)
Importance: Undecided
Public bug reported:
From
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
jammy/jammy/arm64/l/linux-nvidia-6.5/20240131_012859_fd7ca@/log.gz:
7141s dpkg-deb: building package 'linux-nvidia-6.5-tools-6.5.0-1011' in
Public bug reported:
From
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
jammy/jammy/arm64/l/linux-nvidia-tegra-igx/20240121_072109_094a7@/log.gz
:
6243s dpkg-deb: building package 'linux-nvidia-tegra-igx-tools-5.15.0-1007' in
Ubfan1 and I have talking about this out on the Forum: Were we have to help
other Users with this.
RE: https://ubuntuforums.org/showthread.php?t=2494834
I think his idea on something is genius: That if the compiler version is
brought in by the kernel on kernel updates as a dependency, so that
** 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/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.10
---
alsa-ucm-conf (1.2.6.3-1ubuntu1.10) jammy; urgency=medium
* d/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch
- fix typo to make the patch work on mt8390-evk (lp: #2049327)
-- Zhaoxuan Zhai
This bug was fixed in the package alsa-ucm-conf - 1.2.9-1ubuntu3.2
---
alsa-ucm-conf (1.2.9-1ubuntu3.2) mantic; urgency=medium
* d/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch
- fix typo to make the patch work on mtk8390-evk (lp: #2049327)
-- Zhaoxuan Zhai
Here's a no-compromises patch set. No bugs, no delays, it just does the
right thing.
If I haven't changed my mind again on Friday then it will be sent
upstream.
** Patch added: "lp1970069-patchset-20240201a.patch"
Yes, HWE kernels based on the Jammy/Mantic/Noble kernels should get this
fix automatically when the GA versions get 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/2036239
Title:
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: zfs-linux (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Lunar)
Thx a log Heitor! With no mention of some new package fixing this I did not
correlate that to any patch to the kernel.
Will the be fixed in the HWE kernel as well then?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Resetting the bluez package did NOT fix the problem.
Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.
sudo apt remove --purge bluez
rm -rf /var/lib/bluetooth
sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto
The bluetooth system need to be
- This occurs on my daily use laptopm which has been upgraded from 23.04
-> 23.10
- I have just tried to pair on another laptop with freshly installed 23.10
- The dialog displaying the pairing code persists
and I can pair correctly with same keyboard (it can pair with 3 separate
devices)
I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1
Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html
I have managed to have it working in the past, but the 6-digit code pop-
up disappears very quickly (as described,
** Description changed:
Since kernel 6.5, monitor brightness is set to 100%, and cannot be
changed: The brightness controls have disappeared from Settings, and
brightness doesn't respond to the keypad controls.
See the attached screenshot, showing the difference between the settings
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Manuel Diewald
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
Hello! Please what error message do you get, when trying to mount the
disks?
--
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/2050885
Title:
hd will not mount
Status in linux package in
Test packages
[1]: alsa-ucm-conf (1.2.10-1ubuntu3) noble
[1]: alsa-ucm-conf (1.2.9-1ubuntu3.3) mantic
[2]: alsa-ucm-conf (1.2.6.3-1ubuntu1.11) jammy
---
[1] https://launchpad.net/~ethan.hsieh/+archive/ubuntu/sru
[2] https://launchpad.net/~ethan.hsieh/+archive/ubuntu/sru-test
--
You received
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
** Tags added: jammy
--
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/2051703
Title:
Kernel 6.5.0-15-generic: HDMI Screen
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
** Tags added: jammy
--
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/2051922
Title:
Intel(R) Dual Band Wireless-AC 7265,
You have been subscribed to a public bug:
When booting with kernel 6.5.0-15-generic, the screen stays black, but
it is properly detected since I can move the mouse to it. Moreover, if I
reduce the framerate to 30Hz (it normally is at 60Hz) the screen is
visible again.
The HDMI screen works fine
You have been subscribed to a public bug:
Dear Members!
No wifi adapter detected on ubuntu, on win11 it works fine
lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
But wifi failed to manifest on previous versions and on the upcoming 24.04 as
well
** Description changed:
[Impact]
Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs.
mt8370-evk (G510):
https://github.com/alsa-project/alsa-ucm-conf/pull/380
https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97
Despite my comment above, I still have this problem when using netplan.
Here is my /etc/netplan/config.yaml (external IP quatrains have been
changed), the setup is that enp8s1 provides internet access (with metric
49) and enp7s0 provides local lan access *and* (with metric 51) fallback
internet
The attachment "noble.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you
** Patch added: "jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5744077/+files/jammy.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
** Patch added: "mantic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+attachment/5744076/+files/mantic.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
96 matches
Mail list logo
