Fixed in Debian with the introduction of a new quilt patch:
https://salsa.debian.org/systemd-
team/systemd/-/commit/0c6d90f783093fc255e529f8a33b2ed2a8e6c2d6
Counting this as Fix Committed.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug
Also: setting all the other tasks to Invalid as there's noting wrong
with them; the issue (and the fix) belong to systemd.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: fam (Ubuntu)
** Changed in: glibc (Ubuntu Xenial)
Status: New => Invalid
** Changed in: glibc (Ubuntu Bionic)
Status: New => Invalid
** Changed in: glibc (Ubuntu Focal)
Status: New => Invalid
** Changed in: glibc (Ubuntu Groovy)
Status: New => Invalid
--
You received this bug
# VERIFICATION BIONIC
Installed systemd from -proposed :
# dpkg -l | grep systemd
ii libnss-resolve:amd64 237-3ubuntu10.45
amd64nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 237-3ubuntu10.45
Thanks everyone for getting it fixed!
--
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/1913189
Title:
systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8
# VERIFICATION FOCAL
Installed systemd from -proposed :
# dpkg -l | grep systemd
ii libnss-resolve:amd64 245.4-4ubuntu3.5
amd64nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 245.4-4ubuntu3.5
** Description changed:
+ [Impact]
+
+ * 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 launch ubuntu:18.04 bb-lp-1806076
Creating bb-lp-1806076
Starting
Hello Rafael, or anyone else affected,
Accepted isc-dhcp into groovy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.4.1-2.1ubuntu10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Rafael, or anyone else affected,
Accepted isc-dhcp into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.4.1-2.1ubuntu5.20.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Public bug reported:
I am using Android Studio to develop Applications. When i have lots of
windows opened and i try to open a context menu or write code, it shows
a frame of some applications that are below the current window. In the
video it is more clear. I don't know if this is a problem
# VERIFICATION GROOVY
Installed systemd from -proposed :
# dpkg -l | grep systemd
ii libnss-resolve:amd64 246.6-1ubuntu1.2
amd64nss module to resolve names via systemd-resolved
ii libnss-systemd:amd64 246.6-1ubuntu1.2
Public bug reported:
This warning appears when I call some apps, Terminal included (yes, I'm working
in a desktop environment)
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: libjpeg-progs 8c-2ubuntu7
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux
Actually there is more, as it's shown on this other video. The same
problem happens when “there is a display event”…? Like when my mouse go
over an element, even if I can't click on it.
** Attachment added: "VID_20210311_105952.mp4"
Hello Rafael, or anyone else affected,
Accepted isc-dhcp into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.5-3ubuntu7.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
I need to verify a few things, but I believe it is to do with
chiphersuites, seclevel callback, and protocol versions.
When setting chiphersuite string ; or changing security level; or
changing the security level callback; or setting min/mas protocol
versions. All of those things are not checked
** Description changed:
+ [impact]
+
+ systemd spams journal with log messages
+
+ [test case]
+
+ see journalctl output and search for msgs similar to those listed in
+ original description below
+
+ [regression potential]
+
+ any regession would likely result in logs incorrectly not logged
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
Title:
OpenSSL TLS 1.1 handshake fails internal error
Status in openssl package
** Also affects: openssl (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
Title:
OpenSSL TLS 1.1
** Tags added: fr-1204
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
Title:
OpenSSL TLS 1.1 handshake fails internal error
Status in openssl package in Ubuntu:
** Description changed:
[impact]
when libseccomp is upgraded to 2.5.1 on all releases, the systemd
seccomp unit tests will start failing on ppc, as
RestrictAddressFamilies= will no longer work on that arch.
However, the systemd.exec man page has stated that
I didn't include a setter for security level on purpose,
https://bugs.python.org/issue41195 . Most recent Python version only has
a getter to query security level. I strongly believe that user
application should not modify security level. Security level and TLS
versions should be centrally managed
The SRU verification passed for focal. The attached screenshot shows
firmware staged in /lib/firmware/updates that is not included in the
initramfs with version 0.136ubuntu6.3 of initramfs-tools, and then
correctly included in the initramfs with version 0.136ubuntu6.4 of
initramfs-tools.
**
No, initrd needs to include fsck regardless of what's been set in fstab.
Without it even *manual* fsck is impossible.
** This bug is no longer a duplicate of bug 1902103
Ensure default fstab options are sane and consistent across all images
** Changed in: initramfs-tools (Ubuntu)
** Tags removed: rls-hh-incoming
--
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/1917780
Title:
initramfs-tools does not include fsck in initrd if mount pass is 0
Not sure why you have an ordering loop between sockets.target and
dbus.socket, can you provide the output of:
$ systemctl cat dbus.socket
$ systemctl cat sockets.target
$ systemctl list-dependencies sockets.target
$ systemctl list-dependencies --reverse sockets.target
$ systemctl
*** This bug is a duplicate of bug 1902103 ***
https://bugs.launchpad.net/bugs/1902103
We must honor MNT_PASS.
The actual bug is that many things do not set it to 1 by default as they should
have.
I.e. bits in curtin, maas, subiquity, cloud-images.
It is correctly set to 1 on ubiquity
Please note that:
OpenSSL upstream security level 3 only allows TLS v1.1 and above
OpenSSL upstream security level 4 only allows TLS v1.2 and above, DTLS v1.2 and
above
On Ubuntu, these restrictions are brought in earlier at security level
2.
Thus, if one builds upstream OpenSSL with security
Public bug reported:
[impact]
when libseccomp is upgraded to 2.5.1 on all releases, the systemd
seccomp unit tests will start failing on ppc, as
RestrictAddressFamilies= will no longer work on that arch.
However, the systemd.exec man page has stated that
RestrictAddressFamiles= doesn't work on
All autopkgtests for the newly accepted isc-dhcp (4.3.5-3ubuntu7.2) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/3.2-4ubuntu4.5 (armhf)
Please visit the excuses page listed below and investigate the failures,
** Description changed:
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot
reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
Further verification that shows the non-zero return value of shutdown command,
when it fails to schedule a reboot and takes no action.
For Bionic :
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1 -r "REBOOT!"
Failed to set wall message, ignoring: Refusing activation,
wait what?! =/
fsck binaries should totally be there! that sounds very broken if they
are not there.
** Changed in: initramfs-tools (Ubuntu)
Importance: Medium => Critical
** Summary changed:
- initramfs-tools does not include fsck in initrd if mount pass is 0
+ initramfs-tools does not
** Changed in: casper (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: casper (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
I've occasionally seen the same problem in multiple compositors with
multiple different GPUs over the past 10 years. This seems like some
kind of Xorg compositing race/failure.
** Tags added: nvidia
** Summary changed:
- Display glitches when showing context menu
+ [nvidia] Display glitches
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Summary changed:
- Kind of slowly refresh
+ Horizontal noise-like corruption
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Summary changed:
- Horizontal noise-like corruption
+ [i915] Horizontal noise-like screen corruption
** Also affects: linux-signed-hwe-5.8 (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
A similar issue was reported against radeon (bug 1911369) so maybe it's
a problem with Mesa 20.2.6.
** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux-hwe-5.8
(Ubuntu)
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because
Though this is also reminiscent of bug 1896091.
** Changed in: mesa (Ubuntu)
Status: Confirmed => New
** Changed in: mutter (Ubuntu)
Status: Confirmed => New
** Tags added: i915
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Please try some different kernel versions and tell us if any of them do
or don't have the same bug:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
OK, I won't bother Norm with any more questions because comment #7 :)
Instead I'll move this to bug 1918619.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1911369
Title:
Public bug reported:
If /etc/sudoers contains the following (syntactically invalid) line:
%sudo ALL=(ALL:ALL) NOPASSWD ALL
the sudo command will segfault:
$ sudo true
[1]12958 segmentation fault (core dumped) sudo true
A better result would be to fail or warn with a syntax
Public bug reported:
on ubuntu 18.04 while debugging a sudo_1.8.21p2-3ubuntu1.2 problem it
was found that sudo-dbgsym_1.8.21p2-3ubuntu1.2_amd64.ddeb is missing
from http://ddebs.ubuntu.com/pool/main/s/sudo/
the only (easy to find) place that seems to have a copy of this ddeb is
After two times pass for using mesa lib in ppa:oibaf/graphics-drivers, I
reproduce the x server stop error with different stacktrace:
Mar 12 12:43:12 stress-ng: memory (MB): total 15729.63, free 152.17, shared
43.86, buffer 0.36, swap 2048.00, free swap 0.01
Mar 12 12:43:12
*** This bug is a duplicate of bug 1889102 ***
https://bugs.launchpad.net/bugs/1889102
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1889102, so it is being marked as such. Please
** Tags added: amd64 groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1918876
Title:
sudo segfaults when /etc/sudoers has syntax error
Status in sudo package in
** Attachment added: "Captura de tela de 2021-03-11 23-20-34.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1918852/+attachment/5475971/+files/Captura%20de%20tela%20de%202021-03-11%2023-20-34.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
List marks of menu show more tham have
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
I follow the upstream bug to install obiaf ppa's mesa lib and run the
test for two times, then I can get pass successfully for both run. I
plan to run the test three times to make sure the edge mesa lib can
really solve the problem, because the issue seems happens randomly.
** Description
Public bug reported:
I run checkbox job com.canonical.certification::memory/memory_stress_ng
on focal, and the xserver stops unexpectedly with the following
stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
Please check that you haven't enabled:
realtime-scheduling = yes
in /etc/pulse/daemon.conf. And if the problem continues to occur after
that then please report it to the developers at:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues
and tell us the new issue ID.
** Changed
Public bug reported:
My laptop failed to suspend overnight and was unresponsive when I opened
it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and
pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In
syslog, I found a stream of suspend attempts with
Public bug reported:
I use to press Alt+Tab to switch between windows (or frames, whatever)
and I noticed today that when I switch to another window the up bar
blinks.
I already had a display problem once, so I knew it was better with a
external video.
ProblemType: Bug
DistroRelease: Ubuntu
55 matches
Mail list logo
