autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added:
autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added:
autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added:
autopkgtests for apt have passed, so validation was successful. I'm
confident the autopkgtest failures are unrelated intermittent ones; I've
done some more retries.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added:
The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.
** Tags
The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.
** Tags
@Oscar That was never an issue: A2DP always sounded decent. The problem
with Linux Bluetooth headset support comes when you want decent quality
while listening and recording sound, you know e.g. during video calls.
Am Di., 30. März 2021 um 07:35 Uhr schrieb Oscar Pérez del Campo <
I think I am suffering from the same issue.
I have always run without "UsePAM yes" in sshd_config, but I recently
tried turning it on in order to get XDG_ variables set correctly and
proper systemd sessions for ssh logins.
In 18.04 it worked as expected, but in 20.04 I get
sshd[387766]:
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.
Public bug reported:
The Alt+Tab application switcher could benefit from a colored
notification badge. This *could* be a number with the amount of
notifications, but honestly, a simple boolean "has / has no badge" would
suffice already.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg
This is still an issue in Ubuntu 21.04 (development, as of March 30,
2021)
It looks like people have been complaining about this for years, and
while some people have tried to fix it, those fixes never made it in.
Surely it must be of some type of urgency to support 2FA one-time
passwords in the
All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.46) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.4/5.4.0-71.79~18.04.1 (i386)
polkit-qt-1/unknown (i386)
openssh/1:7.6p1-4ubuntu0.3 (ppc64el, arm64,
I'm marking this WONTFIX as both builds have passed on retry.
** Changed in: vim (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: vim (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
All autopkgtests for the newly accepted libseccomp (2.5.1-1ubuntu1~20.10.1) for
groovy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/246.6-1ubuntu1.2 (ppc64el)
Please visit the excuses page listed below and investigate the
Oops, of course apt's test passed, hence verification done :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1918907
Title:
Default Acquire::AllowReleaseInfoChange::Suite to
** Tags removed: verification-donefocal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1916725
Title:
Protected/Important packages are
Can't exactly verify as we did not get another reproducer, but marking
it as verified anyway
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch
All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
upstart/unknown (armhf)
umockdev/0.8.11-2 (i386)
systemd/229-4ubuntu21.30 (amd64)
linux-aws-hwe/unknown (arm64)
apt's tests failed, I believe the regressions are just intermittent
unrelated issues.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
** Tags added: verification-done verification-done-bionic
verification-done-focal
--
You received this bug
All autopkgtests for the newly accepted systemd (229-4ubuntu21.30) for xenial
have finished running.
The following regressions have been reported in tests triggered by the package:
upstart/unknown (armhf)
umockdev/0.8.11-2 (i386)
systemd/229-4ubuntu21.30 (amd64)
linux-aws-hwe/unknown (arm64)
The small simple script also worked with the proposed version:
# python3 a.py
WAITING
^CSeen KeyboardInterrupt()
END
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are
I checked do-release-upgrade -d before upgrading apt, and pressing
Ctrl+C at the prompt for conforming changes left hirsute in
sources.list.
I upgraded to apt 2.1.10ubuntu0.3 from proposed, ran it again, and
Ctrl+C now caused the restore code to run:
Continue [yN] Details [d]^C
Restoring
** Description changed:
[Impact]
- * unattended-upgrades --help crashes in apt.systemd.daily script when
+ * unattended-upgrades --help crashes in apt.systemd.daily script when
locale is not in UTF-8.
[Test Case]
In the fixed case no crash is observed.
rbalint@yogi:~$ lxc
I installed 1.6.13 and could verify that the regression wrt --help is
fixed. unattended-upgrades still logged a lot of errors because for some
reason gettext returned utf8 despite being on non-UTF-8 locale, but
that's all from the APT side.
** Tags removed: verification-needed
Log:
+ /usr/lib/apt/apt.systemd.daily lock_is_held update
---
So I did look at those options, but disabling them did not provide the
experience I was looking for, and required me to do as much or more
manual switching of audio devices.
To be clear, I don't want to disable the functionality that these
options provide. I am happy with the audio switching to
With respect to #12, I am not sufficiently well versed in rolling back to 18_04
in order to try once again, as much as I would love to do so and help by
repeating my earlier steps that lead to the upgrade.
Though, it looks like others have been able to simulate the steps.
Thanks a lot for all
Public bug reported:
I started investigating this due to software-properties in Debian being
listed as under-maintained per https://mako.cc/copyrighteous
/identifying-underproduced-software
AFAICT the source of truth for this package is in the current Ubuntu
packages. Would it be possible to
Ack by the Ubuntu Security team to move rsyslog-gnutls to main, both for
hirsute, and for bionic, focal, and groovy. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Hello Dave, or anyone else affected,
Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The problem is that Xfwm's built-in compositor and virgl don't play nice
together.
Work-around: Boot the VM with virgl=off (on the video device) or gl=off
(on the display), run xfwm4-tweaks-settings in the VM, select the
"Compositor" tab, and uncheck "Enable display compositing". Then shut
down
Updated the [Where problems will occur] part.
** Description changed:
[Impact]
On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.
[Fix]
Disable IEC958 (SPDIF) through ALSA UCM.
[Test]
With the UCM applied, `pactl` and audio panel in gnome-control-center
Setting to verification-done for Focal.
(focal-amd64)root@impulse:/home/bdmurray/source-trees/error-tracker-deployment/trunk#
apt-get update
...
Reading package lists... Done
W: GPG error: http://ddebs.ubuntu.com focal Release: The following signatures
were invalid: EXPKEYSIG C8CAB6595FDFF622
** Tags added: fr-1216
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1920640
Title:
EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
Signing Key
I tested this again in the Ubuntu Error Tracker using ubuntu-dbgsym-
keyring version 2018.09.18.1~18.04.2 and retracing started working
again.
2021-03-30
19:11:42,253:21370:140207348864832:INFO:root:64b7ba98-918a-11eb-8a05-fa163e7a7275:swift:Processing.
2021-03-30
Actually, Christian didn't explicitly ack the stable releases in that
comment (but he did in the MPs I raised for the seed changes). I'll ask
him tomorrow to flip the statuses.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Given Christian's comments in comment #6, and the fact that the seed
changes were done, I'm going to mark the tasks for the stable releases
as "fix committed"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.3) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
asterisk/1:16.12.0~dfsg-1 (amd64)
apt/2.1.10ubuntu0.2 (arm64)
This was addressed in https://ubuntu.com/security/notices/USN-4891-1 .
** Information type changed from Private Security to Public Security
** Changed in: openssl (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug is present in Ubuntu 21.04 and 20.10 daily builds.
** Tags removed: apport-bug i386
** Tags added: groovy hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Thanks for the bug report.
Please check the issue is still present in newer versions of GNOME. If
so then report it to the developers at https://gitlab.gnome.org/GNOME
/gnome-shell/issues and tell us the new issue ID.
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
** Package changed: unity
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
Merge upstream https://gitlab.com/apparmor/apparmor/-/merge_requests/730
it will be part of the next apparmor point releases
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
I try memory stress test with my ppa in #4, the issue is still
reproduced.
** Attachment added: "sosreport-u-Inspiron-1918855-2021-03-31-xbkosvf.tar.xz"
53 matches
Mail list logo
