** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
+
I agree with Scott that putting them in /usr with overrides from /etc is
the best path forward.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849557
Title:
Please revise files in /etc/cloud tree
Maybe you all can already tell this from the crash report, but here's
what syslog says when this happens. As a previous poster noted, it
happens every time the system boots up, and it started immediately after
upgrading to Eoan (from Disco, in my case).
Oct 29 10:28:50 michael-XPS-13-9380
Managed to figure out why this was happening - I had the NUM_VFS in the
card firmware configured to 127 (the maximum value) - reducing this to a
lower number allowed me to successfully switch the cards into switchdev
mode at which point the ip tools all worked again.
The clue that pointed to this
*** This bug is a duplicate of bug 1850485 ***
https://bugs.launchpad.net/bugs/1850485
** This bug has been marked a duplicate of bug 1850485
bionic/linux-hwe-edge: -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was fix-released in ocata via nova 2:15.1.5-0ubuntu1~cloud1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809454
Title:
[SRU] nova rbd auth fallback uses cinder user with libvirt secret
To
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
@dwmw2,
I figured out the issue. Long story short, freeipa (which is our CA),
when we enroll a PC into the realm, it adds the freeIPA cert to
/etc/ssl/certs/ca-certificates.crt like it should, however it also adds
other information that it shouldn't.
This results in p11-kit-trust.so blowing
** Changed in: nautilus
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/1849987
Title:
empty space when on list view and when back to icon view
To manage
This was fix-released in ocata via nova 2:15.1.5-0ubuntu1~cloud1.
** Changed in: nova/ocata
Status: Fix Committed => 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/1809454
Title:
This has been fixed and is available in snapd for multiple releases now.
I'm marking it as fix released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
qemu-system-s390x (nova-compute) on eoan (train) in an lxd container
Short detail, when trying to launch an instance:
Could not access KVM kernel module: Permission denied
2019-10-29T18:03:09.314636Z qemu-system-s390x: failed to initialize KVM:
Permission denied
Full
** Tags added: s390x
** Also affects: ubuntu-z-systems
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/1850530
Title:
qemu-system-s390x permission denied
Why? The default for your GPU is 'modeset'.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850432
Title:
acrually i wanted the
Public bug reported:
After update from: 70.0+build2-0ubuntu0.16.04.1 to
71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
message that I can Refresh Firefox (crash) or Start in safe mode (also
crash).
Tech details:
Description:Ubuntu 16.04.6 LTS
Release:16.04
This is what we're applying to the juju-default profile after
bootstrapping:
https://raw.githubusercontent.com/openstack-charmers/openstack-on-
lxd/master/lxd-profile.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Newer releases should have this fix.
** Tags removed: raring verification-needed verification-needed-trusty
** Tags added: verification-failed-trusty
** Tags removed: verification-failed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trusty release has gone end of support for this package, so marking this
as such.
Newer releases will have this fix though.
** Changed in: bcmwl (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Updated to Ubuntu 19.10 Eoan, changing keyboard (from zh-cn to es-es)
crashes gnome-shell, and displays that logoff is needed, but clicking
logoff button is useless (won't work). Reboot, log in, and a black
screen with movable cursur will be displayed. After some time, the
** Description changed:
[Impact]
* Users on NUMA systems (mostly servers) with
NUMA balancing enabled (which is by default)
might hit a crash/BUG() on a race condition
if two simultaneous page faults of the same
transparent hugepage go into the path for
migration
--- Comment From pac...@us.ibm.com 2019-10-29 14:42 EDT---
> While not having the priority for an upload on their own. If easy to
> backport we should even consider older versions of qemu.
I'm not sure who "we" refers to (comment #20), and there is an
unanswered question directed at
I have re-ran my test cases and the package you provided fixes the
original issue that we saw.
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/1840686
Title:
Xenial images won't reboot if
I also have these issues and many more on the Dell Precision 7540 with
i7 9750H.
Operating System: Arch Linux
KDE Plasma Version: 5.17.1
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1
Kernel Version: 5.3.7-arch1-2-ARCH
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
As I tried to decsribe, that was only after I created an empty db with
executing "touch /home/XXX/.local/share/flatpak/db/documents". Please
ignore that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Added a blacklist item, run followup commands to regenerate initramfs
and poweroff - still not working. Tried on 2 kernels: 5.3.0-20~2
(provided by Feng) and on 5.3.0-19 (latest official Ubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I just tried to reproduce the bug as outlined in the bug description. I
can confirm it is now fixed and working as expected. I'm marking the
snappy task as fix released.
** Changed in: snappy
Status: In Progress => Fix Released
--
You received this bug notification because you are a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Summary changed:
- linux-oracle: -proposed tracker
+ eoan/linux-oracle: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Summary changed:
- linux: -proposed tracker
+ eoan/linux: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the
Public bug reported:
My Bluetooth speaker is disconnecting few minutes after playing youtube
videos on google chrome [no issues when playing videos in mpv], also I
have noticed that ubuntu detecting my speaker as Bluetooth keyboard
instead of speaker !!
Please find the log below
Oct 29
** Summary changed:
- linux-raspi2: -proposed tracker
+ eoan/linux-raspi2: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Summary changed:
- linux-aws: -proposed tracker
+ eoan/linux-aws: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
Yeah that's everything. Ad nothing out of the ordinary from my boot
records from that time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850085
Title:
right-click 'Format' removable drive not
** Summary changed:
- linux-gcp: -proposed tracker
+ eoan/linux-gcp: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Summary changed:
- linux-hwe-edge: -proposed tracker
+ bionic/linux-hwe-edge: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Summary changed:
- linux-azure: -proposed tracker
+ eoan/linux-azure: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Summary changed:
- linux-kvm: -proposed tracker
+ eoan/linux-kvm: -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
(Moving the curtin task to Incomplete as well. Please move both back to
New once you've provided more information. Thanks!)
** Changed in: curtin
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1850513
Title:
package samba 2:4.3.11+dfsg-0ubuntu0.16.04.23 failed to
install/upgrade: subprocess installed
Test-case snippet on modified kernel on ESM (3.13.0-174.225 + patch)
The problem doesn't happen anymore.
[ 169.972017] cpu 4/pid 1765/task TWO :: change_prot_numa() :: address =
0x7f534f80, end = 0x7f534fa0
[ 171.976313] cpu 5/pid 1766/task ONE :: do_huge_pmd_numa_page() ::
Not quite -- using a pastebin (expire 1y):
https://pastebin.ubuntu.com/p/pjMNxkJfJy/
** Description changed:
[Impact]
* Users on NUMA systems (mostly servers) with
NUMA balancing enabled (which is by default)
might hit a crash/BUG() on a race condition
if two simultaneous
Checking if this snippet is properly spaced in a LP comment text
(instead of Description.)
Task 1 / CPU 1Task 2 / CPU 2
do_huge_pmd_numa_page() do_huge_pmd_numa_page()
- pmd_lock().
- trylock_page()
Public bug reported:
just clicked update
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.23
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset
** Attachment added: "test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+attachment/5301230/+files/test.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813018
Title:
Kernel
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 1849856
and then change the status of the bug to 'Confirmed'.
If, due to the
Test-case snippet on original kernel (3.13.0-170.220)
[ 330.980173] cpu 5/pid 2126/task ONE :: Stage 4. T1 wake up T2... it may BUG!
<...>
[ 331.975122] cpu 6/pid 2125/task TWO :: Stage 4. T2 sleep for 1s... BUG
afterward?
[ 332.980237] BUG: unable to handle kernel paging request at
** Attachment added: "kmod.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813018/+attachment/5301231/+files/kmod.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813018
Title:
Kernel
Test-case snippet on original kernel on ESM (3.13.0-174.225)
[ 1387.632017] cpu 4/pid 1920/task TWO :: change_prot_numa() :: address =
0x7f4560e0, end = 0x7f456100
[ 1389.640322] cpu 5/pid 1921/task ONE :: do_huge_pmd_numa_page() :: addr/mask
= 0x7f4560e0, addr = 0x7f4560e0, pmd
This looks hypervisor/kernel related.
Some observations:
The cloud-init.log in the collect-logs shows cloud-init running twice.
The first time, run-time is expected, approx 17s of cloud-init time, the
second boot took much longer, but the bulk if the time is in udev
2019-06-20 18:09:18,951 -
This bug was fixed while snap-confine was a separate package. I'm
marking the snappy task as fix-released.
** Changed in: snappy
Status: In Progress => Fix Released
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
There does not seem to be anything relevant in the server NFS logs. I
can try harder, I can try to add verbose and check that the logs are
actually being produced, if this does not seem to lead us to the problem
source:
With "journalctl -f" only, I can get the following messages. A lot of
them
It seems that loka 29 20:02:33 koira xdg-document-portal[16225]: error: Failed
to load db: invalid gvdb header
is relevant. I wonder if the database, whatever the format, is somehow corrupt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
--- Comment From christian.r...@de.ibm.com 2019-10-29 14:15 EDT---
Verifiedon a system providing CEX5P, CEX6P, and tolerated CEX7P EP11
co-processors, that the fixed opencryptoki package provided via -propsed that
the message regarding different API version did not longer occur. The
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-tweaks (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/1847136
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Also affects: lxd
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Server Team (canonical-server)
** Changed in: ubuntu-z-systems
Importance: Undecided =>
Ah, forgive me.
I think this bug requires someone to sit down and attempt to reproduce
it in a controlled environment. I cannot commit to do that anytime soon
as we have a number of open bugs, features we promised to deliver and a
handful of people working on the project.
I'd like to keep the
fpart 1.1.0-1 is now in Ubuntu Focal
(https://bugs.launchpad.net/ubuntu/+source/fpart/1.1.0-1)
** Changed in: fpart (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I can't install grub
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.6
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CasperVersion: 1.376.2
Public bug reported:
Hi,
As far as I can tell, the ubuntu-core-meta metapackage and the binary
packages it builds:
- ubuntu-core-libs
- ubuntu-core-libs-dev
Are no longer in use by snapcraft, the core snap or any other consumers;
and is out of date with that is considered the accepted list
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
qemu post 4.1.0 (yet untagged)
67192a298f5 x86/cpu: Add support for UMONITOR/UMWAIT/TPAUSE
6508799707b target/i386: Add support for save/load IA32_UMWAIT_CONTROL MSR
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Synced postgresql-common after Debian got the change for 20.04 that we need.
Lets give this a night to trigger tests and then we might need to re-trigger
all kind of hanging proposed migrations with custom triggers to pass.
--
You received this bug notification because you are a member of
Public bug reported:
Ubuntu once goes into sleep mode, doesn't come out of that mode. It just gets
hung on to black screen when I try to resume work. I have to force shutdown the
system and start again.
This problem started one year back when I had upgraded to Bionic release.
ProblemType: Bug
glibc locale codes are defined by a combination of language and country.
There is no "English-Europe" locale and no way to specify this, it
cannot be missing.
You have the option of using the en_DK locale, which uses Denmark as a
proxy for "generic country where English is not spoken natively."
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workflow
Importance:
@vorlon I understand what you said and I already found different working
workarounds. But as stated it is a missing thing useful to many people
and it could be solved providing locales for en_IT, en_DE, en_SE, en_NE,
etc. as suggested on upstream discussion or providing a generic en_EU
locale
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
replaces: bug 1849060
Hi,
Same thing is happening to me in Xubuntu 18.04 with xrdp. Is there any
fix for this? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251281
Title:
gnome-session-flashback/Unity fails to
Telegram-desktop (as currently in Ubuntu 18.04) is now showing popups
telling the user that their software is out of date and that they should
upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
well I cannot see the error anymore. But the r8168-dkms package version
did not change since the install time. Network works as it should. So I
guess maybe this should be closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The actual programmer of this module says we need to upgrade-software-
version.
1)
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746#note_634394
2)
https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-547218557
He believes that this issue is
This bug was fixed in the package python-acme - 0.31.0-2~ubuntu19.04.1
---
python-acme (0.31.0-2~ubuntu19.04.1) disco; urgency=medium
[ James Hebden ]
* Backport packaging to build on Ubuntu Disco (LP: #1836823)
[ Andreas Hasenack ]
* d/p/series: drop unused -p1
python-acme
Given Maciek's comment about reproducing this with classic snaps I'm
marking this as confirmed.
Interested parties can keep track of
https://github.com/snapcore/snapd/pull/7659 where this issue may be
resolved for _some_ snaps but if confirmed, the same cause is affecting
all the strictly
The verification of the Stable Release Update for python-certbot has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package python-acme - 0.31.0-2~ubuntu16.04.1
---
python-acme (0.31.0-2~ubuntu16.04.1) xenial; urgency=medium
[ James Hebden ]
* Backport packaging to build on Ubuntu Xenial (LP: #1836823)
- Drop debhelper compat level to 9
- Drop
@mykizi-ericsson Could I get an update for my last comment? If CPU
hotplugging can't be addressed then perhaps it'd be alright to just mark
the new module parameter as unsafe...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The verification of the Stable Release Update for python-acme has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu16.04.1
---
python-certbot (0.27.0-1~ubuntu16.04.1) xenial; urgency=medium
* Backport to xenial (LP: #1837673):
- d/control, d/compat: go back to debhelper 9, and drop R³
-
** Description changed:
+ SRU Justification
- 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
+
** Description changed:
+ SRU Justification
- 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
+
This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu18.04.1
---
python-certbot (0.27.0-1~ubuntu18.04.1) bionic; urgency=medium
* Backport to bionic (LP: #1837673):
- d/letsencrypt.postrm: purging the transitional package shouldn't
remove the logs (Closes:
This bug was fixed in the package python-acme - 0.31.0-2~ubuntu18.04.1
---
python-acme (0.31.0-2~ubuntu18.04.1) bionic; urgency=medium
* Backport packaging to build on Ubuntu Bionic (LP: #1836823)
python-acme (0.31.0-2) unstable; urgency=medium
* Backport POST-as-GET support
I did regression tests on disco and eoan with proposed enabled and
didn't faced any messages like the one mentioned in the bug title /
description - but I only have access to CEX5 cards.
But I faced a different problem - that led to LP 1850293 (an IBM package that
needs to be adjusted, hence the
Public bug reported:
after upgrading to 19.10 my system get freeze sometimes again and again
when i use it , it start with any application firstly when i open a
application,application is not give any response and when i again try
to open the same application system got freeze a message came
https://paypalnigeria.com
https://paypalexchanger.com
https://praise.ng
http://medicineforsex.com
https://songsdownload.net
https://paypalexchanger.com/buy-verified-paypal-account-ssn/paypal-
nigeria
https://paypalexchanger.com/how-to-open-verified-us-paypal-account-in-
** Tags removed: kernel-release-tracking-bug-live
** Tags removed: kernel-sru-cycle-2019.10.21-3
** Changed in: kernel-sru-workflow
Status: New => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in:
** Tags removed: kernel-release-tracking-bug-live
** Tags removed: kernel-sru-cycle-2019.10.21-3
** Changed in: kernel-sru-workflow
Status: New => Invalid
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Invalid
** Changed in:
We also uploaded very similar packages to the SRU here to our PPA [1]
that has tens/hundreds of thousands of users on Friday and received no
bug reports.
[1] https://launchpad.net/~certbot/+archive/ubuntu/certbot
--
You received this bug notification because you are a member of Ubuntu
Bugs,
301 - 400 of 637 matches
Mail list logo
