** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification be
This bug was fixed in the package gnome-control-center - 1:40.0-1ubuntu2
---
gnome-control-center (1:40.0-1ubuntu2) impish; urgency=medium
* debian/ubuntu-logo-icon.png,
debian/gnome-control-center-data.install,
d/p/d/info-overview-Use-the-Vendor-logo-prominently.patch:
Confirmed fixed on lxd02 and client site, running Focal. No reboot was
done.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates /run/systemd/resolv
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Bionic)
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/1891215
Titl
I notice there is a traceback about mlx5, however, while I check vmcore,
the STACK_END_MAGIC haven't been overridden (I mean $rd 'stack_address'
print 0x57AC6E9D) how can?
//kernel/sched/core.c
static inline void schedule_debug(struct task_struct *prev)
{
#ifdef CONFIG_SCHED_STACK_END_CHECK
I think the patch in comment #1 looks reasonable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928989
Title:
expiring trust anchor compatibility issue
To manage notifications about this bug go to
4.15.0-1120.133~14.04.1 T-azure
** Tags added: sru-20210621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895276
Title:
shmctl04 from ubuntu_ltp_syscalls failed with X-aws + T-azure / 4.15
To man
Speaking of the -server drivers, I'm not sure why they're not listed by
ubuntu-drivers for my hardware, which is an RTX 3060 Ti LHR:
nbryant@alphasite:~/git/webapp$ ubuntu-drivers list
nvidia-driver-460, (kernel modules provided by
linux-modules-nvidia-460-generic-hwe-20.04)
nvidia-driver-465, (k
> that was the atime
yep, really no way around updating the atime, as systemd of course needs
to access the file to check if the content is the same or not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Hi William,
Thanks for the followup. What I'm referring to is the new patch that is
being added under debian/patches/, and that it is a common practice to
explicitly mention which files have been added/removed/changed in the
debian/changelog. So, in this case, a (suggested) changelog entry could
A user still might have written a script or a service which calls
/usr/lib/libmbim/mbim-proxy and by moving the binary we would end up
introducing a regression and that's a scenario we should consider.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I've found that other people with RX 5600 XT had problems with this
version of mesa.
https://bugs.archlinux.org/task/70554
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4691
There is a new release of mesa (21.0.3-2) that fixes the problem for
those users.
Hope that you upload it to focal-pr
ADT results at https://bileto.ubuntu.com/excuses/4594/xenial.html
** Description changed:
[Impact]
* openssl fails to talk to letsencrypt website past September 2021,
despite trusting the letsencrypt root certificate.
[Test Plan]
* Import staging cert equivalent to ISRG Root
PPA with these changes available from https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/4594
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928989
Title:
expiring trust anchor compatibili
python3.5 has stopped passing its testsuite due to expried test certs.
Thus upload of openssl has triggered regression in python3.5
I've cherrypicked updated test certs and keys, but to cherry-pick those
cleanly, I also had to cherrypick an earlier bug fix. All of these are
unmodified from 3.5.10
> So I'm going to reassign the bug to that package as it seems likely to
me that this is where the problem lies.
Actually I'm not sure it's a symbol versioning issue now. Looking at
your error, perhaps it's a protocol negotiation issue in rsync? Either
way, it needs further investigation by a volu
** Description changed:
In order to boot Ubuntu 20.04 on the Unmatched, the version of u-boot
currently in hirsute will need to be SRU'd to focal.
Raspberry pi core and classic images will need to be tested with this
new version of u-boot as well to ensure nothing was broken by the SRU.
Verification for Groovy (246.6-1ubuntu1.5)
# Initial repro on groovy:
root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf
/etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823
1625844823 0 4096
root@groovy:~# i
Sorry, the use cases you describe are not supported by Ubuntu.
You're welcome to hack your system as you wish, but that doesn't mean
that we will necessarily make changes in Ubuntu to accommodate that. We
do try to be helpful, of course. And in this case I agree that it is a
bug that rsync doesn't
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.5) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus/2.20.0+ds-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceedin
Verification for Focal (245.4-4ubuntu3.8)
# Initial repro on focal:
root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf
/etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273
1625844273 0 4096
root@focal:~# ip lin
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You rec
Fixed by that commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934505
Title:
gdb 11 doesn't work on impish/s390x: internal-error:
displaced_step_prepare_status linux_displaced_step_prepare(g
The gdb-11-branch branch has been updated by Simon Marchi
:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=ff32938d4471ebf6dce462934de8ab47f9fd5d66
commit ff32938d4471ebf6dce462934de8ab47f9fd5d66
Author: Simon Marchi
Date: Thu Jul 8 10:05:16 2021 -0400
gdb: don't set Linux-sp
The master branch has been updated by Simon Marchi
:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=74b10a3219e44ba2585e3f7226a6455d41e92c1b
commit 74b10a3219e44ba2585e3f7226a6455d41e92c1b
Author: Simon Marchi
Date: Wed Jul 7 08:57:36 2021 -0400
gdb: don't set Linux-specific
@ddstreet, unfortunately, even with 245.4-4ubuntu3.8 on Focal, the mtime
keeps changing as RAs are received :/
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** 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/1935690
Title:
Lock Screen Failure - Desktop Contents Momentarily Visible
To manag
= Verification =
Before:
14: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8:f1:ae:10 brd ff:ff:ff:ff:ff:ff
altname `�lժ�
altname ��lժ�
After:
15: enp1s0f0np0v0: mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 92:aa:d8
** Tags added: sru-20210621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931325
Title:
cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
To manage notifications about this bug go t
** Description changed:
+ [Impact]
+
+ This bug caused aptdaemon to miss two configuration options that ubuntu-
+ advantage-tools relies on for updating its messaging based on apt state.
+ Apt itself parsed the options despite the syntax mistake, which led to a
+ difference in understanding betwe
What package / application were you reporting a bug about? IIRC most
apport hooks won't ask for dmesg information.
If you remove the crash files in /var/crash/ and lock your screen do you
get another jackd crash in there? It could be that the crash reporting
process for jackd actually is asking fo
Sergio,
The only new file added is a patch, is that what you're referring to?
This attached patch states which source file is modified by the upstream
cherry pick, hopefully that's what you need!
** Patch added: "lp1933678.debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-a
Thank you!
Le ven. 9 juil. 2021 à 3:05, Faustin <1930...@bugs.launchpad.net> a
écrit :
> Hi Carlos!
> Thank you for your report and your help in making Ubuntu better.
>
> Unfortunately, I can not work on your issue because you do not provide
> sufficient information. From the logs, I can only won
** Patch added: "xtables-addons_3.9-1ubuntu0.2~20.04.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1932173/+attachment/5510066/+files/xtables-addons_3.9-1ubuntu0.2~20.04.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
The log shows that you are running non-Ubuntu mlx5 modules, and the
traceback is in those modules. Marking Invalid - you'll need to reach
out to your mlx5 driver provider for support.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kunpeng920
Stat
Hi ,
i do not see the anything after i run pa-info > pa-info.txt command. I did
not understand what to do with your command.
On Thu, Jul 8, 2021 at 11:50 PM Hui Wang <1935...@bugs.launchpad.net>
wrote:
> Please plug the mic in, and run pa-info > pa-info.txt, then upload the
> pa-info.txt
>
> --
Here is the file:
pa-info > pa-info.txt
On Fri, Jul 9, 2021 at 10:18 AM Rabi Sah wrote:
> Hi ,
>
> i do not see the anything after i run pa-info > pa-info.txt command. I did
> not understand what to do with your command.
>
> On Thu, Jul 8, 2021 at 11:50 PM Hui Wang <1935...@bugs.launchpad.net>
Public bug reported:
Merging multiple djvu files should not be a lossy operation, apart from
metadata that only has 1 slot (e.g. author, title, etc). The bookmarks
(aka outline) is lost, not merged:
$ djvused -e 'print-outline' file-a.djvu
(bookmarks
("foo"
"#1" ) )
$ djvused -e 'print-outl
root@test-g1:~# uname -a
Linux test-g1 5.8.0-61-generic #68-Ubuntu SMP Tue Jun 29 15:15:10 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
root@test-g1:~# grep -e ' ref_module' -e ' find_symbol' -e '
each_symbol_section$' -e ' __module_address' -e ' __module_text_address'
/proc/kallsyms
8b75080
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.8) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf)
gvfs/1.44.1-1ubuntu1 (amd64)
linux-oem-5.6/5.6.0-1057.61 (amd64)
munin/2.0.56
Hi Robert!
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately, we cannot work on this bug because your description
didn't include enough information.
At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the
Hi Carlos!
Thank you for your report and your help in making Ubuntu better.
Unfortunately, I can not work on your issue because you do not provide
sufficient information. From the logs, I can only wonder if you did not
install MySQL before MariaDB, in that case remember that they can not
coexist o
As said by Harald Hannelius, this is not related to MariaDB, we do not
provide an apparmor profile (it's commented).
Closing.
** Changed in: mariadb-10.3 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Test results of nvidia-driver-460 are available at
https://docs.google.com/spreadsheets/d/1OvcC1jFqSrm3fWTDh7HXIxy1uVdrRxfIyrMU8hYp5A4/edit#gid=312612113.
Test results of nvidia-driver-465 are available at
https://docs.google.com/spreadsheets/d/1JCQCO92T_6WOVV3KfpRQjDFsWytVhbscny50bhrld8o/edit#gi
As said in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988255 the
fix will be provided in next Debian 10.10 update point.
@otto, I have no idea when this will hit Ubuntu though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
hello,
My ubuntu crashing periodically.
I have tried 18.04, 18.10 and 21.04.
Gnome is crashing and must be restarted using reset button on my case.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-
** Changed in: musescore3 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933782
Title:
Needs updating
To manage notifications about this bug go to:
htt
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
** Tags added: sru-20210621
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
Hi, I am glad that you could resolve your issue.
As said, on my side, there is nothing I can work on because the report
does not provide much information to reproduce the problem.
This bug report will autoclose in 60 days if no more information is
provided.
--
You received this bug notification
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
** Description changed:
SRU Justification:
[Impact]
* The following patches removed an exported symbol that will cause
potential disruption and breakage for customers
modules: inherit TAINT_PROPRIETARY_MODULE
modules: return licensing information from find_symbol
modules:
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3
The document at https://age-encryption.org/v1 says it’s an acronym that
should be pronounced with a hard G.
https://github.com/FiloSottile/age/discussions/239 is a similar
discussion; while the conflict with an existing English word isn’t
brought up, they point out the difficulty of finding the to
Public bug reported:
Issue found on node akis, with bionic/linux 4.15.0-150.155. This is not
a regression as the failure can be found on previous releases.
Error:
filter = vmx_init_signal_test, test = vmx_init_signal_test
Test suite: vmx_init_signal_test
FAIL: INIT signal blocked when CPU in VMX
[machine]
HP ProBook
[OS]
Focal
[systemd version]
245.4-4ubuntu3.8
[test result]
mic mute key works fine.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of U
Public bug reported:
The package/program `age` is listed as 'simple, modern and secure
encryption tool'. The name implies that it is time related, which is
confusing.
** Affects: age (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Tags added: sru-20210621
--
You received this bug notification
[machine]
HP ProBook
[OS]
Groovy
[systemd version]
246.6-1ubuntu1.5
[test result]
mic mute key works fine.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
[machine]
HP ProBook
[OS]
Hirsute
[systemd version]
247.3-3ubuntu3.2
[test result]
mic mute key works fine.
** 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
** Tags added: sru-20210621
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification
Is there a final root cause for all of this? I'm very interested in the
explanation or some link to the specific commits that solve the
issue(s).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927925
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New
How about this case:
- I make a hypothetical package that depends on libxxhash < 0.8 because
I want the "broken/old" xxh128 support;
- I have libxxhash 0.7.3 (that came with Focal);
- I have rsync 3.1.x (that came with Focal);
- Now I release-upgrade my system from Focal to Groovy;
- I get all
> Unfortunately the ppc maas seems down right now
product engineering has access to PPC systems in maas?!? sigh...that
sure would be nice for sustaining engineering to have access to also :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Thanks Robert, I saw that you uploaded to bionic and focal now, any
reason to not merge to impish? If technically the feature doesn't apply
to the current serie maybe we should just merge with a default setting
to false so we just need to turn the option on for the next LTS if
needed?
--
You rece
** 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/1930719
Title:
Replace AMD nvme workaround from oem-5.10 with upstream version
To manage notifications about this bug go to:
https
The attachment "0001-configure.c-add-RISC-V-architecture.patch" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launch
makeinfo is provided in universe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935679
Title:
crash: build failure on RISC-V
To manage notifications about this bug go to:
https://bugs.launchpad.ne
OK, let me close this bug first. If you have other issues, please file a
new bug.
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
Hello Walter,
Thanks for filling the bug and helping in making the Ubuntu server
better.
However, if I get everything right, I think you're mistaken about how it
works and I am sorry but what you're trying to do is not correct! You
cannot just decide to take one of the package from another releas
** Patch added: "0001-configure.c-add-RISC-V-architecture.patch"
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+attachment/5510055/+files/0001-configure.c-add-RISC-V-architecture.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
version: 7.3.0-1ubuntu1
Building crash for RISC-V fails with a segfault. This segfault is due to
missing support for architecture RISC-V in file configure.c. configure
is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch
is at
https://github.com/xypron/crash
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
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/1745155
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects: linux-oem-5.13 (Ubuntu I
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects: linux-oem-5.13 (Ubuntu I
Thanks for that
** Changed in: snapd (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/1935667
Title:
Please switch to fuse3
To manage notifications about thi
Please fix it asap.
We have the same issue. We have migrated our Nagios to Ubuntu 20.04. Now we
have flapping hosts, because of this issue!
Is there a timeline when you will able to fix it ?
Thanks
Silvan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects: linux-oem-5.13 (Ubuntu I
** Changed in: ocfs2-tools
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/1745155
Title:
o2image fails on s390x
To manage notifications about this bug go to:
https
** Changed in: ocfs2-tools
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/1840958
Title:
defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el
To manage n
verified 5.13.0-1007.7 from focal-proposed.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934660
Title:
intel_pmc_
Sure, debdiff and build log of the rebuild attached.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935667
Title:
Please switch to fuse3
To manage notifications about this bug go to:
https://bugs.l
101 - 200 of 251 matches
Mail list logo
