Hi Mitchell,
No other issues here -- your description is perfect!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064930
Title:
dnsmasq cannot execute at systemctl
To manage notifications about
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
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.
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
Update:
Editing /sys/module/snd_hda_intel/parameters/power_save' from '1' to '0'
is a temporary workaround. So it is indeed caused by the audio chipset's
power-saving.
Seems the root cause is that mouse clicks that were never intended to produce a
sound (i.e., clicking empty screen space)
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.
** 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
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
I have included a picture of the audio jacks affected, marked with a red
asterisk in the attachment.
The affected audio jacks are:
-Black (rear speakers)
-Orange (centre and sub speakers)
-Lime (front speakers)
** Attachment removed: "Surround-Sound-Ports.jpg"
I have included a picture of the audio jacks affected, marked with a red
asterisk in the attachment. My setup is 6-channel.
The affected audio jacks are:
-Black (rear speakers)
-Orange (centre and sub speakers)
-Lime (front speakers)
** Attachment added: "Surround-Sound-Ports.jpg"
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
** 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
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
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
I will experiment with different jacks and report back soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072432
Title:
Loud, brief speaker popping/distortion occurs when clicking on empty
or
6.8.4
Uname: Linux 6.8.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:nick 2731 F pipewire
/dev/snd/controlC1: nick 2736 F
-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/seq:nick 2731 F pipewire
- /dev/snd/controlC1: nick 2736 F wireplumber
- /dev/snd
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:nick 2731 F pipewire
/dev/snd/controlC1: nick 2736 F wireplumber
/dev/snd/controlC0: nick 2736 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 7 15:25:28 2024
Public bug reported:
Attempting to use do-release-upgrade to upgrade from mantic to noble,
fails & reverts. Appears (from main.log) to be due to
postgresql-15-postgis-3 being installed.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.14
do you have any more logs than the dh_install step?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071804
Title:
notcurses FTBFS on oracular riscv64
To manage notifications about this bug go to:
thanks for the report. let me look into this and see what's going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071804
Title:
notcurses FTBFS on oracular riscv64
To manage notifications about
==
Ubuntu Security Notice USN-6857-1
June 27, 2024
squid3 vulnerabilities
==
A security issue affects these releases of Ubuntu and its derivatives:
-
** Changed in: systemd (Ubuntu Focal)
Status: Triaged => Won't Fix
** Changed in: systemd (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Noble)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
@xghost it does not sound like you are hitting the original bug that
this upgrader quirk was meant to prevent (bug 2039172), so I would
suggest asking for help on e.g. askubuntu.com or IRC, or look at
https://discourse.ubuntu.com/t/community-support/709. Or, open a new bug
report and provide
Actually, re-opening for systemd for now so it shows up on update-
excuse.
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069834
Thanks! That log confirms that you ran the upgrade using the upgrader
from noble-proposed. That along with your previous comment confirms the
fix.
Thanks again!
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you
There was a lot of work in netplan related to this area in Noble (see
e.g. bug 2060311). This bug has a lot of valuable information, but the
new behavior as changed enough that I don't think we should keep this
open.
And, mantic is EOL soon enough that doing an SRU for mantic specifically
is not
I don't think there is anything to do for systemd for now. I recall some
vague feature request for systemd-sysusers, but that's not something
that is really captured by this bug. If someone feels that feature
should be added, please open an upstream feature request at
My understanding is that we will leave the systemd defaults as-is for
now, so marking won't fix for systemd.
** 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.
** Description changed:
+ Many units shipped by systemd use credentials in some way by default now
+ (in v256). So this issue is now about much more than the original test
+ case failure.
+
+ For example,
+
+ root@oracular:~# apt policy systemd
+ systemd:
+ Installed: 256-1ubuntu1
+
As I mentioned on the LXD PR[1]
https://github.com/canonical/lxd/pull/12698#issuecomment-2105170174,
many important services now use credentials in some way (including
networkd, resolved, journald), so this issue is very apparent with
systemd v256.
--
You received this bug notification because
Thanks, Bart! Can you please attach /var/log/dist-upgrade/main.log as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067886
Title:
Remove the XFS /boot upgrade check for noble
To manage
I have uploaded this to oracular.
In the future I think you could add a bit more detail about the changes
made when bringing in the new upstream, but in this case the major
changes were dropping patches.
** Changed in: python-uefivars (Ubuntu)
Status: New => Fix Committed
--
You
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
** Tags added: update-excuse
--
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 notifications about this bug go to:
I think option (2) is the probably the "best" fix. Another alternative I
can think of is shipping a tmp.mount drop-in on the autopkgtest
environment to change the size to something better. E.g.,
# /etc/systemd/system/tmp.mount.d/size.conf
[Mount]
Options=size=
where could be a percentage of RAM
> Please add to the Test Plan to verify that there are no conffile
prompts in the at-risk upgrade paths.
Added. Thanks.
** Description changed:
[Impact]
There is currently no comment in the default /etc/ssh/sshd_config
explaining that a systemctl daemon-reload is needed for changes to
** 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/2046486
Title:
units with credentials fail in LXD containers
To manage notifications about this bug go to:
Adding block-proposed for now because I believe the armhf autopkgtest
environment will be affected once systemd in oracular-proposed migrates.
I hope to get security.nesting: true turned on in the autopkgtest
environment soon to avoid this, and to let systemd migrate.
--
You received this bug
I found that after working around this issue (with seccomp rules) there
are yet more AppArmor denials during namespace set up.
All in all, systemd services with sandboxing settings (i.e. settings
that require the use of various namespaces) hit more and more denials in
LXD containers. So, after
** Changed in: openssh (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config requires calling systemctl
I have verified the fix using ubuntu-release-upgrader from noble-
proposed:
test@m:~$ do-release-upgrade --proposed
Checking for a new Ubuntu release
= Welcome to Ubuntu 24.04 LTS 'Noble Numbat' =
The Ubuntu team is proud to announce Ubuntu 24.04 LTS 'Noble Numbat'.
To see what's new in this
Have you tried to determine if there is a minimal set of patches that
could be cherry-picked for an SRU, rather than backporting a new
upstream version? Usually, backporting a new upstream version as an SRU
requires a micro release exception, but I do not see any for this
package on [1].
** Description changed:
+ [Impact]
+
+ There is currently no comment in the default /etc/ssh/sshd_config
+ explaining that a systemctl daemon-reload is needed for changes to Port
+ etc. to take effect when systemd socket activation is used (the default
+ on Ubuntu).
+
+ Users may change e.g.
If you are currently hitting this problem, and would like to help verify
the fix, please run the upgrade again with:
$ do-release-upgrade --proposed
** Description changed:
[Impact]
Upgrades for users with XFS /boot are wrongly blocked for noble as the
workaround for mantic hasn't been
I have verified the fix using ubuntu-release-upgrader from noble-
proposed (via do-release-upgrade --proposed):
root@m:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu
ID_LIKE=debian
** Description changed:
[Impact]
Upgrades to noble chmod /dev/null 644, breaking use of the device on
multi-user systems for non-root.
[Test plan]
- 1. do-release-upgrade mantic -> noble
+
+ Upgrade from mantic to noble:
+
+ 1. do-release-upgrade --proposed
2. check that /dev/null
Zero crashes. Service uptime 1d 9h.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To manage notifications about this bug go to:
** Description changed:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
pointer deference.
[ Test Plan ]
* I experienced
** Description changed:
[ Impact ]
* Users experience brick SEGFAULTs under certain not-yet-understood
scenarios. Some reports include a high percentage of small file I/O. I
encountered the issue roughly every hour with Minio backed by GlusterFS
on ZFS.
* This bug introduces
@perdromacedo can you share the output of
$ grep Port /etc/sshd/sshd_config
$ systemctl daemon-reload
$ systemctl status ssh.socket ssh.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069041
** Description changed:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
pointer deference.
[ Test Plan ]
* I experienced
Packages installed and running. Looks good so far. I'll continue to
monitor it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To manage notifications about
Ah, ok. Per https://github.com/canonical/ubuntu-maintainers-
handbook/blob/main/VersionStrings.md#version-adding-a-change-in-ubuntu-
as-a-stable-release-update the part after the dot specifies that it's an
SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The new version in noble-proposed is "11.1-4ubuntu0.1" vs the patch
which has "11.1-4ubuntu1". Is that expected or did I screw up the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Yep! Understood. I'll install them once available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064843
Title:
Brick SEGFAULTs in 11.1
To manage notifications about this bug go to:
** Description changed:
[ Impact ]
* Users experience SEGFAULTs when Ganesha fails to communicate with
Gluster, causing the NFS share to disappear.
* The patch refactors how free_space() is called to avoid the null
pointer deference.
[ Test Plan ]
- * The triggers for
Hi Andreas! I've updated the testing section. PTAL.
** Description changed:
[ Impact ]
* Users experience brick SEGFAULTs under certain not-yet-understood
scenarios. Some reports include a high percentage of small file I/O. I
encountered the issue roughly every hour with Minio backed
** Description changed:
+ [Impact]
+
WSL 24.04 / systemd 255.4-1ubuntu8
* Upstream report: https://github.com/microsoft/WSL/issues/8879
* Upstream PR: https://github.com/systemd/systemd/pull/32534
* Upstream commit:
These patches are included in v256, which is currently in oracular-
proposed, so we just need to upload to noble.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fix for this is included in v256, which is currently in oracular-
proposed. So we just need to upload the fix to noble.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@jibel - thanks for the patch. I already had it prepped in git, so I
will upload that version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067922
Title:
on WSL systemd status fails output
To
** Changed in: systemd (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/2067927
Title:
systemd ships nice.conf override for wrong service
To manage
Thanks for reviewing. I have populated this section now.
** Description changed:
[Impact]
Upgrades to noble chmod /dev/null 644, breaking use of the device on
multi-user systems for non-root.
[Test plan]
1. do-release-upgrade mantic -> noble
2. check that /dev/null remains 666
** Also affects: openssh (Ubuntu Noble)
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/2069041
Title:
Changing Port in sshd_config and restarting
There is really no way around requiring a daemon-reload. The best thing
we can do here is improve the documentation to make this clear to users.
** Changed in: openssh (Ubuntu Noble)
Status: New => Triaged
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Nick Ro
With 24.04 LTS, ssh is socket activated by default. The configuration
for the socket is generated by reading the regular /etc/ssh/sshd_config
(or /etc/ssh/sshd_config.d/ snippets), but the configuration needs to be
reloaded. So, the steps for configuring a new port are:
# Add new port to
Hi Bryce!
I really appreciate you getting this submitted.
I took a day and looked through the code/tests for GlusterFS and
couldn't figure out how to reliably trigger the crash. For my system, I
experienced brick crashes about once per hour, but only with specific
volumes. For instance, the
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068909
Title:
://launchpadlibrarian.net/722931304/buildlog_ubuntu-noble-
amd64.libtraceevent_1%3A1.8.2-1ubuntu2_BUILDING.txt.gz
** Affects: libtraceevent (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Changed in: libtraceevent (Ubuntu)
Assignee: (unassigned
I have noticed the same thing on 3 servers after they were upgraded to
24.04.
I also tested the following:
sudo NEEDRESTART_MODE=l apt full-upgrade --autoremove
i.e. specifying the restart mode in an environment variable (which I
found by Googling), but this also had no effect.
I could be
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Triaged => In Progress
** 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.
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067071
Title:
cannot upgrade from 23.10 to 24.04, error in
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Triaged => In Progress
** 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.
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/530252
Title:
os-prober fails to recognize linux installations with crypted root
partition
To manage notifications
** 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/2067622
Title:
cryptsetup-initramfs disappeared during upgrade from 23.10 to 24.04
leading to failing boot
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
** 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/2067216
Title:
error id modified the contents of
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
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
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067525
Title:
The Wi-Fi becomes extremely slow upon startup or disconnects
To
ubuntu-release-upgrader (Ubuntu Noble)
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/2067585
Title:
Upgrades to noble chmod /dev/null 644
-release-upgrader (Ubuntu Noble)
Status: New => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug not
no attribute '_cand'
-
full logs attached as files.
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided => High
** Changed in: ubuntu-release-upgrader (Ubuntu Noble
)
Importance: Medium
Assignee: Nick Rosbrook (enr0n)
Status: Triaged
** Affects: systemd (Ubuntu Noble)
Importance: Medium
Assignee: Nick Rosbrook (enr0n)
Status: Triaged
** Tags: systemd-sru-next
** Tags added: systemd-sru-next
** Changed in: systemd (Ubuntu
)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ub
** 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/2067922
Title:
on WSL systemd status fails output
To manage notifications about this bug go to:
There are lots of "Found ordering cycle on..." errors in your logs.
Please check your custom units/overrides to find where a cycle might be
created. I don't think this is related to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I sponsored these uploads. Waiting in the unapproved queue.
** Changed in: dotnet6 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: dotnet6 (Ubuntu Mantic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: systemd (Ubuntu Jammy)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2035406
Title:
udev update has broken ubuntu's ability to import photos in
** Changed in: moc (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2034944
Title:
proposed-migration for moc 1:2.6.0~svn-r3005-3bui
** Changed in: lsh-utils (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060846
Title:
lsh-utils 2.1-14build2 FTBFS on armhf
To man
** 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.
https://bugs.launchpad.net/bugs/2041833
Title:
/lib/syst
** Changed in: sbcl (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059044
Title:
proposed-migration for sbcl 2:2.3.7-2
To man
** 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.
https://bugs.launchpad.net/bugs/2041834
Title:
/lib/syst
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: systemd (Ubuntu)
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/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
** Changed in: ubuntu-release-upgrader (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/2061148
Title:
upgrading window shows %s instead of version number
systemd specifies a Suggests: systemd-container. This is because it is
not a hard dependency, but instead something you might want (systemd-
sysupdate is a pretty new tool that by default does not have a lot of
use on Ubuntu). You can install all such packages with apt install
--install-suggests
Please re-open if there is still a relevant task here for systemd. I am
taking the age/silence to suggest otherwise.
** Changed in: systemd (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 10830 matches
Mail list logo
