Re: [Bug 1749283] Re: configured stats_temp_directory does not get created after reboot
This is easily reproducible when systemd is not used to manage postgres lifetime. So, yes, quite easy to reproduce and verify if a fix is valid or not. On Mon., Mar. 25, 2019, 09:25 Christian Ehrhardt , < 1749...@bugs.launchpad.net> wrote: > Yeah Michael, > Making just the commit [1] an SRU where needed would have been my thought > as well. But since it is assigned to Mario I wanted to know if he is still > (or again) working on this to avoid doing the work twice - also they might > as well have ended up with discussions somewhere completely else so getting > feedback from him was the obvious next step. > > @Dmitrii a few things to confirm, to get the ball rolling in case Mario > won't respond. > - are you hitting that at all in regard to pgsql "through ressource agent" > or are you deploying just postgresql alone (to decide which package(s) > actually need fixes)? > - If we would provide a PPA do you have an environment to easily > test/verify them? > > [1]: https://github.com/ClusterLabs/resource- > agents/pull/1102/commits/00d888c00651eb178dc3a97d50359571963b5d44 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1749283 > > Title: > configured stats_temp_directory does not get created after reboot > > Status in postgresql-common package in Ubuntu: > Won't Fix > Status in resource-agents package in Ubuntu: > In Progress > Status in postgresql-common source package in Xenial: > Won't Fix > Status in resource-agents source package in Xenial: > New > Status in postgresql-common source package in Artful: > Won't Fix > Status in resource-agents source package in Artful: > Invalid > Status in postgresql-common source package in Bionic: > Won't Fix > Status in resource-agents source package in Bionic: > New > Status in postgresql-common package in Debian: > Fix Released > > Bug description: > Default postgres installation in Ubuntu (and Debian) configures > stats_temp_directory inside /var/run/postgresql: > > $ grep stats_temp /etc/postgresql/10/main/postgresql.conf > stats_temp_directory = '/var/run/postgresql/10-main.pg_stat_tmp' > > However, this directory is not created after reboot. > > In most cases this is not a problem as systemd starts postgres via > pg_ctlcluster, a "multiversion/cluster aware pg_ctl wrapper", and > pg_ctlcluster will create missing directories before starting > postgres. > > But in cases where systemd is not starting postgres this is a problem. > Specifically, when postgres is controlled by pacemaker (using postgres > resource agent for pacemaker) it is started using pg_ctl wrapper. pg_ctl > won't create missing directories and therefore postgres fails to start. > > The simplest solution for this issue is to have systemd recreate > missing directories via /usr/lib/tmpfiles.d/postgresql.conf file. > > Currently only /var/run/postgresql and /var/log/postgresql are created > using systemd-tmpfiles. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749283 Title: configured stats_temp_directory does not get created after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168115] Re: Ubiquity does not support LUKS in manual partitioning mode
Hi Nicolas, nice script. I believe that this is a sorely missing feature in the installer. It definitely should be part of the installer that you can configure LVM on top of a LUKS encrypted partition. At the moment it is not possible to select LVM on an LUKS encrypted device. In the past I always did this setup manually to work around this sad fact, now I might take your script with a small tweak - a different name for the LUKS device: rename os -> _crypt that makes it more clear that you have an encrypted device in front of you and reduces the danger of accidentally trashing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168115 Title: Ubiquity does not support LUKS in manual partitioning mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1168115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819659] Re: linux-lts-xenial: 4.4.0-144.170~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819660 phase: Testing phase-changed: Thursday, 21. March 2019 14:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1819659 Title: linux-lts-xenial: 4.4.0-144.170~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819703] Re: linux-oracle: 4.15.0-1010.12~16.04.1 -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: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819704 phase: Promote to Proposed phase-changed: Thursday, 21. March 2019 14:08 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819703 Title: linux-oracle: 4.15.0-1010.12~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => 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 see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819703 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 17:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1819704 Title: linux-oracle: 4.15.0-1010.12 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
On 25.03.19 07:53, Christian Ehrhardt wrote: > @Paul - you were so active before - thanks for checking the PPAs and > all that. But I still have no NFS server uncoorperative enough to > trigger this; Could you for the (final) SRU verification as asked on > the comments #18 and #19 confirm that this works in your setup with > the changes that are in proposed [1]. Aren’t they identical to the packages in your PPA? Anyway, I can test the proposed packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820291] Re: fsfreeze-hook script is misplaced in qemu-guest-agent
** Merge proposal linked: https://code.launchpad.net/~ubuntu-virt/ubuntu/+source/qemu/+git/qemu/+merge/365022 ** Merge proposal linked: https://code.launchpad.net/~ubuntu-virt/ubuntu/+source/qemu/+git/qemu/+merge/365023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820291 Title: fsfreeze-hook script is misplaced in qemu-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal
That affects all kernels, because that needs kvm modules parameter enable_vmware_backdoor. I am not comfortable enabling that by default on our kernels. We could enable that during the kvm-unit-tests. But for now, on our own branch of kvm-unit-tests, I decided to simply disable that test to be run by default. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821393 Title: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820315] Re: linux-hwe-edge: 5.0.0-8.9~18.04.1 -proposed tracker
** 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-testing-requested: true kernel-stable-master-bug: 1819759 - phase: Ready for Promote to Proposed - phase-changed: Friday, 22. March 2019 14:30 UTC + phase: Promote to Proposed + phase-changed: Monday, 25. March 2019 09:39 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1820315 Title: linux-hwe-edge: 5.0.0-8.9~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] Comment bridged from LTC Bugzilla
--- Comment From peter.oberparlei...@de.ibm.com 2019-03-25 05:32 EDT--- This error is likely due to using the full block device node (dasda) instead of a partition device node (e.g. dasda1) of a CDL formatted DASD device. Note that the first two tracks (1 track = 48k at 4k block size) of a CDL-formatted DASD device have special properties. Not all data written to these blocks is retained. Instead portions of the data are replaced by an E5 byte pattern. Applications/FS should therefore not use the block device, but only partition devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820315] Re: linux-hwe-edge: 5.0.0-8.9~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820315 Title: linux-hwe-edge: 5.0.0-8.9~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821498] Re: Last card disappears in thirteen
I am setting this bug invalid. Nice that you pointed a reason in your last comment. ** Changed in: aisleriot (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/1821498 Title: Last card disappears in thirteen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1821498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** 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. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1819698 - phase: Packaging - phase-changed: Friday, 22. March 2019 12:38 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 25. March 2019 09:28 UTC reason: - prepare-package-meta: Pending -- package tag not yet published - promote-to-proposed: Pending -- source package tags missing + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819695 Title: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821537] Re: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16
I suggest to enable CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP in Bionic HWE kernels as this will allow to debug via serial console with a simple USB 3 crossover-cable (aka "USB 3.0 super-speed A-to-A debugging cable") without the need of a physical RS-232 interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821537 Title: Enable kernel options CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP for serial Superspeed(+) connections with kernels >= 4.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765367] Re: vmware_backdoors test in kvm-unit-test failed on Artful
*** This bug is a duplicate of bug 1821393 *** https://bugs.launchpad.net/bugs/1821393 ** This bug has been marked a duplicate of bug 1821393 vmware_backdoors will fail on kvm_unit_tests on aws i3.metal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765367 Title: vmware_backdoors test in kvm-unit-test failed on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812671] Re: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities
This bug was fixed in the package virtualbox - 4.3.40-dfsg- 0ubuntu14.04.1 --- virtualbox (4.3.40-dfsg-0ubuntu14.04.1) trusty; urgency=medium * New upstream release (LP: #1812671) -- Gianfranco Costamagna Mon, 21 Jan 2019 14:33:14 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812671 Title: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1812671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767817] Re: Full text search does not work
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.4 --- nautilus (1:3.26.4-0~ubuntu18.04.4) bionic; urgency=medium * d/p/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch: - update the patch to fix a logic error in the code which made tracker never being used even if it's installed (lp: #1767817) -- Sebastien Bacher Wed, 06 Mar 2019 17:31:08 +0100 ** Changed in: nautilus (Ubuntu Bionic) 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/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818880] Update Released
The verification of the Stable Release Update for qemu 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812671] Re: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities
This bug was fixed in the package virtualbox-guest-additions-iso - 4.3.40-0ubuntu1.14.04.1 --- virtualbox-guest-additions-iso (4.3.40-0ubuntu1.14.04.1) trusty; urgency=medium * New upstream release (LP: #1812671) -- Gianfranco Costamagna Mon, 21 Jan 2019 14:33:17 +0100 ** Changed in: virtualbox-guest-additions-iso (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: virtualbox (Ubuntu Trusty) 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/1812671 Title: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1812671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws (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/1821393 Title: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
Thanks, this should be enough in that case. Releasing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818880] Re: Deadlock when detaching network interface
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.35 --- qemu (1:2.5+dfsg-5ubuntu10.35) xenial; urgency=medium * Fix deadlock when detaching network interface (LP: #1818880) Fixed by upstream patch: - d/p/lp-1818880-rcu-disable-atfork.patch: rcu: completely disable pthread_atfork callbacks as soon as possible -- hal...@canonical.com (Heitor R. Alves de Siqueira) Fri, 01 Mar 2019 15:59:01 -0300 ** Changed in: qemu (Ubuntu Xenial) 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/1818880 Title: Deadlock when detaching network interface To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812671] Update Released
The verification of the Stable Release Update for virtualbox 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812671 Title: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1812671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812671] Re: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities
This bug was fixed in the package virtualbox-lts-xenial - 4.3.40-dfsg- 0ubuntu1.14.04.1~14.04.1 --- virtualbox-lts-xenial (4.3.40-dfsg-0ubuntu1.14.04.1~14.04.1) trusty; urgency=medium * Use lts-xenial stack. Build only guest additions (LP: #1424769). -- Gianfranco Costamagna Fri, 01 Mar 2019 15:13:03 +0100 ** Changed in: virtualbox-lts-xenial (Ubuntu Trusty) 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/1812671 Title: [SRU] Virtualbox in trusty 14.04 is an old version and has many security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1812671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821353] Re: bcache-super-show segfaults reading superblock on dasd
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-25 04:49 EDT--- Description will be reversed mirrored from LP ** Tags added: architecture-s39064 bugnameltc-176335 severity-high targetmilestone-inin1904 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821353 Title: bcache-super-show segfaults reading superblock on dasd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348275] Re: gdb message "Got object file from memory but can't read symbols: File truncated."
** Changed in: python 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/1348275 Title: gdb message "Got object file from memory but can't read symbols: File truncated." To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1348275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816650] Update Released
The verification of the Stable Release Update for lldpd 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816650 Title: 4.19+ (and possibly -stable trees?) need a fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lldpd/+bug/1816650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767817] Re: Full text search does not work
Thank you for testing the package, I have promoted it to bionic-updates. The cosmic counterpart still needs verification though. Could someone test the 18.10 package so we could get it released as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767817] Update Released
The verification of the Stable Release Update for nautilus 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816650] Re: 4.19+ (and possibly -stable trees?) need a fix from upstream
Thank you for the verification! I have released this to bionic-updates just now. Could you or someone else perform the same validation on a 18.10 system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816650 Title: 4.19+ (and possibly -stable trees?) need a fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lldpd/+bug/1816650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators
This bug was fixed in the package indicator-application - 12.10.1+18.04.20190308.1-0ubuntu1 --- indicator-application (12.10.1+18.04.20190308.1-0ubuntu1) bionic; urgency=medium [ Iain Lane ] * data/indicator-application.desktop.in: Don't run in ubuntu sessions (LP: #1819103) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Fri, 08 Mar 2019 15:36:29 + ** Changed in: indicator-application (Ubuntu Bionic) 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/1819103 Title: Indicator Application and indicator-applet does not show indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816650] Re: 4.19+ (and possibly -stable trees?) need a fix from upstream
This bug was fixed in the package lldpd - 0.9.9-1ubuntu0.1 --- lldpd (0.9.9-1ubuntu0.1) bionic; urgency=medium * debian/patches/0002-remove-specific-handling-for-bond.patch: Remove specific handling for bonds. Thanks to Vincent Bernat . Closes LP: #1816650. -- Nishanth Aravamudan Wed, 20 Feb 2019 14:24:36 -0600 ** Changed in: lldpd (Ubuntu Bionic) 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/1816650 Title: 4.19+ (and possibly -stable trees?) need a fix from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lldpd/+bug/1816650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819103] Update Released
The verification of the Stable Release Update for indicator-application 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819103 Title: Indicator Application and indicator-applet does not show indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659534] Re: userdel doesn't supports extrausers
This bug was fixed in the package shadow - 1:4.5-1.1ubuntu2 --- shadow (1:4.5-1.1ubuntu2) disco; urgency=medium * debian/patches/1013_extrausers_deluser.patch - add --extrausers option to "userdel" (LP: #1659534) -- Michael Vogt Fri, 22 Mar 2019 19:32:50 +0100 ** Changed in: shadow (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/1659534 Title: userdel doesn't supports extrausers To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819103] Re: Indicator Application and indicator-applet does not show indicators
This bug was fixed in the package indicator-application - 12.10.1+18.10.20190308.1-0ubuntu1 --- indicator-application (12.10.1+18.10.20190308.1-0ubuntu1) cosmic; urgency=medium [ Iain Lane ] * data/indicator-application.desktop.in: Don't run in ubuntu sessions (LP: #1819103) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Fri, 08 Mar 2019 15:36:19 + ** Changed in: indicator-application (Ubuntu Cosmic) 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/1819103 Title: Indicator Application and indicator-applet does not show indicators To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1819103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks
Hi Nicolas, yeah that isn't easy to fix and at least I didn't find the time to develop something completely new to cover this yet. I challenge the statement "Even the default storage pool /var/lib/libvirt/images is not working", it does and it does well. And for things that are under the control of Ubuntu in the Archive even a few alternative paths work (openstack, uvtool, ...). The issue you report is -not- using the default paths, the Deny lists "/mnt/images/ubuntu-admin-qcow2" which clearly is not in one of the common paths. In general for using uncommon paths [1] the solution is that an admin has to declare those paths as allowed in a local apparmor include. So if terraform would usually /a/b/c it should also either recommend the admin to do so or even consider adding it to the files itself. [1]: https://wiki.ubuntu.com/LibvirtApparmor#Using_uncommon_paths ** Changed in: libvirt (Ubuntu Xenial) Status: Confirmed => Won't Fix ** Changed in: libvirt (Ubuntu Zesty) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677398 Title: Apparmor prevents using storage pools and hostdev networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
Please test this kernel: https://people.canonical.com/~khfeng/lp1821434/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821434 Title: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749283] Re: configured stats_temp_directory does not get created after reboot
Yeah Michael, Making just the commit [1] an SRU where needed would have been my thought as well. But since it is assigned to Mario I wanted to know if he is still (or again) working on this to avoid doing the work twice - also they might as well have ended up with discussions somewhere completely else so getting feedback from him was the obvious next step. @Dmitrii a few things to confirm, to get the ball rolling in case Mario won't respond. - are you hitting that at all in regard to pgsql "through ressource agent" or are you deploying just postgresql alone (to decide which package(s) actually need fixes)? - If we would provide a PPA do you have an environment to easily test/verify them? [1]: https://github.com/ClusterLabs/resource- agents/pull/1102/commits/00d888c00651eb178dc3a97d50359571963b5d44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749283 Title: configured stats_temp_directory does not get created after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1749283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810176] Re: libmtp error could not get object handles
Just the same issue with my Galaxy C5 PRO, when i'm trying to get access to Сamera folder inside DCIM folder on the micro-sd card. Both with Ubuntu 16.04 and Ubuntu 18.04 (default nau managers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810176 Title: libmtp error could not get object handles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821391] Re: mongorestore fails with createIndexes command in oplog
I checked the test instructions and mentioned there that timing is
important as that was inhibiting me at first.
Furthermore I checked through releases and marked the tasks accordingly
(fixed in Disco already, B/C affected).
** Description changed:
[Impact]
When an operator of Juju attempts to restore a backup, it fails with a
mongorestore related error[0]. Under the hood, Juju uses the supplied
mongo related command line interfaces (mongodump, mongorestore etc),
using these in conjunction with the oplog related flags for the former
CLIs, the mongorestore fails with the following error:
> Failed: restore error: error applying oplog: applyOps: applyOps had
one or more errors applying ops
The only work around for Juju at the moment is to update mongod, so that
it carries the following commit[1]. MongoDB have an identical issue,
under a different name, which fixes this[2], but there is unfortunately
no work around without upgrading mongod so it caries the former commit.
The original investigation around Juju failing to restore a previous
dump can be seen here[3]
I've verified with the 3.6.11 and the same restore, worked fine.
[Test Case]
- The following test case doesn't require Juju, and can be replicated
- quite easily inside a lxc container. It may require 2 or 3 goes,
- depending on timings of the creation of the index and the mongodump, but
- I've been getting this consistently.
+ The following test case doesn't require Juju, and can be replicated quite
easily inside a lxc container. It may require 2 or 3 goes, depending on timings
of the creation of the index and the mongodump, but I've been getting this
consistently.
+ Please do mind that timing is important, so putting the commands in a script
will help a lot to reliably trigger the issue.
You can also find instructions in one pastebin[4]
// Launch a container
lxc launch ubuntu:18.04 mongo
lxc exec mongo bash
// Install a version of mongo that Juju is using.
sudo apt update
sudo apt install -y mongodb
// Edit /etc/mongodb.conf and add the following line:
replSet = "rs0"
// Restart the service
systemctl restart mongodb.service
// not required, but helps diagnose bsondump
snap install jq
// launch the mongo CLI, running each command
mongo --eval "rs.initiate()"
mongo --eval "rs.status()"
mongo --eval "db.foo.insert({'foo':'bar'})"
mongo --eval "db.foo.createIndex({'bar':1})"
// Get the dump
mongodump --oplog
// check if it's going to fail
// if the output contains a createIndex, but doesn't contain an oid then
it'll fail.
bsondump dump/oplog.bson | jq
// Drop the foo collection, so we don't get any duplication errors
mongo --eval "db.foo.drop()"
// Now restore the dump
mongorestore --oplogReplay dump/
// It should fail with
2019-03-22T17:26:28.034+ preparing collections to restore from
2019-03-22T17:26:28.035+ reading metadata for test.foo from
dump/test/foo.metadata.json
2019-03-22T17:26:28.053+ restoring test.foo from dump/test/foo.bson
2019-03-22T17:26:28.056+ restoring indexes for collection test.foo from
metadata
2019-03-22T17:26:28.062+ finished restoring test.foo (1 document)
2019-03-22T17:26:28.062+ replaying oplog
2019-03-22T17:26:28.064+ Failed: restore error: error applying oplog:
applyOps: applyOps had one or more errors applying ops
After updating the packages, re-run the drop and try to import again,
this time it should work:
# mongo --eval "db.foo.drop()"
MongoDB shell version v3.6.3
connecting to: mongodb://127.0.0.1:27017
MongoDB server version: 3.6.3
true
r
# mongorestore --oplogReplay dump/
2019-03-22T19:49:43.838+ preparing collections to restore from
2019-03-22T19:49:43.840+ reading metadata for test.foo from
dump/test/foo.metadata.json
2019-03-22T19:49:43.856+ restoring test.foo from dump/test/foo.bson
2019-03-22T19:49:43.858+ restoring indexes for collection test.foo from
metadata
2019-03-22T19:49:43.866+ finished restoring test.foo (1 document)
2019-03-22T19:49:43.866+ replaying oplog
2019-03-22T19:49:43.867+ done
-
[Other Info]
0. https://paste.ubuntu.com/p/9r9pYc9g9D/
1.
https://github.com/mongodb/mongo/commit/0d0ba866052fd2b9ceaaa66c2b725a02822b102d
2. https://jira.mongodb.org/browse/SERVER-36951
3. https://bugs.launchpad.net/juju/+bug/1818831
4. https://paste.ubuntu.com/p/HJsDf5yNkS/
** Also affects: mongodb (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: mongodb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: mongodb (Ubuntu)
Status: In Progress => Fix Released
** Changed in: mongodb (Ubuntu Bionic)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Bionic)
Assign
[Bug 1711478] Re: [FTBFS] arm does not define __NR_migrate_pages
Add the following to the same list (for Cosmic) http://autopkgtest.ubuntu.com/packages/l/linux/cosmic/ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711478 Title: [FTBFS] arm does not define __NR_migrate_pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1711478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817258] Re: "numastat" doesn't display correct information for the guest.
Add the following to the same list (for Cosmic) http://autopkgtest.ubuntu.com/packages/l/linux/cosmic/ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817258 Title: "numastat" doesn't display correct information for the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821434] Re: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40
I had a try on kernel 4.15.0-46 in Bionic with efi-pstore module loaded as pstore backend, but I cannot reproduce that kernel panic. It really takes more information before one can investigation more into this issue, so apport runs, even before the panic taking place, is really mandatory. Please give apport a chance to collect some more information by executing `apport-collect 1821434`. By the way, have you tried to enable efi-pstore _without_ that SATA card installed. Maybe it's not related to efi-pstore at all? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821434 Title: Panic on suspend/resume Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: sata_pmp_eh_recover+0xa2b/0xa40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817258] Re: "numastat" doesn't display correct information for the guest.
Looking at the autopkgtest failures and especially the history of them indicates that the remaining few (most worked well) can be ignored. Here references to the remaining issues and their history: http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386 http://autopkgtest.ubuntu.com/packages/l/linux-gcp-edge/bionic/amd64 http://autopkgtest.ubuntu.com/packages/l/linux-oracle/bionic/amd64 @SRU Team - do you want me to get in touch with the kernel Team to mask these tests or can/will you ignore them as-is for the SRU release of this change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817258 Title: "numastat" doesn't display correct information for the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1817258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711478] Re: [FTBFS] arm does not define __NR_migrate_pages
Looking at the autopkgtest failures and especially the history of them indicates that the remaining few (most worked well) can be ignored. Here references to the remaining issues and their history: http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386 http://autopkgtest.ubuntu.com/packages/l/linux-gcp-edge/bionic/amd64 http://autopkgtest.ubuntu.com/packages/l/linux-oracle/bionic/amd64 @SRU Team - do you want me to get in touch with the kernel Team to mask these tests or can/will you ignore them as-is for the SRU release of this change? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711478 Title: [FTBFS] arm does not define __NR_migrate_pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1711478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
src:linux-firmware is only accepted into cosmic-proposed but still waiting in Bionic-unapproved. AFAIK the current status of "Fix committed" will make it not to be seen by the SRU Team (at least for similar cases I had in the past). Therefore to increase the chance to get also the Bionic portion accepted into -proposed lets dial back the current status of the bug task. ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** 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 backports: bug 1819703 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Thursday, 21. March 2019 17:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1819704 Title: linux-oracle: 4.15.0-1010.12 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
After adding the line "/usr/bin/xinit" to gdm3.service I get this in every boot: ProblemType: Crash Architecture: amd64 Date: Mon Mar 25 19:17:11 2019 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1543339632 ProcCmdline: /usr/lib/xorg/Xorg :0 ... Did you guys find out why? And, why does it take too long to show the login screen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
** 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 see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing 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/1819716 Title: linux: 4.15.0-47.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: Ubuntu Cosmic 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
*** This bug is a duplicate of bug 1808389 *** https://bugs.launchpad.net/bugs/1808389 Yep, the changes accepted to B/C-unapproved as part of an SRU should be what we need. Marking as a Duplicate so that we can test that SRU as well to hopefully resolve it for all of us. ** This bug has been marked a duplicate of bug 1808389 iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804841 Title: iwlwifi Microcode SW error detected. Restarting 0x200. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Its look like the issue is on usage the connect/pair command. When use a bluetoothctl 'connect' command, the connection is established, with info: [CHG] Device ServicesResolved: yes [CHG] Device Paired: yes Connection successful but the [LinkKey] section is not stored in 'info' file. When use a bluetoothctl 'pair' command, the connection is established, with info: [CHG] Device ServicesResolved: yes [CHG] Device Paired: yes Pairing successful and the [LinkKey] section is on the 'info' file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818121] Re: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available
@Paul - you were so active before - thanks for checking the PPAs and all that. But I still have no NFS server uncoorperative enough to trigger this; Could you for the (final) SRU verification as asked on the comments #18 and #19 confirm that this works in your setup with the changes that are in proposed [1]. [1]: https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818121 Title: NFSv4 shares with option `-vers=4.0` are not mounted: mount(nfs): no hosts available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1818121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788432] Re: 4.15 s390x kernel BUG at /build/linux-Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565!
** Changed in: ubuntu-z-systems 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/1788432 Title: 4.15 s390x kernel BUG at /build/linux- Gycr4Z/linux-4.15.0/drivers/block/virtio_blk.c:565! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1788432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821351] Re: PXE booted debian-installer fails to install package 'linux-generic' in Xenial
** Attachment removed: "syslog from installer" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821351/+attachment/5248519/+files/mok-syslog ** Attachment added: "syslog from installer" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821351/+attachment/5249158/+files/mok-syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821351 Title: PXE booted debian-installer fails to install package 'linux-generic' in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
