I have looked into it a bit. I have noticed that some functions were not
inlined in 5.15, but were inlined in 5.4. For example `lzma_literal` and
`lzma_match` (see difference in System.map). After removing
`CONFIG_DEBUG_SECTION_MISMATCH=y` from `debian/rules.d/0-common-vars.mk`
(I am not sure why i
Public bug reported:
On Ubuntu Core 24 calling the command line
useradd --extrausers --groups somegroup somenewuser
... fails with:
useradd: cannot lock /etc/group; try again later.
It worked on 22.04. /etc is not writable. It also fails if somegroup is
a group in extrausers.
** Affects: shad
Public bug reported:
On 2.1-14-g2e17a0d6-0ubuntu1~22.04.3
`cloud-init status` reports `status: not-run` even though
`/usr/lib/systemd/system-generators/cloud-init-generator` has run as
generator and marked it as disabled.
The right status which is also what focal gives is `status: disabled`.
`c
We have a related issue in Ubuntu Core 22. It fails the same way. But in
our case it fails because systemd-networkd is not running, because
subiquity has stopped it before calling "netplan apply". And then
"networkctl reload" of course fails.
Was systemd-networkd running when you called "netplan a
Public bug reported:
Since systemd 252, systemd-stub does LoadImage/StartImage to executed
the kernel in the .linux section.
See origin PR: https://github.com/systemd/systemd/pull/24777
Before, it was using the "EFI handover protocol". Unfortunately kernel
handover is now deprecated. Also it was
Public bug reported:
systemd-vmspawn is available since systemd 255. Unfortunately, neither
noble (255) nor oracular (256) seem to have it available.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
As a work-around for this bug, I suggests you make sure that `ubuntu-
desktop-installer.service` does not start before `snapd.seeded.service`.
Unfortunately a user service cannot really wait for a system service.
And `snap wait system seed.loaded` which could have been a good
ExeStartPre command re
On the ISO:
ubuntu@ubuntu:~$ time sudo snap run --hook configure firefox
/usr/share/fonts: caching, new cache contents: 0 fonts, 6 dirs
/usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
/usr/share/fonts/X11/Type1: caching, new cache contents: 43 fonts, 0 dirs
/usr/share/fonts/X11/
You were not waiting for seeding.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2116949
Title:
Since snapd 2.68, initial seeding time increased
To manage notifications about this bug go to:
https:/
It seems every `Run configure hook of ".." snap if present` take 3
seconds to run. But most of them have a configure hook that only
contains `#!/bin/true`. Could we just remove those hooks in the snaps?
That would probably save most of the time.
Still we have to figure out why trying to run them t
Removing pre-seeding tasks, it looks like
Done 2025-07-07T05:51:16Z 2025-07-15T13:51:19Z Run install hook of "snapd" snap
if present
Done 2025-07-07T05:51:16Z 2025-07-15T13:51:19Z Start snap "snapd" (24994)
services
Done 2025-07-07T05:51:16Z 2025-07-15T13:51:19Z Run configure hook of "core"
sna
There is actually hooks. They call the hook from gnome, which runs `fc-
cache --force`. And that takes 3 seconds each.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2116949
Title:
Since snapd 2.68,
12 matches
Mail list logo
