here is intel public issue tracking.
https://github.com/intel/linux-intel-lts/issues/7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918253
Title:
WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't
Public bug reported:
There is no driver for it [8086:7360] when using 5.10 kernel.
$ lspci -nnv -s 55:00.0
55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced
Modem [8086:7360] (rev 01)
Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem
[103c:8337]
hello. Any progress in fixing it? sorry for not replying for so long but
life got hectic on me and I didn't had possibility to access Internet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/489951
** Changed in: tpm2-abrmd (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903539
Title:
/usr/sbin/tpm2-abrmd is linked to non-existing
But we're getting pretty close to the bleeding edge of mutter master
with all this. I strongly suggest we drop the input thread patches
instead of adding more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
But we're getting pretty close to the bleeding edge of mutter master
with all this. I strongly suggest we drop the input thread patches
instead adding more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The failure to raise windows on click sounds like
https://gitlab.gnome.org/GNOME/mutter/-/issues/1660 which is fixed
upstream in 4d54c3c556d753c0b981406937948895141dc1d4. But I doubt that's
the only fix we need.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1660
Public bug reported:
There is no driver for it [03f0:0a6c].
using 5.10 kernel.
$ sudo lspci -nnnv -s 55:00.0
55:00.0 Wireless controller [0d40]: Device [03f0:0a6c]
Subsystem: Hewlett-Packard Company Device [103c:877f]
Flags: fast devsel
Memory at 6e30 (64-bit,
** Description changed:
- When logged into an iSCSI node (isciadm -m -node -l) my laptop won't
+ When logged into an iSCSI node (iscsiadm -m -node -l) my laptop won't
suspend to ram anymore.
"dmesg -T" after such a failed suspend gives
[Mo Nov 4 13:22:54 2019] Suspending console(s)
same here. As the testsuite doesn’t catch this, it clearly means each
shell and mutter updates should be tested both on Xorg and Wayland.
Nvidia user here, so Wayland isn’t an option
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ever since the update to 78.7.1 (64-bit) Thunderbird attempts at showing
icons next to the folders in the folder pane. Hidpi settings cause the
font to scale, but the icons don't scale (at the same level? at all?).
This entirely breaks the rendering of the folder pane on high
Public bug reported:
I'm using lenovo ideapad s340, I installed ubuntu along side with
windows 10 in dual boot, but the problem is my touchpad is not working
at all and i see some glitches on my screen while scrolling. Please
resolve these issues
ProblemType: Bug
DistroRelease: Ubuntu 20.04
@Morgan, please file a new bug so that you can upload apport logs for
your own device for further investigation. And actually I didnot find a
network interface on your PCI bus, maybe you have turned it off in BIOS.
Besides, https://www.dell.com/en-us/shop/dell-laptops/new-
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879633
Title:
Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
To manage
*** This bug is a duplicate of bug 1916950 ***
https://bugs.launchpad.net/bugs/1916950
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1916950, so it is being marked as such. Please
The log in comment #3 kind of looks like the screen was working. Are you
sure that was during the black screen? Regardless, please try following
the steps in comment #2 again. Please also try installing the official
Nvidia driver using the 'Additional Drivers' app.
** Changed in: plymouth
I tried to reproduce this in an up-to-date bionic VM as follows:
# inside the bionic VM
sudo snap install lxd
sudo lxd init # accept defauls
sudo lxc launch ubuntu-daily:hirsute hirsute
sudo lxc exec hirsute /bin/bash
# then inside the hirsute container install livecd-rootfs
apt update
apt
** Changed in: plymouth (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908778
Title:
black screen after grub menu
To manage notifications about this bug go
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
https://discourse.ubuntu.com/t/trying-wayland-by-default-
again/20575/68?u=vanvugt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
Yep, I'd say it's that bug. It's fine under Wayland.
In 21.04 will it be possible to select a Wayland session from the login
screen without commenting out the gdm rule that disables Wayland if the
nvidia
*** This bug is a duplicate of bug 977848 ***
https://bugs.launchpad.net/bugs/977848
** This bug has been marked a duplicate of bug 977848
drracket fails to launch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
[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/1900401
[Expired for plymouth (Ubuntu) because there has been no activity for 60
days.]
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (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/1910542
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You
Public bug reported:
[Impact]
NVidia DP/HDMI aduio disappears after S3.
This is a regression introduced by LP: #1867704.
[Fix]
Update ELD properly so jack status is correctly reported.
[Test]
Perform S3 and open Sound Settings. With the fix applied, the DP/HDMI
audio is always present after S3.
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 1918226
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Approximately two weeks ago after leaving the computer alone the display
turned off like normal but did not come back.The system is working in
the background but the display wont show. I've gotten it to work
sometimes by pulling out the display port cable out and putting it
Actually, it *may* work under Xwayland. I'm not sure. Either way, the
answer is to configure Chrome to use PipeWire. PipeWire is the official
means of screen recording/casting because Wayland by itself does not
allow apps to spy on each other, by design.
If you are having trouble getting PipeWire
. This is not a
regression.
Found a previously reported (expired) bug with the same error:
https://launchpad.net/bugs/1549425
[ 6606.751232] audit: backlog limit Creating nova instance
adt-groovy-arm64-linux-20210308-143145 from image
adt/ubuntu-groovy-arm64-server-20210308.img (UUID
1cfb02a6-bf88-46bb-a8f1
highly doubt this issue will be ever fixed it has been here for 10 over
years
for once it affected multiple Linux users and no idea why people keep
arguing about using the shift button...
https://bugs.freedesktop.org/show_bug.cgi?id=27903
https://gitlab.freedesktop.org/xorg/xserver/-/issues/312
It appears this is a regression, started happening in 3.38.3-3ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918033
Title:
gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
Also tracking in
https://errors.ubuntu.com/problem/ea2e3b8ad662552e9123a94650b2045f3ea15d8c
** Description changed:
- https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8
+ https://errors.ubuntu.com/problem/a9be8b5a5c0f1dc4f3be3c46a7ab42360c7a48c8
+
*** This bug is a duplicate of bug 1918033 ***
https://bugs.launchpad.net/bugs/1918033
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1918033, so it is being marked as such. Please
*** This bug is a duplicate of bug 1918033 ***
https://bugs.launchpad.net/bugs/1918033
** This bug has been marked a duplicate of bug 1918033
gnome-shell crashed with
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed:
*** This bug is a duplicate of bug 1918033 ***
https://bugs.launchpad.net/bugs/1918033
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.38.3-3ubuntu1, the problem page
If the problem does still happen then please run:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and reboot again. If the problem continues to happen after that then
please run:
gsettings get org.gnome.shell enabled-extensions > ext.txt
and attach the resulting text file here.
--
You
Thanks for the bug report. Please try uninstalling/disabling all
extensions you might have added via the 'Extensions' app. Then reboot
and tell us if the problem still happens.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: amdgpu
** Changed in: mutter (Ubuntu)
Yes, unfortunately you will need to do it every time until it happens :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918055
Title:
blurry resolution after resume on second screen
To manage
** Summary changed:
- [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
+ [ASUS X441SA] No sound at all
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: focal
** Summary changed:
- [ASUS X441SA] No sound at all
+ [ASUS X441SA] [8086:2284]
It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs,
*** This bug is a duplicate of bug 1651500 ***
https://bugs.launchpad.net/bugs/1651500
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1651500, so it is being marked as such. Please
** Summary changed:
- no sound when upgrading to Kubuntu-20.04
+ [8086:27d8] No sound when upgrading to Kubuntu-20.04
** Package changed: ubiquity (Ubuntu) => pulseaudio (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
*** This bug is a duplicate of bug 1875259 ***
https://bugs.launchpad.net/bugs/1875259
** Summary changed:
- Bluetooth sound card not detected
+ [Sony VGN-TZ150N] Bluetooth sound card not detected
** This bug has been marked a duplicate of bug 1875259
[8086:27d8] No sound when upgrading
Judging by bug 1918190, this upstream fix should help:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status:
*** This bug is a duplicate of bug 1918033 ***
https://bugs.launchpad.net/bugs/1918033
** Tags added: fixed-in-40 fixed-upstream
** Changed in: mutter (Ubuntu)
Status: Triaged => Fix Committed
** This bug has been marked a duplicate of bug 1918033
gnome-shell crashed with
Also, this crash has stopped happening for me in 0.3.22-2. So that
version is still multiply beneficial to keep.
I've reopened
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/809 to track
this crash again.
** Changed in: pipewire
Remote watch:
Hmm yes, there are still reports of the crash in 0.3.22-2. But 0.3.22-2
has fixed screen recording and remote desktop :)
** Changed in: pipewire (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: pipewire (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed
Should be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu)
Status: New => Triaged
--
You received
Also seen on focal (from the log in bug 1917969).
** Also affects: mutter (Ubuntu Hirsute)
Importance: Undecided
Status: Fix Released
** Tags removed: eoan
** Tags added: focal
** Tags added: rls-ff-incoming
** Changed in: mutter (Ubuntu Hirsute)
Importance: Undecided => High
--
Upstream are not totally sure that fix also addresses this crash so
reopened for now.
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** No longer affects: linux (Ubuntu)
** No longer affects: xorg-server
Also, this is probably not a bug in any Ubuntu packages so I expect it
will be marked as Invalid unless we can find a reason otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918189
Title:
This will never work under Xwayland but it should work using native
Wayland. But Chrome will choose not to use native Wayland by default
(yet). Please try:
google-chrome --enable-features=UseOzonePlatform --ozone-
platform=wayland
and
chrome://flags/#enable-webrtc-pipewire-capturer
If that
Public bug reported:
Release:20.10
Duplicate (but root cause) of #1903539.
Debian had to rebuild the package due to libtss2-esys0 being bumped.
Package is presently broken and needs sync from Debian due to relinking.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972118
** Affects:
I opened
https://bugs.launchpad.net/ubuntu/+source/tpm2-abrmd/+bug/1918221 to
request sync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903539
Title:
/usr/sbin/tpm2-abrmd is linked to
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
>From what I've seen, this is just one of the symptoms of bug 1917926.
** This bug has been marked a duplicate of bug 1917926
Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
--
You received
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926
** Description changed:
- After a recent update in 21.04, I can no longer move windows by clicking
+ After a recent update in 21.04, I can no longer move windows with
+ integrated title bars (eg nautilus,
This bug was fixed in the package neutron -
2:17.1.0+git2021012815.0fb63f7297-0ubuntu4
---
neutron (2:17.1.0+git2021012815.0fb63f7297-0ubuntu4) hirsute; urgency=medium
* d/p/revert-dvr-remove-control-plane-arp-updates.patch: Cherry-picked
from
Public bug reported:
After a recent update in 21.04, I can no longer move windows by clicking
on the taskbar and dragging. I can't resize them either - although the
mouse icon changes, when I click and move the mouse the window doesn't
resize.
I can move a window holding the Super key and
This bug also affected Debian. They rebuilt the package.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972118
** Bug watch added: Debian Bug tracker #972118
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972118
** Also affects: tpm2-abrmd (Debian) via
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tpm2-abrmd (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/1903539
Title:
In version 78.7.1 the behavior is better: still not working, but it raises an
error instead of copying an unusable link.
The error is also ok: "drag and drop not supported".
Definitely better!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/apache2/+git/apache2/+merge/399177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918209
Title:
Detection of systemd
** Description changed:
- apache2ctl detects if systemd is in use by looking at the owner of
/proc/1/exe.
- Under docker, however, this cannot be relied on and may simply be the command
being run:
+ apache2ctl detects if systemd is in use by looking at the owner of
+ /proc/1/exe.
- $
Sorry. As I said, I'm unable to find out which package is causing the
problem. Perhaps someone can help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918177
Title:
Console messages shown on power
Public bug reported:
apache2ctl detects if systemd is in use by looking at the owner of
/proc/1/exe.
Under docker, however, this cannot be relied on and may simply be the
command being run:
$ docker run --rm --name "apache2-test" 26ff08910bcd ls -l /proc/1/exe
lrwxrwxrwx 1 root root 0 Feb
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
AFAICT, there's no need for new images here - we just need to enable TPM
support in our existing builds. I have this queued:
https://salsa.debian.org/qemu-team/edk2/-/commit/3491bed29b4d9fd20b596987fbfa33a256185d02
The existing ARM images already have Secure Boot support. As for the 4MB
Public bug reported:
I checked for broken packages and updated everything through apt.
When running sudo do-release-upgrade, it hangs after the second "Reading
state information... done" after fetching packages, and then gives me
Aborting
Reading package lists... Done
Building dependency
@vicamo - I wasn't sure if it was a bug or not, so posted at
https://answers.launchpad.net/ubuntu/+question/695930
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904249
Title:
nvidia: module
Hi @vicamo, I virtually tried every method in this thread, notably methods 2
and 3 exposed in the summary, and also virtually every other method I could
find on the web, including those ones:
-
@vicamo - Okay thanks, will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904249
Title:
nvidia: module license 'NVIDIA' taints kernel
To manage notifications about this bug go to:
Will this ever get fixed? I need wifi for phone calls sometimes. I get
all the settings juuust right, then bam! Airplane mode. Just for no
reason. I have set it to not save power, ever, for any reason, done the
tweaks. But my settings go back to default after a restart. For some
this not a
> Do you plan releasing this version on PPA
that was for the hirsute release - are you able to test that
(development) release to ensure the problem is fixed? it's the same
patches as for focal, so it may not be fixed there.
Alternately if you have a test environment (NOT some system that you
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
** Tags removed: verification-needed
** Also affects: dkms (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982315
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
I think that more extensive tests should be added in the next cycle, but
for now I think at minimum basic functionality should be checked, for
example just a simple autopkgtest like:
$ sudo needrestart -q -r l
(check for nothing currently needing restart)
$ LIBC=$(realpath
** Changed in: linux (Ubuntu Xenial)
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/1918182
Title:
Xenial update: v4.4.259 upstream stable release
To
** Changed in: linux (Ubuntu Focal)
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/1918158
Title:
Focal update: v5.4.98 upstream stable release
To manage
** Changed in: linux (Ubuntu Focal)
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/1918167
Title:
Focal update: v5.4.99 upstream stable release
To manage
** Changed in: linux (Ubuntu Focal)
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/1918168
Title:
Focal update: v5.4.100 upstream stable release
To
** Changed in: linux (Ubuntu Focal)
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/1918170
Title:
Focal update: v5.4.101 upstream stable release
To
** Changed in: linux (Ubuntu Xenial)
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/1918184
Title:
Xenial update: v4.4.260 upstream stable release
To
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839065
Title:
power8 machines need FW update or qemu/libvirt code - cap-cfpc=broken
To manage notifications about
Corey - they are, and I've been working on them here and there to get
them into shape. The Train version might slightly differ in the
functional tests that are being added, but the actual code change is the
same.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: golang-1.14 (Ubuntu Hirsute)
Importance: High => Low
** Changed in: golang-1.15 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914372
otherwise cross-compile bootstrap is an option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915722
Title:
rustc 1.50 and cargo 0.51 will be required by a future version of
firefox
To manage
you can republish last working on in a ppa, and then have strict build-
depends on version guarded one in the next ppa (with build-dep on the
first ppa) to rebuild fixed one with last fixed toolchain. if there
is one.
--
You received this bug notification because you are a member of Ubuntu
1 - 100 of 464 matches
Mail list logo
