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 receive
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 to
Focal livecd-rootfs `2.664.53` with these proposed changes now in upload
queue
https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=livecd-
rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
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 f
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 ver
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 memb
** 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 __
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 __GI_epoll_c
** 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
> 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
https://github.co
** 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
T
** 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.
https://
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.
https://bugs.l
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: llvm-toolchai
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 in
--- 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 U
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 is
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"
https://bugs.launchpad.net/ubuntu/+source/s390-to
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 unexpectedl
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
** 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 allow
** 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
con
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 is
** 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 notif
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 ve
** 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 notifications
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: op
…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 https://launchpadlibrarian.net/722350666/2404_F9_gone_away
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 would
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 p
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 on
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
** 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 because
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 real
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 Re
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:
i
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 update-excu
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
'verification-done-jammy-linu
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 of
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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
'verification-done-jammy-linu
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 'verificat
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
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
'verification-done-jammy-linu
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 'verificat
Not sure who all the upstream(s) involved might be, but from my personal
PoV at least you can add all the options you like… the topic gets harder
if we talk defaults & changing (e.g.) the lists completely (like that
tabular verbose-explosion thingy from apk or whatever it was). At some
point it mig
All autopkgtests for the newly accepted linux-meta-aws-6.5
(6.5.0.1017.17~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-6.5/unknown (arm64)
Please visit the excuses page listed below and investigate the failur
Public bug reported:
ruby-behance/0.6.1-4 does not support ruby-faraday 2.x and last upstream
commit in the Github repo was from 6 years ago:
https://github.com/amedrz/behance
Apparently, there will not be any further developement. In Debian, the
Ruby team is planning to remove it from the archi
now in proposed
** Changed in: numpy (Ubuntu)
Status: Triaged => 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/2059714
Title:
FFe: update numpy to 1.26.x
To manage notification
Compressing a folder in nemo works now with 44-2 and it works with 43
for me also. Thank you for testing and reporting that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059335
Title:
FFe: S
Public bug reported:
We want to enable tracks for different versions of the out-of-tree
modules. For now we only have R36.3, so create the meta packages for
that version.
These meta packages include:
* linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and
iGPU display drive
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it (pe
The attachment "python-pytest-flake8_1.1.1-4ubuntu1.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
Public bug reported:
ruby-faraday-middleware was marked as deprecated by ruby-faraday 2.x:
https://github.com/lostisland/faraday_middleware?tab=readme-ov-
file#faraday-middleware
As expected, the tests do not work with the new version. We need to follow
Debian and request its removal:
https://b
Public bug reported:
folks build tests are failing.
I reported this issue upstream. It appears to be triggered by glib 2.80
and gobject-introspection 1.80.
We worked around this issue for Ubuntu 24.04 LTS by ignoring build test
failures because it was essential that we build folks to clear
trans
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050083
Title:
generate and ship vmlinux.h to allo
201 - 300 of 384 matches
Mail list logo
