** Changed in: logwatch (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880211
Title:
Logwatch package points to wrong location for zfs utils
Updated the [Where problems will occur] part.
** Description changed:
[Impact]
On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.
[Fix]
Disable IEC958 (SPDIF) through ALSA UCM.
[Test]
With the UCM applied, `pactl` and audio panel in gnome-control-center
commit ba02abf58f8d0405140e658d8238b69e89120576
Author: Jason Gerecke
Date: Wed Jan 6 13:01:29 2021 -0800
data: Add ISDv4 51e9 (Lenovo ThinkPad P15 Gen 1) (#325)
Tablet definition was tested and verified to work by the bug
reporter.
** Patch added: "isdv4-51e9.patch"
The add-isdv4-aes-stylus-group.patch need the isdv4-48ca.patch and
isdv4-48ce.patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921991
Title:
Support isdv4-aes stylus group and multiple AES
commit a864679083c035eb08a75cf084a6564d589c0b1c
Author: Jason Gerecke
Date: Fri Nov 1 11:51:20 2019 -0700
Add multiple AES stylus definitions
Adds definitions for many different AES styli. The precise information
about supported features is hard to come by, but in general most
** Patch added: "isdv4-48ce.patch"
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1921991/+attachment/5482542/+files/isdv4-48ce.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921991
** Patch added: "isdv4-48ca.patch"
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1921991/+attachment/5482541/+files/isdv4-48ca.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921991
commit 8652aa3376bfb0e833af3704dc2ab7948958cd8f
Author: Jason Gerecke
Date: Tue Oct 29 15:26:51 2019 -0700
Add isdv4-aes stylus group to all AES sensors
AES sensors determined based on comments and HID descriptors available
at the wacom-hid-descriptors repository, where available.
Hey Etienne,
Thanks for submitting the debdiff. I'm taking a look in more detail, but
on first glance it looks good to me. If all goes well, I'll push it up
to our security-proposed in a bit.
** Changed in: shibboleth-sp (Ubuntu)
Assignee: (unassigned) => Steve Beattie (sbeattie)
--
You
If its helpful, the proper output looks like this.
- ZFS Report Begin
Total ZFS pools: 1
Total filesystems: 24 (24 mounted)
Total snapshots: 1926
Total volumes: 0
--- ZFS Pool Summary ---
Pool Name
** Description changed:
[Impact]
- * There are lots of stylus couldn't be used on Lenovo's platform, our
+ * There are lots of stylus couldn't be used on Lenovo's platform, our
OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
Gen5, ThinkPad P1 G3.
- * I reviewed
** Tags added: binder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921976
Title:
Can't create additional binder devices the user needs to specify them
To manage notifications about this bug go
This bug is present in Ubuntu 21.04 and 20.10 daily builds.
** Tags removed: apport-bug i386
** Tags added: groovy hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404172
Title:
lightdm: PAM
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909005
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912066
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for calamares (Ubuntu) because there has been no activity for
60 days.]
** Changed in: calamares (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the report. Making this public to get the Desktop team to
take a look at this.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1921826
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
[Impact]
* There are lots of stylus couldn't be used on Lenovo's platform, our
OEM customer request to support ThinkPad P15 Gen 1, ThinkPad X1 Yoga
Gen5, ThinkPad P1 G3.
* I reviewed and tested the below patches from upstream. It could
support the stylus very well on P15,
This change was made by a bot.
** Changed in: linux (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/1920685
Title:
Shity ubujntu 20.04 upgrade
To manage
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
This was addressed in https://ubuntu.com/security/notices/USN-4891-1 .
** Information type changed from Private Security to Public Security
** Changed in: openssl (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: gnome-shell (Ubuntu)
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/1921585
Title:
Screen contents visible when switching between logged
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier
[Bionic regression / autopkgtest]
simple.sh is looking if it doesn't load module by happenstance by
comparing the list before and after, and Bionic w/ 4.15 kernel reveal
that 'devlink' is added along the way. I was able to isolate it to the
networking plugin:
root@srv:~# lsmod | grep -i devlink
[Bionic regression / autopkgtest]
simple.sh is looking if it doesn't load module by happenstance by
comparing the list before and after, and Bionic w/ 4.15 kernel reveal
that 'devlink' is added along the way. I was able to isolate it to the
networking plugin:
root@srv:~# lsmod | grep -i devlink
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
sudo apt install libpcap-dev
on ubuntu 20.04.2
when i use funtcion pcap_findalldevs_ex tip to me undefined reference to
`pcap_findalldevs_ex'
ubuntu 18.04 is rigth...
** Affects: libpcap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Hey Milfred, sorry you are hitting this issue.
What Ubuntu release is this? And can you confirm that the desktop
envirnment you're using is the Ubuntu desktop, and not something else?
Thanks.
** Package changed: ubuntu => gdm3 (Ubuntu)
** Information type changed from Private Security to
*** This bug is a duplicate of bug 1532508 ***
https://bugs.launchpad.net/bugs/1532508
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
Logwatch fails to print info for ZFS due to invalid paths to binaries.
[Test Case]
With ZFS installed, run logwatch and note the missing ZFS information.
+
+ $ sudo apt-get install zfsutils-linux
+ $ sudo logwatch --detail Low --range all --service
[Bionic regression / autopkgtest]
simple.sh is looking if it doesn't load module by happenstance by
comparing the list before and after, and Bionic w/ 4.15 kernel reveal
that 'devlink' is added along the way. I was able to isolate it to the
networking plugin:
root@srv:~# lsmod | grep -i devlink
Relevat bits from UbiquitySyslog
Mar 28 10:33:20 ubuntu grub-installer: info: Installing grub on '/dev/sdb'
Mar 28 10:33:20 ubuntu grub-installer: info: grub-install does not support
--no-floppy
Mar 28 10:33:20 ubuntu grub-installer: info: Running chroot /target
grub-install --force
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
[Focal regression / autopkgtest]
After a few retries, the test passed. I had the same failure at the first run
with Hirsute.
http://autopkgtest.ubuntu.com/packages/s/sosreport/focal/amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello, sorry you are having this issue.
Unfortunately I am unable to reporduce this, with samba 2:4.11.6+dfsg-
0ubuntu1.6 from focal, either by applying iptables rules manually or
enabling firewall rules with ufw:
$ sudo iptables -D INPUT -i lo -j LOG
$ sudo iptables -L INPUT -n
Chain
Hi,
thanks for trying this out.
If this is still reproducible, please give the latest mainline kernel [1] a try
to see if you issue exists in the upstream kernel. Instructions could be found
in [2]
Please flip the bug status back to confirmed after your test.
Thank you!
[1]
Thanks for the bug report.
Please check the issue is still present in newer versions of GNOME. If
so then report it to the developers at https://gitlab.gnome.org/GNOME
/gnome-shell/issues and tell us the new issue ID.
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
** Package changed: unity
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921941
Title:
samba install flushes iptables and sets all chains to policy accept
There aren't many Xorg maintainers left, but if you would like to
communicate with them then please use the upstream page:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/312
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok. I got it working.
I built from here.
git clone https://github.com/thesofproject/linux.git
with
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
I uploaded my kernel debian/ubuntu packages to
https://drive.google.com/drive/folders/1L9DpjMamc37tZ19s5u_4RfmV221F4222?usp=sharing
Affected Spectre X360
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921974
and then change the status of the bug to 'Confirmed'.
If, due to the
II is a great point. Part of the original reason for keeping fwupd
major version locked in stable series was concerns to breaking other
components in Ubuntu such as gnome-software (ubuntu-software). Since
that has now transitioned to snap this is no longer a blocker. And as
you pointed out the
Public bug reported:
ubuntu azure seems not support binder FS.
$ uname -r
5.8.0-1026-azure
$ sudo modprobe binder_linux
$ mkdir ./tbinder
$ sudo mount -t binder binder ./tbinder
mount: /tbinder: unknown filesystem type 'binder'.
$ cat /proc/filesystems | grep binder
Another generic server
I try memory stress test with my ppa in #4, the issue is still
reproduced.
** Attachment added: "sosreport-u-Inspiron-1918855-2021-03-31-xbkosvf.tar.xz"
** Description changed:
+ Upgrade focal fwupd from 1.3.11 to 1.4.7.
+
+ [Impact]
+
+ * touchscreen is working after login on certain HW
+ * Current LTS is the OEM Project scope, so we need to SRU it.
+ * It's a specific HW related upstream fix.
+
+ [Test Plan]
+
+ * Wit this upgraded,
** Changed in: gdm (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865838
Title:
no error displayed on failed fingerprint authentication
To manage
Seb, I've pushed the relevant changes to salsa for focal, when you can
do a release please :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915174
Title:
Fingerprint enrollment error stops user to
Public bug reported:
[Impact]
On CML-R, after S3, No screen show on all three connector(3*DP).
[Fix]
The v4 patch has been landed on drm-tip.
For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.
[Test Case]
1. Connected the monitor on one of 3*DP on CML-R.
2. Suspend the
This bug was fixed in the package exo - 0.12.11-1ubuntu1.20.04.1
---
exo (0.12.11-1ubuntu1.20.04.1) focal-proposed; urgency=medium
* d/patches/lp1874954.patch:
- Allow resizing the xfce4-settings window smaller (LP: #1874954)
-- Sean Davis Sun, 14 Mar 2021 08:32:12
-0400
This bug was fixed in the package exo - 0.12.11-1ubuntu1.20.10.1
---
exo (0.12.11-1ubuntu1.20.10.1) groovy-proposed; urgency=medium
* d/patches/lp1874954.patch:
- Allow resizing the xfce4-settings window smaller (LP: #1874954)
-- Sean Davis Sun, 14 Mar 2021 08:32:12
-0400
The verification of the Stable Release Update for exo 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
As mentioned in the acceptance message, once you've tested the update we
would like you to “please add a comment to this bug, mentioning the
version of the package you tested”.
That said, messed up tags aside, this seems to have been verified as
fixed on the relevant releases.
--
You received
For point 6:
fwupd has two sides:
1. HWE: Given our policy, we won't block version bump in SRU on HWE component.
2. User space interactivity: given the two paths of user interactivity
I. via command line: the major interface is fwupdmgr. Per check it's
arguments, the command-line interface in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: onboard (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/1880114
Title:
Installed VLC, problem is gone. This has been confirmed on multiple
systems. Something about the way FireFox is handling media.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917816
Title:
Firefox
** Changed in: linux (Ubuntu Bionic)
Importance: Medium => High
** Changed in: linux (Ubuntu Focal)
Importance: Medium => High
** Changed in: linux (Ubuntu Groovy)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirmed that on a working system, just updating to the new kernel breaks it.
So that SRU kernel is definitely broken and should not be shipped.
[8.996651] BUG: unable to handle kernel NULL pointer dereference at
e12c1a77
[8.998738] IP: []
** Description changed:
- Per OEM customer workflow and SBAT update and other bugs fixes, we need
- to SRU focal/fwupd to version 1.4.7.
+ Per OEM customer CPU microcode workflow, SBAT update and other bugs
+ fixes, we need to SRU focal/fwupd to version 1.4.7.
[Impact]
* For new features,
When a single test fails occasionally, it can be an issue with LXD or
with the test, but when a bugfix release of a stable kernel suddenly
causes one of the most trivial tests to fail on all architectures, this
strongly suggests that the kernel is the issue.
--
You received this bug notification
This looks like a kernel regression to me.
** Package changed: lxd (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/1921969
Title:
lxd 2.0.11-0ubuntu1~16.04.4 ADT test
** Package changed: gnome-shell-extensions (Ubuntu) => gnome-shell
(Ubuntu)
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Focal)
Importance: Undecided => Wishlist
** Changed in: gnome-shell (Ubuntu Focal)
Hi Rex, took a while but it's now i focal queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905825
Title:
[SRU] Disable CRTCs when system becomes headless
To manage notifications about this
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891034
Title:
Ubuntu 20.04 drag and drop crashes
To manage notifications about this bug go to:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
arm64:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921964
Title:
Crash with "dbus.exceptions.DBusException: Couldn't get DBus name
net.tenshu.Terminator...: Name exists"
To
Merge upstream https://gitlab.com/apparmor/apparmor/-/merge_requests/730
it will be part of the next apparmor point releases
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210330_020010_0f3a6@/log.gz
armhf:
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.6) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
multipath-tools/0.8.3-1ubuntu2 (s390x)
munin/2.0.56-1ubuntu1 (armhf)
Please visit the excuses page listed below
Public bug reported:
I *think* it is ubiquity that causes the error.
What happens? Actually its two bugs I think:
After a standard installation of hirsute (ISO downloaded 2021-03-30)
with ZFS with encryption the bpool is not "mounted". After reboot
/boot/efi is empty so update-grub cannot
Hmm, apparently this is not well supported?
ref: https://askubuntu.com/questions/1318789/ubuntu-v20-does-not-detect-
systemd-boot-as-installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910571
Focal side of the bug should have been fixed by
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1
** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was fixed as part of
https://launchpad.net/ubuntu/+source/mutter/3.36.7+git20201123-0.20.04.1
** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As it seems grub won't be fixed, can you please at least tell me if it's
a good idea or not to replace grub with systemd-boot, and if Ubuntu is
planning to migrate to this too later?
ref: https://askubuntu.com/questions/1225791/how-to-replace-grub-with-
bootloader-systemd-boot-in-ubuntu-20-04
--
1 - 100 of 412 matches
Mail list logo
