Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: wsl-pro-service (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is
Subscribing ubuntu-release as per FFE policy. This bug affects noble
cloud image release
** Also affects: software-properties (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Thanks all. Marking as "Won't Fix" and marked MP as Rejected.
** Changed in: ubuntu-meta (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
With only snapd snap preseeded I get boot times very similar to
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.757s (kernel) + 12.458s (userspace) = 16.216s
graphical.target reached after 12.061s in userspace.
```
Which shows we are still taking a boot time hit of ~1.5 seconds...
> * boot times w/ and w/o preseeded snaps
Without preseeded snaps:
```
ubuntu@cloudimg:~$ systemd-analyze
Startup finished in 3.609s (kernel) + 11.026s (userspace) = 14.636s
graphical.target reached after 10.642s in userspace.
```
With preseeded snapd and core22 snaps:
```
ubuntu@cloudimg:~$
@vorlon
> Also, statically seeding a particular base snap is bad form, as soon
as lxd upgrades its base you lose your performance benefit and have to
play catch-up in a stable release.
yes I don't like this either. Even if we do change it later to core24
then the expectations people have for
Thank you for the detail sdeziel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Title:
Always preseed core and snapd snap in server seed
Status in ubuntu-meta package in
> "other cloud cases that have preseeded snaps" (thinking like ec2 or
oracle that have snapped cloud agent
This isn't something we need to worry about as there will be no change
in this case. If any agent snaps are preseeded then so too will a core
snap and snapd snap.
--
You received this bug
If we don't preseed a core snap and snapd it feels like we're failing to
prioritise the performance of snaps on server/cloud.
But if we acknowledge that knowing that we are prioritising boot speed
then that's fine and we can add it to the noble release notes.
--
You received this bug
> 15 seconds vs 30 seconds, on a thing that won't affect most cloud
customers
I'll see if I can find the data to back this
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2051572
Good points
I'll measure boot speed with and without core snap preseeded and add it
here.
time to initialize any snap was my goal but with lxd as an example as it
is such a popular snap.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
in the server seed @
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/tree/server#n69
[1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Assignee: Philip Roche (philroche)
Status: New
This has been released in Noble version 1.529
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Released
** Also affects: ubuntu-meta (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Changed in: ubuntu-meta (Ubuntu Noble)
Assignee: (unassigned) =>
Public bug reported:
With LXD 5.20 there is a license change to AGPL and it has been decided
to no longer seed the snap in Ubuntu 24.04 and later and instead seed
the lxd-installer package instead.
This bug is to track the work of making that change in the server seed @
Given https://gitlab.gnome.org/GNOME/glib/commit/0d69462 referred to
above it does look like an intentional change and nothing to do with
udisks2. Please close if this is the case.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2
I also refer you to https://gitlab.gnome.org/GNOME/glib/commit/0d69462
which seems to be the cause.
https://gitlab.gnome.org/GNOME/nautilus/issues/312 refers to this too
but I have experienced this in Caja too, not just nautilus.
--
You received this bug notification because you are a member of
Public bug reported:
Apologies if this is not the correct package to file this bug/regression
against.
On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting
network shares (SMB and NFS) they no longer appear under Devices in file
manager (Nautilus or Caja), the mounts do
I had the same issue. For me the issue was caused by a recent install of
EasyScreenCast gnome extension. I deleted the extension from
/home/$USER/.local/share/gnome-shell/extensions/ and was then able to
log in.
--
You received this bug notification because you are a member of Desktop
Packages,
19 matches
Mail list logo
