[Bug 1795292] Re: ELAN469D touch pad not working
Please test this kernel without "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2": https://people.canonical.com/~khfeng/lp1795292/ It overrides IVRS IOAPIC for Lenovo ideapad 330S-15ARR. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375
Please test this kernel: https://people.canonical.com/~khfeng/lp1795292/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837688 Title: Ubuntu won't boot on Dell Inspiron 7375 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833400] Re: named crashes on REQUIRE((disp->attributes assert
** Description changed: + [Impact] + + * A race in the handling of the dispatcher can trigger a crash. +The reason is an assertion of a case that can actually happen (rarely +but it can) + + * The fix is very small and essentially converts the assert into an early +return here a quote of the added comment: + If the attribute DNS_DISPATCHATTR_NOLISTEN is not set, then + the dispatch is already handling a recv; return immediately. + + [Test Case] + + * That is the hardest part on this SRU, this is a race and neither in the +upstream bug [1] nor here someone was able to come up with clear repro +steps. I'm afraid we might just review code and probably keep it in +proposed some extra time? + + [Regression Potential] + + * The change is minimal and upstream (as well as in Ubuntu releases) for +quite some time now. So I'm confident it isn't entirely broken. +The old code was preventing an odd condition to happen, the new code +still does only instead of an aborting assert it now is an early +return. +The regressions I could think of are only theoretical - like someone +having a test for this and now wondering it works - not really an +issue. No really the only issue I can think of is if that early return +on the return path would trigger a bug as it e.g. can't handle the +returned null properly. But TBH that would replace one crash (the +current one) with another one, so it isn't that bad. + + [Other Info] + + * n/a + + + --- + + Ubuntu xenial 16.04, bind9 1:9.10.3.dfsg.P4-8ubuntu1.14 Yesterday the named process started crashing frequently, 49 crashes so far on 49 different servers around the world (one crash each!). We did run OS upgrades yesterday, but bind9 packages were not updated at this time. This particular bind9 package version was mostly deployed out last month. Due to the sudden surge of crashes and the distribution I'm suspecting this might be triggered remotely by an incoming packet. Backtrace from the assert: 2019-06-18T21:42:16.801421+00:00 hostname named[888]: general: critical: ../../../lib/dns/dispatch.c:3691: REQUIRE((disp->attributes & 0x0020U) != 0) failed, back trace 2019-06-18T21:42:16.801890+00:00 hostname named[888]: general: critical: #0 0x555c41aeeaf0 in ?? 2019-06-18T21:42:16.802118+00:00 hostname named[888]: general: critical: #1 0x7f475bd66eaa in ?? 2019-06-18T21:42:16.802315+00:00 hostname named[888]: general: critical: #2 0x7f475ca9f7da in ?? 2019-06-18T21:42:16.802496+00:00 hostname named[888]: general: critical: #3 0x555c41ae3195 in ?? 2019-06-18T21:42:16.802684+00:00 hostname named[888]: general: critical: #4 0x7f475bd8b420 in ?? 2019-06-18T21:42:16.802875+00:00 hostname named[888]: general: critical: #5 0x7f475b7346ba in ?? 2019-06-18T21:42:16.803056+00:00 hostname named[888]: general: critical: #6 0x7f475ae7e41d in ?? 2019-06-18T21:42:16.803245+00:00 hostname named[888]: general: critical: exiting (due to assertion failure) ** Description changed: [Impact] - * A race in the handling of the dispatcher can trigger a crash. -The reason is an assertion of a case that can actually happen (rarely -but it can) + * A race in the handling of the dispatcher can trigger a crash. + The reason is an assertion of a case that can actually happen (rarely + but it can) - * The fix is very small and essentially converts the assert into an early -return here a quote of the added comment: - If the attribute DNS_DISPATCHATTR_NOLISTEN is not set, then - the dispatch is already handling a recv; return immediately. + * The fix is very small and essentially converts the assert into an early + return here a quote of the added comment: + If the attribute DNS_DISPATCHATTR_NOLISTEN is not set, then + the dispatch is already handling a recv; return immediately. [Test Case] - * That is the hardest part on this SRU, this is a race and neither in the -upstream bug [1] nor here someone was able to come up with clear repro -steps. I'm afraid we might just review code and probably keep it in -proposed some extra time? + * That is the hardest part on this SRU, this is a race and neither in the + upstream bug [1] nor here someone was able to come up with clear repro + steps. I'm afraid we might just review code and probably keep it in + proposed some extra time? [Regression Potential] - * The change is minimal and upstream (as well as in Ubuntu releases) for -quite some time now. So I'm confident it isn't entirely broken. -The old code was preventing an odd condition to happen, the new code -still does only instead of an aborting assert it now is an early -return. -The regressions I could think of are only theoretical - like someone -having a test for this and now wondering it works -
[Bug 1833400] Re: named crashes on REQUIRE((disp->attributes assert
Andreas also reviewed the MP and I'll prep the SRU here now. @Heikki - I realized the shutdown that was mentioned is not the whole bind9, but a dispatcher. So it can happen on "lesser" restarts in the bind9 lifecycle. ** Changed in: bind9 (Ubuntu Xenial) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833400 Title: named crashes on REQUIRE((disp->attributes assert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1833400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833400] Re: named crashes on REQUIRE((disp->attributes assert
Thanks Heikki, the public bug now also is open, no repro steps there either. But I have rethought this - while this is a case without clear repro steps I think it is a bug that we can fix to help users. The severity rating of the upstream bug (now that we can see it) also goes that way. On the good side the change is really small and therefore reviewable - so I thnik we can should and go on with the SRU on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833400 Title: named crashes on REQUIRE((disp->attributes assert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1833400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836031] Re: [SRU][B/B-OEM]Fix resume failure on some TPM chips
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1836031 Title: [SRU][B/B-OEM]Fix resume failure on some TPM chips To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839006] Re: No sound is playing from this laptop
Hello Hui, I followed the steps you outlined, but my laptop still isn't playing sound. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
I had a bit of a brainwave this morning - or perhaps just awoke from my stupidity! I also have a laptop which runs ubuntu studio 19.04 amd64. At the moment, my desktop which is suffering has the 5.0.0-23-generic kernel. The laptop has the 5.0.0-21-lowlatency kernel, BUT does not have all these problems. The laptop also has gtk2 and gtk3 packages installed, although I haven't yet done a package-by-package diff. As far as I can remember, they both have mostly the same applications, although studio has a lot more. The laptop currently has upgrades waiting to be installed for the kernel, chromium, chrome and mutter (and quite a few more packages). Should I upgrade those packages on the laptop one at a time, to see whether the same problem appears? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834045] Re: Live-migration double binding doesn't work with OVN
** Also affects: neutron 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/1834045 Title: Live-migration double binding doesn't work with OVN To manage notifications about this bug go to: https://bugs.launchpad.net/networking-ovn/+bug/1834045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839239] [NEW] Sox segfault when using --norm without [=dB-level]
Public bug reported:
After applying the recent security update sox:amd64 (14.4.1-5ubuntu0.1,
14.4.1-5+deb8u4ubuntu0.1) sox now causes a segmentation fault when run
with the --norm option. If I change this to --norm=-3 it does not crash.
e.g
Running this causes a "Segmentation fault (core dumped)"
$ /usr/bin/sox ${SOURCE}*.wav ${DEST}.wav --norm
while running as follows is fine.
$ /usr/bin/sox ${SOURCE}*.wav ${DEST}.wav --norm=-3
In the documentation --norm is an allowed form of normailse.
System details:
Description:Ubuntu 16.04.6 LTS
Release:16.04
$ apt-cache policy sox
sox:
Installed: 14.4.1-5+deb8u4ubuntu0.1
Candidate: 14.4.1-5+deb8u4ubuntu0.1
Version table:
*** 14.4.1-5+deb8u4ubuntu0.1 500
500 http://au.archive.ubuntu.com/ubuntu xenial-updates/universe amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64
Packages
100 /var/lib/dpkg/status
14.4.1-5 500
500 http://au.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
** Affects: sox (Ubuntu)
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/1839239
Title:
Sox segfault when using --norm without [=dB-level]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sox/+bug/1839239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838867] Re: Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107
Same here. Machine is a quad-GPU AMD Threadripper 1950X build. Mine boots and nvidia-smi works, but any attempt to fire up a GPU workload kills the machine on something in nvidia module. See attached dmesg. The machine is headless. ** Attachment added: "dmesg.201908062033" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1838867/+attachment/5281332/+files/dmesg.201908062033 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838867 Title: Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1838867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668148] Re: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668148 Title: pci using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839236] Re: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839236 Title: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1839236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1839171] Re: segfault in i965_dri.so
On 8/6/19 9:08 AM, tomdean wrote: > This does not seem to happen with the 4.15.0-55-generic kernel. I > allowed simple_ra to run for several hours with the 4.15.0-55-generic > kernel. > Update: > uname -a Linux Meerkat 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux After running simple_ra for approx 6 hours, Aug 6 20:27:25 Meerkat kernel: [25816.744943] python2[6866]: segfault at 40 ip 7f5ff38b11c6 sp 7ffdbf5616e0 error 6 in i965_dri.so[7f5ff3271000+a6a000] So, the problem does happen with the 4.15.0-55-generic kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839171 Title: segfault in i965_dri.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831347] Re: Xorg freeze - update
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831347 Title: Xorg freeze - update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1831347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831679] Re: update-manager removes nvidia drivers
[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: update-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831679 Title: update-manager removes nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1831679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831993] Re: Cloud-init service active exited-(Active: active (exited)
[Expired for cloud-init (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831993 Title: Cloud-init service active exited-(Active: active (exited) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1831993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] [NEW] snapd disk write usage very high on 19.04 with snapd 2.39.3
Public bug reported: release: 19.04 snapd: Installed: 2.39.2+19.04 Candidate: 2.39.2+19.04 Version table: *** 2.39.2+19.04 500 500 http://mirrors.yun-idc.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.38+19.04 500 500 http://mirrors.yun-idc.com/ubuntu disco/main amd64 Packages Snapd will continue to occupy writes, the speed reaches 5M / s, but the read is 0, I can only turn off the snapd service after each system startup to ensure that my hardware is not damaged, the disk is nvme protocol ssd ** Affects: snapd (Ubuntu) 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/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839236] Re: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf
This affects bionic (https://gitlab.com/hustle-ci/autopkgtest- ubuntu/-/jobs/265419649) and disco (https://gitlab.com/hustle-ci /autopkgtest-ubuntu/-/jobs/265419647). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839236 Title: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1839236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839236] [NEW] failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf
Public bug reported: When running a patched `autopkgtest-buildvm-ubuntu-cloud` that enables constructing autopkgtest vm with minial cloud images [1], it fails to install linux-firmware at postinst stage because /etc/initramfs-tools/initramfs.conf from package initramfs-tools-core may not have been installed: ``` cloud-init[528]: Setting up linux-firmware (1.173.9) ... cloud-init[528]: update-initramfs: Generating /boot/initrd.img-4.15.0-1039-kvm cloud-init[528]: /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf cloud-init[528]: update-initramfs: failed for /boot/initrd.img-4.15.0-1039-kvm with 2. cloud-init[528]: dpkg: error processing package linux-firmware (--configure): cloud-init[528]: installed linux-firmware package post-installation script subprocess returned error exit status 2 ``` See https://gitlab.com/hustle-ci/autopkgtest-ubuntu/-/jobs/265419649 for full log. [1]: https://cloud-images.ubuntu.com/minimal/daily/ ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Patch added: "patch to add --minimal to autopkgtest-buildvm-ubuntu-cloud" https://bugs.launchpad.net/bugs/1839236/+attachment/5281331/+files/autopkgtest-buildvm-ubuntu-cloud.patch ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) 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/1839236 Title: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1839236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839086] Re: bionic/linux-gke-5.0: 5.0.0-1013.13~18.04.1 -proposed tracker
** 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/1839086 Title: bionic/linux-gke-5.0: 5.0.0-1013.13~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839085] Re: bionic/linux-aws: 4.15.0-1045.47 -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 backports: bug 1839083 (xenial/linux-aws-hwe) derivatives: bug 1839081 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839122 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:16 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 trackers: bionic/linux-aws/aws-kernel: bug 1839081 xenial/linux-aws-hwe: bug 1839083 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839085 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839086] Re: bionic/linux-gke-5.0: 5.0.0-1013.13~18.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 derivatives: bug 1839084 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839093 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 phase: Testing phase-changed: Tuesday, 06. August 2019 19:28 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress promote-to-updates: Pending -- Nvidia objects not found -- current-driver-5.0.0-1013-gke-d1809-0-amd64 regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gke-5.0/gke-kernel: bug 1839084 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839086 Title: bionic/linux-gke-5.0: 5.0.0-1013.13~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839085] Re: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker
** 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/1839085 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839083] Re: xenial/linux-aws-hwe: 4.15.0-1045.47~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 -- kernel-stable-master-bug: 1839085 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Tuesday, 06. August 2019 19:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839083 Title: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839083] Re: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker
** 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/1839083 Title: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839235] [NEW] Opening an NEF raw (Nikon) file in ufraw leads to this error: "'file-ufraw-load' returned no return values"
Public bug reported: Steps: 1. Open NEF file in Gimp. 2. Press "OK" Gimp produces this error and does not load image: Opening '/home/bbogart/tmp/DSC_0002.NEF' failed: Procedure 'file-ufraw- load' returned no return values ufraw-batch segfaults on the NEF file: Program received signal SIGSEGV, Segmentation fault. 0x771b1b64 in lfModifier::~lfModifier() () from /usr/lib/x86_64-linux-gnu/liblensfun.so.1 (gdb) bt #0 0x771b1b64 in lfModifier::~lfModifier() () from /usr/lib/x86_64-linux-gnu/liblensfun.so.1 #1 0x771b1b89 in lfModifier::Destroy() () from /usr/lib/x86_64-linux-gnu/liblensfun.so.1 #2 0x555f557a in ?? () #3 0x555f01ca in ?? () #4 0x75503b97 in __libc_start_main (main=0x555f, argc=4, argv=0x7fffe068, init=, fini=, rtld_fini=, stack_end=0x7fffe058) at ../csu/libc-start.c:310 #5 0x555f265a in ?? () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gimp-ufraw 0.22-3.1~build0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 6 19:44:38 2019 InstallationDate: Installed on 2019-02-09 (179 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ufraw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufraw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839235 Title: Opening an NEF raw (Nikon) file in ufraw leads to this error: "'file- ufraw-load' returned no return values" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufraw/+bug/1839235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773967] Re: Application credentials can't be used with group-only role assignments
** Also affects: keystone (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-archive 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/1773967 Title: Application credentials can't be used with group-only role assignments To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1773967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839006] Re: No sound is playing from this laptop
The audio on your machine is Intel ASoC audio, it is not Intel HDA audio. you need to add ucm conf files specific to this machine: git clone git://git.alsa-project.org/alsa-lib.git cd alsa-lib backup all contents in the folder of /usr/share/alsa/ucm/ sudo cp -rf src/conf/ucm/bytcht-es8316* /usr/share/alsa/ucm/ reboot #check if audio works To restore to original state: restore all contents in the folder of /usr/share/alsa/ucm reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832087] Re: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16
Close as INVALID for the fix is already released at least in 5.0.0-23, though I cannot reproduce this with all the kernel versions listed in comment #30. ** Changed in: linux (Ubuntu) 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/1832087 Title: Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839136] Re: Temporary freeze / delay with some dialog windows
Please start by uninstalling the extra extensions you have: 'gpa...@gnome-shell-extensions.gnome.org' 'user-th...@gnome-shell-extensions.gcampax.github.com' 'no-title-...@franglais125.gmail.com' 'emoji-selec...@maestroschan.fr' 'indica...@johannes.super-productivity.com' 'window-corner-prev...@fabiomereu.it' 'topIcons@adel.gadl...@gmail.com' 'topic...@phocean.net' 'windowIsReady_Remover@lo...@linuxuprising.com' 'mediapla...@patapon.info' 'messagingm...@screenfreeze.net' 'perfect-osd' 'grilo_search_provi...@awamper.gmail.com' 'obmin@konkor' 'dock-settings@lagrangian' 'places-and-files-on-desk...@maestroschan.fr' 'animation-tweaks@Selenium-H' 'minimize-to-t...@elhan.io' 'transparent-win...@pbxqdown.github.com' 'gnom...@panacier.gmail.com' 'dash-to-pa...@jderose9.github.com' We find a large number of bugs are caused by extensions so need to rule those out as a cause before anything else. ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839136 Title: Temporary freeze / delay with some dialog windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1839136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839174] Re: Xorg crashes - segfault error 6 in libc-2.27.so
Thanks for the bug report. I can't seem to find any similar crash reports on: https://errors.ubuntu.com/?release=Ubuntu%2018.04=xorg- server=year Can you please follow these instructions to try and generate a formal crash report? https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment I would like it to confirm exactly what is crashing and where... ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839174 Title: Xorg crashes - segfault error 6 in libc-2.27.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1839174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839233] [NEW] /usr/bin/sonic-pi:11:std::basic_streambuf:std::ostream::flush:std::ios_base::Init::~Init:__run_exit_handlers:__GI_exit
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding sonic-pi. This problem was most recently seen with package version 2.10.0~repack-2.1, the problem page at https://errors.ubuntu.com/problem/47d2ebcb40095412e05d3577b5c529acdab8277e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: sonic-pi (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839233 Title: /usr/bin/sonic- pi:11:std::basic_streambuf:std::ostream::flush:std::ios_base::Init::~Init:__run_exit_handlers:__GI_exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sonic-pi/+bug/1839233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
This bug was fixed in the package gnome-flashback - 3.28.0-1ubuntu1.4 --- gnome-flashback (3.28.0-1ubuntu1.4) bionic; urgency=medium * Backport two upstream commits to fix ibus indicator flickering (LP: #1836659). -- Dmitry Shachnev Tue, 23 Jul 2019 16:09:36 +0300 ** Changed in: gnome-flashback (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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836659] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox again
This bug was fixed in the package gnome-flashback - 3.30.0-1ubuntu6.1 --- gnome-flashback (3.30.0-1ubuntu6.1) disco; urgency=medium * Backport two upstream commits to fix ibus indicator flickering (LP: #1836659). -- Dmitry Shachnev Tue, 23 Jul 2019 16:16:52 +0300 ** Changed in: gnome-flashback (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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836659] Update Released
The verification of the Stable Release Update for gnome-flashback 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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1836659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830341] Re: [SRU] queens stable releases
This bug was fixed in the package cinder - 2:12.0.7-0ubuntu2 --- cinder (2:12.0.7-0ubuntu2) bionic; urgency=medium * d/cinder-common.install: Install of resource_filters.json. cinder (2:12.0.7-0ubuntu1) bionic; urgency=medium * New stable point release for OpenStack Queens (LP: #1830341). -- Sahid Orentino Ferdjaoui Thu, 04 Jul 2019 11:47:37 +0200 ** Changed in: cinder (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/1830341 Title: [SRU] queens stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1830341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839231] [NEW] updating bionic to 237-3ubuntu10.25 restarts systemd-networkd
Public bug reported: I updated my Ubuntu 18.04.2 server from systemd 237-3ubuntu10.24 to 237-3ubuntu10.25. This caused a restart of systemd-networkd, breaking all TCP-over-IPv6 connections. apt history entry: Start-Date: 2019-08-06 19:46:21 Commandline: apt-get dist-upgrade -y Requested-By: shivaram (1000) Upgrade: libsystemd0:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), udev:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libudev1:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd-sysv:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libpam-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libnss-systemd:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), base-files:amd64 (10.1ubuntu2.5, 10.1ubuntu2.6) End-Date: 2019-08-06 19:54:17 systemd journal output: Aug 06 19:47:40 pentos systemd[1]: Reloading. Aug 06 19:47:57 pentos systemd[1]: Reexecuting. Aug 06 19:47:58 pentos systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hie Aug 06 19:47:58 pentos systemd[1]: Detected architecture x86-64. Aug 06 19:47:58 pentos systemd[1]: Stopping Network Service... Aug 06 19:47:58 pentos systemd[1]: Stopped Network Service. Aug 06 19:47:58 pentos systemd[1]: Starting Network Service... Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Gained IPv6LL Aug 06 19:47:59 pentos systemd-networkd[11513]: Enumeration completed Aug 06 19:47:59 pentos systemd[1]: Started Network Service. Aug 06 19:47:59 pentos systemd-networkd[11513]: lo: Link is not managed by us Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: DHCPv4 address 192.168.1.103/24 via 192.168.1.1 Aug 06 19:47:59 pentos dbus-daemon[947]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2341' (uid=100 pid=11513 comm="/lib/systemd/systemd-network Aug 06 19:47:59 pentos systemd-networkd[11513]: ens5: Configured ** Affects: systemd (Ubuntu) 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/1839231 Title: updating bionic to 237-3ubuntu10.25 restarts systemd-networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813063] Update Released
The verification of the Stable Release Update for ndiswrapper 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/1813063 Title: ndiswrapper 1.60-6 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1813063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813063] Re: ndiswrapper 1.60-6 ADT test failure with linux 5.0.0-1.2
This bug was fixed in the package ndiswrapper - 1.60-6ubuntu0.1 --- ndiswrapper (1.60-6ubuntu0.1) bionic; urgency=medium * Fix build for 5.0 (LP: #1813063) -- Connor Kuehl Thu, 09 May 2019 14:40:40 -0700 ** Changed in: ndiswrapper (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/1813063 Title: ndiswrapper 1.60-6 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1813063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832265] Re: py3: inconsistent encoding of token fields
James, I have the same issue. Which package do you want the version on? We have a PoC on Rocky using this charm and have this exact issue. Do we put this repository on the controllers or everywhere (compute nodes, ceph, etc.)? 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/1832265 Title: py3: inconsistent encoding of token fields To manage notifications about this bug go to: https://bugs.launchpad.net/charm-keystone-ldap/+bug/1832265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839082] Re: disco/linux-azure: 5.0.0-1014.14 -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 backports: bug 1839079 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 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 stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839079 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839082 Title: disco/linux-azure: 5.0.0-1014.14 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839082] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** 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/1839082 Title: disco/linux-azure: 5.0.0-1014.14 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839080] Re: bionic/linux-oem: 4.15.0-1049.56 -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 -- kernel-stable-master-bug: 1839122 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Tuesday, 06. August 2019 19:49 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 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839080 Title: bionic/linux-oem: 4.15.0-1049.56 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839228] [NEW] package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: When installing Lubuntu 18.04 on a lenovo ideapad 320-15iap laptop..install always hangs at "installing grub2 package". I've tried multiple times, with fastboot on and off, secure boot on and off, etc. I have even tried boot repair, with no success. I'm using grub2win just to be able to boot into Lubuntu. I have tried the forums for help and all the the suggestions were unsuccessful. I would like to use linux systems more so I can hopefully move away from windows once and for all, and while I've found a temporary fix, I would prefer everything be right. Thanks in advance for looking into this and any assistance you can offer. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 6 17:55:36 2019 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839228 Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1839228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829942] Re: Address performance issue w/ GICv4-based guests
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829942 Title: Address performance issue w/ GICv4-based guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823037] Re: amd_iommu possible data corruption
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830813] Re: TCP : race condition on socket ownership in tcp_close()
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830813 Title: TCP : race condition on socket ownership in tcp_close() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839080] Re: bionic/linux-oem: 4.15.0-1049.56 -proposed tracker
** 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/1839080 Title: bionic/linux-oem: 4.15.0-1049.56 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839079] Re: bionic/linux-azure: 5.0.0-1014.14~18.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 derivatives: bug 1839074 (azure-kernel), bug 1839075 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839082 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:26 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 stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839074 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839079 Title: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839079] Re: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker
** 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/1839079 Title: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839083] Re: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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-stable-master-bug: 1839085 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Testing phase-changed: Tuesday, 06. August 2019 19:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839083 Title: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1839024] Re: display flickering in perpetual loo
Thank you for your reply.The problem does not happen every time I start the laptop. It has not happened again. I will take a snap next time it occurs...Have a good time!Carlos Suárez V Original message From: Daniel van Vugt Date: 8/5/19 21:10 (GMT-05:00) To: cesuare...@unal.edu.co Subject: [Bug 1839024] Re: display flickering in perpetual loo If possible, please also take a video of the problem with a phone andthen attach the video here.** Package changed: xorg (Ubuntu) => linux (Ubuntu)** Summary changed:- display flickering in perpetual loop while starting ubuntu 18.04.2+ [i915] display flickering in perpetual loop while starting ubuntu 18.04.2-- You received this bug notification because you are subscribed to the bugreport.https://bugs.launchpad.net/bugs/1839024Title: [i915] display flickering in perpetual loop while starting ubuntu 18.04.2Status in linux package in Ubuntu: NewBug description: gnome 3.28.2 Laptop needs to be re-started ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 5 14:04:47 2019 DistUpgraded: 2019-03-08 20:01:34,757 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3649] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3649] InstallationDate: Installed on 2018-02-07 (544 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP Pavilion dm3 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=74d5e8df-abd0-45c0-a0c6-ca60e2f84b67 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-09 (149 days ago) dmi.bios.date: 08/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3649 dmi.board.vendor: Flextronics dmi.board.version: 41.3A dmi.chassis.type: 10 dmi.chassis.vendor: Flextronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd08/12/2009:svnHewlett-Packard:pnHPPaviliondm3NotebookPC:pvr03A01024001011012:rvnFlextronics:rn3649:rvr41.3A:cvnFlextronics:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dm3 Notebook PC dmi.product.version: 03A01024001011012 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 8 17:47:08 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modesetTo manage notifications about this bug go to:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839024/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839024 Title: [i915] display flickering in perpetual loop while starting ubuntu 18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839075] Re: bionic/linux-azure-edge: 5.0.0-1014.14~18.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 -- kernel-stable-master-bug: 1839079 packages: meta: linux-meta-azure-edge - phase: Signoff - phase-changed: Tuesday, 06. August 2019 21:18 UTC + phase: Ready for Testing + phase-changed: Tuesday, 06. August 2019 23:10 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 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839075 Title: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839075] Re: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker
** 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/1839075 Title: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816468] Re: [SRU] Acceleration cinder - glance with ceph not working
** Tags removed: verification-rocky-failed ** Tags added: verification-rocky-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816468 Title: [SRU] Acceleration cinder - glance with ceph not working To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1816468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816468] Re: [SRU] Acceleration cinder - glance with ceph not working
Bionic + Stein verified (nova) using [Test Case] Test Output: root@juju-7f1874-lp1816468-sru-stein-0:~# rbd -p nova info 2923df76-c175-4862-a61a-71207390b4cb_disk| grep parent parent: glance/2ea4abff-a978-4b99-b717-5a3c8932b6f6@snap ** Tags removed: verification-stein-needed ** Tags added: verification-stein-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816468 Title: [SRU] Acceleration cinder - glance with ceph not working To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1816468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839225] [NEW] texlive-pstricks is missing a depedency on texlive-luatex
Public bug reported: /usr/share/texlive/texmf-dist/tex/latex/pst-pdf/pst-pdf.sty contains a reference to luatex85.sty which is found in texlive-luatex. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: texlive-pstricks 2018.20190227-1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Aug 6 18:38:52 2019 PackageArchitecture: all SourcePackage: texlive-extra UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839225 Title: texlive-pstricks is missing a depedency on texlive-luatex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1839225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839226] [NEW] Failed to install GRUB on a stripped RAID partition
Public bug reported: MAchine had RAID SATA drives, and I've swapped them out for two SSD? Now this? Headache ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 18:42:09 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839226 Title: Failed to install GRUB on a stripped RAID partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1839226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -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 backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** 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/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839214] Re: Setting vm.overcommit_kbytes = 0 made the entire system explode.
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839214 Title: Setting vm.overcommit_kbytes = 0 made the entire system explode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839208] Re: Upgrade from 16.04 to 18.04 failed.
There seems to have been an issue communicating with the mirror of the Ubuntu archive which you have configured. 2019-08-06 17:37:06,370 DEBUG examining: 'deb http://nl.archive.ubuntu.com/ubuntu/ xenial main restricted' 2019-08-06 17:37:06,370 DEBUG verifySourcesListEntry: deb http://nl.archive.ubuntu.com/ubuntu/ bionic main restricted 2019-08-06 17:37:06,370 DEBUG url_downloadable: http://nl.archive.ubuntu.com/ubuntu//dists/bionic/Release 2019-08-06 17:37:06,370 DEBUG s='http' n='nl.archive.ubuntu.com' p='/ubuntu//dists/bionic/Release' q='' f='' 2019-08-06 17:39:13,639 DEBUG error from httplib: '' ** Changed in: ubuntu-release-upgrader (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/1839208 Title: Upgrade from 16.04 to 18.04 failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1839208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838434] Re: linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+
@Georgi, I just noticed your comment "Reverting to 5.0.0-1012 is ok.", please ignore my last question. I'm seeing if I can reproduce your problem on a Rpi3b+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838434 Title: linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839070] Re: bionic/linux-aws-edge: 5.0.0-1012.13~18.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 -- kernel-stable-master-bug: 1839072 packages: main: linux-aws-edge meta: linux-meta-aws-edge phase: Testing phase-changed: Tuesday, 06. August 2019 19:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839070 Title: bionic/linux-aws-edge: 5.0.0-1012.13~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839070] Re: bionic/linux-aws-edge: 5.0.0-1012.13~18.04.1 -proposed tracker
** 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/1839070 Title: bionic/linux-aws-edge: 5.0.0-1012.13~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -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 derivatives: bug 1837596 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839119 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Tuesday, 30. July 2019 22:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1837596 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837598 Title: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839075] Re: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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 -- kernel-stable-master-bug: 1839079 packages: meta: linux-meta-azure-edge - phase: Ready for Packaging - phase-changed: Tuesday, 06. August 2019 19:33 UTC + phase: Signoff + phase-changed: Tuesday, 06. August 2019 21:18 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - prepare-package-meta: Pending -- version not specified + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839075 Title: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839120] Re: xenial/linux-hwe-edge: 4.15.0-57.63~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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 -- kernel-stable-master-bug: 1839121 packages: meta: linux-meta-hwe-edge - phase: Ready for Packaging - phase-changed: Tuesday, 06. August 2019 19:32 UTC + phase: Signoff + phase-changed: Tuesday, 06. August 2019 21:17 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - prepare-package-meta: Pending -- version not specified + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839120 Title: xenial/linux-hwe-edge: 4.15.0-57.63~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839114] Re: xenial/linux-azure-edge: 4.15.0-1054.59 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Invalid => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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 -- kernel-stable-master-bug: 1839118 packages: meta: linux-meta-azure-edge - phase: Ready for Packaging - phase-changed: Tuesday, 06. August 2019 19:31 UTC + phase: Signoff + phase-changed: Tuesday, 06. August 2019 21:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - prepare-package-meta: Pending -- version not specified + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839114 Title: xenial/linux-azure-edge: 4.15.0-1054.59 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker
** 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/1837594 Title: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -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 derivatives: bug 1837592 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839119 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Signoff - phase-changed: Tuesday, 06. August 2019 20:04 UTC + phase: Ready for Testing + phase-changed: Tuesday, 06. August 2019 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1837592 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837594 Title: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker
** 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/1837598 Title: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839075] Re: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure-edge: -proposed tracker + bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839075 Title: bionic/linux-azure-edge: 5.0.0-1014.14~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839114] Re: xenial/linux-azure-edge: 4.15.0-1054.59 -proposed tracker
** Summary changed: - xenial/linux-azure-edge: -proposed tracker + xenial/linux-azure-edge: 4.15.0-1054.59 -proposed tracker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839114 Title: xenial/linux-azure-edge: 4.15.0-1054.59 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839220] Re: Installation on EFI-requiring hardware requires expert intervention
As a side-note, ideally the installer would be enough also to detect what filesystems are compatible with rEFInd, and give an error if you select them for installation. For example, XFS is not compatible with rEFInd. This implies the EFI detection/question would need to be presented before the partitioning step. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839220 Title: Installation on EFI-requiring hardware requires expert intervention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1839220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839120] Re: xenial/linux-hwe-edge: 4.15.0-57.63~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-hwe-edge: -proposed tracker + xenial/linux-hwe-edge: 4.15.0-57.63~16.04.1 -proposed tracker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839120 Title: xenial/linux-hwe-edge: 4.15.0-57.63~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839220] [NEW] Installation on EFI-requiring hardware requires expert intervention
Public bug reported: This issue is based on my experience installing onto an iMac, which absolutely requires EFI boot. I don't know how well this applies to the broader world of "PCs", I believe some of these either require EFI too, or at least by default have it set in the firmware settings to require it. I apologise if I'm not entirely aware of the EFI capabilities (if any) of the installer, I'm just going from my personal experience trying to install in a normal way. Launching the installer from a USB stick was no problem. At the end of the installer it asks (I'm going from memory) about where to install the grub bootloader. However (unless I am misunderstanding something), this is never going to work for an EFI-only machine. So it's leading the user down a path that will not work for them, and not providing the path they do need. What the installer should ideally do is ideally detect which machines require EFI - or failing that, just provide an EFI option with some advice. The EFI option would install rEFInd automatically, instead of Grub. Even better is if it could even detect all available FAT partitions and ask which to install EFI to (with detection what the current EFI partition is, for the default). ** Affects: debian-installer (Ubuntu) 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/1839220 Title: Installation on EFI-requiring hardware requires expert intervention To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1839220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836949] Re: mtu gets lost in translation from netplan (v2) yaml
This bug was fixed in the package cloud-init - 19.2-5-g496aaa94-0ubuntu1 --- cloud-init (19.2-5-g496aaa94-0ubuntu1) eoan; urgency=medium * New upstream snapshot. - net/cmdline: split interfaces_by_mac and init network config determination - stages: allow data sources to override network config source order - cloud_tests: updates and fixes - Fix bug rendering MTU on bond or vlan when input was netplan. [Scott Moser] (LP: #1836949) - net: update net sequence, include wait on netdevs, opensuse netrules path (LP: #1817368) -- Chad Smith Tue, 06 Aug 2019 13:56:18 -0600 ** Changed in: cloud-init (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/1836949 Title: mtu gets lost in translation from netplan (v2) yaml To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1836949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839219] [NEW] "minimum alignment" check has multiple issues
Public bug reported: I was installing to an external SSD, HP P600 to be specific. This is an annoying bit of hardware, as it's actually 2 125GB SSDs in a single case, so functions as 2 drives. The message... "The partition ... starts at an offset of 3584 bytes from the minimum alignment for this disk, which may lead to very poor performance. Since you are formatting this partition, you should correct this problem now by realigning the partition, as it will be difficult to change later. To do this, go back to the main partitioning menu, delete the partition, and recreate it in the same position with the same settings. This will cause the partition to start at a point best suited for this disk" There are 2 options "Go Back" and "Continue". The issues... 1) Both buttons "Go Back", there is no way to ignore the error and continue. So you need to either only have the "Go Back" button, or truly allow the user to ignore the issue. 2) The advice is incorrect. Recreating the partition does not solve the problem. The problem was with the default partition table on the devices. I have no idea why it was like that, but the resolution was to wipe the partition table, not just recreate the partition without the existing table. This was not trivial to work out, I was messing around trying to find what to do for a while. ** Affects: debian-installer (Ubuntu) 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/1839219 Title: "minimum alignment" check has multiple issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1839219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839213] Re: Bionic update: upstream stable patchset 2019-08-06
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-08-06 -Ported from the following upstream stable releases: -v4.19.63, - v4.14.136, v4.19.64 + Ported from the following upstream stable releases: + v4.19.63, + v4.14.136, v4.19.64 from git://git.kernel.org/ + + staging: vt6656: use meaningful error code during buffer allocation + drm/amd/display: Fill prescale_params->scale for RGB565 + drm/amd/display: Disable ABM before destroy ABM struct + gpu: host1x: Increase maximum DMA segment size + drm/amd/display: Always allocate initial connector state state + drm/amd/display: fix compilation error + mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width + i2c: stm32f7: fix the get_irq error cases + genksyms: Teach parser about 128-bit built-in types + powerpc/mm: Handle page table allocation failures + arm64: assembler: Switch ESB-instruction with a vanilla nop if !ARM64_HAS_RAS + dlm: check if workqueues are NULL before flushing/destroying + proc: use down_read_killable mmap_sem for /proc/pid/pagemap + proc: use down_read_killable mmap_sem for /proc/pid/clear_refs + proc: use down_read_killable mmap_sem for /proc/pid/map_files + proc: use down_read_killable mmap_sem for /proc/pid/maps + mm: use down_read_killable for locking mmap_sem in access_remote_vm + ALSA: ac97: Fix double free of ac97_codec_device + libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl() + vsock: correct removal of socket from the list + NFS: Fix dentry revalidation on NFSv4 lookup + NFS: Refactor nfs_lookup_revalidate() + NFSv4: Fix lookup revalidate of regular files + i2c: qup: fixed releasing dma without flush operation completion + arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ + binder: fix possible UAF when freeing buffer + ISDN: hfcsusb: checking idx of ep configuration + media: au0828: fix null dereference in error path + ath10k: Change the warning message string + media: cpia2_usb: first wake up, then free in disconnect + media: pvrusb2: use a different format for warnings + NFS: Cleanup if nfs_match_client is interrupted + media: radio-raremono: change devm_k*alloc to k*alloc + iommu/vt-d: Don't queue_iova() if there is no flush queue + iommu/iova: Fix compilation error with !CONFIG_IOMMU_IOVA + hv_sock: Add support for delayed close + Bluetooth: hci_uart: check for missing tty operations + sched/fair: Don't free p->numa_faults with concurrent readers + drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl + Fix allyesconfig output. + ip_tunnel: allow not to count pkts on tstats by setting skb's dev to NULL + UBUNTU: upstream stable to v4.14.136, v4.19.64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839213 Title: Bionic update: upstream stable patchset 2019-08-06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839216] Missing required logs.
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 1839216 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839216 Title: xenial VM hangs copying block device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838836] Re: network-manager needs to be restarted frequently
I do not really see in the log snippets where the Wi-Fi does not actually work, or which step of the Wi-Fi connection attempt fails. Perhaps the relevant part is not included. You write: -- Jul 16 19:20:34 serval NetworkManager[617]: [1563330034.2504] device (p2p-dev-wlp62s0): supplicant management interface state: associating -> associated ``` ...snip... ``` Jul 16 19:20:45 serval NetworkManager[617]: [1563330045.2179] supplicant: wpa_supplicant die count reset -- Could you also post the part which you have cut away here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838836 Title: network-manager needs to be restarted frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 641899] Re: Ubuntu Software Center is very slow
It's definitely important to stress test things on a poor quality slow connection. Imagine a new user setting up Ubuntu for a first time, already a bit overwhelmed by everything, and they've just got Dropbox setup and hogging network resources as it downloads many GB of data, while they continue to search for and install apps. There are a few different issues I'm seeing, which I agree would be best posted separately (triage?), but as this issue already exists I'll post it in here... 1) The Install button really needs to be smart. If you go back and forward again, it needs to be at least greyed out if the software in question is already installing or in a queue to be installed. 2) If you do a search, the progress spinner should activate immediately. Currently it lags a bit. A user on a slow connection and bogged down machine has no idea if the extended lag is due to bugs, failed searches, back-logged search requests, or system slow-down. 3) I believe (but could be wrong) that in the current implementation it's possible for a search to come in after the search field has been changed to something else already, due to lag. That should never be possible - if the activate contents of the search field is not a superstring of what a search result has come in for, don't show that search result. 4) Ideally there would also be an installation queue tab so you can see what's in progress. You don't know as a user what has stalled, vs what is just being slow, vs what is back-logged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/641899 Title: Ubuntu Software Center is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/641899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834340] Re: Possible regression on libssl upgrade when using TLSv1.3
Another small update to the patch, just in case anyone wants to build it against OpenSSL versions older than 1.0.2 (let's say on Ubuntu 12.04). It now checks for the OpenSSL version instead of for SSL_CTRL_SET_TLSEXT_HOSTNAME (which has been around since 0.9.8.something, so this change is safe in that regard). The a2i_IPADDRESS function was introduced in 1.0.2; the patch calls it to determine if the ServerName TLS extension info should be set (SNI is not allowed for IP addresses, just for hostnames). For anything before OpenSSL 1.0.2 (because a2i_IPADDRESS is not available there), SNI wouldn't be done. Since nothing before OpenSSL 1.1.1 supports TLSv1.3 anyway (and that's when the problem occurs in the first place), that approach seems better. P.S. have the info on a2i_IPADDRESS version availability from https://github.com/python/cpython/commit/e9370a47389903bb72badc95032ec84a0ebbf8cc, which does even more extra correct things for ancient OpenSSL versions, but that doesn't apply to Ubuntu. ** Patch added: "uw-imap-sni.v3.patch" https://bugs.launchpad.net/ubuntu/+source/uw-imap/+bug/1834340/+attachment/5281308/+files/uw-imap-sni.v3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834340 Title: Possible regression on libssl upgrade when using TLSv1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-imap/+bug/1834340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837586] Re: bionic/linux-raspi2: 4.15.0-1042.45 -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 derivatives: bug 1837584 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839122 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 29. July 2019 09:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1837584 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837586 Title: bionic/linux-raspi2: 4.15.0-1042.45 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -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 derivatives: bug 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839122 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Signoff - phase-changed: Monday, 05. August 2019 16:35 UTC + phase: Ready for Testing + phase-changed: Tuesday, 06. August 2019 20:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839116] Re: trusty/linux-azure: 4.15.0-1054.59~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839118 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Tuesday, 06. August 2019 19:31 UTC + phase: Ready for Testing + phase-changed: Tuesday, 06. August 2019 20:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839116 Title: trusty/linux-azure: 4.15.0-1054.59~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839155] Re: xenial/linux-fips: 4.4.0-1017.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Tuesday, 06. August 2019 19:14 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 06. August 2019 20:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: + automated-testing: Ongoing -- testing in progress prepare-package: Stalled -- package tag not yet published prepare-package-meta: Stalled -- package tag not yet published prepare-package-signed: Stalled -- package tag not yet published - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839155 Title: xenial/linux-fips: 4.4.0-1017.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839163] Re: bionic/linux-fips: 4.15.0-1014.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839122 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Tuesday, 06. August 2019 19:23 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 06. August 2019 20:32 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: + automated-testing: Ongoing -- testing in progress prepare-package: Stalled -- package tag not yet published prepare-package-meta: Stalled -- package tag not yet published prepare-package-signed: Stalled -- package tag not yet published - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839163 Title: bionic/linux-fips: 4.15.0-1014.17 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839216] [NEW] xenial VM hangs copying block device
Public bug reported: With a Xenial kernel running in a VM (32 cores and 65536 MB RAM), the following script hangs in the dd command: == #!/bin/bash dd if=/dev/zero of=in.bin bs=1 seek=6442506751 count=1 cp in.bin out.bin IN=$(losetup --show -f in.bin) OUT=$(losetup --show -f out.bin) typeset -i i=1 while true; do echo $i $(date) dd if=$IN of=$OUT bs=128k i=i+1 done == The trace (sorry, I don't have the exact kernel version... I found this mid-June 2019) looks like: # cat /proc/5230/stack [<0>] io_schedule+0x16/0x40 [<0>] wbt_wait+0x234/0x390 [<0>] blk_mq_make_request+0x103/0x590 [<0>] generic_make_request+0x122/0x2f0 [<0>] submit_bio+0x73/0x150 [<0>] submit_bh_wbc+0x17a/0x1b0 [<0>] __block_write_full_page+0x15b/0x400 [<0>] block_write_full_page+0x10c/0x130 [<0>] blkdev_writepage+0x18/0x20 [<0>] __writepage+0x1d/0x50 [<0>] write_cache_pages+0x228/0x4b0 [<0>] generic_writepages+0x5c/0x90 [<0>] blkdev_writepages+0x2f/0x40 [<0>] do_writepages+0x1f/0x70 [<0>] __filemap_fdatawrite_range+0xc6/0x100 [<0>] filemap_write_and_wait+0x31/0x90 [<0>] __blkdev_put+0x7a/0x210 [<0>] blkdev_put+0x4c/0xd0 [<0>] blkdev_close+0x34/0x70 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9a/0xc0 [<0>] exit_to_usermode_loop+0xce/0xd0 [<0>] do_syscall_64+0x116/0x150 [<0>] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [<0>] 0x If we have used strace on the process, we find that dd is inside "close(1)" as it closes the output file. I don't know if this would reproduce on actual hardware, as I don't have a machine that large to play with. ** Affects: linux (Ubuntu) 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/1839216 Title: xenial VM hangs copying block device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839117] Re: trusty/linux-lts-xenial: 4.4.0-159.187~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-lts-xenial meta: linux-meta-lts-xenial signed: linux-signed-lts-xenial - phase: Promote to Proposed - phase-changed: Tuesday, 06. August 2019 19:12 UTC + phase: Ready for Testing + phase-changed: Tuesday, 06. August 2019 20:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839117 Title: trusty/linux-lts-xenial: 4.4.0-159.187~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839217] [NEW] Bad user experience choosing partition labels
Public bug reported: For FAT partitions, labels have to be upper case. FAT is the default for a new partition, but the default example label is mixed case. This means just going on recommendation, it's not going to work out, and the user will get an error message. A better user experience would be to simply tell the user that their label will be made upper case, and ask them to confirm with yes/no. Or just do it without asking TBH because I think upper-casing it by default is a pretty harmless thing. ** Affects: gnome-disk-utility (Ubuntu) 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/1839217 Title: Bad user experience choosing partition labels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1839217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839107] Re: xenial/linux-aws: 4.4.0-1090.101 -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 derivatives: bug 1839104 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 06. August 2019 19:10 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 trackers: xenial/linux-aws/aws-kernel: bug 1839104 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839107 Title: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839190] Re: crash when doing "sudo do-release-upgrade" to upgrade my ubuntu 17.10 to 18.04
** Tags added: artful2bionic ** Tags added: third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839190 Title: crash when doing "sudo do-release-upgrade" to upgrade my ubuntu 17.10 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1839190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker
** 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/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839107] Re: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker
** 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/1839107 Title: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839211] Re: Upgrade to 2.2.1-1
** Attachment added: "Captura de pantalla de 2019-08-06 16-20-51.png" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+attachment/5281307/+files/Captura%20de%20pantalla%20de%202019-08-06%2016-20-51.png ** Summary changed: - Upgrade to 2.2.1-1 + Upgrade to 2.2.1-1(Debian) ** Summary changed: - Upgrade to 2.2.1-1(Debian) + Please upgrade to 2.2.1-1(Debian) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Please upgrade to 2.2.1-1(Debian) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839208] Re: Upgrade from 16.04 to 18.04 failed.
** Tags added: xenial2bionic ** Tags added: third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839208 Title: Upgrade from 16.04 to 18.04 failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1839208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
