A deployment method improvement in the field will be tracked as a
private bug LP: #1889498.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939898
Title:
Unnatended postgresql-12 upgrade caused MAAS
Closing MAAS task since MAAS just connects to PostgreSQL through tcp
connections.
One correction to my previous statement:
$ sudo lsof / | grep plpgsql.so
postgres 21822 postgres memREG 252,1 202824 1295136
/usr/lib/postgresql/12/lib/plpgsql.so
postgres 21948 postgres
Thanks Christoph for chiming in and a second voice that confirms what I
said.
So to summarize:
- we have found the root cause to be sure what is going on (stored procedures
triggered late lib loading of new on-disk .so files by an old instance of the
server)
- Packaging takes care of
Yeah, only hanging on glibc indeed.
Since the reported test fail is fixed let us mark it "fix released", that way
it shows only the glibc transition and not the (now fixed) update excuse bug in
update-excuses.
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Released
--
You received
Attached is a debdiff for Bionic.
I also ran the three tests in this patch, and they all pass:
ext/mysqli/tests/bug77935.phpt
ext/mysqli/tests/ps_cursor_multiple_result_sets.phpt
ext/mysqli/tests/mysqli_stmt_get_result.phpt
https://paste.ubuntu.com/p/5422Hb6YMg/
** Patch added: "Debdiff for
@aaron,
Tried the 5.11.0-26.28-lp1938999-generic kernel, it works fine. You
could check more about it from this log. Thanks!
** Attachment added: "journalctl.l15.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+attachment/5518358/+files/journalctl.l15.log
--
You
This looks like a very easy fix and one where I don't think there would
need to be a lot of discussion about (correct me if I am wrong). I'll
work on getting the patch ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a debdiff for Focal.
I have run the three tests included in these changes, and they all
succeed:
ext/mysqli/tests/ps_cursor_multiple_result_sets.phpt
ext/mysqli/tests/bug77935.phpt
ext/mysqli/tests/mysqli_stmt_get_result.phpt
https://paste.ubuntu.com/p/ZBz9wtXcDr/
** Description
Public bug reported:
I can't record audio from my bluetooth headset KDM-G2. Also I can't
switch a2dp mode to hsp/hfp mode in ubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname:
This bug was fixed in the package r10k - 3.7.0-2ubuntu1
---
r10k (3.7.0-2ubuntu1) impish; urgency=medium
* d/p/20_disable_test_changing_proxy_settings: skip tests trying to change
the proxy settings, they are failing in the Ubuntu autopkgtest
infrastructure (LP: #1940104).
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (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/1914420
Public bug reported:
Sistem not start
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion:
Than you Brian for the very useful link. This helped a lot as I had no
idea what went wrong up until that point. Also thank you Mario for the
"redirect" to the proper location, I've reported the issue here:
https://github.com/fwupd/firmware-lenovo-thinkpad/issues/147
** Bug watch added:
The verification passed for focal.
ubuntu@ubuntu:~$ apt-cache policy u-boot-sifive
u-boot-sifive:
Installed: 2021.01+dfsg-3ubuntu0~20.04.1
Candidate: 2021.01+dfsg-3ubuntu0~20.04.3
Version table:
2021.01+dfsg-3ubuntu0~20.04.3 500
500 http://ports.ubuntu.com/ubuntu-ports
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938149
Title:
To support AMD W6600 and W6700
To manage
Forgot to mention the most important details: this was tested on Ubuntu
Server 20.04, Kernel version 5.4 (standard install) then also 5.11.
Behavior was the same in both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I am having a RAID 10 made of 24 x Micron 9300 Pro 15.36TB. I have
initialized the array using the command as follows:
mdadm --create /dev/md0 --raid-devices=24 --chunk=32 --level=raid10
/dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1
/dev/nvme5n1
** Description changed:
I installed Ubuntu Core (iotg-focal-core-unencrypted-20210804.img) on
the EHL board (CID:202105-29063) and use default BIOS settings.
The boot process stops with the same error as seen when booting Ubuntu
Core on the TGL-H board
** Description changed:
[Impact]
- With AMDGPU and don't use it as a display output,
- After multiple Suspend, system would hang.
+ With AMD-GPU and don't use it as a display output,
+ After multiple Suspend, system would hang.
[Fix]
Disable BACO for polaris12 series.
+ BACO allow the
** Also affects: snapd (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/1938678
Title:
[intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during
Both Lubuntu & Ubuntu(desktop) focal dailies (2021-08-16) boot on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
(the only box I have that was impacted by this bug)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
KERNEL FAILED ON UEFI BOOT Not Fixed...!!!
UPDATE KERNEL Please!
Daily build 20210816.iso REJECT The Header, Kernel, Modules & Extra Modules
UNSUPPORTED! For UEFI Install using USB.. Latest FIX is a FAILURE. COMPLETE
FAIL< WILL NOT BOOT...
Latest Kernel I have tested that works is
Daily build 20210816.iso REJECT The Header, Kernel, Modules & Extra Modules
UNSUPPORTED! For UEFI Install using USB.. Latest FIX is a FAILURE. COMPLETE
FAIL< WILL NOT BOOT...
Latest Kernel I have tested that works is 5.13.11 @ kernel.org. Works Awesome
for this Version of Ubuntu impish.
Thanks for the bug report. That's a kernel crash in the nouveau driver.
But that driver is not well supported so we would usually recommend the
official Nvidia driver instead. Unfortunately:
1. Your GeForce 310M GPU requires the Nvidia 340 driver only. Newer
drivers don't support that GPU; and
Public bug reported:
[Impact]
With AMDGPU and don't use it as a display output,
After multiple Suspend, system would hang.
[Fix]
Disable BACO for polaris12 series.
[Test Case]
1. Must plug AMD GPU and don't use it as display output
2. Plug DP/hdmi on igpu.
3. Suspend machine.
4. check if system
Thanks. I can't see any relevant problems in that log. Please try
following all of those steps again, and importantly not until the "stop"
happens. Please also remember step 5.
P.S. Is there any reason you might think this is a different issue to
bug 1906449?
--
You received this bug
it happened with me with with kubuntu 20.04.2.0 fresh install
the problem first appeared during installing the first upgrades after OS
installlation during the installation of linux 5.11.0-25 it showed me the same
message that is in bug description
such as
"update-initramfs: Generating
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have created a test kernel for 21.10 at the following link:
https://people.canonical.com/~mreed/lp_1935034_mpt3sas_update_38_100/impish/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935034
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
This bug is closed as a duplicate of bug 1869750 which is also closed.
For any ongoing issues, please open new bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Seeing i915 GPU HANG in 5.11.0-7620-generic.
Aug 14 23:46:50 topper kernel: [88920.160585] i915 :00:02.0: [drm]
Resetting rcs0 for preemption time out
Aug 14 23:46:50 topper kernel: [88920.161300] i915 :00:02.0: [drm] *ERROR*
rcs0 reset request timed out: {request: 0001, RESET_CTL:
This is happening to me too. Fresh install of Debian 11, primary DP
landscape, secondary HDMI portrait. Two effects:
1. A window on the right of the primary screen moves to the left of the
primary screen. Another window on the left of the primary screen does
not move. The moving window also
Thanks
On 8/16/21 8:18 PM, Hui Wang wrote:
> @Michael,
>
> The patch for 5.11.0-31-generic was rejected because it introduced a
> build failure (https://lists.ubuntu.com/archives/kernel-
> team/2021-August/123162.html), the fix patch will be in the -32 kernel,
> and once the -32 kernel merges
I can confirm it happens to me also in 21.04. The PDF opens fine for me
but the instant I hit print the evince process pegs the CPU and stays
there indefinitely. Files are on the local disk. x86_64 architecture.
The most recent PDF that did this to me is here:
@Michael,
The patch for 5.11.0-31-generic was rejected because it introduced a
build failure (https://lists.ubuntu.com/archives/kernel-
team/2021-August/123162.html), the fix patch will be in the -32 kernel,
and once the -32 kernel merges this patch and is ready to test, the
status will be
Correction: the software is mpv and NOT celluloid.
UPDATE: if both of my sounds are 100% (so total 160%) and I press volume
UP on my multimedia keyboard then the volume goes back to 100% (so the
sound from control center -> sound -> goes back from max to 100%)
--
You received this bug
Done and done. Please let me know if there's anything else I can do to
help.
** Attachment added: "a journalctl of the previous boot"
https://bugs.launchpad.net/ubuntu/+bug/1939966/+attachment/5518253/+files/prevboot.txt
--
You received this bug notification because you are a member of
This most likely is not a bug with fwupd, but rather a bug with the
Lenovo firmware. I would suggest you file it here:
https://github.com/fwupd/firmware-lenovo-thinkpad for Lenovo's firmware
team to pull the update and investigate further.
** Changed in: fwupd (Ubuntu)
Status: New =>
Is this still an issue for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639029
Title:
package apt-listchanges 2.85.14ubuntu1 failed to install/upgrade: sub-
processo script
Public bug reported:
Description:Linux Mint 20
Release:20
Hi,
I suffered from a bug when resuming my laptop,
the error would say something related to the "dma push buffer"
I googled and found this thread on the problem, which has been going for
a long time.
You guys mocking around trying to hack headers and wotnot, just build
the bloody kernel and you'll have a full kernel without wondering if you
broke something by hacking stuff! You could have built the kernel a
100x by now!
1) Just build dwarves from hirsute
2) build libbpf from hirsute
3)
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940107
Title:
libvirtd fails to create VM
To manage notifications
sponsored
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930776
Title:
failing test with golang 1.16
To manage notifications about this bug go to:
sponsored
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930772
Title:
currently FTBFS due to TestTLSConfig
To manage notifications about this bug go to:
** Also affects: zfs-linux (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/1939177
Title:
Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send |
Public bug reported:
Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs
during full-screen video playback (watching Youtube videos in Chromium).
Often, it happens just after or during the switch to full-screen.
The system stays running and I can connect via ssh, but restarting
Hello Brian, or anyone else affected,
Accepted livecd-rootfs into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.664.28 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: direvent (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/1904216
Title:
Is there a specific reason this needs updating, apart from the version
number being higher? For example are there any missing features, bugs
fixed, or incompatibilities reduced?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Based on earlier comments, this seems to affect Ubuntu, too, not just
upstream netplan.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please sync intel-ipsec-mb 1.0-1 (universe) from Debian unstable (main)
Changelog entries since current impish version 0.55-1:
intel-ipsec-mb (1.0-1) unstable; urgency=medium
* Sync to latest 1.0 release
* Rename libipsec-mb0 to libipsec-mb1
* Remove debian/watch as
On Mon, Aug 16, 2021 at 02:05:07AM -, Kai-Heng Feng wrote:
> Is there any log in `/var/lib/systemd/pstore`?
No.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939349
Title:
frequent hangs with
On Mon, Aug 16, 2021 at 02:15:25AM -, AaronMa wrote:
> Could you try disabling Secure Boot in BIOS?
Would you expect disabling Secure Boot to have an effect here? It should be
out of the way after the kernel has booted.
I have disabled Secure Boot, and the hang is still reproducible.
--
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
This bug is not limited to just Kubuntu. I am chiming in as a Xubuntu
20.04.2 user. The driver I attempt to install from Driver Manager is
340.108. The results are identical to what is being reported here. And
this bug affects ALL of my machines running v20.04. My Asus laptop with
hybrid Nvidia
@tlk this is similar/same workaround, info posted in #57 is in principles:
1. install problematic package without configuring
2. replace binary files in unpacked package path
3. configure package (this also do dkms modules build)
4. fake libc depend version in status file
this (details in #57)
Public bug reported:
consul/1.8.7+dfsg1-2 (just synced it from Debian) has a test failure
with go1.16:
=== RUN TestDynamicTLSConfig
tls_test.go:263:
Error Trace:tls_test.go:263
tls_test.go:339
Upstream has been working with me to try to determine what is going on
here. The conclusion is that we believe that firmware is piggy-backing
on the ARM_SMCCC_ARCH_WORKAROUND calls, and is clobbering some of the
registers in the x4-x17 range. The patch series mentioned in Comment #9
happens to
This sounds similar to the following forum posting:
https://forums.lenovo.com/topic/view/15028/5092528
** Package changed: ubuntu => fwupd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
The attachment "debdiff" seems to be a debdiff. The ubuntu-sponsors
team has been subscribed to the bug report so that they can review and
hopefully sponsor the debdiff. If the attachment isn't a patch, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are
** 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/1930752
Title:
FTBFS - test failure TestHeadReadWriter_WriteChunk_Chunk_IterateChunks
To manage notifications about this bug go
** 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/1940104
Title:
Proxy tests failing in the autopkgtest environment
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
The attachment "bionic.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
This appears to be fixed in the current beta kernel for 18-pi -
5.4.0-1042.46~18.04.3 r337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
Title:
Bad Linux ARM64 Image magic
To manage
This bug affects me too.
Ubuntu 20.04 with Gnome. The bug appears when using Firefox in my case.
Downgrading the kernel to 5.4 series solves the issue. I have to downgrade from
5.11, the last version of the Hardware Enablement Stack. The bug is present on
5.11 and 5.8 versions.
Intel(R)
Thanks for the review Athos!
I did not forward anything because the next Debian upload should already
contain the fix upstream (I am one of the maintainers in Debian), if it
is not and this becomes an issue there I'll know where to grab the patch
;)
I am adding the extra DEP-3 headers your asked
Thanks Lucas! LGTM
I suppose you decided not to forward this one to Debian because Debian
may never be affected by this specific bug (in case a new prometheus
version lands before go 1.16 does so), which is reasonable.
I also have a short nitpick here: it would be nice to add a "Bug-Ubuntu"
Thanks for the review Athos! I am going to upload the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940104
Title:
Proxy tests failing in the autopkgtest environment
To manage
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
Thanks, Lucas! LGTM
At first I thought this change could be forwarded upstream if instead of
verifying the AUTOPKGTEST_TMP env variable we verified the env variables
were not defined before overriding them.
Then I realized that the functions used to do so are indeed running in a
somewhat
Since we are reaching feature freeze I am adding the mentioned upstream
commit as a delta to finally release this version in Impish. The debdiff
is attached, I tested it locally and it builds fine and autopkgtest is
happy:
autopkgtest [16:16:11]: summary
dh-golang-autopkgtest
@cpaelzer the build and/or autopkgtest requirement for MIR possibly
should be expanded to allow for hardware-specific code like this, where
'normal' testing isn't easy and/or possible. In such cases, IMO at
least, it seems like an exception would be reasonable, but only if the
subscribing team
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
I'm having a similar issue on Ubuntu 20.04. Currently, every time that I
reboot I'm unable to login. I just get a black screen after logging in.
I have noticed that if I first delete the contents of .config
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: meep (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/1926553
Title:
@sylvestre This is a one-line fix that all my interns at MousePaw Media
(where we use Arcanist daily) perform manually after installing. With
Phacility winding down — don't worry, a community fork *is* spinning up
— this is not likely to be fixed upstream of here. I think it'd be worth
doing the
1 - 100 of 431 matches
Mail list logo
