The reason for the crash is that ntp uses an outdated OpenSSL API to use MD5
despite it normally being blocked in FIPS mode. This particular API has been
deprecated with OpenSSL 3 which we ship in Jammy.
This could be mitigated by switching to a newer OpenSSL API, but ntp also seems
to be on
Public bug reported:
Since I upgraded to Noble the lxd vga console doesn't work anymore. I am
using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a
vga console to an lxd vm I get:
unshare: write failed /proc/self/uid_map: Operation not permitted
It seems to be related to
Adding a few more details as requested by Adrien.
I used lxd to run the autopkgtest, in particular:
# Build lxd image
/usr/bin/autopkgtest-build-lxd ubuntu-daily:noble
# Run
autopkgtest -s --apt-pocket=proposed ./openssl_3.0.13-1ubuntu2.dsc -- lxd
autopkgtest/ubuntu/noble/amd64
It is
The resolve plugin only writes directly to resolv.conf if resolvconf is
not available (see
https://docs.strongswan.org/docs/5.9/plugins/resolve.html for details).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As promised, here are some more details on how I tested:
- been running autopkgtest locally and made sure they pass (log attached)
- installed it on my local development machine to see if anything breaks
- tested the upgrade in a lxd container, made sure openssl speed works and does
the right
** Attachment added: "apt install log from fresh noble lxd container"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2056593/+attachment/5754146/+files/openssl_3.0.13-1ubuntu2_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
We have an open MR with a handful of FIPS compatibilty changes we wore hoping
to get into 24.04. The main purpose of the changes is to detect whether the
kernel is running in FIPS mode and adjust the behavior of the library
accordingly by loading the correct provider backend
Public bug reported:
1) Ubuntu 22.04.3 LTS
2) libfreeimage3 3.18.0+ds2-6ubuntu5.1
3) Should open BMP files with all supported dib headersizes
4) When using BMP files with DIB Header sizes != sizeof(BITMAPINFOHEADER)
loading results in "invalid Format"
Since 3.18.0+ds2-6ubuntu5.1
** Patch removed: "rpki-jammy.diff"
https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+attachment/5753356/+files/rpki-jammy.diff
** Patch removed: "rpki-jammy.diff"
Right, new diff attached.
** Patch added: "rpki-jammy.diff"
https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+attachment/5753368/+files/rpki-jammy.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks! Documented both changes and made them clean reverts since that's
easier. New diff attached and pushed to git.
** Patch added: "rpki-jammy.diff"
https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+attachment/5753356/+files/rpki-jammy.diff
--
You received this bug
test build is available at
https://launchpad.net/~tobhe/+archive/ubuntu/testing/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056201
Title:
[BPO] rpki-client/9.0-1 from noble
To manage
** Patch removed: "rpki-jammy.diff"
https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+attachment/5752928/+files/rpki-jammy.diff
** Patch added: "rpki-jammy.diff"
https://bugs.launchpad.net/ubuntu/+source/rpki-client/+bug/2056201/+attachment/5752932/+files/rpki-jammy.diff
jammy backport patch is attached or available via git at
https://code.launchpad.net/~tobhe/ubuntu/+source/rpki-client/+git/rpki-
client/+ref/ubuntu/jammy-backport
** Patch added: "rpki-jammy.diff"
Public bug reported:
[Impact]
rpki-client implements the RPKI standard which is still actively developed and
moving fast.
Running a two year old release at this stage doesn't make a whole lot of sense
so it would be great
if we could make a version with newer features available for Ubuntu LTS
I have the same issue on Ubuntu 23.10 using VirtualBox 7.0.14 when using
i3. It doesn't occur when logging in using Ubuntu (Gnome).
The issue doesn't occur when enabling 3D Acceleration in VirtualBox (but
it slows down everything a lot).
Can also confirm uninstalling libva-wayland2 helps.
--
This is a problem for focal as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696591
Title:
fail2ban default configuration should be "backend = systemd" in Xenial
To manage notifications
After upgrading from 20.04 to 22.04 I'm facing same issue on Thinkpad E480.
When I boot older kernel 5.13.0-41-generic it works as expected. Seems that
issue is related to newer kernel 5.15 or a ubuntu specific kernel patch.
--
You received this bug notification because you are a member of
> does this change the ABI in any way that anything would care about or
notice?
I don't think it does, but you have a point. It might be a little safer
not to touch the function signature. Here's an updated fix.
** Patch added: "Autodetect FIPS kernel focal 2"
> have mysql detect a fips environment and auto-adjust?
This seems to be the best solution in terms of UX. I think auto-
switching to SSL + fips mode is always better than failing with a
cryptic OpenSSL error from a user's point of view.
The attached fix makes both client and server detect if
It looks like this is indeed an exim issue that was fixed in a recent
update. exim bug report can be found at:
https://bugs.exim.org/show_bug.cgi?id=2886
** Bug watch added: bugs.exim.org/ #2886
http://bugs.exim.org/show_bug.cgi?id=2886
** Changed in: exim4 (Ubuntu)
Importance: Undecided
I have forwarded this bug to upstream at
https://gitlab.com/gnutls/gnutls/-/issues/1374
** Bug watch added: gitlab.com/gnutls/gnutls/-/issues #1374
https://gitlab.com/gnutls/gnutls/-/issues/1374
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: mysql-8.0 (Ubuntu)
Assignee: Henry Coggill (henrycoggill) => Tobias Heider (tobhe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971788
Title:
Failure to enable SSL
You are right, 3.7.3-4 from jammy already contains the fix. I am
suspecting that the fix might be the cause of your segfault since this
was the last change in this part of the code and it seems to be a
regression introduced in jammy.
It looks like this bug hasn't been reported upstream yet. so we
** Changed in: exim4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214
Title:
Segfaults on verify callout, in _gnutls_trust_list_get_issuer
To manage
Thanks for taking your time to report this issue and help making Ubuntu
better.
It looks like this crash might be related to the upstream bug at
https://gitlab.com/gnutls/gnutls/-/issues/1277
** Bug watch added: gitlab.com/gnutls/gnutls/-/issues #1277
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974162
Title:
Crashing rtl8192cu on Ubuntu 22.04 LTS (5.15.0-30-generic) with Edimax
EW-7612UAn V2
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973642
Title:
[REGRESSION] Unable to connect to EAP-TLS networks
To manage
I don't know much about dropbear but from your explanation it does
indeed sound like this is an upstream OpenSSH bug that should be
reported at https://bugzilla.mindrot.org/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gcc-12 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972043
Title:
Please add -ftrivial-auto-var-init=zero to default build flags
To
** Changed in: openssl (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971992
Title:
openssl rmd160 digest broken
To manage notifications about this
Hey Jan, thanks for the report. This has been discussed upstream at
https://github.com/openssl/openssl/issues/16994.
OpenSSL 3 has deprecated RIPEMD160 and thus moved them to the legacy provider
according to the official openssl migration guide at
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971992
Title:
openssl rmd160 digest broken
To manage notifications about this bug go
CentOS Stream 9 is not affected as it ships a version >= 2.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941988
Title:
Designate DNS – Secondary zone is failed to be created and gets into
dnspython (python3-dns) package on RHEL (and thus CentOS Stream 8) is patched
with version 1.15.0-11
https://bugzilla.redhat.com/show_bug.cgi?id=2075187
** Bug watch added: Red Hat Bugzilla #2075187
https://bugzilla.redhat.com/show_bug.cgi?id=2075187
--
You received this bug notification
after enabling fractional scaling you can even disable it again after plugging
in the hub/second monitor (useful because it's blurry).
So my workaround looks like this:
boot -> freeze -> unplug hub -> enable fractional scaling -> plug hub in again
-> disable fractional scaling -> adjust display
boot log
** Attachment added: "boot.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970043/+attachment/5585327/+files/boot.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
same problem here.
Dell XPS13, intel graphics,
second monitor connected via USB-C Hub. Mouse connected to same hub can be
moved for halve a second after plugging in the hub, then everything freezes.
X11 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Related pull request on ceph side:
https://github.com/ceph/ceph/pull/46043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881747
Title:
cephadm does not work with zfs root
To manage notifications
I have tested all three packages and they seem to work as intended. The
updated packages also log the correct ssh fingerprint. Below is the log
output of all versions as well as ssh-keygen -l for comparison.
bionic with version 0.10.3-1ubuntu0.1
sec-bionic-amd64 sudo[11266]: pam_ssh_agent_auth:
one more for bionic
** Patch added: "pam-ssh-agent-auth_0.10.3-1ubuntu0.1.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/pam-ssh-agent-auth/+bug/1964486/+attachment/5571259/+files/pam-ssh-agent-auth_0.10.3-1ubuntu0.1.debdiff
--
You received this bug notification because you are a
** Patch added: "pam-ssh-agent-auth_0.10.3-3ubuntu1.21.10.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+attachment/5570440/+files/pam-ssh-agent-auth_0.10.3-3ubuntu1.21.10.1.debdiff
--
You received this bug notification because you are a member of
Here is a new debdiff for focal with improvements proposed by @mdeslaur
** Patch added: "pam-ssh-agent-auth_0.10.3-3ubuntu1.20.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+attachment/5570439/+files/pam-ssh-agent-auth_0.10.3-3ubuntu1.20.04.1.debdiff
hey @ddstreet the security certs team would prefer a fix via SRU rather
than the FIPS PPA as the changes present a general improvement by
getting rid of the deprecated MD5 fingerprints and making them
compatible with what `ssk-keygen -l` outputs
--
You received this bug notification because you
I ported and tested the fix for impish and focal, see attached debdiff.
** Patch added: "Fix for impish and focal"
https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1964486/+attachment/5570087/+files/pam-ssh-agent-auth_0.10.3-3ubuntu2.debdiff
--
You received this bug
> We should file a bug there with the patch.
>
> In addition, it looks like OpenSSH uses a "SHA256:" prefix and base64
> encodes the fingerprint. We should probably update the patch to do the
> same.
I updated the patch to also change the encoding and filed an upstream PR at
** Changed in: pam-ssh-agent-auth (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964486
Title:
crash when in FIPS mode
To manage
Fixed in jammy with
https://launchpad.net/ubuntu/+source/pam-ssh-agent-auth/0.10.3-3.1ubuntu1
As not using md5 is an improvement for everyone (ssh defaults to sha256
fingerprints since at least bionic) we think getting the fix in via SRU makes
more sense than a FIPS-specific package.
--
You
** Changed in: pam-ssh-agent-auth (Ubuntu Jammy)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964486
Title:
crash when in FIPS mode
To manage
I can confirm that after installing the 21.10 version of libserf (and
the necessary depencency libssl1.1), svn will work again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960280
Title:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819869
Title:
linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing
Fix for this is merged in Wallaby and Xena and will be in next releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930446
Title:
Wallaby ceilometer.compute.discovery fails to get domain
I can reproduce this issue as well
Have updated the system to the currently available state (apt-get update,
apt-get dist-upgrade)
The svn command-line client does not seem to try to connect with the svn-server
(no tcp syn can be found in tcpcump)
In early december 2021, I could still checkout
** Summary changed:
- Extreme Screen flickering when non native resolution
+ Extreme Screen flickering when setting a non-native resolution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958538
Public bug reported:
As soon I set the screen resolution to non native (4k laptop display)
the screen begins to flicker and horizontal/vertical lines appear. (See
attached image) Interestingly this happens only to the internal screen,
external monitors work fine.
Also during boot (supposedly
Public bug reported:
I'm maintaining the snap package for some weeks now and I encountered a
very weird aspect of snaps:
The application "manuskript" can be installed normally via snapcraft as
snap and it can be launched but its window (using Python and Qt5) does
not appear. However if you
The proposed patch from bugzilla.kernel.org
** Patch added: "i2c-i801-disable-alert-v2.diff"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+attachment/5542409/+files/i2c-i801-disable-alert-v2.diff
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1950060 ***
https://bugs.launchpad.net/bugs/1950060
** This bug has been marked a duplicate of bug 1950060
Unable to adjust screen backlight brightness on Google Pixelbook Eve
--
You received this bug notification because you are a member of Ubuntu
** Also affects: linux via
https://gitlab.freedesktop.org/drm/intel/-/issues/3680
Importance: Unknown
Status: Unknown
** Also affects: linux-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same issue with my Lenovo Ideapad Duet 3i - Bug 1951692
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1951692
There are patches available upstream to fix this issue.
https://patchwork.freedesktop.org/series/95127/
Freedesktop bug report
Bug 1950060 reports the same issue and the Pixelbook will be fixed as reported
in the Freedesktop bug report by these patches.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950060
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Duet 3i backlight doesn't work with kernel 5.13 on jammy alpha. But it
is currently the same kernel with witch impish runs.
I suspect it needs the parameter i915.enable_dpcd_backlight=1 to make it work.
However this function is broken since 5.12, please backport the
I cannot take any logs with apport-collect, because the boot is to slow too
finish when this happens.
So please change the status to Confirmed.
** Also affects: linux-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
My Lenovo Ideapad Duet 3i with Ubuntu 22.04 (Kernel 5.13) is also
affected (Current workaround disable_features=0x10).
** Bug watch added: Linux Kernel Bug Tracker #177311
https://bugzilla.kernel.org/show_bug.cgi?id=177311
** Also affects: linux via
This also affects MATE ISO 10-11-2021 crashed and failed.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950132
Title:
jammy
Public bug reported:
Install of fresh 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
Looks like your kernel is missing required modules (xfrm_user etc.) or
they were not automatically loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948044
Title:
charon-systemd fails on
Still not solved.
Bug happens on Fresh install of Kubuntu 21.04 with reccomended HDD distribution
on modern Lapotp (Ryzen5, 5500U).
And on older Laptop (~2014) with Ubuntu 20.04 & 21.04, Kubuntu 21.04 and
Lubuntu 20.04 & 20.10 & 21.04. (experienced often, sometimes every few hours)
Kswapd0
> Note: I can't see the libtss2-esys runtime dependency that Tobias
mentioned. @Tobias: is this expected, or am I missing some other flag?
Yes, that's correct. The configure script checks for both tss2-sys and
tss2-esys, but eventually, only tss2-sys is used (possible that Andreas
inten
> However this is not something like a separate module: support for TSS2
is builtin in the strongswan tools.
Correct, it's just part of libtpmtss.
> I didn't check but I imagine this requires a libtss2-* runtime dep.
Yes, libtss2-esys0 will be required (libtss2-esys-3.0.2-0 for Hirsute
and
> The stable Ubuntu releases are "feature frozen", which means that it
is unlikely TSS2 will be enabled in Focal (exceptions are possible, but
a very compelling reason is needed).
Is it a new feature, though? Couldn't it be considered a necessary fix
to actually make the already shipped tpm
> what is --enable-tpm option exactly?
It's a plugin in libtpmtss that implements interfaces to provide
certificates, private keys and random numbers from a TPM 2.0 to the IKE
daemon.
> Does it work without --enable-tss-trousers and --enable-tss-tss2?
No, it requires a TSS implementation, in
Public bug reported:
Occurred during Software Update.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-client 1:8.2p1-4ubuntu0.2
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
--enable-tss-trousers is missing too, so TPM 1.2 support isn't available
either. Which makes enabling the tpm plugin completely useless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940079
Title:
This affects Focal as well, because the kernel is available as HWE.
The pending release is only for Ubuntu Hirsute yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939157
Title:
HWE kernels:
hey there, I have the exact same problem, but I couldn't find a solution yet.
I included the edid file using the script given above:
lsinitramfs /boot/initrd.img-5.11.0-25-generic | grep edid
usr/lib/firmware/edid
usr/lib/firmware/edid/edid.bin
my grub config looks like this:
cat
27.2.1 is in bionic, focal and hirsute. According to @raof it was
SRU'ed, yesterday. Seems this bug slipped through.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936833
Title:
postinst fails when
Public bug reported:
I keep running into the issue that my patches contain "" instead of '' quotes
when submitting patches to GCC (GNU Compiler Collection):
Martin Liška wrote at gcc-patches@ to my patch:
> > Aha, the known issue that Ubuntu 20.04 has a too old flake8 such that I
> > only see a
Hello Olivier,
thanks for your reply and yes I can reproduce the bug. Bevore I
reinstalled it I removed all Preferences.
Now I ran the Command above and got a Mail with this report
A new OAuth token consumer was enabled in Launchpad.
If you did not make this change, please open a new Question
It appears that the build fails because of the `/debian/debian.env`
file. The contents of it changed recently in the 5.10. line (starting
with 5.10.37) - but are OK before that and also in 5.12.x .
It is also noticeable that that "faulty" (?) commits/configs come from
"kathleen" instead of
5.10.x and 5.11.x kernels after this one without diskspace do not build
anymore with even less progress / log output:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.21/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.22/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.37/
used. 1147,8 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
12683 tobias20 0 2653208 300408 224756 R 108,6 3,7 12:59.40 Web
Content
, 5719,6 used, 2008,1 buff/cache
MiB Swap: 26058,0 total, 23596,0 free, 2462,0 used.576,0 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
20866 tobias20
** Changed in: cloud-archive/kilo
Status: Triaged => Invalid
** Changed in: cloud-archive/icehouse
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517763
Regarding "So installing gcc-10-offload-amdgcn will just make gcc build
binaries for amdgcn target which can't run on nvptx target."
GCC can compile a program for multiple GPUs at the same time. Which of
them is used (nvptx or gcn or none/host fallback) is chosen at runtime.
Hence, installing
Fixed by this:
linux-hwe-5.8 (5.8.0-49.55~20.04.1) focal; urgency=medium
[ Ubuntu: 5.8.0-49.55 ]
- cachefiles: Drop superfluous readpages aops NULL check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug affects me as well with the mentioned kernel and the next in line:
ubuntu kernel (affected): 5.8.0-49.55~20.04.1
ubuntu kernel (affected): 5.8.0-50.56~20.04.1
With the ubuntu provided mainline kernels (via mainline) the problem does not
occur:
mainline kernel (not error):
Hi, I've stumbled across this post here after I've searched for the
error message "rnp_op_verify_execute returned unexpected" on Google.
@yg-info I've tested the beta version "88.0b2" (simply downloading the
.tar.bz2 for Linux and executing the "thunderbird" binary) and it's now
working. The two
lspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h
(Models 00h-0fh) Root Complex [1022:1450]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
00h-0fh) I/O Memory Management Unit [1022:1451]
00:01.0 Host bridge [0600]: Advanced Micro
Since upgrading from Ubuntu 20.10 to 21.04 I get this message like every
second in journalctl:
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport :00:03.1: AER: Multiple
Corrected error received: :00:00.0
Apr 09 13:00:28 tobias-MS-7C37 kernel: pcieport :00:03.1: PCIe Bus Error
Changing the "Base Memory" size in VirtualBox under "System ->
Motherboard" from 2048MB to 3072MB helped, now the install does not
crash any more.
I wish there was an easy way to inspect the system state after an
install crash, before having to submit a bug report.
Even better, the installer
Mar 29 06:23:28 xubuntu kernel: [ 265.738745] cat: page allocation
failure: order:6, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO),
nodemask=(null),cpuset=/,mems_allowed=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Failed to fetch
http://th.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Temporary
failure resolving 'th.archive.ubuntu.com'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921680
Title:
21.04
Public bug reported:
I was trying to install Xubuntu 21.04 in VirtualBox and it crashed.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.12
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
I ran into the same issue. And I also think this bug is critical, not
high. I would be very happy if this could be fixed as soon as possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379
** Bug watch added: Linux Kernel Bug Tracker #208883
https://bugzilla.kernel.org/show_bug.cgi?id=208883
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=208883
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Can we get a kernel build with this patch to test if this fixes it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910712
Title:
kernel BUG at fs/cachefiles/rdwr.c:717
To manage notifications
I've managed to make the subwoofer work with some caveats, I've made a
short guide here:
https://gist.github.com/BXZ/48cd8173807676a1402cf4bc7928c0c0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ The Laptop is an Ideapad Flex 5 14ARE05
+
My touchpad is not recognized at all in xinput or libinput list-devices.
There are however some lines mentioned in dmesg about MSFT, Mouse and PS/2
which I think is the touchpad.
-
[0.004374] ACPI: SSDT
Public bug reported:
My touchpad is not recognized at all in xinput or libinput list-devices.
There are however some lines mentioned in dmesg about MSFT, Mouse and PS/2
which I think is the touchpad.
[0.004374] ACPI: SSDT 0xC968F000 007216 (v02 LENOVO AmdTable
0002 MSFT
1 - 100 of 2390 matches
Mail list logo
