Thanks @ffesti ! So I suppose this should be closed upstream, and I'll create a
bugzilla instead?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3073#issuecomment-2092433241
You are receiving this because you are subscribed to this
This helped a lot, but it's still applying the user creation and `%attr()`
processing in the wrong order. I filed issue #3073 about it.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2432#issuecomment-2092096531
You are receiving this
We are currently [trying to move our project to
systemd-sysusers](https://github.com/cockpit-project/cockpit/pull/20365), away
from manual `useradd` calls in the package's `%pre` script. The [rpm
manual](https://rpm-software-management.github.io/rpm/manual/users_and_groups.html)
claims
> Rpm
This was "fixed" in noble by clearing out noble-proposed, thanks! That
took care of the worst fallout.
** Changed in: python-gssapi (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The recent no-change rebuild in
https://launchpad.net/ubuntu/+source/python-gssapi/1.8.2-1ubuntu2
regressed. With -1ubuntu1, the import works:
python3 -c 'import gssapi'
but with -1ubuntu2, it crashes with
Traceback (most recent call last):
File "", line 1, in
File
There are no patches, it's a straight import of the source package into
Ubuntu. Ubuntu *does* have different compiler options than Debian, so
that may be a factor. Otherwise I'm in the same boat as you -- there's
only so much time I can throw at this (I've done full-time "investigate,
report, and
log 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
+Use valid host name in tes
log 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
+Use valid host name in tes
log 2024-04-02 11:11:19.0 +0200
+++ cockpit-287.1/debian/changelog 2024-04-16 09:20:17.0 +0200
@@ -1,3 +1,11 @@
+cockpit (287.1-0+deb12u2) bookworm-security; urgency=medium
+
+ * Add 0001-ssh-Use-valid-host-name-in-test-sshbridge.patch:
+Use valid host name in tes
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of FreeIPA,
which is
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in
Confirmed in current noble.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1946244
Title:
When installing/uninstalling with realmd, uninstalling crashes with
ScriptError
Status in freeipa
Confirmed in current noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946244
Title:
When installing/uninstalling with realmd, uninstalling crashes with
ScriptError
To manage notifications
Public bug reported:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:
2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl',
Public bug reported:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:
2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl',
Public bug reported:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:
2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl',
Yay, today this is finally fixed, pbuilder creation and building a noble
VM image finally works again \o/ Thanks!
** Changed in: perl (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yay, today this is finally fixed, pbuilder creation and building a noble
VM image finally works again \o/ Thanks!
** Changed in: perl (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In other words, having the fix in backports is fine I think.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060014
Title:
CVE-2024-2947 command injection when deleting a sosreport with a
crafted
Marc: Thanks -- no urgency from my side, I just wasn't sure about your
current CVE "must/may fix" policies.
** Changed in: cockpit (Ubuntu Mantic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nathan Scott [2024-04-09 17:30 +1000]:
> > It's not really unknown, it's "just" a file conflict:
>
> Yeah - the unknown bit for me is "why tho" - I cannot see conflicting
> files in those packages that would have any debug symbols (there's
> some common directories... but no binaries shared
Hello Nathan,
Nathan Scott [2024-04-09 16:19 +1000]:
> Is any of this getting through... ? Just checked the Ubuntu tracker
> URL, and looks like every response Ken or I sent has been dropped on
> the ground.
Right, I didn't get any response either (not a surprise, as it's *first*
Launchpad
Aside from curl this can be reproduced most quickly with
sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n
http://archive.ubuntu.com/ubuntu
Errors were encountered while processing:
perl
libdpkg-perl
libperl5.38t64:amd64
dpkg-dev
build-essential
These are all ultimately
I wonder where that comes from --
https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that
5.38.2-3 was deleted, but only from noble-updates. In noble proper it is
merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3
doesn't show it being published anyway, and it's
Aside from curl this can be reproduced most quickly with
sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n
http://archive.ubuntu.com/ubuntu
Errors were encountered while processing:
perl
libdpkg-perl
libperl5.38t64:amd64
dpkg-dev
build-essential
These are all ultimately
I wonder where that comes from --
https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that
5.38.2-3 was deleted, but only from noble-updates. In noble proper it is
merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3
doesn't show it being published anyway, and it's
Public bug reported:
For the last two weeks, building noble VM images for our CI has been
broken. Most of it was uninstallability due to the xz reset, but for the
last three days, `pbuilder --create` has failed [2] because it gets perl
and perl-modules-5.38 in two different versions:
2024-04-08
Public bug reported:
For the last two weeks, building noble VM images for our CI has been
broken. Most of it was uninstallability due to the xz reset, but for the
last three days, `pbuilder --create` has failed [2] because it gets perl
and perl-modules-5.38 in two different versions:
2024-04-08
> They didn't propagate yet due to noble being jammed so much
This happened now \o/, so they are ready to go.
** Changed in: cockpit (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Maybe the missing dbgsym packages are on purpose? The build log has
this:
# Note: --no-automatic-dbgsym not defined for all releases up to
# and including Debian 8 (jessie), but defined after that
# ... expect a warning on older releases, but no other ill
# effects from the
Public bug reported:
In Cockpit's CI we see a lot of pmproxy crashes like [1] in a test which
starts/stops/reconfigures pmlogger, pmproxy, and redis. The journal
(some examples are [2][3][4]) always shows a similar stack trace:
pmproxy[9832]: segfault at 3 ip 767961047e45 sp 7ffe97e825d0
Sorry, clicked the wrong button, I'll expand the bug description. In the
meantime, attaching the core dump.
** Attachment added: "core dump"
Backporters: I uploaded backports from noble-proposed to mantic and
jammy. They didn't propagate yet due to noble being jammed so much, but
we do validate them on both releases upstream. I'll let you decide
whether to accept or stall them.
--
You received this bug notification because you are a
@Marc, security team: I'd like your opinion/preference/guidance for
mantic: It currently has upstream version 300.1. Half a year ago we did
two more upstream point releases for critical bug fixes (aimed at and
uploaded to RHEL): https://github.com/cockpit-
project/cockpit/releases/tag/300.2 and
Note: I tried to add backports tasks, but there's neither a
https://launchpad.net/jammy-backports nor a
https://launchpad.net/mantic-backports project. But not a biggie, these
will both get 314 as soon as it lands in noble.
--
You received this bug notification because you are a member of Ubuntu
and autopkgtest queue
before it can land in noble proper (and thus the backports of mantic and
jammy get updated).
** Affects: cockpit (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Fix Committed
** Affects: cockpit (Ubuntu Mantic)
Importance: Medium
Status
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Control: tag -1 upstream pending
Hello all,
Thorsten Glaser [2024-03-20 3:05 +]:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
>26 | # error
Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/216
Control: tag -1 upstream pending
Hello all,
Thorsten Glaser [2024-03-20 3:05 +]:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
>26 | # error
** Changed in: chrony (Ubuntu)
Status: New => Won't Fix
** Changed in: gnutls28 (Ubuntu)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: chrony (Ubuntu)
Status: New => Won't Fix
** Changed in: gnutls28 (Ubuntu)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that
unshare --user --map-root-user /bin/bash -c whoami
(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.
I am starting to test Cockpit on the
Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that
unshare --user --map-root-user /bin/bash -c whoami
(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.
I am starting to test Cockpit on the
** Tags added: cockpit-test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774000
Title:
Fails to boot cirros QEMU image with tuned running
To manage notifications about this bug go to:
** Tags added: cockpit-test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To manage notifications about this bug go
Public bug reported:
There is an AppArmor regression in current noble. In cockpit we recently
started to test on noble (to prevent the "major regressions after
release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather
Public bug reported:
There is an AppArmor regression in current noble. In cockpit we recently
started to test on noble (to prevent the "major regressions after
release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather
*** This bug is a duplicate of bug 2056739 ***
https://bugs.launchpad.net/bugs/2056739
Absolutely agree, thanks Christian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056747
Title:
Public bug reported:
Merely booting current noble cloud image with "chrony" installed causes
this:
audit: type=1400 audit(1710152842.540:107): apparmor="DENIED"
operation="open" class="file" profile="/usr/sbin/chronyd"
name="/etc/gnutls/config" pid=878 comm="chronyd" requested_mask="r"
Public bug reported:
Running any VM in libvirt causes a new AppArmor violation in current
noble. This is a regression, this didn't happen in any previous release.
Reproducer:
virt-install --memory 50 --pxe --virt-type qemu --os-variant
alpinelinux3.8 --disk none --wait 0 --name test1
(This
Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
Control: severity 1061370 grave
Control: forcemerge -1 1061370
Matthias Klose [2024-02-01 8:30 +0100]:
> please don't file duplicate reports, see #1061370
Ah, sorry -- it wasn't clear from the title that it was about this problem, nor
was it RC. Marking a duplicate, so that it's easier to find.
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2
Control: tag -1 pending
Hallo Matthias,
Matthias Klose [2024-01-29 21:27 +0100]:
> 636s NO TESTS RAN (skipped=4)
> 637s autopkgtest [01:57:06]: test upstream: ---]
> 637s autopkgtest [01:57:06]: test upstream: - - - - - - - - - - results - -
> - - - - - - - -
> 637s upstream
I can't make head or tail of this. aa-complain still enforces deny
rules, there is no (discoverable) way to log deny rules, and
grep -r deny /etc/apparmor.d | grep virt | grep -v /sys | grep -v /dev
doesn't show anything which would apply to /var/lib/libvirt/.
`aa-disable
Control: retitle -1 libvirt-daemon: Deleting external snapshot for non-running
system VM fails with AppArmor
when stracing libvirt, this is what happens:
6557 openat(AT_FDCWD, "/var/lib/libvirt/images/test2.qcow2", O_RDWR|O_CLOEXEC)
= -1 EACCES (Permission denied)
6557 sendmsg(13,
Package: libvirt-daemon
Version: 10.0.0-1
When creating a trivial VM and doing an external snapshot if the VM is *not*
running,
deleting the snapshot fails. As root:
qemu-img create -f qcow2 /var/lib/libvirt/images/test1.qcow2 10G
virt-install --memory 50 --pxe --virt-type qemu --os-variant
** Tags added: jammy regression-release
** Tags removed: regression-release
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe
: #1058214)
+
+ -- Martin Pitt Wed, 10 Jan 2024 08:16:54 +0100
+
sosreport (4.0-2) unstable; urgency=medium
* d/p/0003-systemd-prefer-resolvectl-over-systemd-resolve.patch:
diff -Nru sosreport-4.0/debian/patches/0004-unittest-assertEquals.patch
sosreport-4.0/debian/patches/0004-unittest
: #1058214)
+
+ -- Martin Pitt Wed, 10 Jan 2024 08:16:54 +0100
+
sosreport (4.0-2) unstable; urgency=medium
* d/p/0003-systemd-prefer-resolvectl-over-systemd-resolve.patch:
diff -Nru sosreport-4.0/debian/patches/0004-unittest-assertEquals.patch
sosreport-4.0/debian/patches/0004-unittest
Control: forwarded -1 https://github.com/sosreport/sos/pull/3467
Control: tag -1 upstream pending
Hello Lucas and Eric,
I sent an upstream fix for this to the PR above. Their CI didn't even spot that
error yet (argh big testing gaps).
This has been open for a month now. As this threatens to
Control: forwarded -1 https://github.com/sosreport/sos/pull/3467
Control: tag -1 upstream pending
Hello Lucas and Eric,
I sent an upstream fix for this to the PR above. Their CI didn't even spot that
error yet (argh big testing gaps).
This has been open for a month now. As this threatens to
Control: reassign -1 upower 1.90.2-7
Control: tag -1 fixed-upstream pending
The upower test adjustment landed upstream, I'll cherry-pick it into Debian.
Martin
Control: reassign -1 upower 1.90.2-7
Control: tag -1 fixed-upstream pending
The upower test adjustment landed upstream, I'll cherry-pick it into Debian.
Martin
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/207
Hello Luca,
Luca Boccassi [2023-12-26 12:46 +0100]:
> Not sure whether it was a legitimate change and upower's tests need an
> update, or if it is a new bug, but 0.30.1-1 causes
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/207
Hello Luca,
Luca Boccassi [2023-12-26 12:46 +0100]:
> Not sure whether it was a legitimate change and upower's tests need an
> update, or if it is a new bug, but 0.30.1-1 causes
Martin Pitt [2023-12-25 11:25 +0100]:
> The new upstream release plus regression fix have propagated to testing, to
> Ubuntu devel, and also is progressing well into Fedora. By now the tests have
> validated it enough for me to be confident in the fixes.
>
> I prepared the
Hello Sean and security team,
Sean Whitton [2023-12-24 9:12 +]:
> I have taken responsibility for fixing these CVEs in libssh in buster,
> as part of Freexian-funded LTS work. I would like to see if I can help
> get them fixed in bullseye & bookworm in parallel, to avoid a situation
> where
Hello Salvatore and all,
Salvatore Bonaccorso [2023-12-22 20:34 +0100]:
> On Fri, Dec 22, 2023 at 04:39:46PM +0100, Martin Pitt wrote:
> > Salvatore Bonaccorso [2023-12-22 13:20 +0100]:
> > > > However, the fix for CVE-2023-6004 caused a regression:
> > > > https:
Hello Salvatore,
Salvatore Bonaccorso [2023-12-22 13:20 +0100]:
> > However, the fix for CVE-2023-6004 caused a regression:
> > https://gitlab.com/libssh/libssh-mirror/-/issues/227
> > I will monitor this, and include the fix in the security upload once it is
> > available (or presumably they'll
Hello Salvatore,
Salvatore Bonaccorso [2023-12-19 22:34 +0100]:
> The following vulnerability was published for libssh.
>
> CVE-2023-6004[0]:
> | ProxyCommand/ProxyJump features allow injection of malicious code
> | through hostname
I uploaded the new upstream security fix release 0.10.6 to
Fun, this isn't even reliable. The first atttempt failed:
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log
I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with
Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.
But it is a red herring due to the || true. The upgrade failed on
something
Public bug reported:
In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in openssh package in Ubuntu:
New
Bug
We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:
Setting up
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default
Control: tag -1 pending
Hello IOhannes,
IOhannes m zmoelnig [2023-12-13 8:57 +0100]:
> However, since 'scour' is not marked "Multi-Arch: foreign" (or "Multi-Arch:
> allowed") which makes it somewhat awkward to use when cross-building packages
> (that depend on 'scour').
>
> I would therefore
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
-
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
-
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer:
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer:
Hello Neftali,
Stef Walter [2023-12-11 10:01 +0100]:
> -- Forwarded message -
> Hello, I would like to participate in the cockpit development groups,
> first of all collaborating with the Spanish translations,
That would be great, ¡gracias!
Cockpit is translated on weblate:
I also tried
aa-disable usr.bin.crun
but that doesn't work either. I guess it's not really crun, but
profile="containers-default-0.50.1", but that is created dynamically --
it's not anywhere in /etc/apparmor.d/. I grepped the whole file system
for that:
grep: /usr/lib/podman/rootlessport:
I tried a more targeted workaround, with
aa-complain /etc/apparmor.d/usr.bin.crun
or alternatively (without apparmor-utils, which isn't on the default
cloud image):
sed -i '/flags=/ s/unconfined/complain/' /etc/apparmor.d/usr.bin.crun
but for some reason that breaks podman entirely:
#
Exact same fix uploaded to -proposed SRU review queue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/2040488
Title:
loading lvm2 module crashes: udisks_module_lvm2_new: assertion
** Description changed:
[Impact]
Trying to load the lvm2 module crashes udisks immediately:
busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager
org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true
udisksd[5709]: cannot register existing type
4
Date: Wed Oct 25 12:13:14 2023
DistroRelease: Ubuntu 23.10
ExecutablePath: /usr/libexec/udisks2/udisksd
Package: udisks2 2.10.1-1ubuntu1
** Changed in: udisks2 (Ubuntu Mantic)
Status: New => In Progress
** Changed in: udisks2 (Ubuntu Mantic)
Assignee: (unassigned
** Changed in: udisks2 (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: udisks2 (Ubuntu)
Status: New => Fix Committed
** Changed in: udisks2 (Ubuntu)
Importance: Undecided => High
** Changed in: udisks2 (Ubuntu Mantic)
Importance: Undecide
1 - 100 of 91295 matches
Mail list logo