apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559145/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559142/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559143/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559141/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559140/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559139/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559138/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559137/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559136/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559134/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559135/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559133/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559132/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
Title:
Boot
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1960018/+attachment/5559131/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960018
.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: christian 1890 F pulseaudio
/dev/snd/controlC0: christian 1890 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease
After upgrade to Kernel 5.13.0-28-generic boot fails, screen flashes.
booting into safe mode works, but when I continue with boot, then it fails
again.(flashing screen)
I am appreciative of the other reports, noting the same original
problem, it's comforting to know I was not alone and also the
Version 5.13.0.28 Fails to boot, screen flashes black/white, it will
boot into safe mode, but no further. so can not test.
After upgrade to Kernel 5.13.0-28-generic boot fails, screen flashes.
booting into safe mode works, but when I continue with boot, then it fails
again.(flashing screen)
you are then working
on the remaining required and recommended tasks.
** Changed in: rustc (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Simon Chopin (schopin)
** Changed in: rustc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a me
Review for Package: rustc
[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does need a security review, so I'll assign ubuntu-security
In addition security has to check and state if keeping
Hi,
I jsut came by and rechecked this.
At least on rustc-1.57.0 apt-file and dpkg and the build-log agree.
libcore is in none of them, but at least the consistency issue is gone.
root@j:~/ubuntu-helpers/cpaelzer# apt-file list rust-src | grep libcore
rust-src:
I struggled as well to use that syncpackage behavior right. The time you
trigger the sync is often too far away from the actual migration to
-release to happen. I happened to find my own way around (Not perfect,
but a suggestion).
I call it with --bug and once it has built (but not yet migrated)
This is a universe package that is IMHO rather important, so without
some care it might end up broken in jammy-release. Thanks to Robert
Reitz for bringing this up here!
I tagged it transition-openssl3-jj as that is just as related as the
other fallout that we know so far.
Since this is cause by
Thanks for the report,
to me that seems to be a consequence of the openssl3 transition [0]
Your hint that upstream master has this fixed seems right to me, I found
these to most likely be related:
https://github.com/tpm2-software/tpm2-tss/commit/e5bb5fb9 Remove
deprecated
** Tags removed: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951903
Title:
package libvirt-daemon-system 4.0.0-1ubuntu8.19 failed to
install/upgrade: installed
** Changed in: ipxe (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: ipxe (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959126
Title:
Consider update to 3.68.2
To manage
Thanks a bunch. It also works on a ThinkPad E14 Gen 2 with Ryzen 7 4700u
and AMD Renoir.
When I started with the new kernel I first had graphics issues. No
animations, only internal monitor working, black screen after sleep.
That was caused by a missing graphics driver. Software Updater suggested
Another Interim update:
- while not needed for the transition I filed also a ceph bug 1959744 for this
- on bug 1956949 we asked if unionfs-fuse (only universe) could change as well
to be on the safe side
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Hi,
as part of the overall move to fuse3 as the fuse-library in main.
While there is no strict reason to adapt ceph as the only dependencies come
from the universe packages ceph-fuse and rbd-fuse and thereby do not block the
transition.
It still seems that ceph is ready
FYI - this should be done as part of merging the new version for jammy
which is covered in bug 1959420
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935666
Title:
s390-tools FTBFS when built with
@aakef - while I said unionfs-fuse might not be a blocker I'd still
recommend to upload the change switching to fuse3. On comment #12 it
seemed you are close. Any chance to get this done or did unexpected
blockers show up while trying?
The unionfs-fuse task here is assigned to Graham; @ginggs -
** Changed in: rustc (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: cargo (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interim update:
- s390x-tools was confirmed by fheimes to have a fix before feature freeze
- actually the fix exists already, but a new release containing it will be
tagged
- grub2: still waiting, I pinged bug 1935659
- qemu: will switch to libfuse3-3 with the coming upload of 6.2 soon
-
FYI according to
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse3
This should no more be an issue now, so open-vm-tools will switch to
fuse3 again in the next
Yep, more and more depend on fuse3 (and libfuse3) - I think it would be great
to get this not-too-complex change uploaded.
FYI - the deadline for this is to demote fuse2 to universe before jammy release.
** No longer affects: grub2 (Ubuntu Impish)
** No longer affects: grub2-unsigned (Ubuntu
I'd like to know if there already is an Ubuntu position on this, will we revert
[1] to avoid a yet unknown amount of breakage in Jammy?
I'd like to know to adapt my packages accordingly ...
[1]: https://salsa.debian.org/debian/debhelper/-/commit/6067bc2
--
You received this bug notification
FYI: Keeping things up is even harder, while restarting sockets in the past
complained about services already being up they now restart the service.
So if anyone is looking at this for some package, be careful that you'd also
need to handle .socket files special now as they are affected by this
I can also confirm that it is good not for libvirt again - Thanks for
the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959325
Title:
New binutils causes build failures for many RISC-V
multipath-tools | 0.8.5-2ubuntu3 | jammy | source,
amd64, arm64, armhf, ppc64el, riscv64, s390x
multipath-tools | 0.8.8-1 | testing| source, amd64, arm64,
armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
We should try to get these upstream minor
dnsmasq | 2.86-1.1 | jammy| source
dnsmasq | 2.86-1.1 | jammy/universe | all
** Changed in: dnsmasq (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ok, that at least makes it better than the very-outdated 4.11 version.
Thanks for the testing smb!
Will probably upload this to Jammy after review of the MP.
https://code.launchpad.net/~paelzer/ubuntu/+source/xen/+git/xen/+merge/414651
** Merge proposal linked:
org/libvirt-team/libvirt/-/merge_requests/132
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Jammy)
Status: New => Triaged
** Changed in: libvirt (Ubuntu Jammy)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
Looks like the profile for cups-browsed has a syntax error. (Did you
change something in the profile, or is it the original profile as
shipped in the package?)
Also, AFAIK this profile is shipped with the cups package, therefore I'm
adding that package.
** Also affects: cups (Ubuntu)
e all know are
informational now, but could be a problem later on.
** Changed in: protobuf-c (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Public bug reported:
While still in Debian experimental
virglrenderer | 0.9.1-1~exp1 | experimental-debug | source
It is released upstream quite a while ago (9 months):
https://gitlab.freedesktop.org/virgl/virglrenderer/-/tags/virglrenderer-0.9.1
For Jammy it would be nice if we could have
Thanks Stefan, the qemu builds qemu - 1:6.2+dfsg-2ubuntu1~jammyppa8 and
later have the xen supporting qemu built and a proper compat symlink
now.
root@j:~# dpkg -L qemu-system-x86-xen | grep qemu-system-i386
/usr/bin/qemu-system-i386
/usr/share/man/man1/qemu-system-i386.1.gz
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946834
Title:
Merge multipath-tools from Debian unstable for 22.04
To
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
To manage notifications about this bug go to:
** Description changed:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel under
KVM using DIAG 0x318 instruction execution.
* The
** Changed in: qemu (Ubuntu Focal)
Status: Incomplete => 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/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for
version 5.13.0-27-generic - will not boot cleanly, just get a flashing
screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956467
Title:
powerlight stays on after shutdown
To manage
Uploaded to focal-unapproved
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel -
Are the tests run with security.nesting=true set?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959013
Title:
systemd test_exec_umask_namespace fails in privileged container
To manage
** Changed in: protobuf-c (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956617
Title:
[MIR] protobuf-c
To man
** Changed in: Ubuntu Jammy
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958109
Title:
[MIR] v4l2-relayd
To manage notifications about this
** Changed in: openssh (Ubuntu Bionic)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863930
Title:
SSH 1.99 clients fail to conn
FYI - right now I have nothing else in the SRU queue for qemu.
The plan to handle this upload without being a "useless" download for any
non-s390x users will be that we drive the SRU normally but set block-proposed.
There it will be picked up by a subsequent qemu security update in not too much
Well, IMHO the question is why is it active in your case ...
cloud-initramfs-copymods has a rather clear, cut use case:
- If booted with an external kernel/initrd make the modules from initrd
available in /lib/modules/
- If not, do nothing
That is why "usually" (tm) one has the package
It would be great if anyone with xen experience and setup would be willing to
test the PPA [1] with:
- xen 4.16
- qemu 6.2
- libvirt 8.0
I'd be especially interested if it works in regard to this bug here with
the different kernel compression.
But you can test it in general and let me know, I
FYI this also breaks "systemctl restart snapd.seeded.service" in the
same environment, and since this is unconditionally called from
/var/lib/dpkg/info/snapd.postinst any snapd update on such a system will
get stuck forever.
The former workaround of stopping the snapd.seeded unit thereby is not a
Thank you for the backported patches,
With those I've created a test PPA for Focal at [1] (still building atm).
@Frank AFAIK you need that to test the current proposed kernel.
Once you can confirm me that this looks good we can prep and kick off the SRU
process of this upload here as well.
[1]:
FYI - as planned part of the merge of 8.0.0 for jammy in bug 1946869
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588576
Title:
libvirt apparmor profile blocks access to ceph config file if
Public bug reported:
Hi,
please remove uvp-monitor from jammy, it seems without maintenance in Ubuntu
nor by Upstream (never was in Debian).
It came in for this case
https://bugs.launchpad.net/ubuntu/+bug/1714968
But since then is pretty much static
We got 8.0 (our target) into Debian now, starting a merge of that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946869
Title:
Merge libvirt from Debian unstable for 22.04
To manage notifications
For xen itself we know now how to "work around it" which is retry until running
on one of the new builders. Leaving the bug open as it clearly seems to be a
real issue.
I also leave the PPA as-is so that you can grab sources from there for
recreating this binutils issue.
--
You received this
Hi Michael,
it seems suspicious as it is the same test that fails.
But the assertion is different.
In the referred Debian bug it is
AssertionError: b'megasearch.net: 192.168.42.1' not found in
In the Ubuntu fail it is
subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']'
Public bug reported:
Upon running e.g. Puppet's r10k, which makes use of ruby-faraday
(version 0.15.4-3), a few lines of deprecation warnings are thrown on
every invocation:
# /usr/bin/r10k deploy environment -p
/usr/lib/ruby/vendor_ruby/faraday/options.rb:166: warning: Capturing the given
Being a platform dependent (thereby rather severe, but easy to miss)
crash in binutils I feel it is time to bump priority of this to get it
onto the radar avoiding to ship it that way (potentially breaking more)
in our next LTS.
** Changed in: binutils (Ubuntu)
Importance: Undecided =>
FYI - blocked by
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1957086 for the
time being
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946854
Title:
Merge dnsmasq from Debian unstable
This build ran 10:26 -> 10:33 and the crash happened "in between". As i
said in local sbuild those are not fatal but on LP they are. Therefore
attaching the build log ...
** Attachment added: "build log that did not exit fatally, but triggered the
crash we also see on LP (there fatally)"
The build log I attached above shall help to spot the versions needed
for debug symbols to read this crash correctly.
** Attachment added: "Crash file of x86_64-linux-gnu-ld.bfd as seen in local
sbuild"
Thanks for the hint,
in case anyone needs to do the same - you can see the associated builder right
when the build starts - then abort it immediately, refresh and rebuild.
That way you get 1 build try <1min, I got
lgw01 018
lgw01 044
lgw01 023
lcy02 001
And the build on the latter I let finish
Thanks Colin, even without debug symbols that still is probably enough
to confirm it is actually the same crash that I see on my laptop.
While I do not see why it is fatal for the build on LP but not on local
sbuild or dpkg-buildpkg in a local VM it means that most likely someone
looking into
And as comment #8 and #3 outlined the use of it in boost is not a real
problem for build or usage in the distribution, setting that task to
invalid.
** Changed in: boost1.74 (Ubuntu)
Status: New => Invalid
** Changed in: grub-legacy-ec2 (Ubuntu)
Assignee: Miriam España Acebal
Per comment #7 and
bzip2 | 1.0.8-5| jammy | source, amd64, arm64, armhf,
i386, ppc64el, riscv64, s390x
Setting that to fix released.
** Changed in: bzip2 (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of
I had the same icon-does-not-appear-in-systray problem with the
nextcloud desktop client on Ubuntu 20.04 (which upgraded from 18.04,
which upgraded from 16.04 ... all the way to 10.04). The solution was
comment #21, adding dbus-launch to the exec command.
--
You received this bug notification
** Changed in: grub-legacy-ec2 (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: ceph (Ubuntu)
Assignee: Miriam España Acebal (mirespace) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956166
Title:
Ubuntu 22.04 doesn't boot with xen
To manage notifications about this bug go to:
Hi Colin,
so far I've seen it only on lgw01, but I didn't mass-submit it yet to try the
other builders.
Is there a better way than re-building/re-submitting to get onto the lcy02?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-xmlschema (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953363
Title:
[MIR] python-xmlschema, elementpath, importlib-resources
To
FYI: I've seen some shortening of the reported crashes going on.
For example in journal it was "x86_64-linux-gn" and in the build log it was
after "x86_64-linux-gnu-ld". The local (non fatal) crash I got eventually was
in "x86_64-linux-gnu-ld.bfd".
This might or might not be the same crash on
FYI - I wanted to look if I could make at least xen 4.16 available on
jammy as I really think a new LTS should have a newer xen, no matter how
much it is in universe :-)
But unfortunately there are awkward issues blocking further progress at
the moment, with platform dependent segfaults:
Public bug reported:
FTBFS in Jammy on LP infra:
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
Related PPA:
Assigning to Dave as discussed on #ubuntu-devel.
Thank you!
** Changed in: open-iscsi (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
You need to keep the tarball (derived by the front of the version) identical.
The following should do it:
https://code.launchpad.net/~paelzer/ubuntu/+source/cmark-gfm/+git/cmark-gfm/+ref/back-to-former
It reverts the debian/* portion as-is and the code portion as new patch in d/p/
Thereby it
Ok, great - let me know if this worked out or if we all have missed a
dependency path :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957050
Title:
[MIR] suitesparse-graphblas
To manage
I tested the test of 249.5-2ubuntu2 (running autopkgtest against the dsc
file of 249.5-2ubuntu2) vs the binary systemd build in your PPA
(systemd_249.7-1ubuntu1~slyon0) + the dnsmasq from proposed.
And I got:
resolved: domain-restricted DNS servers ... ok
That means:
1. the fix is not in
Public bug reported:
I've seen that pandoc fails, example:
root@j:~# pandoc
pandoc: error while loading shared libraries: libcmark-gfm.so.0.29.0.gfm.0:
cannot open shared object file: No such file or directory
That made me wonder about this dependency and I found others like gitit:
root@j:~#
This isn't a normal review, this is a source split, and we really have to see
what we gain/lose due to that:
- Version upgrade 5.0.5 -> 6.0 (better)
- Maintained and tracked individually (better)
- No tests (as before)
Since it is the same code as before not that much review is needed to be
Bumped up the priority according to the MIR review in bug 1957050
** Changed in: suitesparse-graphblas (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958152
Note: There is only x86 and arm support (and 32 bit versions of that) in
ipxe, no need to plan for "more" architectures right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890230
Title:
arm64
Hi Dimitri,
thanks for the suggestion - it isn't that we deliver "x86 on arm" instead it is
an arch-all package that - as of today - only has builds for x86. So while it
is a slight difference we "deliver x86 everywhere as intended" and the request
is to also deliver arm64.
On the ISO (also
Confirmed in kernel.5.11.0.46
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956467
Title:
powerlight stays on after shutdown
To manage notifications about this bug go to:
Finally I found some time for this ...
Right now, we have those x86 binaries:
pkg:ipxe /usr/lib/ipxe/ipxe.efi -> /boot/ipxe.efi
pkg:grub-ipxe /boot/ipxe.efi
file /boot/ipxe.efi
#/boot/ipxe.efi: MS-DOS executable PE32+ executable (DLL) (EFI application)
x86-64, for MS Windows
As suggested
New Collectd and UHD migrated and the NBS removals of 20.11 are done,
fully complete now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946856
Title:
Merge dpdk from Debian unstable for 22.04
To
Due to the current state these won't auto-expire.
I agree with the discussion so far, and after half a year without
further insights or new ways to attack this I'd even say we close this
and if there is anything new that might help it can be re-opened. But
until then it will be off the recheck
Incomplete since we wait for the proper rebase for the backports as I
asked in early December.
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
on present, but none needed for this case (user visible)?
Problems: None
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libio-prompt-tiny-perl (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => Lukas Märdian (slyon)
--
You r
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957086
Title:
Autopkgtest systemd fail against dnsmasq 2.86 (22.04)
To manage notifications about this bug go to:
FYI: Also Fixed in jammy-release via
https://launchpad.net/ubuntu/+source/dpdk/21.11-1 which has our former
delta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939861
Title:
dpdk: ppc64el
701 - 800 of 23108 matches
Mail list logo
