Thanks for the bug report. Please try adding this kernel parameter:
i915.enable_psr=0
which you can do by editing /etc/default/grub, adding the parameter to
the GRUB_CMDLINE_LINUX_DEFAULT line, and then run:
sudo update-grub
and reboot.
** Package changed: xorg (Ubuntu) => linux-hwe-5.11
Public bug reported:
After the laptop goes to sleep mode, it starts to flicker when i try to
use the laptop.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
The updated openssl package does not change any behaviour w.r.t. config
or engine use. It only has three patches applied to prevent potential
use-after-free errors. It also relies on installing the new PKA engine
with patches from github.
Has the new PKA engine been recompiled and installed
Thanks for that advice.
I'm a bit in trepidation about removing the default HWE. How do I protect
myself from having an unbootable system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Changed in: grep (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1940999
Title:
FTBFS against glibc 2.34
Status in grep package
** Attachment added: "grep_3.7-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520321/+files/grep_3.7-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
** Patch added: "upstream-ChangeLog.diff"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520323/+files/upstream-ChangeLog.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
This summary file is the differences to the debian directories between
3.6-1 and 3.7
** Attachment added: "changes.summary"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520322/+files/changes.summary
--
You received this bug notification because you are a member
To address this I propose picking up the new version of grep.
** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files/grep_3.7-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a
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.
Launchpad has imported 11 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=11053.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
> we should be careful to ignore NICs with randomly generated MACs (see
bug 1936972).
ugh nics with LAA?
yeah, it can be hard to 'uniquely' identify a nic, especially since it's
so common to clone macs for bonds, bridges, vlans, and in some cases
even duplicate hw devices with the same nic (e.g.
Public bug reported:
The package grep failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .
The failure is in automated test, as follows:
stack-overflow: failed test: grep never printed
Public bug reported:
'test-regex' fails when building grep against glibc 2.34.
Per commentary from grep upstream at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069,
the test failure can be attributed to skew between the glibc built-in regex and
the one that is found in the grep source
Thanks for reporting this issue, but we disabled SSLv3 in 2015 in Ubuntu
16.04 LTS. There is absolutely no chance we will be enabling it again.
** Changed in: openssl (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@ddstreet I agree that systemd is behaving as designed. But I'm not sure
what the proper fix for this is, and therefore where changes would be
required.
My initial thought is that perhaps subiquity installs should do what
MAAS installs do and configure netplan to always use the install-time
The same problem with HP DeskJet 3830
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1886653
Title:
cups-pki-expired
Status in cups package in Ubuntu:
Confirmed
Bug
Your suggested message presupposes that busybox is used on a particular
distribution. That's not necessarily the case. Remember, e2fsprogs
is designed for all distributions, not just for Ubuntu. If Canonical
wants to make a change like that to e2fsprogs, all distributions are
free to make any
** Changed in: systemd (Ubuntu Bionic)
Assignee: Heather Lemon (hypothetical-lemon) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Assignee: Heather Lemon (hypothetical-lemon) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Hirsute)
Assignee: Heather
Thank you, options are discussed.
I'll set the bug to incomplete to reflect this isn't blocked on security right
now.
** Changed in: busybox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The updated OpenSSL package is not behaving as expected, openssl config
file (/etc/ssl/openssl.cnf) has PKA dynamic engine enabled. But
execution of `openssl engine` doesn't show (PKA) engine as one of the
listings. And also, offloading to PKA doesn't happen by default. Ex:
Executing speed test of
** Description changed:
[impact]
when talking to upstream nameservers, systemd-resolved limits its
advertised max packet size as 512 in its edns0 opt. However, one of the
primary benefits of edns0 is to allow using packet sizes larger than
512, which is the pre-edns0 max packet size.
> The server answers and then resolved sends an ICMP Destination Unreachable
> (Port Unreachable) response!
> This breaks name lookups frequently.
I'm unclear on how/why you are connecting these two statements...can you
explain why it's breaking name lookups?
** Changed in: systemd (Ubuntu)
I'm just driving past the sponsorship queue.
How can we validate that the CPE_NAME you're adding is definitely the
correct one for us to use in Ubuntu?
Your debdiff doesn't include adding BUILD_ID, so maybe this bug needs
renaming to be specific to CPE_NAME? BUILD_ID sounds like something
based
systemd/udevd appears to be working exactly as advertised, using the
phys_port_name when it's provided by the device's kernel driver; should
this be marked invalid for systemd, or is there actually some change
needed there?
--
You received this bug notification because you are a member of Ubuntu
hello
a completely lost user => https://forum.ubuntu-fr.org/viewtopic.php?id=2066473
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1939238
Title:
UNEXPECTED
Can somebody confirm my assumptions on the architecture of the test ?
First, it sets up a veth with router_eth42 at one end and test_eth42 at
the other (the itf names might be different ?). dnsmasq is bound against
router_eth42 which is configured manually via iproute with both IPv4 and
IPv6
** Description changed:
Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server
** Description changed:
+ Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
+
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server
Public bug reported:
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server answers and then
resolved sends an ICMP Destination Unreachable (Port
>From the log:
Bind to port 22 on 0.0.0.0 failed: Address already in use.
Something on your system already blocks the default SSH port which the
service will try to consume on install/update. You'd want to find what
owns this port and remove/reconfigure that - afterwards the openssh-
server
This update includes one of the two changes we have as delta.
Another Fix (group collisions) and the fix for this issue here.
I think despite FF, this could be re-merged to resolve this and the other
mentioned bugs.
I'll tag it to be more likely to be considered.
But to avoid collisions
** Also affects: network-manager (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Focal)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Focal)
Assignee: (unassigned) => Heather Ellsworth (hellsworth)
--
You received
Bug affects also to me in upgrading to 5.11.0-27
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
Release:20.04
Codename: focal
The solution proposed by @MikeR works for me:
I have created a file t.txt with missing modules
Thanks for the bug report. Please try adding this kernel parameter:
i915.enable_psr=0
which you can do by editing /etc/default/grub, adding the parameter to
the GRUB_CMDLINE_LINUX_DEFAULT line, and then:
sudo update-grub
and reboot.
** Summary changed:
- Screen keeps flickering on
*** This bug is a duplicate of bug 1939417 ***
https://bugs.launchpad.net/bugs/1939417
** Summary changed:
- Xorg freeze
+ amdgpu kernel freeze
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** This bug has been marked a duplicate of bug 1939417
Ubuntu GUI crashes (w and w/o
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414
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 1922414, so it is being marked as such. Please
Thanks for the bug report. It sounds like you have either a hardware
problem or a kernel bug. First please try using a USB keyboard and
verify that does not have the bug.
Second please try the latest kernel update:
sudo apt update
sudo apt install linux-generic-hwe-20.04
and reboot.
**
Sosumi is not supported here. It appears it was supported by the
developer at https://github.com/popey/sosumi-snap/issues but that
project appears to have been shut down.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug
It appears you have the kernel parameter 'nomodeset' which will disable
the Intel graphics driver. Please remove that parameter and if you
continue to experience problems then open a new bug.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New =>
*** This bug is a duplicate of bug 1939417 ***
https://bugs.launchpad.net/bugs/1939417
** Summary changed:
- Xorg crash
+ amdgpu kernel crash
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** This bug has been marked a duplicate of bug 1939417
Ubuntu GUI crashes (w and w/o
Workaround that worked for me: add
/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings Cx ->
sanitized_helper, # Print Dialog
to
/etc/apparmor.d/usr.bin.evince
*** /tmp/usr.bin.evince 2021-08-24 18:11:43.031953626 +1200
--- usr.bin.evince 2021-08-14 10:15:55.455083638 +1200
42 matches
Mail list logo
