[Bug 1833618] Re: MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case).
@rharper: feel free to review the MR for Disco and Bionic (they're basically the same). server-hwe team: feel free to test version from the PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1833618 I think this is it, if no bad feedback, SRU is good to go in my POV. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833618 Title: MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case). To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1833618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844559] Re: [GLK-R]enable CPUID
Is it for J32363-201 board that we've received 2y ago? I don't think we have tools to update the firmware on it to support GLK-R -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844559 Title: [GLK-R]enable CPUID To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1844559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762835] Re: Conflicting mmc modules built in
** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762835 Title: Conflicting mmc modules built in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
There appear to be no bug reports from 18.04 either. Although I could make a patch for 18.04, it would never get released unless someone was able to reproduce the bug and verify it. ** Changed in: mutter (Ubuntu Bionic) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)
** Also affects: fftw3 via https://github.com/FFTW/fftw3/issues/182 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843733 Title: fftw3 ftbfs in eoan (armhf only) To manage notifications about this bug go to: https://bugs.launchpad.net/fftw3/+bug/1843733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797975] Re: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting
*** This bug is a duplicate of bug 1762835 *** https://bugs.launchpad.net/bugs/1762835 ** Changed in: linux (Ubuntu) Status: Triaged => Confirmed ** This bug has been marked a duplicate of bug 1762835 Conflicting mmc modules built in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797975 Title: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762835] Re: Conflicting mmc modules built in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762835 Title: Conflicting mmc modules built in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833618] Re: MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case).
Provided a fix for Ubuntu Disco at the PPA and pushed changes into the merge request. --- # Ubuntu Disco (showing the problem) kernel: usb 2-6: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd kernel: usb 2-6: New USB device found, idVendor=1b1c, idProduct=1a0c, bcdDevice= 1.00 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 2-6: Product: Voyager Mini 3.0 kernel: usb 2-6: Manufacturer: Corsair kernel: usb 2-6: SerialNumber: 070851D0E490C776 mtp-probe[17351]: checking bus 2, device 3: "/sys/devices/pci:00/:00:14.0/usb2/2-6" mtp-probe[17351]: bus: 2, device: 3 was not an MTP device kernel: usb-storage 2-6:1.0: USB Mass Storage device detected kernel: scsi host2: usb-storage 2-6:1.0 kernel: usbcore: registered new interface driver usb-storage kernel: usbcore: registered new interface driver uas mtp-probe[17360]: checking bus 2, device 3: "/sys/devices/pci:00/:00:14.0/usb2/2-6" mtp-probe[17360]: bus: 2, device: 3 was not an MTP device kernel: scsi 2:0:0:0: Direct-Access Corsair Voyager Mini 3.0 000B PQ: 0 ANSI: 6 kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0 kernel: sd 2:0:0:0: [sdb] 30283008 512-byte logical blocks: (15.5 GB/14.4 GiB) kernel: sd 2:0:0:0: [sdb] Write Protect is off kernel: sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 kernel: sd 2:0:0:0: [sdb] No Caching mode page found kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through kernel: sdb: sdb1 kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk systemd-udevd[17357]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg80 --raw' failed with exit code 15. kernel: usb 2-6: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd systemd-udevd[17357]: Spawned process '/usr/bin/sg_inq --export --page=sn /dev/sdb' [17363] is taking longer than 59s to complete systemd-udevd[17357]: Process '/usr/bin/sg_inq --export --page=sn /dev/sdb' failed with exit code 99. systemd-udevd[17357]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg83 --raw' failed with exit code 15. and the serial: P: /devices/pci:00/:00:14.0/usb2/2-6/2-6:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 N: sdb1 L: 0 S: disk/by-id/scsi-32000acde48234567-part1 S: disk/by-label/ESD-USB S: disk/by-id/scsi-3-part1 S: disk/by-id/scsi-28765432ab567abcd-part1 S: disk/by-uuid/B068-2D19 S: disk/by-id/wwn-0x2000acde48234567-part1 S: disk/by-id/scsi-1USB_DISK_2.0-part1 S: disk/by-partuuid/2ff58786-01 S: disk/by-path/pci-:00:14.0-usb-0:6:1.0-scsi-0:0:0:0-part1 E: DEVPATH=/devices/pci:00/:00:14.0/usb2/2-6/2-6:1.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 E: SUBSYSTEM=block E: DEVNAME=/dev/sdb1 E: DEVTYPE=partition E: PARTN=1 E: MAJOR=8 E: MINOR=17 E: USEC_INITIALIZED=1623657380 E: SCSI_TPGS=0 E: SCSI_TYPE=disk E: SCSI_VENDOR=Corsair E: SCSI_VENDOR_ENC=Corsair\x20 E: SCSI_MODEL=Voyager_Mini_3.0 E: SCSI_MODEL_ENC=Voyager\x20Mini\x203.0 E: SCSI_REVISION=000B E: SCSI_IDENT_LUN_T10=USB_DISK_2.0 E: SCSI_IDENT_LUN_EUI64=8765432ab567abcd E: SCSI_IDENT_LUN_NAA_EXT=2000acde48234567 E: ID_SCSI=1 E: ID_VENDOR=Corsair E: ID_VENDOR_ENC=Corsair\x20 E: ID_MODEL=Voyager_Mini_3.0 E: ID_MODEL_ENC=Voyager\x20Mini\x203.0 E: ID_REVISION=000B E: ID_TYPE=disk E: ID_WWN=0x2000acde48234567 E: ID_WWN_WITH_EXTENSION=0x2000acde48234567 E: ID_BUS=scsi E: ID_SERIAL=3 E: ID_SERIAL_SHORT=2000acde48234567 ... # Ubuntu Disco with fixed proposed version: Oct 09 03:26:40 lenovo kernel: usb-storage 2-6:1.0: USB Mass Storage device detected Oct 09 03:26:40 lenovo kernel: scsi host2: usb-storage 2-6:1.0 Oct 09 03:26:40 lenovo mtp-probe[22823]: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-6" Oct 09 03:26:40 lenovo mtp-probe[22823]: bus: 2, device: 5 was not an MTP device Oct 09 03:26:40 lenovo mtp-probe[22826]: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-6" Oct 09 03:26:40 lenovo mtp-probe[22826]: bus: 2, device: 5 was not an MTP device Oct 09 03:26:41 lenovo kernel: scsi 2:0:0:0: Direct-Access Corsair Voyager Mini 3.0 000B PQ: 0 ANSI: 6 Oct 09 03:26:41 lenovo kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0 Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] 30283008 512-byte logical blocks: (15.5 GB/14.4 GiB) Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] Write Protect is off Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] No Caching mode page found Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through Oct 09 03:26:43 lenovo kernel: sdb: sdb1 Oct 09 03:26:43 lenovo kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk Oct 09 03:26:43 lenovo systemd-udevd[22819]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg80 --raw' failed with exit code 15. Oct 09 03:26:43 lenovo systemd-udevd[22819]: Process '/usr/bin/sg_inq --export --inhex=/sys/block/sdb/device/vpd_pg83 --raw' failed with exit co
[Bug 1847058] Re: MAAS deployment failed with vgchange command
BTW from our test log on the Jenkins server, it looks like this issue first occurs in 3 days 19 hrs before. And this is blocking the kernel SRU testing to some extent. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
I've now tried nvidia-390 on 18.04 and still can't reproduce the bug there. Diego, can you provide a screenshot or photo of the corruption you see in 18.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845999] Re: 19.10 gnome-sushi doesn't preview in nautilus
It's working after a restart! ** Changed in: gnome-sushi (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845999 Title: 19.10 gnome-sushi doesn't preview in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1845999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Known mitigation options at this point: - live migrate for upgrades - prohibited by SR-IOV usage - Tech to get SR-IOV migratable is coming (e.g. via net_failover, bonding in DPDK, ...) - load the modules you need in advance - Note: lacking an explicit "load module" command makes this slightly odd for now - but using iscsi or ceph is never spontaneous, a deployment has or hasn't the setup to use those - Create a single small read-only node and attach this to each guest, that will load the driver and render you immune to the issue. While more clunky, this isn't so much different than how it would be with an explicit "load module" command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847389] Re: Confusing zpool status in Ubuntu 19.10 installed onZFS
We wrote on another bug report BertN45 to not upgrade your bpool. Only power users will use zpool status command to list and we expect them to know the implication. I think I'll retarget this bug for preventing bpool upgrade. ** Summary changed: - Confusing zpool status in Ubuntu 19.10 installed onZFS + Prevent bpool (or pools with /BOOT/) to be upgraded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Just theorizing for now ... For a packaging solution we would need: - qemu-block-extra / qemu-system-gui binary packages would need sort of a -$buildid in the name. That could be the version string (sanitized for package name) - /usr/lib/x86_64-linux-gnu/qemu/*.so would need a -$buildid - loading of modules from qemu would need to consider $buildid when creating module names. util/module.c in module_load_one / module_load_file It already searches in multiple dirs, maybe it could insert the $buildid there - We'd need a way of detecting running versions of qemu binaries and only make them uninstallable once the binaries are all gone. I have not seen something like that in apt yet (kernel is easy in comparison as only one can be loaded at a time). ALTERNATIVES: - disable loadable module support - add an option to load all modules in advance (unlikely to be liked upstream) and not desirable for many setups using qemu (especially not as default) - add an option to load a module (e.g via QMP/HMP) which would allow an admin to decide doing so for the few setups that benefit. - that could down the road then even get a libvirt interface for easier consumption Heads up - None of the above would be SRUable ** Changed in: qemu (Ubuntu) Importance: Undecided => Wishlist ** Changed in: qemu (Ubuntu) Status: Confirmed => Triaged ** Description changed: + --- initial report --- + Upgrading qemu binaries causes the on-disk versions to change, but the in-memory running instances still attempt to dynamically load a library which matches its same version. This can cause running instances to fail actions like hotplugging devices. This can be alleviated by migrating the instance to a new host or restarting the instance, however in cloud type environments there may be instances that cannot be migrated (sriov, etc) or the cloud operator does not have permission to reboot. This may be resolvable for many situations by changing the packaging to keep older versions of qemu libraries around on disk (similar to how the kernel package keeps older kernel versions around). + + --- testcase --- + + $ apt install uvtool-libvirt + $ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic + $ uvt-kvm create --password ubuntu lateload arch=amd64 release=bionic label=daily + + cat > curldisk.xml << EOF + + + + + + + + + EOF + + # Here up or downgrade the installed packages, even a minor + # version or a rebuild of the same version + + $ virsh attach-device lateload curldisk.xml + Reported issue happens on attach: + root@b:~# virsh attach-device lateload cdrom-curl.xml + error: Failed to attach device from cdrom-curl.xml + error: internal error: unable to execute QEMU command 'device_add': Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk2' + + In the log we can see: + Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so + Note: only modules from the same build can be loaded. + + --- solution options (WIP) --- + + For a packaging solution we would need: + - qemu-block-extra / qemu-system-gui binary packages would need + sort of a -$buildid in the name. That could be the version + string (sanitized for package name) + - /usr/lib/x86_64-linux-gnu/qemu/*.so would need a -$buildid + - loading of modules from qemu would need to consider $buildid + when creating module names. + util/module.c in module_load_one / module_load_file + It already searches in multiple dirs, maybe it could insert + the $buildid there + - We'd need a way of detecting running versions of qemu binaries + and only make them uninstallable once the binaries are all + gone. I have not seen something like that in apt yet (kernel + is easy in comparison as only one can be loaded at a time). + + ALTERNATIVES: + - disable loadable module support + - add an option to load all modules in advance (unlikely to be + liked upstream) and not desirable for many setups using qemu + (especially not as default) + - add an option to load a module (e.g via QMP/HMP) which would + allow an admin + to decide doing so for the few setups that benefit. + - that could down the road then even get a libvirt interface + for easier consumption + + Heads up - None of the above would be SRUable + + --- mitigation options --- + + - live migrate for upgrades + - prohibited by SR-IOV usage + - Tech to get SR-IOV migratable is coming (e.g. via net_failover, + bonding in DPDK, ...) + - load the modules you need in advance + - Note: lacking an explicit "load module" command makes this + slightly odd for now + - but using iscsi or ceph is never spontaneous, a deployment + has or hasn't the setup to use those + - Create a single small read-only node and attach this to each guest, + that will load the driver and render y
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
I have added testcase, solution options and mitigations to the description, there we can update them as new things come up int the discussion. That helps other people joining this bug to read what things are about in just the description. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)
5.0 Kernel + following patched [1] + AMD 19.30 driver [2], the issue is fixed. [1] Takashi Iwai's sound component support patch for AMDGPU - https://patchwork.kernel.org/patch/10540417/ [2] AMD 19.30 driver: https://www.amd.com/en/support/kb/release-notes /rn-amdgpu-unified-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847219 Title: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831295] Re: Firefox freeze when I drag an URL address to a Nautilus window
Ah, I hadn't tried in a Wayland session. I can indeed reproduce the problem in 19.04 in a Wayland session, after trying to drag and drop the URL in different places into a nautilus window, I eventually get firefox to stop responding, probably because it didn't register a drop event. And I can confirm this doesn't happen in 19.10. ** Changed in: firefox (Ubuntu) Status: Incomplete => Fix Released ** Tags added: rls-dd-incoming ** Also affects: firefox (Ubuntu Disco) Importance: Undecided Status: New ** Summary changed: - Firefox freeze when I drag an URL address to a Nautilus window + Firefox freeze when I drag an URL address to a Nautilus window under Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831295 Title: Firefox freeze when I drag an URL address to a Nautilus window under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1831295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846714] Re: Merge "BUG/MEDIUM: server: Also copy "check-sni" for server templates."
Set up HAProxy with the attached configuration. The server-template directive will generate 3 upstreams based on the DNS-answers for letsencrypt.status.io. This is basic HAProxy DNS-service-discovery. If you now check back with the stats socket or the webinterface, you will notice that while the first upstream will be L7OK, all the following upstreams are going to be L6RSP, doe to the fact that the check-sni setting does not get replicated for any of the generated upstreams than the first. The patch fixes this so the check-sni argument gets applied to all generated upstreams. With a patched version of HAProxy all the 3 upstreams will be L7OK. ** Attachment added: "HAProxy configuration with server-template" https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1846714/+attachment/5295763/+files/haproxy.cfg ** Changed in: haproxy (Ubuntu Bionic) Status: Triaged => New ** Changed in: haproxy (Ubuntu Disco) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846714 Title: Merge "BUG/MEDIUM: server: Also copy "check-sni" for server templates." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1846714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
The code around module_load_one is mapped to a few helper names:
60 #define block_module_load_one(lib) module_load_one("block-", lib)
61 #define ui_module_load_one(lib) module_load_one("ui-", lib)
62 #define audio_module_load_one(lib) module_load_one("audio-", lib)
Currently there seems to be no invocation of those other than attaching
such a type of device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847361
Title:
Upgrade of qemu binaries causes running instances not able to
dynamically load modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847415] Re: xubuntu 19.10 daily (Wed 09 Oct 2019 ) is stuck on install
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847415 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847415 Title: xubuntu 19.10 daily (Wed 09 Oct 2019 ) is stuck on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Using 19.2-36-g059d049c-0ubuntu1~18.04.1 any of our new AWS instances can not get networking. A standard package update AMI build resulted in moving from 19.2.24 to 19.2.36 and now our instances come up inaccessible. Our cloudconfig does not make any adjustments to the networking. The specific environment where we have the issue is AWS, US-West-2, m5.Xlarge instances, on a private subnet, within a VPC. Please let me know what information I can provide that may help to troubleshoot. I'm unable to access any instances running the new cloud init so information I can retrieve from them is limited. --- --- [ 30.990869] cloud-init[729]: Cloud-init v. 19.2-36-g059d049c-0ubuntu1~18.04.1 running 'init' at Wed, 09 Oct 2019 05:09:30 +. Up 30.80 seconds. [ 13.017666] cloud-init[736]: ci-info: +++Net device info [ 13.019271] cloud-init[736]: ci-info: ++---+---+---+---+---+ [ 13.020911] cloud-init[736]: ci-info: | Device | Up | Address |Mask | Scope | Hw-Address| [ 13.022470] cloud-init[736]: ci-info: ++---+---+---+---+---+ [ 13.024021] cloud-init[736]: ci-info: | ens5 | False | . | . | . | 06:57:5b:c1:24:52 | [ 13.025576] cloud-init[736]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | [ 13.027182] cloud-init[736]: ci-info: | lo | True | ::1/128 | . | host | . | [ 13.028763] cloud-init[736]: ci-info: ++---+---+---+---+---+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
While mentioned, QMP loading of modules never came to life it seems [1]. [1]: http://manpages.ubuntu.com/manpages/eoan/man7/qemu-qmp-ref.7.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847391] Re: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable
** Attachment added: "kylin-nm_1.0.3_buildlog.txt.gz" https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+attachment/5295755/+files/kylin-nm_1.0.3_buildlog.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847391 Title: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Up/Downgrade with a command like this: v=1:2.11+dfsg-1ubuntu7.18; apt install qemu-block-extra=$v qemu-system-common=$v qemu-system-x86=$v qemu-utils=$v qemu-running: 1:2.11+dfsg-1ubuntu7.19 lib installed: 1:2.11+dfsg-1ubuntu7.18 Reported issue happens on attach: root@b:~# virsh attach-device lateload cdrom-curl.xml error: Failed to attach device from cdrom-curl.xml error: internal error: unable to execute QEMU command 'device_add': Property 'virtio-blk-device.drive' can't find value 'drive-virtio-disk2' In the log we can see: Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-curl.so Note: only modules from the same build can be loaded. So it is not a full ABI/API like a normal lib with an soname, it really is an internal .so with hard dependency on the real buildid. In the design [1] it was mentioned that there could be options to load modules later via HMP/QMP. In there also are some reasoning why to modularize and why to load things late. [1]: https://wiki.qemu.org/Features/Modules @Billy - comment #4 and #5 answer the questions I had to you above - I was too thrilled and tested it myself :-) ** Changed in: qemu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847391] Re: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable
** Attachment added: "kylin-nm_1.0.2-0ubuntu1_1.0.3_201910091035.diff.gz" https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+attachment/5295752/+files/kylin-nm_1.0.2-0ubuntu1_1.0.3_201910091035.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847391 Title: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847415] [NEW] xubuntu 19.10 daily (Wed 09 Oct 2019 ) is stuck on install
Public bug reported: Installer is stuck with spinning wheel after clicking CONTINUE at the "Updates and other software" screen. QA-install, full disk ; both download updates & install 3rd party selected, then CONTINUE.. It's been stuck at screen maybe an hour. Box - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) fyi: "Check disc for defects" passed prior to install; I'll re-do check & try again. Box was used for multiple Lubuntu installs yesterday without issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.16 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Wed Oct 9 05:32:43 2019 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.16 xubuntu ** Description changed: Installer is stuck with spinning wheel after clicking CONTINUE at the "Updates and other software" screen. QA-install, full disk ; both download updates & install 3rd party selected, then CONTINUE.. It's been stuck at screen maybe an hour. Box - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) + + fyi: "Check disc for defects" passed prior to install; I'll re-do check & try again. + Box was used for multiple Lubuntu installs yesterday without issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.16 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Wed Oct 9 05:32:43 2019 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847415 Title: xubuntu 19.10 daily (Wed 09 Oct 2019 ) is stuck on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Using proposed and UCA I did some experiments in Bionic: qemu-block-extra: 1:3.1+dfsg-2ubuntu3.2~cloud0 500 500 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/stein/main amd64 1:2.11+dfsg-1ubuntu7.19 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:2.11+dfsg-1ubuntu7.18 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages I should be able to switch between those. Also there is a trick to do all this without a complex ceph/issci setup. cat > curldisk.xml << EOF EOF $ virsh attach-device lateload curldisk.xml Among many (many!) dependent libs from the system this also will late- load the qemu curl .so file. root@b:~# diff libsloaded.pre libsloaded.post 4a5,29 > qemu-syst 18362 libvirt-qemu mem REG 0,64 26936 > 2603 /lib/x86_64-linux-gnu/libnss_dns-2.27.so > qemu-syst 18362 libvirt-qemu mem REG 0,64 39208 > 2529 /lib/x86_64-linux-gnu/libcrypt-2.27.so > qemu-syst 18362 libvirt-qemu mem REG 0,641082648 > 10066 /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6 > qemu-syst 18362 libvirt-qemu mem REG 0,64 300888 > 3424 /usr/lib/x86_64-linux-gnu/libhx509.so.5.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 60400 > 3418 /usr/lib/x86_64-linux-gnu/libheimbase.so.1.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 165880 > 10090 /usr/lib/x86_64-linux-gnu/libwind.so.0.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 88680 > 10058 /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 217560 > 3416 /usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 661696 > 9860 /usr/lib/x86_64-linux-gnu/libasn1.so.8.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 573464 > 9987 /usr/lib/x86_64-linux-gnu/libkrb5.so.26.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 35360 > 3420 /usr/lib/x86_64-linux-gnu/libheimntlm.so.0.1.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 14256 > 2573 /lib/x86_64-linux-gnu/libkeyutils.so.1.5 > qemu-syst 18362 libvirt-qemu mem REG 0,64 265712 > 3410 /usr/lib/x86_64-linux-gnu/libgssapi.so.3.0.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 43616 > 9991 /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1 > qemu-syst 18362 libvirt-qemu mem REG 0,64 14248 > 308068 /lib/x86_64-linux-gnu/libcom_err.so.2.1 > qemu-syst 18362 libvirt-qemu mem REG 0,64 199104 > 9985 /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1 > qemu-syst 18362 libvirt-qemu mem REG 0,64 877056 > 9989 /usr/lib/x86_64-linux-gnu/libkrb5.so.3.3 > qemu-syst 18362 libvirt-qemu mem REG 0,64 55544 > 173467 /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2.10.8 > qemu-syst 18362 libvirt-qemu mem REG 0,64 327024 > 172527 /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2.10.8 > qemu-syst 18362 libvirt-qemu mem REG 0,64 305456 > 3412 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 > qemu-syst 18362 libvirt-qemu mem REG 0,64 55136 > 10054 /usr/lib/x86_64-linux-gnu/libpsl.so.5.2.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 113584 > 10059 /usr/lib/x86_64-linux-gnu/librtmp.so.1 > qemu-syst 18362 libvirt-qemu mem REG 0,64 153352 > 10024 /usr/lib/x86_64-linux-gnu/libnghttp2.so.14.15.2 > qemu-syst 18362 libvirt-qemu mem REG 0,64 510408 > 208529 /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4.5.0 > qemu-syst 18362 libvirt-qemu mem REG 0,64 25600 > 308756 /usr/lib/x86_64-linux-gnu/qemu/block-curl.so 143a169,177 > qemu-syst 18362 libvirt-qemu 30u IPv495769740t0 > TCP b.lxd:47940->urayuli.canonical.com:http (ESTABLISHED) > qemu-syst 18362 libvirt-qemu 31u a_inode 0,13 0 > 10884 [eventfd] > qemu-syst 18362 libvirt-qemu 32u a_inode 0,13 0 > 10884 [eventfd] > qemu-syst 18362 libvirt-qemu 33u IPv495754160t0 > TCP b.lxd:47942->urayuli.canonical.com:http (ESTABLISHED) > qemu-syst 18362 libvirt-qemu 35u IPv495769790t0 > TCP b.lxd:47948->urayuli.canonical.com:http (ESTABLISHED) > qemu-syst 18362 libvirt-qemu 36u IPv495758250t0 > TCP b.lxd:47950->urayuli.canonical.com:http (ESTABLISHED) > qemu-syst 18362 libvirt-qemu 37u IPv495754180t0
[Bug 1846264] Re: iwlwifi firmware version: 36.77d01142.0 crashing on association
XPS 13 9350 is not found in Ubuntu-certified directory. Removed the tag. Besides, I thought it should[1] equips DW1820A 2x2 802.11ac 2.4/5GHz, which should be compatible with Broadcom BCM4350[2], but your log shows as Intel® Dual Band Wireless-AC 8260. Is that an manually upgraded one? >From the support page[3] it shows that's only compatible with XPS 15 9550 and Precision 5510. [1]: https://www.techadvisor.co.uk/review/laptops/dell-xps-13-9350-review-3605875/ [2]: https://wikidevi.com/wiki/Dell_Wireless_1820A_(DW1820A) [3]: https://www.dell.com/support/home/gh/en/ghdhs1/drivers/driversdetails?driverid=tm8tm ** Changed in: linux-firmware (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/1846264 Title: iwlwifi firmware version: 36.77d01142.0 crashing on association To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1846264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
The current list of extra .so files that we have are: ## Package: .so files ## qemu-system-gui: audio-pa.so, ui-gtk.so qemu-block-extra: block-curl.so, block-iscsi.so, block-rbd.so I don't think that there is an action that would load audio or ui late. So they should be safe against the reporte issue. On the other hand block-* has the way of hotplugging the first disk of some kind that will load the .so file then. So I'd assume this is how you have hit this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
@Billy - a few questions to complete the picture here: 1. Did this only fail on a major e.g. qemu 2.5 -> 3.1 upgrade or does it in your experience insist on the exact build ID so e.g. 2.5-1ubuntu1 -> 2.5-2ubuntu1 ? Depending on that answer the versioned package name becomes harder/easier - if you don't know please tell me then I will have to do some tests to confirm. 2. Most decisions to load-or-not are made on the initial instantiation, but as you say hotplug of e.g. new storage types might be an issue. What was your actual example to hit this - what did you hotplug (XML of guest and hotplug device if you have it still) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Interesting bug, thanks Billy for the report. Packaging of qemu (and actually many other applications as well) splits its capabilities into a main binaries and .so files (or similar tech, even am extra python module if you want). That is for flexibility of attack surface (less active code), size management (install footprint), dependency management (some might be optional or less supported), ... Some of these technologies can load these modules "late" and this is what happens here. Qemu will not load all its .so files that are installed immediately, but when needed. That is what happens when I personally don't think packaging it with versioned binary packages like a lib or the kernel is the right way (as more packages are design- wise affected by the same and wouldn't we want to switch all of them then), but I don't have a great alternative yet either - this clearly needs some discussions about the way to go with it. We might need to analyze which of these can load late and maybe provide an option to load them early or automatically before upgrades? OTOH that seems a very big and undetected change in behavior if e.g. reducing attack surface was your intention. As I said, very interesting bug ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847228] Re: Installer crashes at partitioning stage
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847228 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847228 Title: Installer crashes at partitioning stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847283] Re: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter"
** Attachment added: "prompt when installing dkms package" https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+attachment/5295737/+files/photo_2019-10-09_12-41-51.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847283 Title: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847283] Re: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter"
** Attachment added: "MOK enrollment after reboot" https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+attachment/5295739/+files/photo_2019-10-09_12-40-35.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847283 Title: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847283] Re: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter"
** Attachment added: "prompt for MOK password" https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+attachment/5295738/+files/photo_2019-10-09_12-40-32.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847283 Title: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847283] Re: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter"
You don't need to do anything to trigger the key generation and enrollment, everything should be automatic and you will be prompted for what to do when the DKMS package is installed. I am going to attach some photos for you to see what should happen. How did you install this DKMS package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847283 Title: Not work: "01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1847283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847058] Re: MAAS deployment failed with vgchange command
Hi, thanks for the reply, I tried to re-sync the Eoan image today and deploy it on a node that does not work before (bavor), it's still failing, but the error message is a bit different: curtin.util.ProcessExecutionError: Unexpected error while running command. Command: ['vgscan', '--mknodes'] Exit code: 5 Reason: - Stdout: Reading all physical volumes. This may take a while... Found volume group "vg_459" using metadata type lvm2 Stderr: Command failed with status code 5. Please find the attachment for the output from maas. ** Attachment added: "bavor-eoan.log" https://bugs.launchpad.net/maas/+bug/1847058/+attachment/5295736/+files/bavor-eoan.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847058 Title: MAAS deployment failed with vgchange command To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1847058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847333] Re: Installer crashes during installation
*** This bug is a duplicate of bug 1847228 *** https://bugs.launchpad.net/bugs/1847228 ** This bug has been marked a duplicate of bug 1847228 Installer crashes at partitioning stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847333 Title: Installer crashes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847315] Re: Choosing ZFS during 19.10 install bootloader install failed
*** This bug is a duplicate of bug 1847228 *** https://bugs.launchpad.net/bugs/1847228 ** This bug is no longer a duplicate of bug 1847311 Choosing ZFS during 19.10 install bootloader install failed ** This bug has been marked a duplicate of bug 1847228 Installer crashes at partitioning stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847315 Title: Choosing ZFS during 19.10 install bootloader install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847326] Re: Crash during Ubiquiti installer - testing ZFS support
*** This bug is a duplicate of bug 1847228 *** https://bugs.launchpad.net/bugs/1847228 ** This bug has been marked a duplicate of bug 1847228 Installer crashes at partitioning stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847326 Title: Crash during Ubiquiti installer - testing ZFS support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847311] Re: Choosing ZFS during 19.10 install bootloader install failed
*** This bug is a duplicate of bug 1847228 *** https://bugs.launchpad.net/bugs/1847228 ** This bug has been marked a duplicate of bug 1847228 Installer crashes at partitioning stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847311 Title: Choosing ZFS during 19.10 install bootloader install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847406] Re: Installing 19.10 daily for 2019-10-08 + zfs failed install
*** This bug is a duplicate of bug 1847228 *** https://bugs.launchpad.net/bugs/1847228 ** This bug has been marked a duplicate of bug 1847228 Installer crashes at partitioning stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847406 Title: Installing 19.10 daily for 2019-10-08 + zfs failed install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
** Changed in: gnome-shell Status: Unknown => 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/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1846941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847298] Re: eoan/linux: 5.3.0-18.19 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 08. October 2019 16:21 UTC reason: prepare-package-meta: Stalled -- package tag not yet published - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed,signed:retry-needed trackers: bionic/linux-hwe-edge: bug 1847297 eoan/linux-aws: bug 1847291 eoan/linux-azure: bug 1847292 eoan/linux-gcp: bug 1847293 eoan/linux-kvm: bug 1847294 eoan/linux-oracle: bug 1847295 eoan/linux-raspi2: bug 1847290 eoan/linux-snapdragon: bug 1847296 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/1847298 Title: eoan/linux: 5.3.0-18.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524215] Re: Lenovo B50-70 inverted internal microphone
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (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/1524215 Title: Lenovo B50-70 inverted internal microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847406] [NEW] Installing 19.10 daily for 2019-10-08 + zfs failed install
Public bug reported: Installing the 19.10 daily for 2019-10-08 using the zfs option and the installer errors out. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.15 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.423 Date: Tue Oct 8 23:13:23 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash --- LiveMediaBuild: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191008) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.15 ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847406 Title: Installing 19.10 daily for 2019-10-08 + zfs failed install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839603] Re: Wifi breaks and needs restart after Laptop's wake up
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-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/1839603 Title: Wifi breaks and needs restart after Laptop's wake up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839632] Re: did not want a UEFI partition, forced ACPI bypass failure
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (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/1839632 Title: did not want a UEFI partition, forced ACPI bypass failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1839632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837453] Re: 18.04 overheating at lock screen or closed lid
[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/1837453 Title: 18.04 overheating at lock screen or closed lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1837453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846264] Re: iwlwifi firmware version: 36.77d01142.0 crashing on association
** Tags removed: ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846264 Title: iwlwifi firmware version: 36.77d01142.0 crashing on association To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1846264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1683 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1683 ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1463 => gitlab.gnome.org/GNOME/gnome-shell/issues #1683 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Tags added: fixed-in-3.34.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1846941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846012] Re: bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker
5.0.0-1020.20~18.04.1 - gcp Regression test CMPL, RTB. Issue to note in gcp: ubuntu_k8s_unit_tests - scheduler and spdy (bug 1824136) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) msg_zerocopy in net (bug 1812620) t race_printk in ftrace (bug 1830084) ubuntu_ltp - test timeouted with 4 hours threshold on jenkins (bug 1837206) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) msgstress03 (bug 1797341) stime01 (bug 1845620) clock_settime01 Skipped / blacklisted: * libhugetlbfs * ubuntu_seccomp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846012 Title: bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
This may fix the issue: https://lore.kernel.org/lkml/20191002121808.59376-1-c...@endlessm.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1846019 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge - phase: Promote to Proposed - phase-changed: Monday, 07. October 2019 13:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 09. October 2019 03:51 UTC reason: - promote-to-proposed: Alert -- packages no longer available + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait replaces: bug 1844355 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/1846018 Title: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847391] Re: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847391 Title: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+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
>From linux-firmware postinst script it has:
5 if [ -x /usr/sbin/update-initramfs ]; then
6 /usr/sbin/update-initramfs -u -k all
7 fi
and since this is optional, there is no dependency to initramfs-tools-
bin declared. I think we can test if the initramfs-tools package has
completed installation instead: `dpkg-query --show -f '${Status}'
initramfs-tools`.
** Changed in: linux-firmware (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: linux-firmware (Ubuntu Disco)
Importance: Undecided => Low
--
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 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => New ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team (ubuntu-sru) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846018 Title: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+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
Should be low as one can always issue another dpkg-reconfigure later to easily fix this situation. -- 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 1842910] Re: Desktop right click menu appears in the wrong place if a Terminal window is open
** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu) ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Eoan) ** Tags added: fixed-in-3.34.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842910 Title: Desktop right click menu appears in the wrong place if a Terminal window is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1842910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847399] Re: Help me
Please don't convert this (or other bugs) to a question so quickly. It's easier and less confusing for people to keep the conversation in one place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847399 Title: Help me To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847399] Re: Help me
Thank you for taking the time to report this issue and helping to make Ubuntu better. This bug report can be converted to a question (which is aimed at support). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847399 Title: Help me To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847021] Re: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set
> @Peng Wu: Are you able to summarize the purpose of those reversals? Do they, as I'm implying, make ibus-libpinyin more stable and prevent certain crash types? @Gunnar Hjalmarsson: Yes, it will prevent some kind of file corruption. > The dictionary built in conjunction with libpinyin 2.2 cannot be ported > to version 2.3. @Gunnar Hjalmarsson: It will only clean up the user data, and provide better dictionary data in libpinyin. Please use the tar ball release for packaging, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847021 Title: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1847021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847399] Re: Help me
Please describe the kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1847399 Title: Help me To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847400] Re: Printer drivers crashes after printing something
*** This bug is a duplicate of bug 1845548 *** https://bugs.launchpad.net/bugs/1845548 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1845548, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1847400/+attachment/5295704/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295708/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295717/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295719/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295720/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295721/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1847400/+attachment/5295722/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1845548 implicitclass crashed with SIGABRT in __malloc_assert() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847400 Title: Printer drivers crashes after printing something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1847400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846692] Re: PCI/internal sound card not detected
If we use 5.0 generic kernel, the kernel should load the legacy hda driver because there is no sof driver in the 5.0 generic kernel. For this problem, the legacy hda driver is not loaded, maybe users forget to install linux-modules-extra- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846692 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847399] [NEW] Help me
Public bug reported: Sorry I don't understand ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 9 03:56:09 2019 DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3] InstallationDate: Installed on 2015-04-17 (1635 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago) dmi.bios.date: 11/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30AD_M31AD_M51AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: K30AD_M31AD_M51AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Tue Sep 18 15:20:24 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847399 Title: Help me To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1847399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847389] Re: Confusing zpool status in Ubuntu 19.10 installed onZFS
Do NOT upgrade your bpool. The dangerous warning is a known issue. There has been talk of an upstream feature that would allow a nice fix for this, but nobody has taken up implementing it yet. I wonder how hard it would be to temporarily patch zpool status / zpool upgrade to not warn about / upgrade a pool named bpool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Confusing zpool status in Ubuntu 19.10 installed onZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846011] Re: bionic/linux-gcp-edge: 5.0.0-1020.20~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846012 packages: meta: linux-meta-gcp-edge - phase: Ready for Testing - phase-changed: Tuesday, 08. October 2019 11:25 UTC + phase: Ready for Promote to Updates + phase-changed: Wednesday, 09. October 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy 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/1846011 Title: bionic/linux-gcp-edge: 5.0.0-1020.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846018] Re: bionic/linux-oracle-edge: 5.0.0-1004.8~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 -- boot-testing-requested: true kernel-stable-master-bug: 1846019 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Promote to Proposed phase-changed: Monday, 07. October 2019 13:35 UTC reason: - promote-to-proposed: Stalled -- review FAILED + promote-to-proposed: Alert -- packages no longer available replaces: bug 1844355 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/1846018 Title: bionic/linux-oracle-edge: 5.0.0-1004.8~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846011] Re: bionic/linux-gcp-edge: 5.0.0-1020.20~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846011 Title: bionic/linux-gcp-edge: 5.0.0-1020.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847391] [NEW] [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable
Public bug reported: This new release fixed a bug and added the function to connect to hidden wifi: * New upstream release: - Fix that the connect state doesn't update after net cable plug in or out. (LP: #1831818) - Add the function to connect to hidden wireless network. (LP: #1829807) And it has been tested in my ppa for a while (ignore the wrong version number there, there have the same contents): https://launchpad.net/~feng-kylin/+archive/ubuntu/1910test Thanks a lot! ** Affects: kylin-nm (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/1847391 Title: [FFe] Please sync kylin-nm 1.0.3-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kylin-nm/+bug/1847391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847222] Re: serverX crashes randomly
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: gnome-session (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1847222 Title: serverX crashes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1847222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845999] Re: 19.10 gnome-sushi doesn't preview in nautilus
I think today's many updates fixed this, but let me reboot and check again for sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845999 Title: 19.10 gnome-sushi doesn't preview in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1845999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846542] Re: Kernel panic 5.3.0-13
*** This bug is a duplicate of bug 1845454 *** https://bugs.launchpad.net/bugs/1845454 Yes that is bug 1845454. ** This bug has been marked a duplicate of bug 1845454 Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846542 Title: Kernel panic 5.3.0-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847042] Re: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5
*** This bug is a duplicate of bug 1845454 *** https://bugs.launchpad.net/bugs/1845454 ** This bug has been marked a duplicate of bug 1845454 Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847042 Title: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838678] Re: radeon kernel driver fails to resume from suspend
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838678 Title: radeon kernel driver fails to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847389] [NEW] Confusing zpool status in Ubuntu 19.10 installed onZFS
Public bug reported: The bpool status is confusing. Should I upgrade the pool or is it on purpose that the bpool is like this. I do no like to see this warning after installing the system on ZFS from scratch. See screenshot ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-10-08 21-49-50.png" https://bugs.launchpad.net/bugs/1847389/+attachment/5295679/+files/Screenshot%20from%202019-10-08%2021-49-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Confusing zpool status in Ubuntu 19.10 installed onZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843794] Re: CML CPUIDs
Commit-ID: 8d7c6ac3b2371eb1cbc9925a88f4d10efff374de Target 5.4 rc release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843794 Title: CML CPUIDs To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1843794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
P: /devices/pci:00/:00:1c.0/:01:00.0 E: DEVPATH=/devices/pci:00/:00:1c.0/:01:00.0 E: DRIVER=radeon E: FWUPD_GUID=0x1002:0x6665 E: ID_MODEL_FROM_DATABASE=Jet PRO [Radeon R5 M230] E: ID_PCI_CLASS_FROM_DATABASE=Display controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Display controller E: ID_VENDOR_FROM_DATABASE=Advanced Micro Devices, Inc. [AMD/ATI] E: MODALIAS=pci:v1002d6665sv1028sd0967bc03sc80i00 E: PCI_CLASS=38000 E: PCI_ID=1002:6665 E: PCI_SLOT_NAME=:01:00.0 E: PCI_SUBSYS_ID=1028:0967 E: SUBSYSTEM=pci E: USEC_INITIALIZED=6275515 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847298] Re: eoan/linux: 5.3.0-18.19 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 08. October 2019 16:21 UTC reason: prepare-package-meta: Stalled -- package tag not yet published - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe-edge: bug 1847297 eoan/linux-aws: bug 1847291 eoan/linux-azure: bug 1847292 eoan/linux-gcp: bug 1847293 eoan/linux-kvm: bug 1847294 eoan/linux-oracle: bug 1847295 eoan/linux-raspi2: bug 1847290 eoan/linux-snapdragon: bug 1847296 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/1847298 Title: eoan/linux: 5.3.0-18.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847387] [NEW] Create 5.0 linux-oracle-edge kernel
Public bug reported: Creating a 5.0 linux-oracle-edge kernel based on the disco 5.0 kernel. ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Create a 5.0 linux-oracle-edge + Create 5.0 linux-oracle-edge kernel ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847387 Title: Create 5.0 linux-oracle-edge kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1847387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844559] Re: [GLK-R]enable CPUID
No New code was needed to add the CPUID Part of ./arch/x86/include/asm/intel-family.h You should have received GLK-R CPU from Intel. Please test and let us know if you see any issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844559 Title: [GLK-R]enable CPUID To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1844559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page
This bug was fixed in the package firefox - 69.0.2+build1-0ubuntu2 --- firefox (69.0.2+build1-0ubuntu2) eoan; urgency=medium * Install the minidump-analyzer executable (LP: #1845205) - update debian/firefox.install.in -- Olivier Tilloy Tue, 08 Oct 2019 14:51:08 +0200 ** Changed in: firefox (Ubuntu) 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/1845205 Title: Cannot submit crash reports from firefox' "this tab crashed" page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen
** Changed in: ubuntu-dock Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834967 Title: Activities overview doesn't shrink some windows adequately and they are partially off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847382] [NEW] Controller ID report to console shows ctrlid as hex with no 0x in front to denote this
Public bug reported: The controller ID shown in output from id-ctrl option going to the console gives a hex value without typical hex delineation. If it has no a-f digits it looks like a decimal value as it does not start with 0x like other fields that give hex values. If JSON output is requested, then the value is given as a correct decimal value in the JSON. The console should either give a true decimal value or have the 0x prefix added. ** Affects: nvme-cli (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/1847382 Title: Controller ID report to console shows ctrlid as hex with no 0x in front to denote this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1847382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847378] Re: lubuntu 19.10 encrypt install bad unsquash configuration - filesystem.squashfs does not exist
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847378 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847378 Title: lubuntu 19.10 encrypt install bad unsquash configuration - filesystem.squashfs does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1847378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847163] Re: [FFe] Firmware bump for Pi 4 boot support
I'm booting my Pis without u-boot with this in my config.txt: [pi4] enable_gic=1 armstub=armstub8-gic.bin total_mem=1024 [all] kernel=vmlinuz initramfs initrd.img followkernel arm_64bit=1 gpu_mem=32 dtparam=eee=off This exact setup works fine on my Pi 3B+ (and also my Pi 2B has this non-u-boot-setup - they both boot fine this way.) The Pi 4 only even tries to boot with that total_mem=1024 line in the config.txt. Without that line (i.e. with the full 4GB RAM) it stays at the rainbow screen. But this isn't the big issue. When booting, it's failing to detect the SD card and thus the root filesystem. This is with today's updates and your PPA included. cmdline.txt is: root=/dev/mmcblk0p2 rootfstype=ext4 rootflags=noload rootwait verbose nosplash net.ifnames=0 dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes modprobe.blacklist=sdhci_iproc So what does u-boot do differently than the internal bootloader? Or what could be the issue in my setup? I'd like to keep going without u-boot if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847163 Title: [FFe] Firmware bump for Pi 4 boot support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1847163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847325] Re: ZFS Installer refuses to install the boot loader on both disks
Just to clarify, my experience referenced in comment #1 was with the Ubuntu Desktop daily-live CD posted at http://cdimage.ubuntu.com/ubuntu /daily-live/20191008/ running under Oracle Virtualbox v6.012. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847325 Title: ZFS Installer refuses to install the boot loader on both disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847378] [NEW] lubuntu 19.10 encrypt install bad unsquash configuration - filesystem.squashfs does not exist
Public bug reported: sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT) Lubuntu QA-checklist install - full disk, ENCRYPTion, UEFI, NO internet thumbdrive has been checked (check disc for defects) twice; once on d755-5 (prior live test) & once on this box three tries (with reboots); they all ended with `Installation failed. Bad unsquash configuration. The source filesystem "/cdrom/casper/filesystem.squashfs" does not exist` (please note the above was typed, so it may not be letter perfect) from logs 2019-10-09 - 10:33:16 [1]: ERROR: Installation failed: 2019-10-09 - 10:33:16 [6]: - message: "Bad unsquash configuration" 2019-10-09 - 10:33:16 [6]: - details: "The source filesystem \"/cdrom/casper/filesystem.squashfs\" does not exist" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: calamares 3.2.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true userSwapChoices: none drawNestedPartitions: true defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: LXQt Date: Wed Oct 9 10:48:52 2019 RelatedPackageVersions: calamares-settings-ubuntu-common 1:19.10.6 calamares-settings-lubuntu 1:19.10.6 xfsprogs 5.0.0-1ubuntu1 btrfs-progs 5.2.1-1ubuntu1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - I'll add more on real keyboard + sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT) + Lubuntu QA-checklist install - full disk, ENCRYPTion, UEFI, NO internet + + thumbdrive has been checked twice; once on d755-5 (prior live test) & + once on this box + + three tries (with reboots); they all ended with + + `Installation failed. Bad unsquash configuration. The source filesystem + "/cdrom/casper/filesystem.squashfs" does not exist` + + (please note the above was typed, so it may not be letter perfect) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: calamares 3.2.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true userSwapChoices: none drawNestedPartitions: true defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: LXQt Date: Wed Oct 9 10:48:52 2019 RelatedPackageVersions: calamares-settings-ubuntu-common 1:19.10.6 calamares-settings-lubuntu 1:19.10.6 xfsprogs 5.0.0-1ubuntu1 btrfs-progs 5.2.1-1ubuntu1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT) Lubuntu QA-checklist install - full disk, ENCRYPTion, UEFI, NO internet thumbdrive has been checked twice; once on d755-5 (prior live test) & once on this box three tries (with reboots); they all ended with - `Installation failed. Bad unsquash configuration. The source filesystem - "/cdrom/casper/filesystem.squashfs" does not exist` + `Installation failed. Bad unsquash configuration. The source filesystem "/cdrom/casper/filesystem.squashfs" does not exist` + (please note the above was typed, so it may not be letter perfect) - (please note the above was typed, so it may not be letter perfect) + from logs + 2019-10-09 - 10:33:16 [1]: ERROR: Installation failed: + 2019-10-09 - 10:33:16 [6]: - message: "Bad unsquash configuration" + 2019-10-09 - 10:33:16 [6]: - details: "The source filesystem \"/cdrom/casper/filesystem.squashfs\" does not exist" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: calamares 3.2.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 .etc.calamares.modu
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Changed in: sylpheed (Debian) Status: Unknown => 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/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847325] Re: ZFS Installer refuses to install the boot loader on both disks
I had a similar experience doing a clean install with the Experimental ZFS option. This happened repeatably for devices /dev/sda and /dev/sda1, i.e., the installer refused to install to either device and I ended up manually fixing this issue from chroot operations from the livecd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847325 Title: ZFS Installer refuses to install the boot loader on both disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845571] Re: ubiquity offers installation media as an install target
The reason that I argued for the importance to be lowered is that I'm
not super confident about fixing it on a short turnaround without
causing other problems. In disco and before, casper would mount the
entire device (say /dev/sdb) containing the installation media (i.e.
mount /dev/sdb not /dev/sdb1) and that would cause partman base to
exclude /dev/sdb entirely (code around
https://git.launchpad.net/ubuntu/+source/partman-
base/tree/init.d/parted?h=ubuntu/eoan-
proposed&id=ac4be1bb9c00f28d8e19f4ec0c6323769085d593#n156). Now casper
mounts /dev/sdb1 and so that filtering doesn't remove the disk (well,
unless sdb1 fills the device, anyway). It would be possible to cause
that filtering to still exclude the disk but that would break the dell
use case where the installer is in a recovery partition and expects to
install to another partition on the same device (see
https://bugs.launchpad.net/bugs/1846762).
So filtering needs to be added to partman-auto, specifically in
automatically_partition/{replace,reuse,some_device}. The thing is, it
looks like get_auto_disks in lib/auto-shared.sh is _already_ trying to
exclude the device with the install media on it:
# Skip devices containing the installation medium
[ -e "$dev/installation_medium" ] && continue
This file is supposed to be being created by init.d/parted but
apparently isn't. And also fixing this would seem to break the Dell use
case.
And now I'm giving up for now :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845571
Title:
ubiquity offers installation media as an install target
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1845571/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846506] Re: autopkgtest fail in Eoan
the latest autopkgtest retries show that the problem is present in the release pocket, so I have hinted away the failure and am closing the tasks on the reverse-dependencies, since they will no longer be blocked. ** Changed in: python-cryptography (Ubuntu) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769132] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font
xenial version working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769132 Title: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1769132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
