The attachment "allow-classic.diff" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
This doesn't really seem to be a bugfix only release? It's not clear to
me how introducing a new “tracker export” command is a bugfix - I could
be persuaded of this, as it sounds from the NEWS item that it might be
required for future upgrades?
--
You received this bug notification because you
Public bug reported:
Welcome to Linux Lite 4.8 vec
terça 22 setembro 2020, 23:24:41
Memory Usage: 1949/2992MB (65.14%)
Disk Usage: 19/22GB (91%)
Support - https://www.linuxliteos.com/forums/ (Right click, Open Link)
vec ~ pacmd
Welcome to PulseAudio 11.1! Use "help" for usage
I have done the merge and uploaded it to the security-proposed PPA -
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa -
and have confirmed the iptables autopkgtest tests all pass as well as
the ufw tests.
Oibaf - since you requested this, would you be able to also test this?
This is the in-progress fix I've been working on. It does not quite
work right though: switching to an async hook for these commands is
resulting in the daemon killing the client on a protocol error.
This might be a problem with the hooks patch set itself. I need to
investigate a bit further.
** Package changed: meta-gnome3 (Ubuntu) => shared-mime-info (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1887425
Title:
php files now open by default
You have been subscribed to a public bug:
Until at least 16.04, php files used to open by default in Gedit.
I'm talking about when you double click on them in Nautilus (or the
first "open with " options that shows up in the right-click
menu)
After I upgraded to 20.04 (not sure in which version
** Description changed:
+ GNOME project libxml2 v2.9.10 and earlier have a global buffer over-read
+ vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.
+
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977
- Upstream patch:
-
Christian - thanks for your work on debugging this - can you please
remove the block-proposed tag if you are happy that 3.0.0~beta1-0ubuntu6
resolves this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Description changed:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977
Upstream patch:
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49
+
+ GNOME project libxml2 v2.9.10 and earlier have a global buffer over-read
+ vulnerability in
** Also affects: kde-cli-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
misidentifies
** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1857824
Title:
kmimetypefinder5
** Changed in: shared-mime-info (Ubuntu)
Status: Invalid => New
** Bug watch added: Debian Bug tracker #887709
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887709
** Also affects: shared-mime-info (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887709
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
** Patch added: "diff for bionic to support named param. (backport from cosmic)"
https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5413349/+files/apport_2.20.9-0ubuntu7.18.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Patch removed: "diff for xenial to support named param. (backport from
cosmic)"
https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5405275/+files/apport_2.20.1-0ubuntu2.25.debdiff
** Patch removed: "diff for bionic to support named param. (backport from
cosmic)"
Updated debdiff and made sure autopkgtest were successful on both xenial
and bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv
I've reported a new bug providing a complete and correct description:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682
This one can be safely closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
New bug reopened with complete and correct explanation:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682
** Changed in: shared-mime-info (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
In groovy the code for vte-keep-FD patch has been refactored to support
new upstream code.
However, I think it's the time we plan to remove this next cycle, given
that gdebi is the only project using it so far [1], and that upstream
already suggested a better way to do it [2].
So, if someone is
problem seems gone since 5.4.0-48-generic #52
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Title:
[XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio
After running that commands I got the following output:
$ ...
Running kmimetypefinder5 "/home/alex/Desktop/index.html"
application/x-perl
It seems like that kmimetypefinder5 is major culprit here. I've found another
unrelated bugreport here which was reported about a year ago:
** Package changed: ubuntu => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1896646
Title:
bluetooth no longer installed
Status in bluez package in Ubuntu:
You have been subscribed to a public bug:
22 september 2020 update removed bluetooth capability. No Bluetooth
hardware detected by system, cannot turn on or add devices.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu
I uploaded 3.0.0~beta1-0ubuntu6 just now that should address this issue.
Thanks Christian for your debugging!
** Changed in: apparmor (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This was fixed in snapd in 2.44 via
https://github.com/snapcore/snapd/pull/8467
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Released
** Changed in: snapd (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu11
---
pulseaudio (1:13.99.1-1ubuntu11) groovy; urgency=medium
[ Kai-Heng Feng ]
* d/p/0001-alsa-mixer-Add-support-for-HP-Thunderbolt-Dock.patch
* d/p/0002-alsa-mixer-Expand-comments-in-the-HP-Thunderbolt-Doc.patch
Public bug reported:
Certain programs don't seem to co-operate well with a dual monitor
setup. If it is of any importance, my setup is a laptop with a TV
plugged in via HDMI. So far I've found that VLC media player and Oracle
Virtualbox won't play nicely with two monitors. When both monitors are
Public bug reported:
Certain programs don't seem to co-operate well with a dual monitor
setup. If it is of any importance, my setup is a laptop with a TV
plugged in via HDMI. So far I've found that VLC media player and Oracle
Virtualbox won't play nicely with two monitors. When both monitors are
Please use CVE-2020-16122 for this issue. Thanks.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16122
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
This is growing my syslog file like crazy. Often running out of space in
/var partition (yes, I have a different partition for this).
Deleting the files /var/crash/ stops this. Restarts again after a
reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks a bunch mfo!!
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Status
** Tags added: sts-sponsor-mfo
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
Status in subiquity:
Fix Released
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1865504
Title:
hwclock reports incorrect status in audit message
Status in util-linux
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858802
Title:
libblkid: no bcache UUID due to ambivalent detection of bcache and
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870316
Title:
'sudo hwclock -s' fails with 'settimeofday() failed: Invalid argument'
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886300
Title:
rename.ul refuses to rename links that don't resolve (regression)
** Tags added: patch
--
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/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Status
This bug was fixed in the package apport - 2.20.11-0ubuntu27.9
---
apport (2.20.11-0ubuntu27.9) focal; urgency=medium
[ YC Cheng ]
* apport/apport/hookutils.py: add acpidump using built-in
dump_acpi_tables.py. (LP: #1888352)
* bin/oem-getlogs: add "-E" in the usage, since
[sts-sponsors]
Sponsored and uploaded into groovy.
Let's now wait until the package lands in groovy-releases before proceeding
with the SRU.
Thanks mfo and gpiccoli for your contributions.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The verification of the Stable Release Update for apport has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Patch added: "groovy_cryptsetup_lp1879980_V3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5413208/+files/groovy_cryptsetup_lp1879980_V3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Hi Eric,
I just updated the changelog with a more detailed description per file.
If it looks good to you for Groovy I'll update the stable releases too.
Thanks!
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: apparmor (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
The verification of the Stable Release Update for squid3 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package squid3 - 3.5.12-1ubuntu7.14
---
squid3 (3.5.12-1ubuntu7.14) xenial; urgency=medium
* d/squid.resolvconf: Invoke "systemctl reload --no-block" if we are
using systemd. This prevents squid from blocking if the reload
action is being issued
FYI, there was a components mismatch where apparmor-notify pulled
python3-notify2 (and its Depends) into main. For now, I've demoted
apparmor-notify to universe and adjusted the seed (in practical terms,
the security team will fix bugs in apparmor-notify regardless of where
it lives). We might
Public bug reported:
I ve no idea what happend or why.
The system reports me a bug, I thought I would send the information.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic
I just follow this thread and fix the issue.
https://forums.whonix.org/t/live-mode-breaks-apparmor/7559/7
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
That's right, I masked them by hand following some advice on the internet for
how to make systemd stop suspending, since it was not responding to settings in
login.conf even after restating logind
service.
Regardless of my motivation, it seems buggy that changing these settings
should lead to
sorry, you can withdraw this bug as I discovered it is a kernel bug, not
systemd.
(I wanted to withdraw it earlier but did not know how to get back to this
report.)
thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
systemd-resolve has been deprecated in favor of the new name
'resolvectl', but the resolvectl binary does provide backwards
compatibility with systemd-resolve (which is symlinked to resolvectl),
so there should be *some* kind of manpage for it, as long as that
backwards compatibility symlink is
Public bug reported:
When resizing a window with the mouse by dragging the edge or corner,
the window begins to flicker. It only flickers when actively being
resized, and when I stop dragging, it looks normal. This behavior is
does not occur on same pc in 20.04.
ProblemType: Bug
DistroRelease:
Public bug reported:
// System
Ubuntu 20.04 LTS
64-bit
user@ubuntu:~/Desktop$ sudo apparmor_parser --version
AppArmor parser version 2.13.3
Copyright (C) 1999-2008 Novell Inc.
Copyright 2009-2018 Canonical Ltd.
user@ubuntu:~/Desktop$ systemctl status apparmor.service
● apparmor.service - Load
> by unmasking
those targets don't come masked by default, how did they get masked?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
You need to provide some kind of logs to review.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1896395
Your ethernet driver or hw is preventing suspend:
[231201.406221] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x50 [e1000e] returns -2
[231201.406226] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
[231201.406230] PM: Device :00:19.0 failed to suspend async: error -2
[231201.406291] PM:
Tested the change - works as expected, prepping an MP
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
Apparmor 3.0.0 does not load profiles in containers
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/apparmor/+git/apparmor/+merge/391134
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
That patch by Christian Bolz is already applied (which seems reasonable after
that much time),
but when merging 3.0 the old patch for bug 1824812 should have been dropped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi Guilherme,
I can handle that while you're out.
cheers,
Mauricio
--
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/1879980
Title:
Fail to boot with LUKS on top
As refrence, it is a re-occurrence of
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812 , look
who filed that bug :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://gitlab.com/apparmor/apparmor/-/commit/61c27d8808f0589beb6a319cc04073e8bb32d860
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1895967
Title:
Apparmor 3.0.0 does
And we are back with Christian Bolz :-)
commit 61c27d8808f0589beb6a319cc04073e8bb32d860
Author: Christian Boltz
Date: Fri Jun 21 19:22:15 2019 +0200
Fix and simplify setting SFS_MOUNTPOINT
The question is why isn't this in the apparmor 3.0 package in groovy-
proposed ?
--
You received
Hi Eric, all the changes are part of the same functionality - the local-bottom
script for example is a clean-up for the files created in the local-top phase.
I think it'd be unnecessary verbosity to explain file by file, and this bug is
waiting for a long time to be fixed (especially due to the
Isn't that "Not starting AppArmor in container" message just in:
/lib/apparmor/apparmor.systemd
-> /lib/apparmor/rc.apparmor.functions
-> function is_container_with_internal_policy()
That looks unchanged (except a comment) but it behaves differently:
root@testguest-apparmor-good:~# .
@gpiccoli,
Can you break down everything this debdiff does per file being modified
in the d/changelog along with the summary you have already provided ?
It would ease for future reference and make the d/changelog more
accurate about the changes.
* d/cryptsetup-initramfs.install:
-
*
Linux Mint 19.3 user and I can also confirm this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth headsets in
In the original report, the issue happened randomly on boot when a
service[1] was triggering a reload while systemd-logind was starting,
resulting in a list of queued jobs that were never executed.
The issue can happen too under high load conditions, as reported upstream:
I meant, see *also* https://bugs.launchpad.net/bugs/1895302, no idea yet
if it's related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1888575
Title:
Split motd-news
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1882098
Title:
Packagekit lets user install untrusted local packages in Bionic and
Focal
Status
** Patch added:
"0001-aptcc-Do-not-trust-local-debs-allows-root-privileges.patch"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+attachment/5413161/+files/0001-aptcc-Do-not-trust-local-debs-allows-root-privileges.patch
--
You received this bug notification because you
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
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/1896577
Title:
FFE: new upstream release
restarting systemd-logind is not safe, as existing sessions can be
logged out.
also performing daemon-reload, mid-boot, also is not safe.
Can you explain the usecase and why these actions are performed
together, racing each other?
--
You received this bug notification because you are a member
This bug was fixed in the package netplan.io - 0.100-0ubuntu4
---
netplan.io (0.100-0ubuntu4) groovy; urgency=medium
* debian/tests/cloud-init
- Improve reboot test to avoid failure on arm64
-- Lukas Märdian Mon, 21 Sep 2020
12:23:02 +0200
** Changed in: netplan.io
Still chasing this down
The apparmor.systemd file is unchanged from focal.
The change is in rc.apparmor.functions which is a dependency of
apparmor.systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Public bug reported:
In certain scenarios, such as high load environments or when "systemctl
daemon-reload" runs at the same time a dbus service is starting (e.g.
systemd-logind), systemd is not able to track properly when the service
has started, keeping the job 'running' forever.
The issue
in fact the script doesn't seem to used shared-mime-info
$ XDG_UTILS_DEBUG_LEVEL=1 xdg-mime query filetype index.html
Running mimetype --brief --dereference "/tmp/index.html"
text/html
could you try to use the command with the same environement variable and
share the output?
--
You received
Bad case:
$ ./repro.sh bad
+ '[' bad == bad ']'
+ echo 'Bad case: Using apparmor from proposed'
Bad case: Using apparmor from proposed
+ BADCASE=1
+ lxc stop --force testguest-apparmor-bad
+ lxc delete --force testguest-apparmor-bad
+ lxc launch ubuntu-daily:groovy/amd64 testguest-apparmor-bad
See https://bugs.launchpad.net/bugs/1895302
On Tue, Sep 22, 2020, 07:41 Oliver Grawert <1888...@bugs.launchpad.net>
wrote:
> please note that the stable UbuntuCore18 images regressed due to this:
>
> https://github.com/snapcore/core18/issues/170
>
> ** Bug watch added:
The wrapper used depends of the environment, the previous one was under
a command line clean instance, on a GNOME based desktop
$ XDG_UTILS_DEBUG_LEVEL=1 xdg-mime query filetype index.html
Running gio info "/tmp/index.html"
text/html
--
You received this bug notification because you are a
here is output of running
journalctl -b -u whoopsie
journalctl -b -u apport-autoreport
on Ubuntu 20.10
which has same 100% used by systemd
** Attachment added: "output of running journalctl -b -u whoopsie and
journalctl -b -u apport-autoreport"
It seems it comes down to a change in /lib/apparmor/apparmor.systemd
which now refuses to load profiles when running in a container.
Example with 3.0:
$ /lib/apparmor/apparmor.systemd reload
Not starting AppArmor in container
Example with 2.x
/lib/apparmor/apparmor.systemd reload
Restarting
Great that it worked out. The downgrade was trying to remove things
because libglib binaries need to be on the same version so it was
necessary to downgrade libglib2.0-bin/focal in addition to the main
library
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
please note that the stable UbuntuCore18 images regressed due to this:
https://github.com/snapcore/core18/issues/170
** Bug watch added: github.com/snapcore/core18/issues #170
https://github.com/snapcore/core18/issues/170
--
You received this bug notification because you are a member of
package works as expected. test suite check done with the binary upload.
** 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 seeded packages, which
FYI - other testing might miss this as "starting a guest on groovy"
works with the new versions, but it will be without apparmor. Migrating
from focal or a pre-upgrade groovy shows the issues broken by apparmor
not being enabled.
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
I have backed up this container and its snapshot for later and re-run
the whole automation which got me that bad state.
That allowed me to run my automation again without removing this
container (in case we need it for debugging later). So I ran everything
again to check if it would happen again
To be noted that this issue also exists in Debian 10 and Ubuntu 18.04.
Because they all has commit 781b3e5efc3 (tftp: Do not use priority
queue).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Verified that focal grub2 with above commit works.
grub> linux vmlinuz-5.4.0-47-generic
grub> echo $?
0
grub> initrd initrd.img-5.4.0-47-generic
grub> echo $?
0
Rebuild grub2 deb with above commit and install
$ git clone -b applied/ubuntu/focal-updates
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug is no longer a duplicate of bug 1890913
init is using 100% of processor
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug is no longer a duplicate of bug 1890913
init is using 100% of processor
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a
Will be fixed in next systemd upload, in 246.6-1ubuntu1, at least for the
systemd part.
https://github.com/systemd/systemd/issues/16669
** Changed in: systemd (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Groovy)
Importance: Undecided => High
** Bug
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
Will be fixed in next upload, in 246.6-1ubuntu1
https://github.com/systemd/systemd/issues/16669
** Bug watch added: github.com/systemd/systemd/issues #16669
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1890913
init is using 100% of processor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1890913
init is using 100% of processor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Ok, I have definitely a snapshot left that has "conserved" the bad
state.
$ lxc stop testkvm-groovy-from
$ lxc restore testkvm-groovy-from orig
$ lxc start testkvm-groovy-from
$ lxc exec testkvm-groovy-from
# aa-status
apparmor module is loaded.
15 profiles are loaded.
15 profiles are in enforce
** Description changed:
Mesa 20.2.0 has been delayed by upstream, but we still want it in 20.10.
- It's currrently at rc4, final was supposed to be out a month ago.
+ It's currrently at rc4, final was supposed to be out a month ago. It's
+ been in debian experimental since rc1.
The
1 - 100 of 112 matches
Mail list logo
