Hm, yeah looking at the amd64[1] vs arm64[2] builds for libdnf on noble,
they were done a few days apart. There was enough of a gap that amd64
was built with dh-python 20231223ubuntu2, whereas arm64 was built with
6.20240401.
From a quick look (`apt-file search "_module.cpython"` on noble amd64),
The dh-python change seems reasonable. But if we wanted to avoid a dh-
python SRU, and if libdnf is apparently the only affected package, could
we instead add a hack in libdnf's d/rules to fix the incorrect renaming?
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Newer versions of systemd ships services that utilized systemd
credentials more[1].
Unfortunately, lxd's default apparmor restrictions are overly
restrictive and prevent these from working. Assuming you are using
unprivileged containers, the solution is to set security.nesting=true in
the LXD conf
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092463
Title:
Upgrading the repository information resulted in a invalid file so a
bug reporting process is being star
** Description changed:
[Impact]
Upgrades from Ubuntu Studio 22.04 to 24.04 cannot be calculated. A quirk
is required to install pipewire-audio, and remove pulseaudio during the
upgrade.
[Test Plan]
1. Confirm that upgrades on Ubuntu Studio are able to be calculated, and
tha
** Description changed:
[Impact]
Some packages such as libcap2-bin or ghostscript-x get replaced by
cross-graded/or cross-replacement packages, such as
libcap2-bin:amd64 => libcap2-bin:i386
ghostscript-x:amd64 => ghostscript:i386 (should be ghostscript:amd64)
These are Multi-Arch:
We do not use systemd-stub in Ubuntu classic installs. It seems like
this question is better suited for upstream:
https://github.com/systemd/systemd/issues
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I need to spend more time on this, but what I have observed so far is
that the service failure is due to /usr/bin/nginx not being
visible/executable. This is probably a sandboxing issue, but needs more
investigation.
Before running the repro steps, I added:
# /etc/systemd/system/nginx.service.d/o
untu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I believe this is because in systemd v250 (which is in between 22.04's
systemd v249, and 24.04's systemd v255), a network interface naming
scheme was added for Xen netfront interfaces[1].
So, basically, udev is using a different name for the interface now.
One way to work around this in the futur
** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092945
Title:
upgrade from 22 to 24 broke static ip
To manage notifications a
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => 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/2083942
Title:
snaps are not upgraded to the latest version befo
Thanks for your detailed bug report.
> 1. Install the current release of `openssh-server`.
Can you please be more specific? The output of `apt policy openssh-
server` on the affected server would be most helpful.
> 3. Exceed the configured number of attempts. For good measure, I
suggest attempti
** Tags added: foundations-todo
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078639
Ti
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
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/2092648
Will this bug be fixed for Budgie anytime soon? I'm waiting until it's
done before upgrading. Is there an alternative workaround other than
re-install?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New => 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/473436
Title:
Primary monitor doesn't wake up out of power save m
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
systemd autopkgtests are failing in kinetic, and they are not considered
regressions. The failing test is one within networkd-test.py:
==
ERROR: test_resolved_domain_restricted_dns
** Description changed:
[SRU TEMPLATE]
[DESCRIPTION]
We currently use Ubuntu 22.04.1 LTS including updates for our production
cloud (switched from legacy Centos 7).
Although we like the distribution we recently hit serious systemd buggy
behavior described in [1] bugreport using pac
** Description changed:
[SRU TEMPLATE]
[DESCRIPTION]
We currently use Ubuntu 22.04.1 LTS including updates for our production
cloud (switched from legacy Centos 7).
Although we like the distribution we recently hit serious systemd buggy
behavior described in [1] bugreport using pac
** Tags added: systemd-sru-next
** Also affects: dnsmasq (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status:
** Changed in: containerd (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.launchpad.net/bugs/2089893
Title:
Please merge 1.7.23_ds2-1 into plucky
To manage notificat
** Changed in: avahi (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.launchpad.net/bugs/2090963
Title:
Please merge 0.8-14 into plucky
To manage notifications about
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003250
Title:
networkctl reload with bond devices causes slaves to go DOWN and UP,
causing couple of seconds of netwo
om ideal, expanding this hack has become the go-to
for existing stable releases.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: systemd (Ubuntu Noble)
Importance: Medium
Assignee: Nick Rosbrook (enr0n)
Status: Triaged
** Tags: systemd-
I see the following in the apt log:
MarkInstall linux-generic:amd64 < none -> 6.8.0-50.51 @un uN Ib > FU=1
Installing linux-image-generic:amd64 as Depends of linux-generic:amd64
linux-image-generic:amd64 Depends on
linux-modules-extra-6.8.0-50-generic:amd64 < none @un H > can't be satisfi
Public bug reported:
got error messages during an "apt -y upgrade"
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-50-generic 6.8.0-50.51
ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12
Uname: Linux 6.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_modeset
This does indeed go away will all-proposed=1.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Tags removed: 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/2091318
Titl
I have uploaded a patch for the devel series (plucky) for now. But
before we try to push an SRU through, I would like to dig more into the
restart-ability of glusterd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Also affects: glusterfs (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/2085070
Title:
[SRU] glusterd should not be automatically restarted
To
The After= makes complete sense. It's the Requires= I am not sure of.
Have you tried without that? Or maybe use Wants= instead?
If glusterd.service is safe to restart (i.e. won't disrupt the mount),
then it should be allowed to do so. Removing Requires= would prevent
dependent services from being
I completely missed that libnftnl was a separate source package. Based
on previous bugs I immediately jumped to look at the pinning, and then
found the recent autopkgtest bug. Sorry about that.
Removing affects: nftables to unblock its migration.
** No longer affects: nftables (Ubuntu)
** Change
With autopkgtest upstream (HEAD at 8c8368c074 at time of writing), I get
this behavior:
autopkgtest cmdline: /home/nr/ubuntu/code/autopkgtest/runner/autopkgtest
systemd --shell-fail -U --test-name upstream --apt-
pocket=proposed=src:nftables -- qemu /home/nr/ubuntu/autopkgtest-
testbeds/autopkgtes
** Summary changed:
- upstream test misconfigures priority trigger packages
+ upstream test misconfigures pin-priority for trigger packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091318
Title
I am thinking this might actually be an autopkgtest bug[1], not related
to the upstream test.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088971
** Bug watch added: Debian Bug tracker #1088971
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088971
--
You received this bug notif
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
I am intentionally marking nftables as well, because I would like to
hold it in -proposed if possible to investigate this today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091318
Title:
upstream
Public bug reported:
In this test for example[1], where nftables is a trigger, we see:
4476s Some packages could not be installed. This may mean that you have
4476s requested an impossible situation or if you are using the unstable
4476s distribution that some required packages have not yet been
Have you intentionally prevented your system from having merged /usr?
Having unmerged /usr is not supported on Ubuntu. Can you please fix this
and then try again?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of U
** Changed in: cdebconf (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.launchpad.net/bugs/2090950
Title:
Please merge 0.274 into plucky
To manage notifications abou
** Changed in: mailcap (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.launchpad.net/bugs/2090933
Title:
Please merge 3.74 into plucky
To manage notifications about
Is it really necessary for the mount unit to Requires=glusterd.service?
Does restarting glusterd.service actually make the shared mount
unusable?
If you remove the Requires=glusterd.service (or the
Requires=shared.mount on the other unit), and restart glusterd.service,
does everything carry on OK?
** Also affects: keepalived (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: needrestart (U
Public bug reported:
Tracking bug.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Nick Rosbrook (enr0n)
Status: In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu)
Importance: Undeci
From what I can tell, and according to my own tests, this is working
correctly. I think this is a misunderstanding of a couple things:
1. OnCalendar= can be specified multiple times, allowing multiple
trigger times. If you want to completely override the original setting,
you need:
[Timer]
# This
As the output says, you need to resolve the conflict with postgresql-10
before upgrading. If you have already migrated everything on this system
away from postresql-10 to a newer version, then it is safe to remove the
old package.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
** Package changed: ubuntu-release-upgrader (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2090793
Title:
installed linux-image-6.8.0-49-generic package post-installation
** Changed in: ubuntu-release-upgrader (Ubuntu)
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/2090612
Title:
Lost icons after upgrade from 24.04 LTS to 24.10
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089847
Title:
syste
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
** Tags added: rls-jj-incoming
** Also affects: ubuntu-release-upgrader (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/2055825
Title:
fips-update
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
** Also affects: systemd (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Oracular)
Importance: Undecided => Medium
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Based on the many stack traces in dmesg, I think this is more likely a
kernel bug.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085314
Title:
systemd-netowrk segfault (question #819069)
To manage notifications about this bug go to:
https://bugs.l
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088268
Title:
systemd /tmp cleaning removes files that it shouldn't
To manage notifications about this bug go to:
https
Can you please enable debug logs on systemd-networkd, and attach logs
from a time where the bug occurs? E.g.,
$ mkdir -p /etc/systemd/system/systemd-networkd.service.d
$ cat > /etc/systemd/system/systemd-networkd.service.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF
$ rebo
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
You have a lot of third-party sources enabled, including some Debian
sources. All of these versions are causing conflicts with what is in the
Ubuntu archive.
Besides removing packages installed from those sources, I am not sure
what to suggest. Sorry.
** Changed in: ubuntu-release-upgrader (Ubunt
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874927
Title:
do-release-upgrade's upgradeable package check doesn't consider kept
back packages
To manage notificati
Ah, I did not realize this was from a Debian patch. Thanks for opening
the bug in Debian!
** Also affects: tigervnc (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087925
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a memb
** Changed in: ubuntu-release-upgrader (Ubuntu)
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/2086793
Title:
do-release-upgrade 22.04 => 24.04 Could not calculate the u
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
Yes, it looks like your mirror does not have information for the 24.04
release:
2024-11-01 09:24:29,016 DEBUG Checking pkg: ubuntu-standard
2024-11-01 09:24:29,020 DEBUG examining: 'deb
https://it1.mirror.vhosting-it.com/ubuntu/ jammy main restricted'
2024-11-01 09:24:29,020 DEBUG verifySourcesLi
I am going to sync the Debian change over my Ubuntu upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088947
Title:
python-distutils-extra: FTBFS: AssertionError: 'ERROR: Python module
setupt
Also, can you all try to restore socket activation, and see if the
problem persists? You can restore socket activation by running:
# This removes the symlink to mask the generator, if needed.
$ rm -f /etc/systemd/system-generators/sshd-socket-generator
$ systemctl daemon-reload
$ systemctl disable
Chris, Kevin, John, or anyone else affected:
Is it possible that you changed your sshd_config without actually
reloading and restarting ssh.socket, a while (hours, days, etc.) before
the upgrade occurred? I am wondering if it's possible that the
configuration was already broken by a local change,
** Changed in: pappl-retrofit (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/2058771
Title:
proposed-migration for pappl-retrofit 1.0~b2-0ubuntu7
To mana
*** This bug is a duplicate of bug 2080216 ***
https://bugs.launchpad.net/bugs/2080216
Thanks for this bug report. This is effectively a duplicate of bug
2080216 (same root cause, same fix).
The patch for this is currently available in noble-proposed, and should
hopefully land in noble-update
Adding a jammy task for systemd because I see the error there now. At
the very least I want to just skip the test in jammy to get a green
baseline again.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undeci
This log shows the tests-in-lxd test passing now:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/s/systemd/20241120_155239_e1b7a@/log.gz.
The autopkgtest run overall fails due an existing failure in networkd-
test.py, but that is unrelated. Unfortunately that test comes and
** Changed in: openssh (Ubuntu)
Status: Triaged => 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/2088207
Title:
cloud-init enables ssh password auth in an unexpected config file
** Changed in: openssh (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/2089049
Title:
systemd-socket-activation test can be flaky
To manage notifications
I have sponsored the uploads for oracular and noble.
** Changed in: ssh-import-id (Ubuntu Noble)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: ssh-import-id (Ubuntu Oracular)
Assignee: (unassigned) => Olivier Gayot (ogayot)
** Changed in: ssh-import-id (Ubuntu Noble)
Thanks for the debdiff. This looks good! I have sponsored with one small
change - normally with merges, when the new changelog entry contains an
old bug number reference (as this one does), we change:
(LP: #1234567) -> (LP #1234567)
i.e., we remove the ":". This makes it so that Launchpad does no
This is currently in the Ubuntu Sponsors queue, but I don't see an
actionable request.
The changes were uploaded to Plucky already, and I don't see an MP or
anything else for stable releases, so I am unsubscribing Ubuntu Sponsors
for now.
--
You received this bug notification because you are a m
De-prioritizing for now due to lack of feedback.
** Tags removed: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
There is a race condition in this test when checking the the ssh.service
ActiveState after calling systemctl reload. E.g. from [1]:
1537s autopkgtest [11:13:00]: test systemd-socket-activation:
[---
1538s Stopping ssh.service...
1538s Checking that ssh.so
Public bug reported:
Under Software and Updates -> Additional Drivers, I have enabled the IPU6
Driver for the webcam
Now at least this seems to install without a crash
However, no application can detect a camera (Skype, Cheese, Gnome Camera)
If I query the devices, this is the output.
$ v4l2-ct
I have verified the fix using systemd 255.4-1ubuntu8.5 from noble-
proposed:
$ cat > /etc/apt/sources.list.d/proposed.sources << EOF
> Types: deb
URIs: http://archive.ubuntu.com/ubuntu/
Suites: noble-proposed
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-arc
I verified the fix using systemd 249.11-0ubuntu3.13 in jammy-proposed.
First, I confirmed that my systemd and kernel combination is affected by
this bug:
$ uname -a
Linux clean-jammy-amd64 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Tue May 7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/
If you have not already, I would recommend opening a bug against
upstream tigervnc. As I said, I think it needs to re-work it's runtime
directory handling, and that is something that is best driven by
upstream, as opposed to in Ubuntu.
--
You received this bug notification because you are a membe
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1086308:
Package: src:python-distutils-extra
Version: 3.0
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to
build:
As mentioned on bug 2088433, you can create a local override if you want
something different than the default. E.g. create
/etc/tmpfiles.d/tmp.conf with your own configuration for /tmp.
Regarding x11.conf, this has been that way for a long time AFAICT, and I
don't know enough about that package to
1 - 100 of 9815 matches
Mail list logo
