@Henrik,
forget to reset the patch that disables d3cold_allowed and please try this
again. thanks
the d3cold_allowed shoube 1.
https://drive.google.com/drive/folders/17qeSGLKz8hR8TLsr35qS_4RSDUZcpaLu?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Also, do you have any animated indicators in your panel like indicator-
multiload? (I am thinking of bug 784055)
How about apps that are rendering constantly? Web browsers? Which ones?
What apps are close to gnome-shell in the 'top' list?
--
You received this bug notification because you are a
root@ubuntu:~# cat /etc/apt/sources.list.d/ubuntu-focal-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse
universe
root@ubuntu:~# apt policy linux-image-kvm
linux-image-kvm:
Installed: 5.4.0.1033.31
Candidate:
I am trying to do the security review of flashrom for this MIR but
currently it FTBFS with the attached debdiff in comment 9 - the build
log is attached. Can this please be resolved (along with removing the
'WILLIAM we're doing tests!' part of the output :)
** Attachment added:
Hey Chris, as written on bug #1925822 for Lukasz that's on our merge
list, we will try to get to it today
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924888
Title:
gnome-disks can't create exfat
The same problem in Linux Mint (Ubuntu derivative).
I think duplicates are showing when the same package exists in two or more
repos.
Synaptic is combining package with repo so if package exists in two repos then
the 4 identical packages are displayed (2 repos x 2 packages)...
--
You received
This bug was fixed in the package libvirt-dbus - 1.4.0-2ubuntu0.1
---
libvirt-dbus (1.4.0-2ubuntu0.1) hirsute; urgency=medium
* d/postinst: add libvirtdbus to group libvirt to be able to access the
sockets of libvirtd (LP: #1802005)
-- Christian Ehrhardt Fri, 23 Apr
2021
The verification of the Stable Release Update for libvirt-dbus 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
This looks like a candidate for release into hirsute-updates, but it's
not clear whether or not this is fixed in impish yet. If it's fixed in
impish could you please update the bug status, and if it's not fixed in
impish yet could you please fix it there? :)
--
You received this bug notification
This patch may help, please give it a try:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8bf7111b4bda00ae82e2de0cd871af997c3f2e9b
--
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/1914143
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-aws (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923415
Title:
Hirsute update: v5.11.13 upstream stable
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-aws (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926999
Title:
Hirsute update: v5.11.16 upstream stable
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850667
Title:
Please test with generic kernel, and set both DAC1 and DAC2 to maximum,
download the attached set-verb.sh, chmod a+x set-verb.sh, sudo ./set-
verb.sh. Check if the bass spk could output sound?
thx.
** Attachment added: "set-verb.sh"
This was fixed with linux 4.4.0-211.243 in Ubuntu 16.04 ESM (Infra).
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is apparently fixed in Hirsute, and now the Focal SRU, but that
would seem to leave Groovy without working bluetooth on the Pi 400 and
CM4? Is there any plan for an SRU to Groovy, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-8.0 (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/1928493
Title:
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Impish)
** Changed in: linux-oem-5.6 (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/1879341
Title:
test_350_retpolined_modules from ubuntu_qrt_kernel_security failed
Hello Lukáš,
You mentioned "initiate it with cloud-init (userdata + metadata)", may I
know how did you initiate userdata and metadata? also you mentioned
guestinfo.userdata and guestinfo.metadata, did you use the way described
here: https://github.com/vmware/cloud-init-vmware-guestinfo ?
Another
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4
---
openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium
* Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
-
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.4
---
openssl (1.1.1f-1ubuntu2.4) focal; urgency=medium
* Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
-
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4
---
openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium
* Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0
to validate, as it is common on self-signed leaf certificates.
(LP: #1926254)
-
Unable to run apport-collect 1928744 command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928744
Title:
Disk IO very slow on
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 192
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1928889
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1928890
and then change the status of the bug to 'Confirmed'.
If, due to the
** Summary changed:
- test_utils_testsuite linux ADT test failure with linux/5.11.0-18.19 (ERROR:
capability CAP_CHECKPOINT_RESTORE not found in severity.db)
+ test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with
linux/5.11.0-18.19
** Description changed:
This is a
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
** Changed in: linux (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/1885271
Title:
kernel oops xr-usb-serial
To manage notifications about this bug go
@piotr (peterq94)
refer comments #22 & #24 on this report.
I've written about this (work-around) on Lubuntu's discourse I believe
too (https://discourse.lubuntu.me/t/login-screen-flashes/1634/7 and
maybe elsewhere too). I've lost access to the d990 (which wasn't my
box) so I can't test further
The verification of the Stable Release Update for openssl 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
The verification of the Stable Release Update for openssl 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 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 1928600
and then change the status of the bug to 'Confirmed'.
If, due to the
Thanks. Not all logs will show the problem since a full lockup might
prevent pending log messages from reaching the disk. The log in comment
#10 however looks related and ends with some problems in the 'amdgpu'
kernel driver, which is what I expected.
So this bug is now assigned to the correct
Hi Dan, thanks for that. Interestingly it was much harder to reproduce
the problem with debugging enabled, but we got it on about the 15th try.
The log is attached.
** Attachment added: "systemd-networkd-1.log"
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 1928744
and then change the status of the bug to 'Confirmed'.
If, due to the
The verification of the Stable Release Update for rtl8812au 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
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.9
---
zfs-linux (0.8.3-1ubuntu12.9) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:45
+0100
--
You received this bug notification because
This bug was fixed in the package virtualbox-hwe - 6.1.16-dfsg-
6ubuntu1.20.04.2
---
virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:25
+0100
** Changed in:
This bug was fixed in the package virtualbox -
6.1.16-dfsg-6~ubuntu1.20.04.2
---
virtualbox (6.1.16-dfsg-6~ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:42:15
+0100
** Changed in:
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.4
---
v4l2loopback (0.12.3-1ubuntu0.4) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:12
+0100
** Changed in: virtualbox (Ubuntu Focal)
This bug was fixed in the package sysdig - 0.26.4-1ubuntu0.3
---
sysdig (0.26.4-1ubuntu0.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:03
+0100
** Changed in: v4l2loopback (Ubuntu Focal)
This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg-
0ubuntu13~20.04.2
---
rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:52
This bug was fixed in the package r8168 - 8.048.00-1ubuntu0.20.04.2
---
r8168 (8.048.00-1ubuntu0.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:42
+0100
** Changed in: rtl8812au (Ubuntu Focal)
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu6~20.04.2
---
oss4 (4.2-build2010-5ubuntu6~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:32
+0100
** Changed in: r8168 (Ubuntu
This bug was fixed in the package nvidia-graphics-drivers-340 -
340.108-0ubuntu5.20.04.2
---
nvidia-graphics-drivers-340 (340.108-0ubuntu5.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:47
+0100
This bug was fixed in the package lttng-modules -
2.12.2-1ubuntu1~20.04.2
---
lttng-modules (2.12.2-1ubuntu1~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:09
+0100
** Changed in:
This bug was fixed in the package lime-forensics - 1.9-1ubuntu0.2
---
lime-forensics (1.9-1ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:00
+0100
** Changed in: lttng-modules (Ubuntu Focal)
This bug was fixed in the package liblzf - 3.6-2~ubuntu1.20.04.2
---
liblzf (3.6-2~ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 17:11:50
+0100
** Changed in: lime-forensics (Ubuntu Focal)
This bug was fixed in the package iptables-netflow - 2.4-2ubuntu0.4
---
iptables-netflow (2.4-2ubuntu0.4) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:51
+0100
** Changed in: liblzf (Ubuntu Focal)
This bug was fixed in the package gost-crypto - 0.3.2-2ubuntu0.2
---
gost-crypto (0.3.2-2ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:41
+0100
** Changed in: iptables-netflow (Ubuntu Focal)
This bug was fixed in the package evdi - 1.7.0+dfsg-1ubuntu1~20.04.3
---
evdi (1.7.0+dfsg-1ubuntu1~20.04.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:32
+0100
** Changed in: gost-crypto (Ubuntu
This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1.2
---
dm-writeboost (2.2.9-1ubuntu1.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:23
+0100
** Changed in: evdi (Ubuntu Focal)
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu6.2
---
dahdi-linux (1:2.11.1~dfsg-1ubuntu6.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:14
+0100
** Changed in: dm-writeboost
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-
0ubuntu7~20.04.2
---
bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:27
+0100
** Changed in:
This bug was fixed in the package backport-iwlwifi-dkms -
8324-0ubuntu3~20.04.3
---
backport-iwlwifi-dkms (8324-0ubuntu3~20.04.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:04
+0100
** Changed in:
This bug was fixed in the package acpi-call - 1.1.0-5ubuntu0.2
---
acpi-call (1.1.0-5ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:55
+0100
** Changed in: acpi-call (Ubuntu Focal)
Thanks for the bug report.
1. It looks like you don't have any custom extensions installed, is that
correct? You can check using the app called 'Extensions' where there
should be only 3 default extensions listed.
2. Next time the problem is happening, please open a Terminal and run:
All autopkgtests for the newly accepted python3-stdlib-extensions
(3.9.5-0ubuntu3~21.04) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
python-pip/20.3.4-1ubuntu2 (arm64)
sshuttle/1.0.4-1ubuntu4 (amd64, ppc64el, arm64)
OK, wrote an email to realtek codec expert to ask for help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926165
Title:
Bass speakers not enabled on Lenovo Yoga 9i
To manage notifications about
You need four files:
1. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.4/amd64/linux-
headers-5.12.4-051204-generic_5.12.4-051204.202105140931_amd64.deb
2. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.4/amd64/linux-
headers-5.12.4-051204_5.12.4-051204.202105140931_all.deb
3.
changed HWE to linux as I see no reference to a HWE (5.4) kernel
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the help Brian, really appreciated.
This is just to inform you that it will take a while until I can try
this and report the results back to you. This machine is located at my
workplace, but due to the recent increase of Covid-19 cases in Singapore
we are supposed to work from home for
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928586
Title:
Desktop icons disappearing
To manage
Performing verification for Groovy
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.20.10.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
Thanks uriel, that is the same error in your log as comment #34. It
seems we have at least some correlation if not causation. I'm not yet
convinced it's a fix but can anyone test the patch and verify it fixes
this bug?
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1794.patch
Maybe
Performing verification for Hirsute
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.21.04.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12
---
initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hooks/fsck:
- don't check
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1
---
initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5
---
initramfs-tools (0.136ubuntu6.5) focal; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12
---
initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hooks/fsck:
- don't check
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1
---
initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5
---
initramfs-tools (0.136ubuntu6.5) focal; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12
---
initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hooks/fsck:
- don't check
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1
---
initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5
---
initramfs-tools (0.136ubuntu6.5) focal; urgency=medium
* scripts/local-premount/resume:
- Use readlink -f to correctly handle non-symlink $resume
(LP: #1876570)
* hook-functions:
- when
The verification of the Stable Release Update for initramfs-tools 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
The verification of the Stable Release Update for initramfs-tools 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
Performing verification for Focal
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu4.2
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
Performing verification for Bionic
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.1.8-3.6ubuntu2.18.04.3
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
struck Linux mint 20.4 (focal, right?) - "just" lvm2 was removed though,
not cryptsetup.
I definitely did not remove lvm2 by hand but usually run autoremove.
Maybe I'll actually read the "these packages will be removed" next time
o_O
My setup was encrypted root, encrypted raid5 and none of those
The verification of the Stable Release Update for initramfs-tools 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
Has the Xenial SRU been tested? I only see verifications for Bionic,
Focal, Groovy, and Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924589
Title:
Please update to 20210414.00 upstream
The focal and groovy autopkgtest failures in apt-clone look suspiciously
like real regressions. Do we have an analysis of those?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU]
This bug was fixed in the package google-guest-agent -
20210414.00-0ubuntu1~20.10.0
---
google-guest-agent (20210414.00-0ubuntu1~20.10.0) groovy; urgency=medium
* Rebuild for Groovy
google-guest-agent (20210414.00-0ubuntu1) hirsute; urgency=medium
* New upstream release (LP:
This bug was fixed in the package google-guest-agent -
20210414.00-0ubuntu1
---
google-guest-agent (20210414.00-0ubuntu1) hirsute; urgency=medium
* New upstream release (LP: #1924589)
- call restorecon on ssh host keys (#98)
- add ipv6 forwarded ip support (#101)
- add
This bug was fixed in the package google-guest-agent -
20210414.00-0ubuntu1~20.04.0
---
google-guest-agent (20210414.00-0ubuntu1~20.04.0) focal; urgency=medium
* Rebuild for Focal
google-guest-agent (20210414.00-0ubuntu1) hirsute; urgency=medium
* New upstream release (LP:
This bug was fixed in the package google-guest-agent -
20210414.00-0ubuntu1~18.04.0
---
google-guest-agent (20210414.00-0ubuntu1~18.04.0) bionic; urgency=medium
* Rebuild for Bionic
google-guest-agent (20210414.00-0ubuntu1) hirsute; urgency=medium
* New upstream release (LP:
The verification of the Stable Release Update for google-guest-agent 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
On Wed, May 19, 2021 at 12:13:24AM -, Achim Behrens wrote:
> The Problem is that this blocks the Grub-Menu from beeing displayed
That is not the problem reported in this bug. If you are seeing issues with
the grub menu not being displayed when it is configured to do so, please
file a
Thanks a lot for coming back to me. I couldn't run apport-collect as we
don't have python-launchpadlib installed. I did check (apt install
python3-launchpadlib) and in my case it would install quite a lot of
dependent packages - we would like to avoid that due to the nature of
our server.
But I
** Description changed:
After leaving my laptop on sleep mode for a while, then bringing it up
again causes the touchpad to stop responding completely. Checked for it
in the bus/input/devices folder and didn't see it.
Laptop model: ASUS X450L
Touchpad manufacturer: I presume to also
Mine still happens every day about 5 minutes after starting up
On Tue, May 18, 2021, 15:10 Merlin <1919...@bugs.launchpad.net> wrote:
> I saw this for a few days after a fresh install of Hirsute. It would
> happen shortly after boot, but it seems to have stopped. It could be
> because tracker
Public bug reported:
After leaving my laptop on sleep mode for a while, then bringing it up
again causes the touchpad to stop responding completely. Checked for it
in the bus/input/devices folder and didn't see it.
Laptop model: ASUS X450L
Touchpad manufacturer: I presume to also be ASUS
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/1928878
Title:
Touchpad suddenly not responding
To
1 - 100 of 396 matches
Mail list logo
