Public bug reported:
I created a zfs-encrypted pool at /dev/sda (a 16Gb pendrive), to use it
as storage for lxd on this raspberry pi5 with 8Gb of RAM.
Creating the pool worked just fine, as did making it a storage for lxd.
I then launched a test container, and it hung.
ProblemType: Bug
DistroRel
The verification of the Stable Release Update for thermald 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 encounter a
Hi @rickywu, in comment #5 you wrote:
> 1. Noble 6.8.0-53-generic with linux-firmware
> 20240318.git3b128b60-0ubuntu2.8. It worked fine without any
> problem.
That is not the correct version of linux-firmware from noble-proposed.
noble-proposed has 20240318.git3b128b60-0ubuntu2.10, and noble-up
The verification of the Stable Release Update for linux-firmware 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 enco
The verification of the Stable Release Update for linux-firmware 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 enco
The verification of the Stable Release Update for ipu6-drivers 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 encoun
Was this part of the test plan conducted:
Full test plan is done via checkbox camera tests by multiple parties.
?
--
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/2084059
Title:
OVTI0
** Also affects: wireless-regdb (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: boot-managed-by-snapd (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Plucky)
Importance: Undecided
Status: Confirmed
**
Adding block-proposed due to
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2096979.
Looks like any update of this package will break on tpm+fde systems.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Hello Danilo, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
The verification of the Stable Release Update for qemu 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 encounter a reg
Please don't just change the verification tags without a comment stating
what your verification was.
** Tags removed: verification-done-oracular
** Tags added: verification-needed-oracular
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
The verification of the Stable Release Update for ubuntu-meta 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 encount
I would really like to see https://bugs.launchpad.net/ubuntu-
image/+bug/2082947 fixed, it's not just this SRU that it is impacting.
That being said, since this fix here is container to arm64, the first
part of the test plan was done, and we are about to build images for
24.04.2 release candidates
This is missing the SRU template.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be removed from) raspi desktop
Status in protection-domain-mapper pac
Is qemu still in need for a fix here?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/2077731
Title:
[SRU] riscv64 EDK 2 crashes in KVM based emulation
Status in edk2 package
The verification of the Stable Release Update for firmware-sof 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 encoun
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 encou
omprog is quite hard to confine correctly in a way that is still usable
for all cases. Whatever you do, it would be best to deal with local
overrides, and not change the main profile shipped by the rsyslog
package.
That being said, I don't know of a way to override the flag: the current
override m
> 2. Make sure firmware-sof, alsa-ucm-conf and kernel version support
RT722+RT1320.
alsa-ucm-conf is missing the verification on
https://launchpad.net/bugs/2089273
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
h
These new test runs now passed and are green.
--
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/2085162
Title:
Bluetooth devices can't reconnect after reboot or sleep
Status in Bluez Utili
The verification of the Stable Release Update for bluez 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 encounter a re
Like with other packages I have seen[1] in my shift, there are also tons
of "in progress" autopkgtests for this package that don't seem to be
running at all, yet are flagged as such in the report.
I'll trigger new runs for those:
$ ./retry-autopkgtest-regressions -s oracular --state RUNNING --bloc
The verification of the Stable Release Update for edk2 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 encounter a reg
I see ipu6-drivers 0~git202407190257.9369b88e-0ubuntu1.1 in oracular-
unapproved[1], and an unanswered question in comment #40 above.
Unsubscribing sponsors.
1.
https://launchpad.net/ubuntu/oracular/+queue?queue_state=1&queue_text=ipu6-drivers
--
You received this bug notification because you
a) It looks like the patches are changing many more things than "just"
CS35L56 support. I'm not familiar with firmware-sof and these binary
files, but that's what it looks like (output truncated below for
brevity):
$ dquilt push -a
Applying patch 0001-Add-2.11-topology2-production-binaries.patch
p
Confirmed https://launchpad.net/ubuntu/+source/firmware-
sof/2024.06-1ubuntu2 in plucky-proposed, marking corresponding task as
"fix committed" for clarity.
** Changed in: firmware-sof (Ubuntu Plucky)
Status: New => Fix Committed
--
You received this bug notification because you are a mem
Ok, this is verification-failed then, I'm changing the tag. Thanks for
catching this.
** Tags removed: verification-done-noble
** Tags added: verification-failed-noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubunt
>> And with alsa-ucm-conf 2023.12.1-1ubuntu1, there is no sound at all?
>
> May I know where is the version from? I don't see the version in
> noble/oracular/plucky.
Oh, sorry, that was firmware-sof.
This SRU has 2 packages: firmware-sof, and alsa-ucm-conf. I was querying
if the original package
This upload of firmware-sof is also fixing
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2069760, but
that verification has not concluded successfully yet (there is no sound
coming from the right speaker).
--
You received this bug notification because you are a member of Kernel
Pack
> I test on my Latitude 9510, the right speaker has no sound if I apply the
> alsa-ucm-conf 1.2.10-
> 1ubuntu5.1.
And with alsa-ucm-conf 2023.12.1-1ubuntu1, there is no sound at all?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-u
Hi @mschiu77, please don't change the verification tags without a
comment demonstrating the verification that was done.
>From comment #3 above:
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the
> package you tested, what testing has been
Hi @mschiu77, please don't change the verification tags without a
comment demonstrating the verification that was done.
>From comment #13 above:
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the
> package you tested, what testing has been
I'm marking the nfs-utils task as incomplete again, because so far this
looks like a kernel issue, and not userspace.
** Changed in: nfs-utils (Ubuntu Noble)
Status: Confirmed => Incomplete
** Changed in: nfs-utils (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Hello Jessica, or anyone else affected,
Accepted zfs-linux into noble-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.2-0ubuntu9.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
The current test plan doesn't seem to cover what is described in the
impact section.
Please update the test plan to include a test for the actual impact this
is having, which, from the description, is:
This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel
as writes to a f
Is anybody in a position to try out the kernel from the ubuntu 24.10
upcoming release? There will be a beta out this week of Ubuntu Oracular
24.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
Thanks all for your input. I'll add a kernel task to this bug, but keep
the userspace one open for now.
** 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 U
I was able to reproduce this in jammy lxd VM, and tweaked the test plan
a bit.
I'm going to accept this into jammy-proposed in order to allow for
testing to begin quickly, but we still need the noble and oracular
uploads as well.
The APT noble test plan could also use some refinement, there are s
Hello Ankush, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
** Description changed:
(For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 vi
** Description changed:
(For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 vi
Hello You-Sheng, or anyone else affected,
Accepted usbio-drivers into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/usbio-
drivers/0~git202312141918.78ffb706-0ubuntu2.1 in a few hours, and then
in the -proposed repository.
Please help us by te
> Install the built dkms binary package and
> linux-headers-generic-hwe-22.04/jammy. The dkms build should be
>triggered and complete successfully, and the devices with BIOS of 69W or a
>newer version should work as
> usual.
The jammy task of this bug is marked as invalid, but the test plan is
Finally, and pardon my ignorance, but could /dev/dri/card0 be used for
non-graphical things, like servers doing gpu calculations? And in that
case, removing it could break that workload?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvid
During boot, when does exactly "/bin/rm /dev/dri/card0" run? Would that
run in the initrd environment? I ask because of comment #37, which said
they lost the display during the luks password prompt. Although I
believe that's because of the workaround they were using then, which was
to disable simpl
This regression potential concerns me, thank you for raising it:
"""
Removing the simpledrm card is only safe when it's not being used. If somehow a
machine wasn't using the installed Nvidia driver then there could be a risk of
deleting the only working display.
"""
It may be obvious to you that
The verification of the Stable Release Update for zfs-linux 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 encounter
The verification of the Stable Release Update for zfs-linux 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 encounter
** Package changed: software-properties (Ubuntu) => linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2064370
Title:
Blank screen after boot in raspberry pi 4
St
Hi,
the test plan calls out for two additional steps which I don't see in
your verification:
> run hciconfig, the hci0 shows up.
> run checkbox testcase, it could pass.
> [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]
Could you please clarify if you have performed
*** This bug is a duplicate of bug 2056442 ***
https://bugs.launchpad.net/bugs/2056442
** This bug has been marked a duplicate of bug 2056442
Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod
`run/shm`: Operation not supported
--
You received this bug notification becaus
Adding a release notes task to put a note under "known issues".
** Also affects: ubuntu-release-notes
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/
Marking the userspace component (src:nfs-utils) task as invalid, since
it's a bug in the kernel.
** Changed in: nfs-utils (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
That would be
https://github.com/torvalds/linux/commit/fce7913b13d0270bcf926f986b7ef329e2e56eec
--
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/2060217
Title:
NFSv4 fails to mount in nobl
> Could I know the kernel version which use for below test?
Search for "testbed running kernel". In the case of that test, it's:
859s autopkgtest [01:53:38]: testbed running kernel: Linux 6.6.0-14-generic
#14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023
--
You received this bug notification because
I have GuoqingJiang access to the s390x vm where this bug can be
observed.
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in Ub
Perhaps try an older kernel, from when the test last passed?
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in Ubuntu on IBM z
** Tags added: update-excuse
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in linux package in Ubuntu:
New
Status in nfs-uti
I have a VM where this can be reproduced, if anyone is interested.
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in linux pack
> Does running `mount -vvv ...` provide more information?
Nope, same as single -v:
root@nfs:~# mount /mnt/nfs_home -vvv
mount.nfs: timeout set for Mon Apr 8 15:48:10 2024
mount.nfs: trying text-based options
'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Input/output error
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Just filing the bug now to keep track of it. No troubleshooting done
- yet.
-
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x
Looks like it has been failing for a long tim
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 encou
Ethan, thanks for the verification.
In the future, please include the exact version of the package that you
tested, and where it came from. I.e., the output of "apt-cache policy
" shows all that information.
There have been a few cases in the past where the verification was
mistakenly done using
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.
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 encou
** Description changed:
The tuned package has some plugins which rely on the perf python module
[1], and right now they are not working because we do not have the perf
python module available in Ubuntu.
Initially, this was reported in this other bug [2], but it seems the
scope of that
We (server team) are working on the src:tuned[0] package, and several of
its profiles make use of the python perf module. That module comes from
the linux kernel AFAIK, and we are just not building it.
In Fedora, it's shipped in the bin:python3-perf package:
[root@f39 ~]# rpm -ql python3-perf
/usr
Hello Lee, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Please amend the test case to test with both the GA and the (affected)
6.1 OEM kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2051068
Title:
GUI crashed after installed
This still needs a verification for mantic (I added the missing tag),
and the fix also needs to land in noble.
** Tags added: verification-needed-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bug
> because of lp:2047492, I can't verify it on mantic.
If this can't be verified in mantic, then please don't flip the mantic
verification tags :)
** Tags removed: verification-done-mantic
** Tags added: verification-needed-mantic
--
You received this bug notification because you are a member o
** Tags removed: verification-done-mantic
** Tags added: verification-needed-mantic
--
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/2031412
Title:
Support mipi camera on Intel Met
I just ran this command on my mantic laptop, according to the [test
plan]:
sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
And that PPA does not have mantic packages:
Err:24 https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu
mantic Release
This was uploaded, removing sponsors as there is nothing further to
sponsor.
--
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/2031412
Title:
Support mipi camera on Intel Meteor Lak
Hello You-Sheng, or anyone else affected,
Accepted ipu6-drivers into mantic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202310180730.3f813580-0ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.
Please help us b
Could https://github.com/openzfs/zfs/pull/15651 be picked up for this
update still?
--
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 z
The verification of the Stable Release Update for zfs-linux 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 encounter
Oh, I missed this bit in https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2040181/comments/10 in the other bug:
"It is still worth it to release this sru, before staging the next one
in proposed"
--
You received this bug notification because you are a member of Kernel
Packages, which is
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181
updating mantic to 2.2.0 final is in mantic-proposed, and this bug here
is in mantic-unapproved.
Should we drop 2.2.0 from mantic-proposed in favor of this one here?
--
You received this bug notification because you are a member of
@Artur,
a) you had a previous debdiff for mantic which used version
1.2.9-1ubuntu3.1, which is what we expect for an SRU to mantic, but now
in the mantic unapproved queue I see that you changed the version to
1.2.9-1ubuntu4 again.
The upgrade path between ubuntu releases still works:
alsa-ucm-con
Generally, it's your call, unless what you mean is that the current
version in unapproved, without the fix for 2044991, is broken/bad/not-
worth-it. Keep in mind that you would be adding another bug to the sru,
requiring again the full SRU template (impact, test plan, validation),
and all of the li
ipu6-drivers in mantic unapproved is addressing more than just this bug:
its changes[1] file lists 2012407 2021740 2026402 2031412.
#2021740 had a question about using a ppa in the test case
#2026402 didn't have a test case, and Timo recently added a comment saying that
this bug was actually alre
** Description changed:
- NOTE: this SRU depends on intel-usbio-dkms from bug #2041800
-
[SRU Justification]
== ipu6-driver ==
[Impact]
Missing Intel MIPI firmware for Meteor Lake platform.
[Fix]
Based on upstream tag
https://github.com/intel/ipu6-driv
** Description changed:
+ NOTE: this SRU depends on intel-usbio-dkms from bug #2041800
+
+
[SRU Justification]
== ipu6-driver ==
[Impact]
Missing Intel MIPI firmware for Meteor Lake platform.
[Fix]
Based on upstream tag
https://github.com/intel/ipu6-d
Can we change the test case to this:
# enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
# reboot into the 6.5.0-14.14 kernel
$ sudo apt install intel-ipu6-dkms intel-vsc-dkms
$ sudo apt install intel-usbio-dkms # from bug 2041800
$ sudo add-apt-repository ppa:oem-solutions
ok, so let's see:
> [Test Case]
>
> With all other changes in position, Intel VSC driver modules are to be loaded
> as a soft dependency of some selected camera sensor modules. LJCA modules
> should be loaded automatically on MTL platforms as well.
>
> To actually verify the camera framework:
>
The src:ivsc-driver package produces bin:intel-vsc-dkms
The src:ipu6-drivers package produces bin:intel-ipu6-dkms
We need the test case to use these binary dkms packages from mantic-
proposed (once they get accepted). These are the packages being proposed
for the SRU, so they are the ones that ha
Hi,
this review is about the ipu6-driver portion of this SRU, which I will
paste below and add inline comments to:
> == ipu6-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.
The changes in ipu6-drivers are not adding a new firmware as far as I
can
Hi,
this review is about the ivsc-driver portion of this SRU, which I will
paste below and add inline comments to:
> == ivsc-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.
The patches added to the ivsc-driver package do not seem to be about a
mis
Also, the "linux" task of this bug, for mantic, is "fix committed". It's
this one I believe:
https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14
So can the tests be made using that kernel? It is claiming to have added
support for MIPI cameras, to some extent:
* Support mipi camera on Intel
No update since Oct 27th, unsubscribing sponsors. Please subscribe again
if there is an update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
T
The verification of the Stable Release Update for mutter 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 encounter a r
I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic.
Sample:
$ sudo dmesg -T|grep Atomic
[qua nov 1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update
failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799,
scanline start 1753, end 1804
[qua nov 1
I agree that a merge from debian would be better, since we are quite
behind:
iproute2 | 6.5.0-4 | testing
But we have been at 6.1.0 since at least lunar, so I don't know how long
that would take. I think we can take these patches for noble.
I would ask that you also add this one, thou
Hi Chengen, or someone else:
could you please clarify that you also performed the test with the 5.15
GA kernel for Jammy, not just 6.2, which is what I assume you did?
I see that @mfo tested with 5.15 in comment #7, but that was before the
package landed in jammy-proposed.
--
You received this
Hello ethan.hsieh, or anyone else affected,
Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.8 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pa
Hello ethan.hsieh, or anyone else affected,
Accepted alsa-ucm-conf into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu9.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pa
** Also affects: alsa-ucm-conf (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: alsa-ucm-conf (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: alsa-ucm-conf (Ubuntu Jammy)
Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)
** Changed in:
1 - 100 of 253 matches
Mail list logo
