This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1023.23~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-linux-
nvidia-tegra-5.15' to
I faced the same problem on Ubuntu 22.04 a couple of week ago. I checked these
kernels:
- 5.15.0-100-generic — does not work
- 5.15.0-101-generic — does not work
- 6.5.0-26-generic — does not work
- 5.15.0-97-generic — works well!
--
You received this bug notification because you are a member
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1023.23 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-linux-nvidia-tegra' to
Public bug reported:
fprintd fails to build from source
https://launchpad.net/ubuntu/+source/fprintd/1.94.2-3build1
** Affects: fprintd (Ubuntu)
Importance: High
Status: New
** Affects: fprintd (Debian)
Importance: Unknown
Status: Unknown
** Tags: noble
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ipmiutil (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047036
Title:
fossfreedom, I am unable to get the compress a folder feature to work
with nemo and file-roller 43.
However, I did verify https://gitlab.gnome.org/GNOME/file-
roller/-/issues/231 and am pushing a new version to Debian and the PPA
to include that fix.
** Description changed:
Freeze Exception
You're right that the automounting of the partition is irrelevant if
we're just going to go ahead an umount whatever, but it's still
perplexing not to know *why*.
Anyways, another good point about keeping zram on. We do have that for a
reason. Thus, the recommendation of `swapoff -a` is not a
** Also affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
The noble release pocket is currently in an inconsistent state because
of rebuilds for CVE-2024-3094. This is not a bug in the pam package.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094
** Changed in: pam (Ubuntu)
Status: New => Invalid
--
You received this bug
Public bug reported:
I am seeing an issue with the Cortex-A78 PMU counters on the
Genio1200-evk.
Linux perf reports for Cortex-A78 PMUs when I run the following
commands:
taskset -c 7 perf stat -e cycles sleep 5
taskset -c 7 perf stat -r r11 sleep 5
Infact none of the standard PMU events
Public bug reported:
When trying to install libpam0g-dev on noble numbat, I get the following
output:
The following packages have unmet dependencies:
libpam0g-dev : Depends: libpam0g (= 1.5.2-9.1ubuntu3) but 1.5.3-5ubuntu3 is to
be installed
E: Unable to correct problems, you have held broken
Geekley I personally agree and would go a lot further and hide even most
dependencies (you don't really care which libraries you are installing,
just about choices made, e.g. if there's an a | b dependency it should
tell you that it picked a).
So if you want to think about it that terse mode
…even more confusing since F9 shortcut is still mentioned in Nautilus «
preferences / help »
( at least in french language, I did not check in other languages ).
See also https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2059871
and
Is there a strong use case for installing openssh-server, but then not
wanting it to run as a daemon (i.e. disabling the necessary systemd
units)? The purpose of this snippet is to migrate to socket activated
sshd by default, which is the case for new installs of openssh-server.
** Changed in:
** Tags added: unmetdeps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059985
Title:
libavformat60, libavcodec60 can't be installed on Noble because of
version mismatches
To manage
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053038
Title:
Syntax warning while upgrading
To manage
I believe that 0.3 improves the situation, because it now passes `-cpu
max` rather than `-cpu host` and thus improves the fallback behavior.
Additionally, I think this is a bug in Ubuntu's infrastructure, because
the `/dev/kvm` device is writable to the autopkgtest user and not
working. Earlier
I have done a quick test with ubuntu budgie and nemo.
For some unknown reason, the right-click compress option no longer
compresses the chosen folder. This worked with the gtk3 version.
Extracting an archive does work and correctly uncompresses the tar.gz
Potentially there is a compatibility
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059872
Title:
Unable to listen on port 22 if multiple Port= present in sshd
** Description changed:
Impact
--
I request permission to sync the gnome-software packaging from Debian. The
biggest change is splitting gnome-software's .deb support into a separate
package, gnome-software-plugin-deb, to match the existing -snap and -flatpak
packages. This will
Public bug reported:
OS: Ubuntu 22.04.4 LTS
Kernel: 6.5.0-26-generic
Whenever I close the lid on my Lenovo Yoga (Yoga-Slim-7-ProX) laptop while it
is in suspend, it immediately wakes up. It must be an issue with the kernel,
because while looking this up, I found a similar problem reported with
Fix committed: https://salsa.debian.org/glibc-
team/tzdata/-/commit/7cef9e552df97611cd7f097c867f21138cbfa7ba
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055718
Title:
timezone changed
Meanwhile I've navigated through the challenges in noble and have a successful
PPA build here:
launchpad.net/~fheimes/+archive/ubuntu/lp2059303
and the s390-tools and the s390-tools-signed debdiffs attached.
** Attachment added: "debdiffs.tgz"
I'm setting to Incomplete because I'd like to allow Flavor Leads a
chance to comment
** Description changed:
+ Freeze Exception Request
+
+ I request to sync file-roller 44 from Debian. The largest change is that
file-roller was ported from GTK3 to GTK4. However, this
--- Comment From i...@de.ibm.com 2024-04-02 13:14 EDT---
Hi, yes, I used the upstream testcase there.
I just checked the C program with 4 levels of optimization, and it works fine
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In the proposed fix, will there be some sort of flag and/or
configuration for apt and apt-get to let me NOT see this list of
"deferred due to phasing" packages? I agree it's important to list them
for users who want to see it, but it's also important to not bloat the
output with a bunch of extra
marked old toolchain versions as won't fix
** Changed in: gcc-9 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in: gcc-10 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in: gcc-11 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in:
both packages in -proposed
** Changed in: webdis (Ubuntu)
Status: New => Fix Committed
** Changed in: libevent (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Update file-roller to 44
+ FFe: Sync file-roller 44-1 (main) from Debian unstable (main)
** Changed in: file-roller (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059951
Title:
mlxbf_gige: stop interface during shutdown
> Not sure what would be best, if RM the package or invest time into
patching it.
Since no action happened last week, my teammate Chris Lalancette patched
the existing version to work with current flake8 on noble-proposed
7.0.0. I have updated the upstream PR with the information
** Description changed:
[ Impact ]
Currently, the Pro client support a daemon named ubuntu-advantage.service that
performs two actions:
* Actively look for Pro licenses on Azure and GCP images to perform an
auto-attach
* Retry auto-attach on Pro images if that command fails on boot
** Description changed:
[ Impact ]
Currently, the Pro client support a daemon named ubuntu-advantage.service that
performs two actions:
* Actively look for Pro licenses on Azure and GCP images to perform an
auto-attach
* Retry auto-attach on Pro images if that command fails on boot
Let me provide the debdiff for jammy and update the bug to make it ready
for SRU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1990630
Title:
tracker-extract-3 crashed with signal 31 in
** Also affects: tracker-miners (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1990630
Title:
tracker-extract-3 crashed with signal 31 in
This should not impact Ubuntu Cinnamon as I don't believe there are any
components that specifically rely heavily on gnome-software.
ubuntucinnamon-meta will need to add the new entry for gnome-software-
plugin-deb, but that's about it.
--
You received this bug notification because you are a
Uploaded 2.0.0+svn315-7fakesync1ubuntu1 without any changes.
** Changed in: splix (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060038
Title:
splix
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
Hello, Nathan,
Thank you very much for reporting this bug.
The team is aware of the gaps and we have an open item to implement the missing
API endpoints.
We will keep you posted.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Dheyay Desai (dheyayd)
--
You
** Changed in: nauty (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059130
Title:
Autopkgtests fail with 2.8.8+ds-2
To manage notifications about
As discussed in the MIR meeting I created a dotnet8 MIR bug; see LP:
#2060056
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023531
Title:
[MIR] dotnet6
To manage notifications about this bug go
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is in the Noble release pocket now.
** Changed in: ubuntu
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055432
Title:
[needs-packaging] Metapackage
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060039
Title:
Public bug reported:
This is a follow up to the dotnet6 MIR (see LP: #2023531). We would like
to have dotnet8 in main too, which was already discussed during the
dotnet6 MIR (see comment 13 [1]).
The dotnet8 package is structurally nearly identical. We do this
deliberately to lower the
@vanvugt: I appreciate you opening the Jammy task, but I'm not holding my
breath for this to get fixed after reading
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/comments/1
Basically, they knew this bug was coming when they removed the 390 package, but
they
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055712
Title:
Pull-request to address bug in mm/page_alloc.c
To manage notifications about this bug go to:
--- Comment From cha...@us.ibm.com 2024-04-02 11:43 EDT---
Can you check if vTPM is enabled and disable it and see if that allows you to
install?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056491
Title:
not
** Description changed:
[ Impact ]
- If the user has specified custom setup for the Pro client through cloud-init,
there is a high chance that this setup will be ignored.
+ Currently, the Pro client support a daemon named ubuntu-advantage.service that
+ performs two actions:
- This happened
** Changed in: timeshift (Ubuntu Jammy)
Assignee: (unassigned) => Ponnuvel Palaniyappan (pponnuvel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009885
Title:
Timeshift 21.09.1-1 broken
This is related to recent xz cve, the repositories might be broken
packages as being rebuilt. Check your other issue (about libzvbi0), you
need apt pinning override to be able to install packages properly as I
described more detailed there.
You might want to check apt-cache policy for affected
** Also affects: lxml (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958539
Title:
Move lxml.html.clean into external project
To manage
With this in light (but we have the wider "everything that is in main
for a very long time in ubuntu, even being security reviewed and got
multiple uploads), I would agree that -server could have another
security/fresh look. Do you think it’s something the security team has
the capacity to look?
Confirming that the only REQUIRED TODO is now fixed. Thanks for checking
it slyon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2004442
Title:
[MIR] aom (dependency of libheif)
To manage
This is caused by changes related to recent cve of xz backdoor and the
repositories might be broken as of now where the most of packages are
being rebuilt againt a clean package or something like that. More
information can be found at page
https://ubuntu.com/security/CVE-2024-3094
Meanwhile you
Hey everyone and Paul. First, sorry for the delayed answered (I was
thinking you would get me reassign and for some reason, I missed
subscribing to the bug)
> But I do not really understand the harm of having these entries kept
for documentation, except this could pile up and become a mess at
We agreed that the "#MISSING: " lines will be downgraded to a
Recommended MIR TODO.
Do you want those #MISSING: symbols dropped? IMO it should be fine
as-is. Upstream is aware and want's to drop it anyway
#MISSING is fine unless it keeps adding more and more and more of
them
So this should
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059961
Title:
genetlink: fix single op policy dump when do
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059310
Title:
mlxbf_gige: call request_irq() after NAPI
Thank you for adding all the QA and clarifying more.
When you change dependencies to pull this in (I see Ubuntu-meta already
did change).
This is trying to get the value to the users, but not clutter where possible.
I think we should depend on libbpf-tools instead of the current bpfcc-tools.
I'll not mark it "in progress" yet waiting for the "which -tools" to use.
But it would be ready once you settled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052813
Title:
[MIR] bpfcc
To manage
Public bug reported:
I was investigating removing Software Properties calls to pro 'security-
status --format=json' because it is deprecated and has at least a known
fail point.
But the API doesn't seem to provide an end-point to query the
availability of a service, which is required at [1].
** Changed in: dotnet8 (Ubuntu)
Status: New => Confirmed
** Changed in: dotnet7 (Ubuntu)
Status: New => Confirmed
** Changed in: dotnet6 (Ubuntu)
Status: New => Confirmed
** Changed in: dotnet6 (Ubuntu)
Importance: Undecided => Low
** Changed in: dotnet7 (Ubuntu)
Thanks! I applied basically what your patch said (the file is
dynamically generated). This will be in 8u402-ga-7
** Changed in: openjdk-8 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good news this bug has been resolved.
https://github.com/ubuntu/gnome-sdk/issues/188
The fix is currently in the candidate channel of gnome-42-2204 content
snap. I can confirm from my own testing it indeed fixes this bug.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: dotnet6 (Ubuntu)
Status: New => Confirmed
** Changed in: dotnet7 (Ubuntu)
Status: New => Confirmed
** Changed in: dotnet8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Note: The new autopkgtests made this issue invalid. It was valid before.
** Changed in: dotnet8 (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044550
** Changed in: dotnet8 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: dotnet8 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
101 - 200 of 378 matches
Mail list logo
