Public bug reported:
fresh install ubuntu 20.04 then ran
apt-get update
apt-get upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-pc 2.04-1ubuntu26.17
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
ApportVersion:
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066066
Title:
cloud-init startup failure with Python 3.9.5,
There's no postfix bug described here.
** Changed in: postfix (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065546
Title:
postfix configuration must
Public bug reported:
Audio will work fine for a period of time, then randomly, you will hear
static, and then every sound effect is a static pop. The auto complete
"miss" sound in terminal is awful for example.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Same issue for me. Was using a script for Proton VPN loaded into the LAN
connection. Deleted the custom connection and rebooted. VMnet1 and 8
stopped trying to connect, and as a bonus now my KDE weather widget is
working again. Will use the GUI ProtonVPN application to make changes to
VPN.
--
Hoping to see the issue go away with the new Ubuntu 24.04 on a HP HP
ProDesk 400 G3 DM/82A5 and it uses Intel HD Graphics 630. But nope still
happens. I needed to pull the power for a bit before screen would come
back properly. Is there additional information needed to troubleshoot
the issue?
Public bug reported:
The version of duply (v2.4.1) included with Noble Numbat is not able to restore
files. I get this error when attempting a fetch (restore) operation:
--- Start running command FETCH at 2024-04-26 05:45:23.076 ---
CommandLineError: Option '--file-to-restore was changed in
Public bug reported:
Running ykman-gui on 22.04 currently shows the following. ykman works
fine.
NameError: name 'yubikey' is not defined
)
qml: qrc:/qml/YubiKey.qml:208: TypeError: Cannot read property 'success' of
undefined
"PyOtherSide error: Traceback (most recent call last):\n\n File
Hi Martin,
On Tue, Apr 9, 2024 at 6:09 PM Martin Pitt wrote:
>
> Nathan Scott [2024-04-09 17:30 +1000]:
> > > It's not really unknown, it's "just" a file conflict:
> >
> > Yeah - the unknown bit for me is "why tho" - I cannot see conflicting
> &
** Changed in: cyrus-imapd (Ubuntu)
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/1971469
Title:
FTBFS against openssl 3
To manage notifications about
Public bug reported:
Recent changes to Python which have been backported to Python 3.11 and
3.12 break colcon argument parsing due to a dependency on private API in
argparse.
A fix has been released in colcon-core 0.16.1 which should be backported
to any platforms which will receive the updated
I just downloaded the ISO, and used that ISO to start a Virtualbox guest
installation and got this error. No flash drives or physical mediums.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874662
I don't know how that got lost... "git clone" should be:
git clone https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058578
28f
2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f
I am running on KDE neon 6.0 release 22.04
Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP
PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
This works fine for me:
#!/bin/bash
git clone
cd jammy
git remote add upstream
https://git.kernel.
Public bug reported:
I have a local APT repository with a non-lowercase suite identifier.
apt-add-repository always forces it into lowercase, which causes apt to
emit warnings when it notices the mismatch:
$ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
Repository: 'deb
See same issue using Ubuntu 23.10 on a HP HP ProDesk 400 G3 DM/82A5 and
it uses Intel HD Graphics 630. Occasionally I will get a black screen
with no ability to activate which then requires a reboot. Sometimes I
will need to power off and unplug hdmi cable.
i915 :00:02.0: [drm] *ERROR*
*** This bug is a duplicate of bug 1976585 ***
https://bugs.launchpad.net/bugs/1976585
** This bug has been marked a duplicate of bug 1976585
Ubiquity Installer Crash (Consistently Repeatable)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Ubiquity installer fails with the following steps, booting off a 22.04
LTS USB.
Steps to reproduce:
- Select: *Try or Install Ubuntu [wait for bootup]
- Select: Try Ubuntu (with English) [wait for boot]
- Run "Install Ubuntu 22.04 LTS" icon in the top left corner of the
/var/log/syslog
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+attachment/5594427/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm trying to install Ubuntu with third party apps so that I can use
secure boot. I also am choosing to use zfs with encryption. If fails
when I press next on the timezone step.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature:
I am observing the same issue on 22.04. I cannot drag and drop from
nautilus into chrome or slack.
If I switch to an xorg session I can drag and drop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We've been running Sergio's exim 4.95-4ubuntu3~ppa2 for 27 hours so far
with no segfaults (previously it was segfaulting every few minutes) --
looks like the bug is fixed with those patches; thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Sergio, unfortunately your patched package does not fix the problem
-- we still see segfaults.
From the upstream discussion, I think we may need this commit as well:
https://git.exim.org/exim.git/commitdiff/8c74b00980bc7e3e479e8dfcd7c0008b2ac3f543
--
You received this bug notification
Wouldn't it just be an extensive list of if/then conditional statements
that covered all the official and point releases? Once done the first
time it would only be updated each time a new release was released or an
old one was archived to make sure it pointed to the correct path for the
upgrade
It seems to be a very simple issue. do upgrade already tells you what
version you have and if there is an upgrade path on new releases. Why
can't it do that for every release going back into antiquity. There are
probably only 40ish official releases that would need to be covered.
When a release is
Public bug reported:
do-release-upgrade seems to have failed on grub-efi, wondering if it
choked on my config; attached logs as per error message.
System was left in bootable, runnable state, but a zpool was blown away.
--
system pools and one pool on NVMe were ok:
sribe@sribe000:~$ sudo
@tobhe Thanks for looking into this. However that upstream bug was
apparently fixed in GnuTLS 3.7.4; I just tried libgnutls30
3.7.4-2ubuntu1 from kinetic and I still see these crashes in exim4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer
+ Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Description changed:
We are experiencing segfaults in exim since upgrading from impish
(4.94.2-7ubuntu2 with libgnutls30
A similar/identical issue appears to have been discussed briefly on the
Exim list:
https://lists.exim.org/lurker/message/20211008.224037.c1fee944.gl.html
They suggest that it may be a GnuTLS bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
We are experiencing segfaults in exim since upgrading from impish
(4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy
(4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in
_gnutls_trust_list_get_issuer, seemingly in the sender verify callout
during message submission.
Public bug reported:
An unresolvable problem occurred while calculating the upgrade.
This was caused by:
* Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem,
please try again later.
If none of this applies, then please report this bug using the
command
I was also unable to use NFS mounts since upgrading my client to 22.04.
My server is a QNAP running version 5.0.0.1986.
Enabling NFSv4 on the server did not solve the issue.
Adding vers=3 as a mount option on the client lets NFS mounts work again
for me.
--
You received this bug notification
Public bug reported:
I'm not sure if this is incorrect behavior in schroot or incorrect
assumption in sbuild-launchpad-chroot.
I have a system where I was not able to use union, so the focal-amd64
config that was built by sbuild-launchpad-chroot looks like below. When
attempting to build from
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967812
Title:
ubuntu 22.04 beta crash regarding gnome-shell and several others
also...
To manage
Public bug reported:
Hello to all, Under the Ubuntu 22.04 final Beta on live usb mode after
startup I noticed a crash regarding gnome-shell and also I noticed
several others on my end also meaning several other crashes and the
several other crashes I don't know what they are unless I boot to it
This bug report is a decade old and the reported system has long since
failed and been recycled. The nearest similar system I can access is a
Core 2 Duo T8100, which is able to both start and exit the latest
Memtest (in Jammy) using regular onscreen command keys. I suspect this
means that the
apport information
** Attachment added: "VarLogDistupgradeMainlog.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574702/+files/VarLogDistupgradeMainlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeLspcitxt.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574701/+files/VarLogDistupgradeLspcitxt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeApttermlog.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574700/+files/VarLogDistupgradeApttermlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeAptlog.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574699/+files/VarLogDistupgradeAptlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574698/+files/VarLogDistupgradeAptclonesystemstate.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "VarLogDistupgradeAptHistorylog.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574697/+files/VarLogDistupgradeAptHistorylog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574696/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967078
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574694/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967078/+attachment/5574695/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 959 F pulseaudio
-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 959 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Mar 30 04:28:02 2022
HotplugNewDevices:
HotplugNewMounts
** Changed in: python-caja (Ubuntu)
Status: Confirmed => 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/1863498
Title:
raise ValueError('malformed node or string: ' + repr(node))
Public bug reported:
I was training a neural network on CPU using Tensorflow + Keras in
Python. The crash happened twice in the same day after installing an
update to Ubuntu.
1) Ubuntu 20.04.4 LTS
2)
intel-microcode:
Installed: 3.20210608.0ubuntu0.20.04.1
Candidate:
** Summary changed:
- swtmp fails in focal with apparor
+ swtpm fails in focal with apparor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859506
Title:
swtpm fails in focal with apparor
To
@Noah,
cloud-init isn't doing anything wrong. Its working as designed.
'growroot', which is provided by cloud-initramfs-tools (upstream [1],
package [2]) also didn't do anything wrong. It's sole purpose in the
initramfs is to do what it is doing.
I'm not sure what code creates the image you've
> I thought cloud-initramfs-growroot was solely used with old kernels that
> can't resize mounted
> filesystems but I could be wrong. Wondering though why we install that
> package all of a sudden.
that is another option, to remove cloud-initramfs-growroot from the
image/initrd.
The problem
@Noah,
The image you pointed at there has the package 'cloud-initramfs-growroot'
in its initramfs. cloud-initramfs-growroot is going to run growpart on the
root filesystem during the initramfs unless one of the following files
exists on the root filesystem:
/var/lib/cloud/instance/root-grown
debian/postfix/usr/share/man/man1
This was due to a quoting error in debian/rules in 3.6.3. What's being
expanded there is:
'$(shell date -s @$(SOURCE_DATE_EPOCH))'
Nothing to do with NTP.
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: sbuild-launchpad-chroot (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: sbuild-launchpad-chroot (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Nothing is checking exit code of tar when the downloaded tarball is
extracted.
Tar could fail for many reasons including permission or
filesystem full.
If tar failed, sbuild-launchpad-chroot would just continue on.
The user would likely fail in a less obvious way later on.
In theory, yes. In practice, it would be very complicated and it's not
something that's likely to get done in the near-term.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957884
Title:
postfix
Does restarting (not reloading) or stopping/starting postfix get things
back in sync?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957884
Title:
postfix warns about differing chroot files after
It's postfix@$INSTANCE. If you don't have multi-instance setup, the
default instance is "-", so you would look for postfix@-, not postfix@.
This is discussed in README.Debian. You should probably file a new bug
for this problem if you don't get it figured out.
--
You received this bug
out
it and get them to incorporate it. I don't plan to add it as a patch unless
Debian actually needs it, which we don't so far.
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956505
Title:
Merge 3.
In case it helps, I noticed that in Ubuntu 21.04, my
~/.config/GIMP/2.10/pluginrc contained
(menu-path "/File/Create/Acquire/XSane/Device dialog...")
within the (proc-def "xsane" ...) s-expression. No menu-path appears in
my Ubuntu 21.10 ~/.config/GIMP/2.10/pluginrc.
--
You received this bug
Thanks. I'll reassign this to Ubuntu's dkimpy package. They should
consider doing a stable release update to fix this.
** Project changed: dkimpy-milter => dkimpy (Ubuntu)
** Changed in: dkimpy (Ubuntu)
Importance: Undecided => High
** Changed in: dkimpy (Ubuntu)
Status: New =>
Not a ca-certificates issue.
** Changed in: ca-certificates (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915238
Title:
warning:
This is an unneeded leftover and the file in the chroot
(/var/spool/postfix) can be deleted.
When using smtp*_tls_CAfile, the smtp or smtpd daemon copies from
/etc/ssl/certs before entering the chroot (CApath is different), so it
doesn't need to be there. We stopped copying the file into the
So I looked into this a bit more and based on
http://www.postfix.org/postconf.5.html#smtp_tls_CAfile is doesn't appear
to me that the ca-certificates.crt file needs to be in the chroot at
all. What happens if you just delete the chroot copy? Looking in the
git history, I can see we used to
to validate the media: https://askubuntu.com/questions/1383225/how-
to-boot-from-a-live-usb-stick-on-a-mac
I look forward to hearing from you.
Kind regards, Scott.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
Debian now has jack-mixer 17. This might be a good time to see if a
sync is possible or at least do a merge so it's clear what's different
between the packages.
** Affects: jack-mixer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Incorporation of this patch in postfix upstream is currently being
discussed on the postfix-users mailing list. The specific question
asked by Wietse is:
Has this been adopted, or do people on 3.5.* still have to tinker with
their /etc/resolv.conf files?
If anyone from Ubuntu could comment on
I'm not convinced that CVE-2021-20230 is the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847275
Title:
stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS
vulnerability
Public bug reported:
On multiple Azure VMs running Ubuntu 18.04.6 LTS, when cloud-init
21.3-1-g6803368d-0ubuntu1~18.04.4 was installed, it re-created the SSH
host keys. This caused an obvious security scare that our machines had
been hacked.
** Affects: cloud-init (Ubuntu)
Importance:
I'm open to putting a fix in Debian. I haven't come up with a solution
that I'm happy with and don't currently have a lot of time to work on
this.
I think Paride Legovini's "wall-of-text" post is on the right track, but
I would really prefer to avoid asking a question about this.
Anything in
Public bug reported:
Performing installation, error occured after coping files
ProblemType: Bug
DistroRelease: Ubuntu 21.10
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
This has been done finally in 3.0.2-2. :-)
** Changed in: xlsxwriter (Ubuntu)
Status: Triaged => 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/1478006
Title:
Include test
Public bug reported:
Error message on startup: "Malformed URL
/tmp/mozilla_supaplex0/linuxmint.torrent" then exits after I hit OK.
https://github.com/supaplextor/cloudy-chance-tcpip-
checks/blob/master/Screenshot%20from%202021-10-17%2017-14-41.png
The torrent file is not there.
ProblemType:
This is still a bug in Ubuntu 21.04 and 21.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
then text cursor
xe-guest-utilities is the Xen equivalent to open-vm-tools which is still
in Ubuntu to support VMware.
Though xe-guest-utilities may have been added to Ubuntu for one
particular cloud, it is needed on all installations of Ubuntu in VMs
running on Citrix Hypervisor / XenServer, or on XCP-ng etc..
** Changed in: wxwidgets3.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944381
Title:
package wx3.0-i18n (not installed) failed to install/upgrade: trying
This error message is reporting that the wx3.0-i18n and wx3.1-i18n
packages both contain the file
/usr/share/locale/ca/LC_MESSAGES/wxstd.mo. The wx3.1-i18n package is
not part of Ubuntu, so you'll need to report this problem to wherever
you obtained that package (perhaps a PPA?).
--
You
I copied over this from another host (same results):
=
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
# This will use (up to):
# - 4 sources from ntp.ubuntu.com which some are
Public bug reported:
Source: CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0.pdf
Link: https://workbench.cisecurity.org/files/3228 (download PDF)
cis-audit level2_server fails on rule_CIS-2.2.1.3 but passes all manual
checks.
===
Title Ensure chrony is configured
Rule
default
build.
The hardening script seems to fail to inject the code. Not sure why.
Will keep testing.
Scott
** Attachment added: "common-files"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5524209/+files/common-files.zip
--
Yo
Please find attached.
** Attachment added: "common-account.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5522351/+files/common-account.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please find attached.
** Attachment added: "common-auth.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5522352/+files/common-auth.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: cis-audit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942010
Title:
Ensure lockout for failed password attempts is configured
To manage notifications about this bug go to:
Public bug reported:
Source: CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0.pdf
Link: https://workbench.cisecurity.org/files/3228 (download PDF)
cis-audit level2_server fails on rule_CIS-5.3.2 but passes all manual checks.
===
Title Ensure lockout for failed password attempts is
@Eli,
I can recreate your problem, but it looks to me like a bug in ksh. ksh
complains that 'local can only be used in a function, when as shown
below it *is* being used in a function.'
My suggestion is to file a bug with ksh2020.
root@focal1:~# ksh -c 'foo() { local a=1; echo $?; }; foo'
ksh:
Public bug reported:
When building some software (https://github.com/puzzleos/uefi-dev)
I ran into a problem/bug in efitools 'sign-efi-sig-list'.
The end result in my case was that an attempt to update the PK variable
in uefi (ovmf files from 20.04 with qemu from 20.04) resulted in an
exit code
I believe this is no longer an issue because it doesn't occur under
Python 3 and Python 2 is EOL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100758
Title:
suds.sax.text.Text objects with
This released on Bionic and Hirsute a week ago, but Focal still has
Rustc 1.47.0. Is there a reason for that?
(1.51 also doesn't seem to be in any of the Focal branches on
https://code.launchpad.net/ubuntu/+source/rustc, but I don't entirely
know how the workflow for package releases works.)
--
This issue was fixed in https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/994 which avoids changing `xkb-options` unless
the Alternate Characters dialog is opened. (That was originally part of
MR 910, but was split off so it could be merged without being blocked on
design
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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: NFSv4.1 NULL pointer dereference
To
Public bug reported:
Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes
(in this case with a NetApp filer mounted):
[ 266.199481] BUG: kernel NULL pointer dereference, address:
[ 266.199495] #PF: supervisor read access in kernel mode
[ 266.199500] #PF:
It happened to me too
** Attachment added: "Crash log of amdgpu driver"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
GEneral install crap out, probably my fault, ignore
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: fonts-adf-gillius (not installed)
ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
Uname: Linux 5.4.0-80-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Marking this fix-released in focal as bug 1923232 was released to focal.
So this should be fixed in '1:4.0.6-0ubuntu1~20.04.1'.
** Changed in: lxc (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Norman,
Thanks for the comment. On first pass, it looks like you've diagnosed a failure
correctly.
Please open another bug and add output of 'cloud-init collect-logs'.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can not reproduce on QA side with 1031 kernel over than 350 times
SKU: ANDW-DVT2-C3
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X101
bios-version: 1.3.0
kernel:5.10.0-1031-oem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
lxc auto package tests show green for 4.0.6-0ubuntu1 other than i386,
which failed previously.
* amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lxc/20210525_040935_c4b64@/log.gz
* arm64:
** Description changed:
Hi. I'm using 20.04, and I need a fix for
https://github.com/lxc/lxc/pull/3589
I think my only options to get that via packaging are
a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master
b.) build my own.
I don't love either of those
Just fwi, this is in 4.0.6 which is up for SRU in LP: #1923232.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918955
Title:
SRU network: fix LXC_NET_NONE cleanup
To manage notifications about
1 - 100 of 44587 matches
Mail list logo
