Public bug reported:
I have the libc6-prof package installed to provide a frame pointer
enabled libc.so.6.
I have a custom configuration file in /etc/ld.so.conf.d putting
/lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker
search paths. (I really like having frame pointers!)
Thanks for the additional info Ake!
Do you happen to have simple steps you could share to help reproduce the
issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2053146
As is usual with these MREs, the verification phase is considered done
when all dep8 tests pass. This is now true for the Jammy upload.
Therefore, tagging the bug accordingly.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
Based on the data, I'm in the "No" camp as well.
--
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
On Fri, Feb 16, 2024 at 06:51:46PM -, Philip Roche wrote:
> @vorlon @jchittum @paelzer given the above findings are you still -1 on
> any snap preseeding? Based on the data, I vote not to preseed any snaps.
That is my position. Thanks for bringing data to this!
--
You received this bug
It looks like something on our autopkgtest-cloud-worker may also be
regularly changing the contents of /tmp but we've set up an experiment
for over the weekend and will report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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...
this bug is fixed for a long time, in Debian. Closing the bug report
** Changed in: cron (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cron (Ubuntu)
Assignee: (unassigned) => Georges Khaznadar (georgesk)
--
You received this bug notification because you are a member of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2054153
Title:
package linux-image-5.15.0-94-generic 5.15.0-94.104~20.04.1
Public bug reported:
no details
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-94-generic 5.15.0-94.104~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-92.102~20.04.1-generic 5.15.131
Uname: Linux 5.15.0-92-generic x86_64
NonfreeKernelModules: vtsspp sep5 socperf3 pax
Public bug reported:
The upstream version 0.52.24-2 should be merged into noble. The current
version is 0.52.24-1ubuntu1.
* PPA for review: https://launchpad.net/~mateus-
morais/+archive/ubuntu/newt-merge
Note: this is a tracking bug
** Affects: newt (Ubuntu)
Importance: Undecided
> * 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:~$
Any news on this bug? Latest patches did not affect it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049988
Title:
Latest kernel kills wifi.
Status in
Attached is my manual verification steps of testing the proposed package
for Focal.
Package version tested: 2.7.18-1~20.04.4
Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined
No, it does not need an epoch, but we do need to do another gobject-
introspection upload to stop building the binary packages that glib now
provides.
I have requested a review from another Debian maintainer:
https://salsa.debian.org/gnome-team/gobject-introspection/-/merge_requests/14
** Also
** Merge proposal linked:
https://code.launchpad.net/~jbicha/software-properties/+git/software-properties/+merge/460707
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
Attached is my manual verification steps of testing the proposed package
for Jammy.
Package version 2.7.18-13ubuntu1.2
Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined that
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2051405
Title:
ProtectHome setting in
It's marked failed to upload on all architectures right now:
INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
I guess that
** Description changed:
When attempting to remove multiple logical volumes (LVs) with the
`lvremove -y` command, if any of the LVs are in use, the command fails
but still causes the LVs to disappear from the system. However, these
LVs reappear upon reactivating the volume group (VG),
With ProtectHome=read-only autopkgtests passed but when updating locally
the systemd service failed to start due to an access problem in the /run
directory.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/460703
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2051405
AIUI he suggests keeping the boot time cleanup, and that it could be
nice to have the 30d behavior back. In any case that's what I'd prefer.
I know we're speaking of file age; certainly not of blindly deleting
everything every month or so :-)
--
You received this bug notification because you are
Reported upstream as well: https://gitlab.com/lvmteam/lvm2/-/issues/10
** Bug watch added: gitlab.com/lvmteam/lvm2/-/issues #10
https://gitlab.com/lvmteam/lvm2/-/issues/10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
When attempting to remove multiple logical volumes (LVs) with the
`lvremove -y` command, if any of the LVs are in use, the command fails
but still causes the LVs to disappear from the system. However, these
LVs reappear upon reactivating the volume group (VG), indicating they
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in xorg package in Ubuntu:
New
Bug
You have been subscribed to a public bug:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => David Fernandez Gonzalez (litios)
** Also affects: openssl (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openssl
On Fri, Feb 16, 2024 at 01:06:07PM -, Paride Legovini wrote:
> Maybe we could make that 40d, as 30d is likely to be a time interval at
> which a lot of periodic things happen (e.g. an off-site backup).
The period here is the age at which files are considered old and to be clean
up, not the
You say "Nick's preference", but it's Nick who took the position here
that the default behavior should not change?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2019026
** Changed in: devhelp (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: devhelp (Ubuntu)
Assignee: (unassigned) => Georgia Garcia (georgiag)
** Changed in: epiphany-browser (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: epiphany-browser (Ubuntu)
@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
FWIW I agree with Nick's preference (clean at boot && clean files older
than 30d). Maybe we could make that 40d, as 30d is likely to be a time
interval at which a lot of periodic things happen (e.g. an off-site
backup). A retention period >30d is less likely be synchronized with it
in an unlucky
This bug was fixed in the package apt - 2.7.11
---
apt (2.7.11) unstable; urgency=medium
[ David Kalnischkies ]
* Remove erroneous -a flag from apt-get synopsis in manpage
* Support -a for setting host architecture in apt-get source -b
[ Julian Andres Klode ]
* For
This bug was fixed in the package apt - 2.7.11
---
apt (2.7.11) unstable; urgency=medium
[ David Kalnischkies ]
* Remove erroneous -a flag from apt-get synopsis in manpage
* Support -a for setting host architecture in apt-get source -b
[ Julian Andres Klode ]
* For
Public bug reported:
I'm testing Noble using multipass and I got this error when I try to upgrade
the system:
ubuntu@ubuntu2404:~$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Error!
Some packages
I can confirm this on my system which is quite peculiar because I was
testing the changes on it but it's possible I made additional changes
after the changes that made software-properties work that broke it, or
something.
I'll schedule to look at this the week after next.
** Changed in:
piuparts ppa test(pass)
** Attachment added: "piuparts-apport.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2045705/+attachment/5746586/+files/piuparts-apport.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: ghostwriter (Ubuntu)
Status: Fix Released => 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
/usr/share/apport/apport-gtk is shipped by apport-gtk and
/usr/lib/python3/dist-packages/apport/ui.py is shipped by
python3-apport.
apport.ui.Action was introduced in commit
36ae3310861f1286eae8875a3195551126290914 in 2.25.0.
apport-gtk depends on python3-apport (>= ${source:Version}) so that
Public bug reported:
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 55, in
class GTKUserInterface(apport.ui.UserInterface):
File "/usr/share/apport/apport-gtk", line 232, in GTKUserInterface
) -> apport.ui.Action:
AttributeError: module 'apport.ui' has
https://github.com/canonical/apport/pull/266 got merged upstream.
** Changed in: apport
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://github.com/canonical/apport/pull/278 got merged.
** Changed in: apport
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Also affects: akonadiconsole (Ubuntu)
Importance: Undecided
Status: New
** Changed in: akonadiconsole (Ubuntu)
Importance: Undecided => High
** Changed in: akonadiconsole (Ubuntu)
Status: New => In Progress
** Changed in: akonadiconsole (Ubuntu)
Milestone: None =>
Public bug reported:
OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
output instead of an exception when detecting wrong padding
(https://github.com/openssl/openssl/pull/13817).
There are available backports already:
* 3.0 https://gitlab.com/redhat/centos-
060+5-1ubuntu2 landed in noble.
** Changed in: dracut (Ubuntu)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
All autopkgtests for the newly accepted openldap (2.5.17+dfsg-0ubuntu0.22.04.1)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
exim4/4.95-4ubuntu2.5 (ppc64el)
Please visit the excuses page listed below and investigate the
48 matches
Mail list logo
