Attached is an SRU for focal.
** Patch added: "lp1901043_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901043/+attachment/5457510/+files/lp1901043_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Precise debdiff.
** Patch added: "2021a-precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+attachment/5457509/+files/2021a-precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Trusty debdiff.
** Patch added: "trusty-2021a.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+attachment/5457507/+files/trusty-2021a.debdiff
** Changed in: tzdata (Ubuntu Xenial)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: tzdata (Ubuntu
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
Looking to identify when the following selinux kernel patch was added to
the focal Ubuntu branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git/commit/?id=464c258aa45b09f16aa0f05
I went through the code with @hypothetical-lemon and the patches do
appear to fix the issue; with the previous code they were adding new
messages into a deque without any throttling, but now they are using a
different queue class that, while it still uses deques internally,
returns a future object
** Description changed:
+ [Impact]
+
+ * Since Xenial has released, setuptools and pip have dropped support for
+Python 3.5 (and 2.7), upstream.
+ * Virtualenv installs the latest upstream pip and setuptools during
+virtualenv creation, from the Internet.
+ * Python packages gained a
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Groovy)
Im
the newer upstream changes you linked is bigger, for security update only small
build fix of first patch absolutely necessary I suppose ubuntu security team
would consider (along with the third patch with security fix).
however it would be good to have a certain answer before continuing to invest
Hello Dimitri, or anyone else affected,
Accepted u-boot-menu into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/u-boot-
menu/4.0.1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
[Impact]
* With update-manager versions 1:20.04.10.3 or 1:20.10.2, update-manager would
crash
while processing the apt cache.
[Test Case]
* Look at the Error Tracker issues and make sure the versions 1:20.04.11 and
1:20.10.3 do not
cause this same error.
[Where problems could occur]
Public bug reported:
Could not determine the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log
Note to self during testing: Pay attention to libcaribou-gtk-module,
dpkg-shlibdeps warning:
dh_shlibdeps -- -xlibgtk2.0-0
dpkg-shlibdeps: warning:
debian/libcaribou-gtk-module/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcaribou-gtk-module.so
contains an unresolvable reference to symbol g_module
** Description changed:
New upstream version affecting the following timestamp:
+
+ - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Changed in: caribou (Ubuntu Hirsute)
Assignee: (unassigned) => Fantu (fantonifabio)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912060
Title:
[SRU] caribou: Segfault (as regression of xor
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
when opening both apps its always a big complication with a lot a
latency and distortion
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
ApportVer
keep this MIR alive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887187
Title:
[MIR] nftables
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nftables/+bug
Fantu: The upstream patch fixes have been put in upstream and a few vala
version changes were made.. I suggest checking
https://gitlab.gnome.org/GNOME/caribou/-/commit/11da0e0b21867921ba2f6d2af45af16a7db1ab92
and seeing if the debian patch is the same, ensure the patch is the same
and includes this
I can reproduce on a 2008 iMac and a 2011 Mac Mini. I can also confirm
that Rowan's steps in comment #23 work to fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867092
Title:
Failed
** Changed in: samba (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750
Title:
samba-tool domain provision crash with "password hash userPassword
schemes"
Maybe a better illustration, see attachment gtk-FE-deb-snap.png
** Attachment added: "gtk-FE-deb-snap.png"
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1913336/+attachment/5457484/+files/gtk-FE-deb-snap.png
--
You received this bug notification because you are a member o
Public bug reported:
I recently installed a new SSD (860 Evo) on legacy MBR Bios machine
(Gigabyte ga-ma770-ds3 v.01) with F6 Bios version. Debian can't find
this SSD, Ubuntu can, but only installs 'well' with ZFS. Other FS and/or
partitioning options result in freeze after reboot following fresh
Hi MAYRE Inkscape launchpad is now in read mode.
Please test with current version (1.0.2) and report bugs here
https://inkscape.org/report
Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14910
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
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
*** This bug is a duplicate of bug 1913482 ***
https://bugs.launchpad.net/bugs/1913482
** This bug has been marked a duplicate of bug 1913482
Update tzdata to version 2021a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
New upstream version affecting the following timestamp:
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/us
PPA test on Focal is good on 19.11.6-0ubuntu0.20.04.1~ppa2
1.0.0 (14:15:38): phys (BM) tests
1.1.0 (14:15:38): initialize environment
1.1.1 (14:17:07): testpmd => Pass
1.1.2 (14:18:35): check testpmd output => Pass
2.0.0 (14:18:35): prep virtual test environment
1.0.0 (14:21:11): virt
Thank you for your reply.
OK, that confirms my suspicion that the upstream bug referenced in the
original description does not (entirely) relate to this issue.
I was able to confirm a few things:
- This bug is reproducible in hirsute as well, which means that the
latest version of samba in our r
Attached is a patch to SRU groovy.
** Patch added: "lp1913476_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+attachment/5457474/+files/lp1913476_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Attached is a patch to SRU focal.
** Patch added: "lp1913476_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+attachment/5457473/+files/lp1913476_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
*** This bug is a duplicate of bug 1913482 ***
https://bugs.launchpad.net/bugs/1913482
Public bug reported:
New upstream version affecting the following timestamp:
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets changed in the
updated package i
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: In Progress => 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/1724872
Title:
nvidia-graphics-drivers-340 340.102-0ubunt
Build in PPA complete, testing ...
$ ll /var/run/qemu/
ls: cannot access '/var/run/qemu/': No such file or directory
$ sudo apt install --reinstall qemu-block-extra
$ ls -laFd /var/run/qemu; ls -laF /var/run/qemu; ls -laF /var/run/qemu/*
drwxr-xr-x 3 root root 60 Jan 27 20:02 /var/run/qemu/
total
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
In "Settings>Sound>Output"
If set my "Output Device" to "HDMI / DisplayPort 5" and set
"Configuration" to "Digital Surround 5.1" If I close the receiver and
open it again... The configuration will reset to "Digital stereo"
The expected behavior would be to keep the "Digital
Validated for Groovy according to test case from description:
root@groovy-vm:~# dpkg -l | grep dirmngr
ii dirmngr2.2.20-1ubuntu1.1 amd64
GNU privacy guard - network certificate management service
root@groovy-vm:~# apt-key adv --fetch-keys
https://
Validated for Focal according to test case from description:
root@focal-vm:~# dpkg -l | grep dirmngr
ii dirmngr2.2.19-3ubuntu2.1 amd64
GNU privacy guard - network certificate management service
root@focal-vm:~# apt-key adv --fetch-keys
https://w
Attached is a patch to SRU groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913476
Title:
/usr/bin/update-manager:TypeError:/usr/bin/update-
manager@118:start_update:start_available:refresh
** Branch linked: lp:update-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913476
Title:
/usr/bin/update-manager:TypeError:/usr/bin/update-
manager@118:start_update:start_available:refres
Michael, thanks for reporting this. This shouldn't have been missed in
the initial patch. I've confirmed that if the config option isn't set at
deploy time, openvswitch-switch doesn't get restarted by the charm after
rendering /etc/default/openvswitch-switch. The charm needs an update to
restart th
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
** Also affects: update-manager (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: update-manager (Ubuntu Focal)
Importance: U
** Branch linked: lp:~jawn-smith/update-manager/apt-pkg-typeerrror
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913476
Title:
/usr/bin/update-manager:TypeError:/usr/bin/update-
manager@118:star
vmware-gos-Yuhua (yhzou) and cloud users:
The latest Xenial daily build has the required changes, serial 20210127
http://cloud-images.ubuntu.com/xenial/20210127/
The vmdk and ova were both validated in the following way:
1) downloaded vmdka and ova from http://cloud-images.ubuntu.com/xenial
Traceback (most recent call last):
File "/usr/bin/update-manager", line 118, in
app.start_update()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
220, in start_update
self.start_available()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-manager. This problem was most recently seen with package version
1:20.04.10.3, the problem page at
https://errors.ubuntu.com/problem/b4e18d21aa7526e3a98130b1556e4d38ffaff9e0
contains mor
Just saw this in bionic, I guess it's not important enough for an SRU?
# apparmor_parser -r -T -W --Complain /etc/apparmor.d/pam_roles
/etc/apparmor.d/usr.sbin.sshd
Warning failed to create cache: pam_roles
Warning failed to create cache: usr.sbin.sshd
--
You received this bug notification beca
Adjusting affected package to qemu instead of kernel.
** Package changed: linux (Ubuntu) => qemu (Ubuntu)
** Also affects: qemu (Ubuntu Hirsute)
Importance: Undecided
Status: Incomplete
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: q
Thanks for the bug report and for following up on it. I tried creating
a Focal VM and installing unbound in it, and it succeeded. Since it is
not clear how to reproduce the issue, and no logs were provided, I am
marking this bug as Incomplete. If you happen to find more details
about the problem
Thanks for the bug report. I'm marking this bug as Triaged and
subscribing ubuntu-server to it. When the feature is accepted upstream
we can decide whether it makes sense to backport it or to wait for a new
upstream release of the package.
** Changed in: sosreport (Ubuntu)
Status: New =>
Sorry, I forgot to add X11 in the bug description. "qemu(5.2+dfsg-
3ubuntu1)+virgl on GTK/X11" is the bad case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912706
Title:
Ubuntu 21.04 QEMU virgl C
Thanks for the reply, Peter.
Yes, if you start rabbitmqctl directly via the command line then the
systemd unit will not be invoked, and process will use the default
limits specified by the system. If that is the way you invoked
rabbitmqctl, then what you can do is modify the limits before executi
--- Comment From boris_fiuczyn...@de.ibm.com 2021-01-27 13:50 EDT---
I have sent a patch to the upstream mailing list for review:
https://www.redhat.com/archives/libvir-list/2021-January/msg01149.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
if the ABI changes without changing the soname, we should rename the
library packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913268
Title:
ImageMagick: please pull in patch to stabilize API
if the ABI changes without changing the soname, we should rename the
library packages:
Package: clucene-core
Format: 3.0 (quilt)
Binary: libclucene-dev, libclucene-core1v5, libclucene-contribs1v5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Tags added: cdo-release-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906280
Title:
[SRU] Add support for disabling mlockall() calls in ovs-vswitchd
To manage notifications about this b
** Description changed:
command "qenu-system-x86_64 ...-accel kvm -device virtio-gpu,virgl=on
-display gtk,gl=on ... " failed with "qemu-system-x86_64:
../src/dispatch_common.c:863: epoxy_get_proc_address: Assertion `0 && "Couldn't
find current GLX or EGL context.\n"' failed."
- [1] 105637 ab
Thanks for the clarification, Heitor!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840043
Title:
bcache: Performance degradation when querying priority_stats
To manage notifications about this bu
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904024
Title:
package flash-kernel 3.98ubuntu12 failed to install/upgrade: installed
flash
The workaround suggests that there's an interaction between the NVIDIA
driver and another kernel module at play here. Presumably, adding the
NVIDIA kernel modules to the initrd causes them to be loaded before the
other module. Maybe video.ko, which registers its own brightness
handler?
The modeswi
We are still seeing this issue using the -next version of the ovn-
chassis charm, as seen during this test run for the charm release:
https://solutions.qa.canonical.com/testruns/testRun/23d8528d-2931-4be6-a0d1-bad21e3d75a5
Artifacts can be found here: https://oil-
jenkins.canonical.com/artifacts/2
This fix does not working and the bug still exists. There is a race condition
between the `ip route show` check and the `/bin/ip route add` command, and
systemd will launch multiple `ifup` concurrently.
Maybe the failure of `/etc/network/if-up.d/avahi-autoipd` should be ignored to
avoid causing
Hi Daniel,
Thanks for the response, attaching the file. The installation is pretty
new and has no additional GNOME extensions. Also submitted a new crash
report today:
https://errors.ubuntu.com/oops/ed647ea2-60cb-11eb-8e09-fa163e6cac46
By the way: found out today I can still access the system ex
Fix:
Add "Machine: Raspberry Pi ? Rev 1.0" after "Machine: Raspberry Pi 4
Model B Rev 1.4" to /usr/share/flash-kernel/db/all.db
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904024
Title:
package
** Description changed:
+ [Impact]
+
+ * Virtualenvs created on Ubuntu 20.04 are not as empty as they are
+expected to be. They are expected to contain pip and setuptools.
+But the way pip's vendored dependencies were de-vendored resulted
+in the libraries being exposed in the new vi
user@desktop:~$ apt-cache rdepends --installed linux-image-5.8.0-36-generic
linux-image-5.8.0-36-generic
Reverse Depends:
user@desktop:~$ apt-cache rdepends --installed
linux-modules-nvidia-460-generic-hwe-20.04
linux-modules-nvidia-460-generic-hwe-20.04
Reverse Depends:
linux-modules-nvidia-455
also
Linux hetman-Lenovo-V580c 5.4.0-64-generic #72-Ubuntu SMP Fri Jan 15
10:27:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Description:Ubuntu 20.04.1 LTS
Release:20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Patches for bionic and focal are in the queue now, they just need
reviewing by the SRU team.
It's kind of two-bugs-in-one, but I hope that's OK. I didn't want to ask
Fantu, a new contributor, to do a lot of work to split the bugs.
** Description changed:
+ [Impact]
+ There are some cases where n
*** This bug is a duplicate of bug 1861968 ***
https://bugs.launchpad.net/bugs/1861968
Let's use bug #1861968 for this
** This bug has been marked a duplicate of bug 1861968
Removal of a drive closes all windows and stops file transfers
--
You received this bug notification because you a
The security fix is the third patch, first is needed to fix build (or it
fails), the second is another fix, I don't have time now to done another
build without it and test if work correctly and usable also with the fix
of second patch as it is related to the part.
--
You received this bug notific
Liam, thanks for the patch. This has been uploaded to the groovy unapproved
queue where it is awaiting SRU team review.
https://launchpad.net/ubuntu/groovy/+queue?queue_state=1&queue_text=ovn-octavia-provider
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: nemo (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: nemo (Ubuntu Bionic)
Assignee: (unassigned) => Fantu (fantonifabio)
** Changed in: nemo (Ubuntu Focal)
Assignee: (unassigned) => Fantu (fantonifabio)
** Changed in: nemo (Ubuntu Bionic)
Problem persists with nvidia-driver-460 (460.39-0ubuntu0.18.04.1) on
Lenovo X1 Extreme. The comment #11 workaround still works for this
laptop model.
** Description changed:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX
1050 Ti Mobile]:
WORKS FINE:
nvidia-dr
Hi,
Bug confirmed here (Ubuntu 20.04, inkscape 0.92). Exactly same conditions.
Moslty with graphics issued from python's matplotlib or R's ggplot2.
It's really annoying and sad...
Any new's about a possible resolution of the bug ?
--
You received this bug notification because you are a member
First: How do we reproduce the error? That'd be the best way to dig
deeper.
Second: libffi doesn't build against cffi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912535
Title:
[SRU] python-cffi
1) # aa-enforce usr.sbin.sssd (default)
journal contains:
Jan 27 17:46:27 s2r5node66 sssd[3382]: ldb: unable to open modules directory
'/usr/lib/x86_64-linux-gnu/ldb/modules/ldb'
Jan 27 17:46:25 s2r5node66 systemd[1]: Starting System Security Services
Daemon...
Jan 27 17:46:25 s2r5node66 system
Public bug reported:
i am getting error while upgrade=ing ubuntu from 18.04 to 20,04 via
upgrade manager:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please u
Public bug reported:
Similar to LP: #1727202 and other packages (libvirtd, e.g.) it seems
like sssd also needs an `attach_disconnected` profile option.
Symptomatically, what we see is that when we boot a node that uses sssd
for authentication with the `overlayroot=tmpfs` option, sssd fails to
star
Public bug reported:
don't upgrade version
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-modules-4.4.0-201-generic 4.4.0-201.233
ProcVersionSignature: Ubuntu 4.4.0-197.229-generic 4.4.241
Uname: Linux 4.4.0-197-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.28
AptdaemonVersion: 1
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913469
Title:
package linux-modules-4.4.0-201-generic 4.4.0-201.233 failed to
install/upgrade: package linux-mo
Upon further investigation, it appears as though libffi was built on an
older version of cffi, which would probably explain this a little
further. Adding libffi to the bug.
** Summary changed:
- [SRU] python-cffi in Groovy needs a no-change rebuild
+ [SRU] python-cffi and libffi in Groovy need a
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: puppet 5.5.10-4ubuntu3
ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jan 27 17:11:14 2021
PackageArchi
*** This bug is a duplicate of bug 1875848 ***
https://bugs.launchpad.net/bugs/1875848
Public bug reported:
The puppet 5.5 version available in Focal throws a lot of ruby warnings,
which interferes with the puppet installation traces.
remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: war
Public bug reported:
[Impact]
* Improve u-boot-menu UX in focal
[Test Case]
* Boot riscv64 image built with new u-boot-menu
* Observe that menu entry says "Ubuntu", instead of "Debian".
* When booting, observe that riscv64 instance is booting with
"earlycon" in the kernel commandline, wit
> retry the test
That has been done. Now the only red is netplan.io.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907433
Title:
[SRU] New stable release 2.64.6
To manage notifications about this
Public bug reported:
remote: ^[[1;31mError: Execution of '/usr/bin/gem install --no-rdoc --no-ri
uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption)
remote: invalid option: --no-rdoc
remote: Did you mean? no-force^[[0m
remote: ^[[1;31mError: /Stage[main]/Mys_serv
Then how do you explain the error?
SystemError: ffi_prep_closure(): bad user_data (it seems that the
version of the libffi library seen at runtime is different from the
'ffi.h' file seen at compile-time)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Merge proposal linked:
https://code.launchpad.net/~dgadomski/ubuntu/+source/ceph/+git/ceph/+merge/397034
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908375
Title:
ceph-volume lvm list cal
Here are the steps I used to reproduce the bug:
1. install Linux Mint 20.1 MATE
2. install package knockd
3. in /etc/knockd.conf, add Interface = eno1 (or your network interface)
4. in /etc/default/knockd, set START_KNOCKD=1
5. run "sudo systemctl enable knockd"
6. restart
7. after restarting, kno
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (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/1901125
Title:
pack
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913463
Title:
package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to
install/upgrade: installed grub-
Public bug reported:
Description:Ubuntu 20.10
Release:20.10
grub-efi:
Installed: (none)
Candidate: 2.04-1ubuntu35.2
Version table:
2.04-1ubuntu35.2 500
500 http://us.archive.ubuntu.com/ubuntu groovy-updates/main amd64
Packages
2.04-1ubuntu35 500
500 ht
Isn't more pragmatic before considering changes introduced with kernel
5.9, a backport to Focal be commited/released in advance (the kernel
there is 5.8)? 🧐😉 There is a proposal presented in Bug #1910555 comment
21! 🤔 This Bug is related to kernel 5.6. New package changes (new patch)
related to rec
Attached is a patch for hirsute. For hirsute we will begin using quilt
patches for changes.
** Patch removed: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457125/+files/lp1891952_hirsute.debdiff
** Patch added: "lp1891952_hi
** Tags added: fr-1088
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913388
Title:
clucene-core: please pull in patch to stabilize API on s390x during
upgrade to glibc 2.33
To manage notificatio
krb5 has now migrated with the fix to openldap.
** Changed in: krb5 (Ubuntu)
Status: Triaged => 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/1913179
Title:
krb5 fails dep8 in H
** Changed in: linux-oem-5.10 (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/1913372
Title:
Fix the video can't output through WD19TB connec
Focal verification done.
Groovy verification done (with manually modified config.txt as u-boot is
no longer used by default on groovy); booted successfully on all models
including CM4.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug not
101 - 200 of 389 matches
Mail list logo
