This is expected behavior.
Since /tmp is a tmpfs by default, the default
/usr/lib/tmpfiles.d/tmp.conf is configured with a 10d cleanup age for
/tmp, but it is *not* configured to clean /tmp at boot, because that is
unnecessary for a tmpfs.
If you want to clean /tmp at boot *and* have your tmp.mou
** Description changed:
+ [Impact]
+
+ Server users will see an unnecessary error message about failing to
+ disable the lock screen, which may cause confusion.
+
+ [Test Plan]
+
+ * Obtain a console on Impish server, e.g. ssh to a remote host.
+ * Verify that XDG_SESSION_TYPE is set to 'tty':
** Package changed: ubuntu-release-upgrader (Ubuntu) => firefox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974079
Title:
Firefox and Thunderbird fail to open after recent updates
To ma
I think this a duplicate of, or closely related to bug 1966203.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971955
Title:
systemd-udevd call unshare process when attaching nvme volume
To manag
I think there are actually two similar bugs here. The first I think is
caused by [1], which I have confirmed is present in impish, but not
focal or jammy. This can be demonstrated by the following:
$ resolvectl dns eth0 8.8.8.8 8.8.4.4 1.1.1.1
$ resolvectl dns eth0
Link 110 (eth0): 8.8.8.8 8.8.4.
** Description changed:
+ [Impact]
+
+ Users upgrading to Jammy, rather than doing a fresh install, will not
+ have snapd-desktop-integration installed on their systems. This snap is
+ seeded in Jammy, so users upgrading to Jammy should also get it
+ installed.
+
+ [Test Plan]
+
+ From Impish,
Hi Paul,
Please run `apport-collect 1976293` from a terminal on the affected
system. This will attach the relevant log files from your system to this
bug report.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you ar
It looks like the upgrade failure is ultimately caused by pacakges from
the ondrej/php PPA. In particular, libgd3
2.3.0-2+ubuntu16.04.1+deb.sury.org+1 depends on a version of libpng12-0
that creates a conflict for usrmerge.
Please try removing packages from ondrej/php using the `ppa-purge` tool,
a
It looks like there was a network issue during your upgrade attempt:
# From VarLogDistupgradeMainlog.txt
2022-05-29 00:18:25,030 DEBUG url_downloadable:
http://in.archive.ubuntu.com/ubuntu//dists/impish/Release
2022-05-29 00:18:25,030 DEBUG s='http' n='in.archive.ubuntu.com'
p='/ubuntu//dists/im
I have tested upgrade from Impish to Jammy using version 1:22.04.11
using the test plan above (and appending --proposed to do-release-
upgrade), and I have verified this issue is fixed.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug not
I have tested upgrade from Impish to Jammy with package version
1:22.04.11 using the test plan above (and appending --proposed to do-
release-upgrade), and I have verified this issue is fixed.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this
I have tested upgrade from Impish to Jammy with package version
1:22.04.11 using the test plan above (and appending --proposed to do-
release-upgrade), and I have verified this issue is fixed.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this
9@/log.gz
[3]
https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/ppc64el/libc/libcloud/20220526_090523_a6c63@/log.gz
** Affects: libcloud (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: In Progress
** Changed in: libcloud (Ubuntu)
Assignee
** Patch added: "libcloud-lp-1977320.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libcloud/+bug/1977320/+attachment/5594672/+files/libcloud-lp-1977320.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Patch added: "libcloud-lp-1977320-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libcloud/+bug/1977320/+attachment/5594714/+files/libcloud-lp-1977320-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I have verified the fix using systemd 255.4-1ubuntu8.2 from noble-
proposed:
nr@zero:~$ lxc launch ubuntu-daily:n n
Creating n
Starting n
nr@zero:~$ lxc exec n bash
root@n:~# vim /etc/apt/sources.list.d/ubuntu.sources
root@n:~# apt update && apt install -t
I have verified the fix using systemd 255.4-1ubuntu8.2 from noble-
proposed:
nr@six:/t/t/mkosi$ apt policy systemd
systemd:
Installed: 255.4-1ubuntu8.2
Candidate: 255.4-1ubuntu8.2
Version table:
*** 255.4-1ubuntu8.2 100
100 http://us.archive.ubuntu.com/ubuntu noble-proposed/main amd
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
** Tags removed: foundations-todo
** Tags added: systemd
It is correct that LTS to LTS+1 upgrades are not enabled until the .1
release of LTS+1. This usually happens around August.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
samba has a test failing[1] because of this, which is blocking systemd
from migrating. The same apparmor denials can be seen in the test log.
These denials cause systemd-resolved to fail to start in the member-
server container, which ultimately causes the test to fail.
We should be able to fix th
** Package changed: systemd (Ubuntu) => ntpsec (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071911
Title:
ntpsec: mssntp in ntp.conf breaks time service to all clients
To manage notific
Fixed in https://salsa.debian.org/systemd-
team/systemd/-/merge_requests/267, so we will get it in Ubuntu soon.
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
LP is eating my indentation in the changelog entry example, but
hopefully you get the idea.
** Changed in: puppetdb (Ubuntu Noble)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Thanks for finding the minimal patches required for this. A few
organizational things:
1. 0008-Resolve-ftbfs-with-java-21.patch: It would be good to have an
Origin: field in the patch showing where you got this. It's good you
have the Author: for credit, but links are easier to follow. I also
pref
Thanks! I have gone ahead and uploaded.
I did make one minor adjustment because I forgot to mention something
before. Generally, it is a good idea to follow [1] when selecting a
version number for SRUs. In this case, it might not technically matter
because oracular already has a new upstream versi
Public bug reported:
As seen in this build log[1], the distro build flags are not used. This
should be fixed so that e.g. -fno-omit-frame-pointer is picked up.
[1] https://launchpadlibrarian.net/723749641/buildlog_ubuntu-noble-
amd64.cdparanoia_3.10.2+debian-14build3_BUILDING.txt.gz
** Affects:
This happens because in debian/rules, there is:
export CFLAGS += ...
instead of
export DEB_CFLAGS_MAINT_APPEND = ...
After making that change, there is FTBFS due to warnings as errors:
make[2]: Entering directory '/<>'
gcc -O2 -fsigned-char -g -O2 -fno-omit-frame-pointer
-mno-omit-leaf-frame-
** Changed in: cdparanoia (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/2073149
Title:
cdparanoia does not build with distro build flags
To manage notif
** Also affects: grub2 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-release-upgrad
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: systemd (Ubuntu)
Status
Is systemd-networkd enabled? Is this a server or a desktop installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073087
Title:
org.freedesktop.network1 doesn't start after boot
To manage not
I.e., can you show the output of systemctl is-enabled systemd-networkd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073087
Title:
org.freedesktop.network1 doesn't start after boot
To manage noti
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069834
Title:
systemd defaulting to tmpfs for /tmp causes enospc errors
To manage
I am tagging this so that Foundations can review. There are some
developers who specifically work on the Python toolchain, and I would
prefer that they be the ones to review and sponsor this.
A couple things in the meantime:
* There has been a security update since the last time you refreshed the
** Merge proposal linked:
https://code.launchpad.net/~lukasrettler/ubuntu/+source/kubectx/+git/kubectx/+merge/469569
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073369
Title:
zsh completion n
Hi! I have left a comment on the MP here:
https://code.launchpad.net/~lukasrettler/ubuntu/+source/kubectx/+git/kubectx/+merge/469569.
Related to the SRU process, this bug is already fixed in the development
series [1] (oracular), so this only needs to be fixed in noble. I am
updating the bug statu
Hi John,
1. The first thing I notice is that the bug number is missing from all of the
debdiffs.
2. Second, I am not an SRU team member, but before sponsoring I would want to
be sure this has an acceptable test plan and regression risk analysis. IMO,
this is currently lacking those two things.
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 looks like a server side error with your mirror:
2024-08-30 17:37:16,197 DEBUG examining: 'deb
http://nl3.archive.ubuntu.com/ubuntu/ jammy main restricted'
2024-08-30 17:37:16,197 DEBUG verifySourcesListEntry: deb
http://nl3.archive.ubuntu.com/ubuntu/ noble main restricted
2024-08-30 17:37:
** 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/2078720
Title:
Upgrading from jammy to noble results in a linux-headers package being
in a broken state
To manage noti
*** This bug is a duplicate of bug 2078555 ***
https://bugs.launchpad.net/bugs/2078555
Thanks for your bug report. As you noted, this is the same issue as bug
2078555 so I am marking this as a duplicate to consolidate.
** This bug has been marked a duplicate of bug 2078555
Upgrading from 2
c:nield -a source
No reverse dependencies found
[1]
https://launchpadlibrarian.net/744524684/buildlog_ubuntu-oracular-amd64.nield_0.6.1-2build1_BUILDING.txt.gz
[2]
https://lore.kernel.org/netdev/6f24a4f8-fb07-409b-955a-9aad4ab37...@gmail.com/T/
** Affects: nield (Ubuntu)
Importance: Undecided
As
: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: glosstex (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Description changed:
glosstex 0.4.dfsg.1-4build1 is stuck in -proposed.
+
+ It FTBFS[1] and has no reve
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1066361:
Source: atlas
Version: 3.10.3-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid,
Public bug reported:
sslh 2.1.1-1 is stuck in -proposed.
** Affects: sslh (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: sslh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Summary chan
** 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/209
Title:
PTP device symlink missing after running udevadm trigger command
To manage notifications about this bug
process returned exit status 2
It seems that a simple fix is to remove the hard coded -D_FORTIFY_SOURCE
lines in the relevant Makefiles, and instead let the distro build flags
take precedence.
[1]https://launchpadlibrarian.net/744524447/buildlog_ubuntu-oracular-
amd64.detox_2.0.0-3_BUILDING.t
I did forward this to debian, but unfortunately forgot to include the
link in Bug-Debian in the patch header.
** Changed in: detox (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Debian Bug tracker #1080967
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080967
** Also aff
revious definition
cc1: all warnings being treated as errors
** Affects: mmc-utils (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: mmc-utils (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
_url
/usr/lib/python3/dist-packages/datalad/support/s3.py:23: in
import boto3
E ModuleNotFoundError: No module named 'boto3'
** Affects: datalad-next (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: Fix Committed
** Affects: datalad-ne
** Bug watch added: Debian Bug tracker #1080969
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080969
** Also affects: datalad-next (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080969
Importance: Unknown
Status: Unknown
** Changed in: datalad-next (Ubuntu)
icit-function-declaration]
91 | iattr = ntohl(*(u32 *)data);
| ^
make[1]: *** [Makefile:22: object.o] Error 1
[1] https://launchpadlibrarian.net/744527373/buildlog_ubuntu-oracular-
armhf.vstream-client_1.2-7ubuntu1_BUILDING.txt.gz
** Affects: v
** Bug watch added: Debian Bug tracker #1075628
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075628
** Also affects: vstream-client (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075628
Importance: Unknown
Status: Unknown
--
You received this bug notificati
This patch is in v256.5, which I prepared and uploaded today.
** Changed in: systemd (Ubuntu Oracular)
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/209
** Changed in: ubuntu-release-upgrader (Ubuntu Oracular)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074309
Title:
upgrade 22.04 -> 24.04 won't start due to fe
gtest [07:19:42]: test ncdu: ---]
** Affects: cruft-ng (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: cruft-ng (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Description
Forwarded to debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1081002
** Changed in: cruft-ng (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Debian Bug tracker #1081002
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081002
** Also affects: cruft-ng (Debian) via
Ugh, LP ate my comment and I didn't notice. Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079513
Title:
Please remove sslh from the archive
To manage notifications about this bug
** Description changed:
sslh 2.1.1-1 is stuck in -proposed.
+
+ This package FTBFS on all arches (except riscv64), e.g.
+ https://launchpadlibrarian.net/744540879/buildlog_ubuntu-oracular-
+ amd64.sslh_2.1.1-1_BUILDING.txt.gz.
+
+ It has no reverse dependencies:
+
+ nr@six:~$ reverse-depends
There is still one more build-time test failure on armhf:
https://launchpadlibrarian.net/747678259/buildlog_ubuntu-oracular-
armhf.detox_2.0.0-3ubuntu1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Changed in: glibc (Ubuntu Noble)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648
Title:
Support upgrades from unmerged 22.04 - was: package libc6
2.3
Public bug reported:
E.g. https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/s390x/i/initramfs-tools/20240909_091354_592dd@/log.gz
1489s autopkgtest [09:13:45]: summary
1489s qemu-ata-onlySKIP Test lists explicitly supported architectures,
but the
I don't think I see a reason to remove from the release pocket.
** Changed in: sslh (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079513
Title:
Please rem
Is sshd not accessible at all over ipv4? How did you notice that sshd
was not listening on ipv4?
In the default case, we should end up with ssh.socket listening on
[::]:22, but with IPV6_V6ONLY=0 so that sshd is still accessible over
ipv4.
> Setting net.ipv6.bindv6only=0 also helps, but that's no
** 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/2080233
Title:
[wsl] do-release-upgrade fails with systemd disabled
To manage notifications about this bug go to:
https:
We don't remove old versions of postgres ourselves due to the risk of data
loss when upgrading to new versions so it should be an informed user-
driven process.
If you are absolutely sure you no longer need that version of postgres,
you can remove it and try the upgrade again.
** Changed in: ubun
** 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/2051407
Title:
qemu-net autopkgtest fails: Failed to send exit request: Resource
tempora
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: systemd (Ubuntu)
Status
systemd-binfmt should just exit when /proc/sys/fs/binfmt_misc is not
mounted rw, which I thought was usually the case in LXD containers.
Are you running a privileged or unprivileged container?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Imp
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Lo
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: systemd (Ubuntu)
Status
Are you able to run unprivileged containers instead? That would be the
suggested configuration from upstream LXD.
There are many things that do not work with systemd in privileged LXD
containers due to AppArmor etc. Upstream systemd does not like adding
workarounds for issues caused by AppArmor ru
The package built successfully:
https://launchpad.net/ubuntu/+source/systemd-hwe/255.1.4
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
** 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
** Tags added: foundations-todo
** Changed in: systemd (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/2080257
Title:
[WSL] syst
This autopkgtest result for systemd 255.4-1ubuntu8.1 shows the unit-
tests test now passing:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/s/systemd/20240522_201458_f86bd@/log.gz.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-don
You could install libnss-myhostname (provided by systemd) instead of
adding the hostname to /etc/hosts. libnss-myhostname takes care of
mapping the local hostname to 127.0.0.1, so that listing the hostname
explicitly in /etc/hosts is not necessary. See
https://github.com/systemd/systemd/issues/1279
** Tags added: rls-nn-incoming
** Changed in: ubuntu-release-upgrader (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/2067071
Title:
cannot upgrade from 23.1
The autopkgtest regressions were all resolved with retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065964
Title:
test-execute fails because of apparmor unprivileged userns
restrictions
To
The autopkgtest regressions were all resolved with retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064096
Title:
Services fail to start in noble deployed with TPM+FDE
To manage notification
The autopkgtest regressions were all resolved with retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
Dist upgrades from Jammy to Noble crash [Oh no! Something has gone
wrong.]
The autopkgtest regressions were all resolved with retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047975
Title:
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
installe
As far as I know, systemd-networkd has never been enabled by default for
Desktop installations. It is enabled by default on Server installations.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
systemd-pull is provided by the systemd-container package. Please
install systemd-container and try again.
** 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.laun
** 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/2067071
Title:
cannot upgrade from 23.10 to 24
My understanding from the Debian bug is that this really is a netplan
issue, not systemd. Is that accurate?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => Low
** Chan
This sounds like a bluez bug, not systemd.
** Package changed: systemd (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064869
Title:
systemd bluetooth not honoring stop se
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: systemd (Ubuntu)
Status
** 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/2065580
Title:
package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс
из пакета udev установлен сценари
This is just a debug message and can be ignored AFAICT.
** Changed in: systemd (Ubuntu)
Status: New => Opinion
** Changed in: systemd (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
*** This bug is a duplicate of bug 2065580 ***
https://bugs.launchpad.net/bugs/2065580
** This bug has been marked a duplicate of bug 2065580
package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из
пакета udev установлен сценарий post-installation возвратил код ошибки 1
-
Is this still an issue? My understanding was that there was some
debootstrap issue, but that this is not actually related to systemd. Not
sure if anything was fixed though.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided =>
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs,
systemd 252 was in Lunar, which is EOL.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042756
Title:
package systemd 252.5-2ubuntu3.2
** Changed in: systemd (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/1912855
Title:
debugfs shouldn't be mounted by default
To manage notifications about th
Debian is going back to upstream behavior for this, and we will follow
(except for extending the clean up age for /tmp to 30d). This will be in
the next oracular upload, but we won't backport.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notificatio
*** This bug is a duplicate of bug 1791102 ***
https://bugs.launchpad.net/bugs/1791102
** This bug is no longer a duplicate of bug 2065580
package udev 249.11-0ubuntu3.12 failed to install/upgrade: подпроцесс из
пакета udev установлен сценарий post-installation возвратил код ошибки 1
** Th
I don't think there is anything left in systemd to do for this.
** 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/1874337
Title:
resolvconf
1 - 100 of 1166 matches
Mail list logo
