** Changed in: kernel-sru-workflow/promote-to-proposed
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/1819614
Title:
linux-aws: 4.18.0-1012.14 -proposed tr
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the
This bug was fixed in the package linux - 3.13.0-167.217
---
linux (3.13.0-167.217) trusty; urgency=medium
* linux: 3.13.0-167.217 -proposed tracker (LP: #1819917)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Pa
This bug was fixed in the package linux - 3.13.0-167.217
---
linux (3.13.0-167.217) trusty; urgency=medium
* linux: 3.13.0-167.217 -proposed tracker (LP: #1819917)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Pa
Thanks for the feedback.
This is the old patch that I used to compile the test kernel in #4:
https://pastebin.ubuntu.com/p/dkGBkd2R85/
I think I have found the cause, the compiled-in option was not set.
If you run "make menuconfig" against a clean source to enable TER16x32
(Library routines >>
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 3.13.0-167.217
---
linux (3.13.0-167.217) trusty; urgency=medium
* linux: 3.13.0-167.217 -proposed tracker (LP: #1819917)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
- [Pa
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Tags removed: block-proposed-trusty
** Tags removed: block-proposed
** Description changed:
This bug will contain st
** Merge proposal linked:
https://code.launchpad.net/~azzar1/ubuntu/+source/gtk+3.0/+git/gtk+3.0/+merge/364501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592177
Title:
Focus drops from searc
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
** Bug watch added: Debian Bug tracker #924620
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924620
** Also affects: edk2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924620
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
This bug was fixed in the package linux - 4.4.0-143.169
---
linux (4.4.0-143.169) xenial; urgency=medium
* linux: 4.4.0-143.169 -proposed tracker (LP: #1814647)
* x86/kvm: Backport fixup and missing commits (LP: #1811646)
- KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.4.0-1077.87
---
linux-aws (4.4.0-1077.87) xenial; urgency=medium
* linux-aws: 4.4.0-1077.87 -proposed tracker (LP: #1814651)
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: fix crash during failed resume from hi
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-lts-xenial -
4.4.0-143.169~14.04.2
---
linux-lts-xenial (4.4.0-143.169~14.04.2) trusty; urgency=medium
* linux-lts-xenial: 4.4.0-143.169~14.04.2 -proposed tracker (LP:
#1814649)
* Packaging resync (LP: #1786013)
- [Packaging] update hel
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.4.0-1077.87
---
linux-aws (4.4.0-1077.87) xenial; urgency=medium
* linux-aws: 4.4.0-1077.87 -proposed tracker (LP: #1814651)
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: fix crash during failed resume from hi
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot
This bug was fixed in the package linux-aws - 4.4.0-1039.42
---
linux-aws (4.4.0-1039.42) trusty; urgency=medium
* linux-aws: 4.4.0-1039.42 -proposed tracker (LP: #1814648)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] drop
This bug was fixed in the package linux-kvm - 4.4.0-1041.47
---
linux-kvm (4.4.0-1041.47) xenial; urgency=medium
* linux-kvm: 4.4.0-1041.47 -proposed tracker (LP: #1814654)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
* linux-buildinfo: pull out ABI i
This bug was fixed in the package linux-raspi2 - 4.4.0-1104.112
---
linux-raspi2 (4.4.0-1104.112) xenial; urgency=medium
* linux-raspi2: 4.4.0-1104.112 -proposed tracker (LP: #1814655)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Conf
This bug was fixed in the package linux-raspi2 - 4.4.0-1104.112
---
linux-raspi2 (4.4.0-1104.112) xenial; urgency=medium
* linux-raspi2: 4.4.0-1104.112 -proposed tracker (LP: #1814655)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Conf
This bug was fixed in the package linux-snapdragon - 4.4.0-1108.113
---
linux-snapdragon (4.4.0-1108.113) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1108.113 -proposed tracker (LP: #1814657)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the assoc
This bug was fixed in the package linux-snapdragon - 4.4.0-1108.113
---
linux-snapdragon (4.4.0-1108.113) xenial; urgency=medium
* linux-snapdragon: 4.4.0-1108.113 -proposed tracker (LP: #1814657)
* linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/security-signoff
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/1819917
Title:
linux: 3.13.0-167.217 -proposed tracker
T
** 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 title.
For an explanation of the tasks and the associated workflow see:
https
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819917
Title:
linux: 3.13.0-167.217 -proposed tracker
To
On Fri, Mar 15, 2019 at 02:41:22PM -, Jonathan Kamens wrote:
> >You should be able to remove or edit /etc/cron.d/certbot, and by policy
> packaging is required to respect your change. Does this not work?
>
> Yes, this appears to work (at least, after removing the file, `apt-get
> install --rei
** Changed in: resolvconf (Ubuntu Disco)
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/1817903
Title:
systemd-resolve appends "options edns0" to resolv.c
Maybe related to https://github.com/zeromq/libzmq/issues/1462
** Bug watch added: github.com/zeromq/libzmq/issues #1462
https://github.com/zeromq/libzmq/issues/1462
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: xymon (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819378
Title:
package xymon 4.3.28-3build1 failed to install/upgrade: installed
Additionally, apport-retrace cannot load the core dump:
$ apport-retrace /var/crash/_usr_bin_dbus-daemon.1000.crash
ERROR: Invalid core dump: BFD: warning: /tmp/apport_core_pj5lncdz is truncated:
expected core file size >= 2015232, found: 61440
--
You received this bug notification because you a
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
Thank you for your bug report, the change was reverted from the ubuntu-
settings overide and done in imagemagick itself, that has been removed
in disco with the rtaional that imagemagick is not installed by default
https://launchpad.net/ubuntu/+source/imagemagick/8:6.9.10.14+dfsg-
7ubuntu1
' * D
Same issue here. UnreportableReason is usually something about core dump sizes.
systemctl --user status dbus does not seem to indicate anything is off.
** Attachment added: "_usr_bin_dbus-daemon.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5246446/+files/
** 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 --
boot-testi
** 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 title.
For an explanation of the tasks and the associated workflow see:
https
Public bug reported:
Hello,
I am embedding custom GPG public key in grub and sign (detached) the
4.15.0-46-generic kernel with GPG private key. The grub is not
validating the kernel. I am getting an error "/vmlinuz-4.15.0-46-generic
has invalid signature".
However this process used to work fine
This bug was fixed in the package console-setup - 1.178ubuntu11
---
console-setup (1.178ubuntu11) disco; urgency=medium
* kbdnames-maker: Call `{bind,}textdomain` after switching locale.
There's a change in perl 5.28 to use `uselocale()` & friends instead of
gettext directly
A new resolve package with today's update solved the problem; apparently
it was an issue with name resolving.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820048
Title:
Samba share not automounted
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-hwe (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-hwe (Ubuntu Xenial)
Status: New => Fix Commit
Public bug reported:
The fsfreeze-hook in the package is installed on the path /etc/qemu
/fsfreeze-hook/fsfreeze-hook but the default path is /etc/qemu/fsfreeze-
hook.
This means that to make it work, I had to:
- add "-F/etc/qemu/fsfreeze-hook/fsfreeze-hook" to the DAEMON_ARGS in
/etc/default/qe
** 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 --
kernel-sta
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Andrea Righi (arighi) => (unassig
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Tags removed: block-propo
>You should be able to remove or edit /etc/cron.d/certbot, and by policy
packaging is required to respect your change. Does this not work?
Yes, this appears to work (at least, after removing the file, `apt-get
install --reinstall python3-certbot` on disco doesn't recreate it), but
as I understand
** Tags added: regression-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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/1819917
Title:
This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.13
---
ubuntu-release-upgrader (1:19.04.13) disco; urgency=medium
[ Brian Murray ]
* Add a lintian override for unsafe symlinks after removing some crufty
symlinks.
[ Dimitri John Ledkov ]
* Fix up minor
** 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 --
boot-testi
This bug was fixed in the package s390-tools - 2.8.0-0ubuntu5
---
s390-tools (2.8.0-0ubuntu5) disco; urgency=medium
* zkey: on Ubuntu, use default benchmarked Argon2i with LUKS2. LP:
#1820049
-- Dimitri John Ledkov Fri, 15 Mar 2019 13:50:25
+
** Changed in: s390-tools (
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1819917
Title:
linux: 3.13.0-167.217 -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (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/1814069
Title:
I can't get logs from the system because it's kernel panic'd.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Fully up-to-date Fedora 29 VM, the chromium snap still fails to launch
with the same error.
** Also affects: snapd
Importance: Undecided
Status: New
** Summary changed:
- [snap] core18-based snap fails to start on Solus
+ [snap] core18-based snap fails to start on Solus/fedora29
--
Y
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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 se
Public bug reported:
Deploying application through "Deploy directory or WAR file located on server"
in tomcat manager
does not work anymore since 18.04 (it used to work until 16.04 and is working
in regular tomcat)
Context configuration set in "XML Configuration file URL" is not copied
anymore
** Description changed:
Feature Freeze exception for AppArmor 2.13.2
The security team is pushing to get AppArmor 2.13 into 19.04 since we
- want AppArmor 3 (or higher) in 20.04 and we'd like to incrementally
- update to it to test the new features that are available now and make
- the over
** Attachment added: "Simple application to reproduce the issue"
https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1820288/+attachment/5246435/+files/hello.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
raising erlang bug task; I think we need to address the two ERL-* issues
in the xenial erlang version as identified in #13.
** Also affects: erlang (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
** Changed in: apparmor (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817799
Title:
[FFe] apparmor 2.13
To manage notifications about this bug go to:
htt
** Summary changed:
- netplan removes keepalived configuration
+ Restarting systemd-networkd breaks keepalived clusters
** Summary changed:
- Restarting systemd-networkd breaks keepalived clusters
+ [master] Restarting systemd-networkd breaks keepalived clusters
--
You received this bug notifi
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
** This bug has been marked a duplicate of bug 1815101
Restarting systemd-networkd breaks keepalived clusters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
Heres a possible workaround until its solved (did not test it, but seems
valid): https://chr4.org/blog/2019/01/21/make-keepalived-play-nicely-
with-netplan-slash-systemd-network/
Personally i can live with
Added -mzvector, fixed up a few more packaging bits, and it looks like
z13 optimized libraries are fully built.
Please test:
sudo add-apt-repository ppa:ci-train-ppa-service/3679
sudo apt-get update
On Ubuntu Disco (19.04), and let me know if you see performance
improvements on a z13+. It is sti
Same result (freeze on s2disk screen) in both kernels.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
** Attachment added: "4.15-46.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+attachment/5246431/+files/4.1
** Attachment added: "5.0.2.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+attachment/5246432/+files/5.0.2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819915
Title:
s2
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 1820287
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Same annoying problem AMD APU 9720P RX 540.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807511
Title:
AMDGPU Radeon RX540 system freezes poor performance with ac adapter
plugged in
To manage n
** Description changed:
[impact]
systems upgraded from pre-Bionic releases to Bionic or later will
continue to use ifupdown/resolvconf for network conf and management, but
resolvconf has a new systemd service in Bionic and later that pulls
systemd-resolved stub-resolv.conf into its lo
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: s390-tools (Ubuntu)
Status: New => 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/18
Previous change reverted and new fix uploaded (after ddstreet discussion
with xnox) in Disco.
- Eric
** Changed in: resolvconf (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've seen this twice, once upgrading packages on 18.4.2 and once upgrading to
18.4.2.
coping critical.cfg to critical.cfg.bak bypassed the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819378
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
** Description changed:
This bug is for tracking
Thanks for the testing, Nicolas!
The cloud-init team also completed the full suite of testing for the
SRUs late yesterday; as we didn't want to release on a Friday, we'll be
aiming to release the SRUs on Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xymon (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/1819378
Title:
pack
Thank you for confirming the bug, it looks like libnfsidmap's code base was
imported into nfs-utils by Redhat on 10/26/2017 by Justin Mitchell, it
already had the line modification inside nss.c at that point.
I found where the commit was made, it was on the master branch of
https://github.com/Dist
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-15 08:55 EDT---
Description will be mirrored via reverse mirroring
** Tags added: architecture-s39064 bugnameltc-176142 severity-high
targetmilestone-inin1904
--
You received this bug notification because you are a member of Ubuntu
B
** Description changed:
- Description will follow
+ This report show a kernel oops in the btrfs lugin , happened every few
+ days when running a test suite on a test system. It looks like their
+ systemd/Journal failed to kick off a dump immediately following the
+ panic.
+
+ The exploiter is usi
Public bug reported:
A machine in our test lab kernel panic'd during PXE boot from MAAS.
It was running 4.15.0-46-generic #49-Ubuntu
I've attached a screenshot of the call trace.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: cdo-qa foundations-engine
**
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
** Description changed:
This bug is for tracking
** Summary changed:
- netplan, keepalived, netplan-apply
+ Restarting systemd-networkd breaks keepalived clusters
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd
Public bug reported:
Hello,
Managing a HA floating IP with netplan and keepalived brings trouble.
Im managing a two node keepalived cluster with a floating IP.
Everything works out except if i run on a the master node (which holds floating
ip) "netplan apply".
Prob netplan resets the whole inte
301 - 400 of 679 matches
Mail list logo
