It was nice to have LXD around and ready for many test/dev workloads,
and I feel it was worth it back then.
But we already replaced it with lxd-installer in minimal environments and it
was fine there too.
I never heard someone complaining that LXD takes a bit there, but every second
of boot time
This bug was fixed in the package apparmor - 4.0.0~alpha4-0ubuntu1
---
apparmor (4.0.0~alpha4-0ubuntu1) noble; urgency=medium
[Georgia Garcia]
* New upstream release.
* Add unconfined profiles to support the use unprivileged user namespace
(LP: #2052297, LP: #2046844)
-
** Summary changed:
- Upgrade libwayland on ubuntu 22.04.3 LTS
+ Upgrade libwayland to 1.22.0
** Also affects: wayland (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: wayland (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: wayland
This bug was fixed in the package apparmor - 4.0.0~alpha4-0ubuntu1
---
apparmor (4.0.0~alpha4-0ubuntu1) noble; urgency=medium
[Georgia Garcia]
* New upstream release.
* Add unconfined profiles to support the use unprivileged user namespace
(LP: #2052297, LP: #2046844)
-
** Description changed:
Since the last three weeks' updates, I have encountered several
challenges with the audio functionality on my system. Primarily, upon
starting my laptop, the audio often fails to work, displaying "Dummy
Output." To resolve this, I find myself needing to restart the
** Also affects: wayland (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: wayland (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have
finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.27.0-0ubuntu5 (amd64)
apt/2.7.3ubuntu0.1 (armhf)
auto-apt-proxy/14.1 (arm64)
livecd-rootfs/23.10.57 (ppc64el)
All autopkgtests for the newly accepted apt (2.7.3ubuntu0.1) for mantic have
finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.27.0-0ubuntu5 (amd64)
apt/2.7.3ubuntu0.1 (armhf)
auto-apt-proxy/14.1 (arm64)
livecd-rootfs/23.10.57 (ppc64el)
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland on ubuntu 22.04.3 LTS
Status in wayland package in Ubuntu:
New
** Merge proposal linked:
https://code.launchpad.net/~vpa1977/ubuntu/+source/apport/+git/apport/+merge/460642
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2045705
All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished
running.
The following regressions have been reported in tests triggered by the package:
livecd-rootfs/2.765.38 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding
All autopkgtests for the newly accepted apt (2.4.12) for jammy have finished
running.
The following regressions have been reported in tests triggered by the package:
livecd-rootfs/2.765.38 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding
Public bug reported:
I tried to record sound with my internal Mic. Nothing is working. I use
arecord.
```
bagus:~$ arecord test.wav
arecord: main:834: audio open error: Operation not supported
bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav
ALSA lib pcm.c:2675:(snd_pcm_open_noupdate)
Public bug reported:
Ubuntu 22.04.3 LTS
systemd 249.11-0ubuntu3.12
systemd issue tracker says this version is too old to report upstream
and I should report to downstream bug tracker.
IPv6 default routes are getting lost and not renewed.
We're using IPv6 RA to find default routes for our
Thank you for the detail sdeziel
--
You received this bug notification because you are a member of Ubuntu
Touch seeded 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
> "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
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228
** This bug has been marked a duplicate of bug 2053228
software-properties-gtk does not start
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_
Regardless of how the bluetooth device works, enabling unbonded devices
in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be
enabled by the security team.
Perhaps GNOME or other desktops could become more aware of gaming
controllers with these issues to make pairing easier, without
FYI, snapd is a "base-less" snap:
$ lxc launch ubuntu-minimal-daily:22.04 c1
$ lxc shell c1
root@c1:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
root@c1:~# snap install snapd
2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart...
snapd 2.61.1 from Canonical✓
Hello Bryce, or anyone else affected,
Accepted openldap into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openldap/2.5.17+dfsg-0ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I agree with vorlon in general. It is a bit odd to not be seeding snapd
by default, since snaps are a recognized package format. preseeding
snapd will bring in its base, but there's no guarantee that base will
match any other snaps.
Flip side is that somewhere back in history, it was decided that
Public bug reported:
Everything freezes, several times per day. I am not sure if it's NVIDIA
related or not. I am willing to troubleshoot as long as I am told very
specifically what needs to be done.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature:
> 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 Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
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
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 Ubuntu
Touch seeded packages, which is
We *should* get this via normal stable update processes relatively soon.
If for some reason it doesn't land in systemd-stable in time (unlikely
since the upstream PR is tagged for stable backport), then we will
backport it in Ubuntu directly.
** Changed in: systemd (Ubuntu)
Status: New =>
> This is a significant difference and for a workload we intend to remain as a
> core tested
> and tracked workload. As such I propose we re-introduce core22 and snapd
> snaps to our seed.
I disagree that the image should be optimized by default to prioritize
the one-time startup performance of
** Changed in: steam (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation
Particularly on the case of PS3 controller, I still think this is a
regression that could be fixed.
PS3 controllers do not use the standard Bluetooth connection procedure.
Instead, they require a connection via USB, and keys are exchanged via
there. There is the special `sixaxis` BlueZ plugin to
Given that systemd-v255 has just migrated from noble-proposed to noble
yesterday, this bug is now present in Ubuntu 24.04 as-is, without the
proposed repo enabled. Can this fix be backported before 22.04 releases
so people don't run into network issues with a newly-installed 22.04?
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Mekaniserad, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mekaniserad, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Andy, or anyone else affected,
Accepted apt into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.7.3ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Andy, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
** Summary changed:
- Don't migrate glib yet
+ glib requires gobject-introspection >= 1.78.1-13
** Changed in: glib2.0 (Ubuntu)
Status: Invalid => Triaged
** Tags removed: block-proposd
** Tags added: update-excuse
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Committed
@juliank Testing was done by running autopkgtest locally against the
source package only (-B, --no-built-binaries), I didn't rebuild the
binaries.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
Verifying this should be fairly simple.
Look at the definition of Authmethod in auth.h and compare to how
method_gssapi is initialized compared to method_gsskeyex.
As for it being the only report it is only "AuthenticationMethods gssapi-keyex"
that is not working.
We have "AuthenticationMethods
This failed to build due to missing update-maintainer, I'm adding this and
uploading it but wondering how it was tested:
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer:
does not have Ubuntu address
E: Failed to
Hello and thanks for this bug report. The analysis looks sensible to me,
but I'm not really familiar with gss. To better understand the situation
I have a couple of questions:
- Does this mean that gss is unusable in Jammy at the moment? AFAICT
this is the only bug report about it, so I would be
Public bug reported:
We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see
the following Weston-13.0 dependencies are not met for the same.
libwayland*: required version >= 1.22.0
So we request to upgrade these packages on Ubuntu 22.04.3 LTS.
The release of Ubuntu we are using:
Confirmed by
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/
software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
Installatio
ic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitect
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2
---
mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium
* patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on
Intel DG2. (LP: #2051068)
mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium
This bug was fixed in the package directx-headers -
1.610.2-2~ubuntu0.22.04.1
---
directx-headers (1.610.2-2~ubuntu0.22.04.1) jammy; urgency=medium
* Backport to jammy. (LP: #2037604)
-- Timo Aaltonen Fri, 27 Oct 2023 08:57:55 +0300
--
You received this bug notification
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2
---
mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium
* patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on
Intel DG2. (LP: #2051068)
mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium
Test builds are done here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1982336
** Information type changed from Private to Public
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: gdb (Ubuntu)
Status: New => In Progress
--
You received this bug
debdiff
** Patch added: "debdiff_gdb_noble_from_14.1-0ubuntu2_to_14.1-0ubuntu3.diff"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1982336/+attachment/5746408/+files/debdiff_gdb_noble_from_14.1-0ubuntu2_to_14.1-0ubuntu3.diff
--
You received this bug notification because you are a
56 matches
Mail list logo
