[Bug 1899308] Re: failure to boot groovy daily (again)
Further to my comment #46 I booted again (still same thumb-drive) without issue on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) and booted successfully on hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) (ubuntu groovy daily 2020-10-14, these are not recorded on iso.qa.ubu as it's no longer the latest ISO) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867118] Re: dasd_fba io error and kernel panic
I just 'found' that it's included in upstream stable update 5.4.69: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.69 So it will find it's way into focal via this route. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867118 Title: dasd_fba io error and kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880629] Re: Ubuntu 20.04: Titlebar buttons on the Left not working properly; titlebar disappears in Tweaks app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-tweaks (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880629 Title: Ubuntu 20.04: Titlebar buttons on the Left not working properly; titlebar disappears in Tweaks app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1880629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899487] Re: cloud-init hard codes MTU configuration at initial deploy time
I can't let go of why the same version of cloud-init renders different config with the same data source. So a question: are there other data sources in use that we have not yet examined? Information from the hypervisor configuration trickling through the virtio drivers or something like that? I will compare the qemu configuration for the to instances and see if there are any differences. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899487 Title: cloud-init hard codes MTU configuration at initial deploy time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1899487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896394] Re: Prevent add to favorite and vise versa when move apps to left or right
** Changed in: gnome-shell-extension-ubuntu-dock (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/1896394 Title: Prevent add to favorite and vise versa when move apps to left or right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899889] Re: Add option to sort app icons by name
I verified it's a missing feature on both focal and groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: Add option to sort app icons by name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899909] [NEW] [gdm3] Screen keyboard doesn't work after session locked
Public bug reported: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 ** Affects: gnome-shell (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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867118] Re: dasd_fba io error and kernel panic
Ican see that this patch was brought upstream on 20200923 and was picked up with v5.9-rc7, hence it's first of all not in stock 5.4 or 5.8. Digging a bit deeper into this I found that it already landed in groovy (Ubuntu-5.8.0-21.22) via: "Groovy update: v5.8.13 upstream stable release" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898076 Hence it was obviously tagged upstream as stable update for the 5.8 series. But I couldn't find it in current focal master-next. So the questions is: was it also tagged as upstream stable update for the 5.4 series (which would be recommended)? Or does it need to be manually SRUed to focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867118 Title: dasd_fba io error and kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Chris, There seems to be a difference between the first boot and the subsequent boots in your hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) It might depend on the creation of the ext4 partition behind the image of the iso file, which happens only in the first attempt to boot. Another difference is that the partition is available for reading and writing at once in the following attempts to boot. If you have the time, you could wipe the whole USB drive (with mkusb, slow process) and then clone from the current iso file again, and when booting add the boot option 'nopersistent' before continuing to boot. A more convenient method would be to replace the cloning with creating a 'nopersistent' boot drive using mkusb-plug (but it replaces 'quiet splash' with 'nopersistent'). This way, the drive should look the same during all subsequent boots. The question is: will the computer boot every time or fail every time? Or will there still be differences between the boot attempts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899764] Re: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected
After further investigations, the problem could come from the computer itself. I finished my distro / kernel tests with a windows installation, and I discovered that the mic is still unavailable... Sorry for the inconvenience, I think you can close this ticket. I am going to bring in the on-site support to fix the problem on window, before going further on the linux side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899764 Title: [Realtek ALC257][Lenovo T14 Gen1] Internal mic or headset mic not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Jags Desai, It is possible that your problem depends on the graphics, if there is nvidia graphics. Have you tried to boot in recovery mode or with the boot option 'nomodeset'? But if your HP does not even reach grub, you may need a workaround for the boot process. Please try to install mkusb (mkusb-dus) and make with a persistent live drive with the settings - 'msdos partition table' - 'usb-pack-efi' for your HP computer. Using 'msdos partition table' should work in BIOS mode (alias CSM alias legacy mode) but you can expect it to fail in UEFI mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899852] Re: Cannot assign requested address: AH00072: make_sock: could not bind to address
** Description changed: Hello, Let's first list my configuration items: * apache2 2.4.29-1ubuntu4.14 * release: Ubuntu 18.04.5 LTS Upon reboot, the following message is seen in apache2.service logs: -- Unit apache2.service has begun starting up. Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [REDACTED IPV6.33]:443 Oct 14 12:18:32 SERVER apachectl[3833]: no listening sockets available, shutting down Oct 14 12:18:32 SERVER apachectl[3833]: AH00015: Unable to open logs Oct 14 12:18:32 SERVER apachectl[3833]: Action 'start' failed. Oct 14 12:18:32 SERVER apachectl[3833]: The Apache error log may have more information. Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Failed with result 'exit-code'. Oct 14 12:18:33 SERVER systemd[1]: Failed to start The Apache HTTP Server. The apache2 configuration is using the ipv4 and ipv6 present on the server: /etc/apache2/ports.conf:Listen :443 /etc/apache2/ports.conf:Listen :443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::33]:443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::35]:443 - and the /etc/network/interfaces look as this (no netplan): + and the /etc/network/interfaces looks like this (no netplan): # Additional IPs that are used to serve https traffic for # releases.ubuntu.com so that archive doesn't respond on 443. auto bond0:1 iface bond0:1 inet static - address .247/32 - # Using up/down to avoid LP:1347246. - up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 - down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 + address .247/32 + # Using up/down to avoid LP:1347246. + up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 + down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 # Additional IPs that are used to serve *.clouds.archive.ubuntu.com # with HTTPProtocolOptions unsafe, which is needed to work around # cloud-init bug LP:1868232 (cRT#125271). auto bond0:2 iface bond0:2 inet static - address .245/32 - # Using up/down to avoid LP:1347246. - up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 - down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 + address .245/32 + # Using up/down to avoid LP:1347246. + up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 + down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 - I was surprised that the apache2.service does not contain a + I was surprised that the apache2.service does not contain a After=network-online.target $ systemctl show apache2.service | grep -E '(Wants|Require|After|Before)' RemainAfterExit=no Requires=system.slice sysinit.target -.mount Before=multi-user.target shutdown.target After=basic.target sysinit.target systemd-journald.socket system.slice network.target nss-lookup.target systemd-tmpfiles-setup.service remote-fs.target -.mount RequiresMountsFor=/var/tmp /tmp $ systemctl show network.target | grep "^After" After=network-pre.target ifup@bond0.service ifup@ens2f0.service ifup@ens2f1.service systemd-resolved.service ufw.service networking.service systemd-networkd.service So I was wondering if the "ifup@bond0" was enough as a dependency here, to be sure to have the ipv6 up and running or if we would need something like "ifup@bond0:2" and "ifup@bond0:1" as part of the list of the services in the network.target "After" list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899852 Title: Cannot assign requested address: AH00072: make_sock: could not bind to address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1899852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899889] Re: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page
** Package changed: dash (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896394] Re: Prevent add to favorite and vise versa when move apps to left or right
The bug is not confirmed until at least one other person understands and confirms it. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896394 Title: Prevent add to favorite and vise versa when move apps to left or right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899897] [NEW] package nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10
Public bug reported: Crash report at computer start ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 Uname: Linux 5.4.66-rt38 x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 14 23:10:01 2020 ErrorMessage: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-09-23 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450 Title: package nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899897 Title: package nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1899897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899889] Re: Add option to sort app icons by name
Thanks for the explanation. Just one note. This is affecting my Groovy install not Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: Add option to sort app icons by name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899902] [NEW] systemd unit service file does not wait for bind9 to be ready
Public bug reported: The details of this issue are available at Debian Bug report #900788 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788). The named service in Focal is defined as follows: $ cat /lib/systemd/system/named.service [Unit] Description=BIND Domain Name Server Documentation=man:named(8) After=network.target Wants=nss-lookup.target Before=nss-lookup.target [Service] EnvironmentFile=-/etc/default/named ExecStart=/usr/sbin/named -f $OPTIONS ExecReload=/usr/sbin/rndc reload ExecStop=/usr/sbin/rndc stop [Install] WantedBy=multi-user.target Alias=bind9.service Unfortunately, since bind9 starts up asynchronously, the services that depend on nss-lookup.target may fail DNS resolution due to bind9 not being started up in time. This, in some cases, leads to the crashing of services that resolve domain names on startup, for example, nginx that resolves its proxy upstream servers. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Description changed: The details of this issue are available at Debian Bug report #900788 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900788). The named service in Focal is defined as follows: $ cat /lib/systemd/system/named.service [Unit] Description=BIND Domain Name Server Documentation=man:named(8) After=network.target Wants=nss-lookup.target Before=nss-lookup.target [Service] EnvironmentFile=-/etc/default/named ExecStart=/usr/sbin/named -f $OPTIONS ExecReload=/usr/sbin/rndc reload ExecStop=/usr/sbin/rndc stop [Install] WantedBy=multi-user.target Alias=bind9.service Unfortunately, since bind9 starts up asynchronously, the services that depend on nss-lookup.target may fail DNS resolution due to bind9 not - being started up in time. This, in some cases, leads to crashing of + being started up in time. This, in some cases, leads to the crashing of services that resolve domain names on startup, for example, nginx that resolves its proxy upstream servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899902 Title: systemd unit service file does not wait for bind9 to be ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1899902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
@sudodus Using mkusb-dus / usb-pack-efi to prepare the live usb, I was able to boot the "Persistant Live" of Ubuntu MATE Groovy Desktop 20.10 Oct 14, 2020 ISO. Though the system booted fine, and I got to see the desktop screen, I have not actually installed the OS yet as I need to free up a partition for that. Many thanks for all the help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893711] Re: [hns3-0901]add hns3_gro_complete for HW GRO process
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893711 Title: [hns3-0901]add hns3_gro_complete for HW GRO process To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1893711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899907] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 10:18:16 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-04-15 (1643 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-15 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899907 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899907] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899907 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899260] Re: flightgear should be available in groovy
BTW, I succesfully built and tested it in my PPA: https://launchpad.net/~oibaf/+archive/ubuntu/test/+packages?field.name_filter=flightgear -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899260 Title: flightgear should be available in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/flightgear/+bug/1899260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
FYI- I do not have any HP boxes to test on re: bug 1899308 booting prob. my mixture is dell/lenovo/acer/mac/IntelNuc and InWin - none of these with boot issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899586] Re: Fix broken MSI interrupt after HDA controller was suspended
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Groovy) ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899586 Title: Fix broken MSI interrupt after HDA controller was suspended To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899889] [NEW] In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last pa
Public bug reported: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1899889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899889] Re: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page
I think this is correct. The current design allows you to drag icons and define your own order. Meaning the order of icons should stay unchanged, not sorted, even after installing new apps. But rather than closing this bug I will turn it into an enhancement request for the option to sort the icons. ** Summary changed: - In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. + Add option to sort icons by name ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Summary changed: - Add option to sort icons by name + Add option to sort app icons by name ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899889 Title: Add option to sort app icons by name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898817] Re: Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled server image
** Package changed: linux-raspi-5.4 (Ubuntu) => linux-raspi2 (Ubuntu) ** Changed in: linux-raspi2 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898817 Title: Wifi device disappear after upgrading linux-firmware-raspi2 with 18.04.3 preinstalled server image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1898817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899349] Re: Jack_control in jackd2 1.9.14 will not accept char parameters
This bug was fixed in the package jackd2 - 1.9.14-0ubuntu3.1 --- jackd2 (1.9.14-0ubuntu3.1) groovy; urgency=medium * debian/patches/git_dbus_bytes.patch: - Fix jack_control handling of dbus bytes, thanks Len (lp: #1899349) -- Sebastien Bacher Wed, 14 Oct 2020 09:59:30 +0200 ** Changed in: jackd2 (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/1899349 Title: Jack_control in jackd2 1.9.14 will not accept char parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899782] Re: lxqt-policykit-agent crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
I do not understand. It could happen when I log into graphical software that requires access to the root privileges of the lxqt operating system In the logs I see messages from: :~$ dmesg | grep policy [0.561388] AppArmor: AppArmor sha1 policy hashing enabled [ 106.605930] traps: lxqt-policykit-[2684] general protection fault ip:7fc153acc671 sp:7ffefa6161a8 error:0 in libgobject-2.0.so.0.6400.3[7fc153a9e000+36000] [ 180.309766] traps: lxqt-policykit-[6084] general protection fault ip:7fde2b1bd671 sp:7fff1ab2ffa8 error:0 in libgobject-2.0.so.0.6400.3[7fde2b18f000+36000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899782 Title: lxqt-policykit-agent crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-policykit/+bug/1899782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899780] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
** Tags added: lxqt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899780 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
FWIW, I tried the dwc2 overlay again with kernel 5.4.0-1021-raspi - as before in #21 this changes nothing - network still dies during first major (>100MB) download, while other USB ports continue working. On the plus side, the Pi can now actually boot with an external NIC plugged in. I'm not sure if the issue I had (boot getting stuck with external USB Ethernet adapter) got fixed or a hardware change I made (Apple USB Ethernet adapter -> generic RTL8153-based adapter) is responsible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR
I can confirm that it's fixed with image: http://cdimage.ubuntu.com/ubuntu-server/daily-live/20201014.1/groovy-live-server-s390x.iso I did two installations - on z/VM and on LPAR (both of course zFCP) - and the blockprobe issues no longer occurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893818 Title: Several blockprobe errors if trying to install the groovy daily live on LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
Probably distantly related to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/717 ** Tags added: focal osk ** Tags added: lock ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #717 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/717 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi again Jags Desai, I'm glad that you managed to boot when using mkusb. When you want to install Ubuntu-MATE, please read the tips at this link: https://help.ubuntu.com/community/mkusb/persistent#Installing_- _using_the_Install_icon_on_the_desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899499] Re: nvidia-kernel-source-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (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/1899499 Title: nvidia-kernel-source-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1899499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
In the meantime I'm on 5.4.0-51-generic #56, but it's still happening. Google more about the error, there are some indications that it could be a faulty/bad firmware problem: https://www.kernel.org/doc/html/v5.4/sound/hd-audio/notes.html#codec- probing-problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899776] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
same problem with latest mainline Linux x 5.9.0-050900-generic #202010112230 SMP Sun Oct 11 22:34:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899776 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899893] [NEW] [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements
Public bug reported: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) 1. Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg 2. Add screen keyboard modes (option to morph into several keyboards) Normal(default), Thumb and Standard (standard has all keys has on physical keyboard) https://gitlab.com/cloud.ch/bugs/-/raw/master/modes.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/thumb.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/standard.jpg 3. Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Enable it through universal access > screen keyboard then it quite annoying due pop up often) https://gitlab.com/cloud.ch/bugs/-/raw/master/screenkeyboard.png ** Affects: gnome-shell (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/1899893 Title: [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I solved the problem changing the gnome theme to Adwaita using gnome tweaks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Chris, 1. In the meantime I tested the current Lubuntu Groovy iso file in the HP Elitebook 8560p. It boots when I made a nopersistent live drive using mkusb-plug, and I could repeat it. 2. I don't know if the error that you see at shutdown causes failure at the next boot (when there is an ext partition). Maybe. I think we help from Steve or Thomas to dig deeper into that problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896575] Re: [UBUNTU 20.04] syslog daemon stop running unexpectedly
The SCSI devices in the logs made me think that this is an environment
with standard zFCP storage - iSCSI is of course d different thing.
Sharing /etc/fstab and some more details about the disk and filesystem layout
could be helpful.
I assume that the second system has a similar configuration than the first one
(again iSCSI)?
I saw that lszdev shows several DASDs - is /var/log is placed on a local
(DASD) disk or on an iSCSI volume?
If the disk/fs for rsyslogd is on iSCSI (especially on sdq or sdaa in
your example) I think this problem is likely a follow-on problem of the
disk issues that are reported:
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB:
Inquiry 12 01 c9 00 fe 00
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664542] sd 3:0:0:2: [sdt] tag#81 Sense
Key : Illegal Request [current]
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664543] sd 3:0:0:2: [sdt] tag#81 Add.
Sense: Invalid field in cdb
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664656] sd 4:0:0:2: [sdq] tag#32 Done:
SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 CDB:
Inquiry 12 01 c9 00 fe 00
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664657] sd 4:0:0:2: [sdq] tag#32 Sense
Key : Illegal Request [current]
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664658] sd 4:0:0:2: [sdq] tag#32 Add.
Sense: Invalid field in cdb
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664773] sd 5:0:0:2: [sdaa] tag#48
Done: SUCCESS Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664774] sd 5:0:0:2: [sdaa] tag#48 CDB:
Inquiry 12 01 c9 00 fe 00
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664775] sd 5:0:0:2: [sdaa] tag#48
Sense Key : Illegal Request [current]
The sense codes 3 4 and 5 of the driver byte point to:
3 MEDIUM ERROR
4 HARDWARE ERROR
5 ILLEGAL REQUEST
(https://www.t10.org/lists/2sensekey.htm)
Such errors occur in your initial log (bug description) as well as in the
attached rsyslog.debug output.
If you have system with local storage only (e.g. DASD only) I would
assume that you will not face such rsyslogd issues. Can you please try
or check on an existing non-iSCSI system, too?
And btw. did you ran 'multipath -ll' (and maybe 'lvs') when the problem
happened and rsyslogd stopped? Were any failures ('Failed Path' or
'device-mapper: multipath: Failing path') reported?
I at least saw some access timeouts in the logs.
(Just as a side note: this problem is reported on 'Launchpad', the bug
and issue tracking system of Canonical/Ubuntu. In case the problems
occurs on a production system, it's recommended to open a salesforce
case based on an UA account. That would provide dedicated severity
levels and response times.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896575
Title:
[UBUNTU 20.04] syslog daemon stop running unexpectedly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896575/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899913] [NEW] touchpad not detected lenovo yoga slim
Public bug reported: I have installed ubuntu 20.04 in lenovo yoga slim 7i, the touchpad is not getting detected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: puneethchanda 1338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 13:58:50 2020 InstallationDate: Installed on 2020-10-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82A1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=c1f15954-8464-48af-bba3-e2d5152112cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN27WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDHCN27WW:bd05/22/2020:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899913 Title: touchpad not detected lenovo yoga slim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899766] Re: Xorg freeze after selecting large cursor
Found the source of the v4l warnings; I was experimenting with v4lloopback to use a camera as webcam. Disabled that and it's gone away. Unfortunately, /var/crash is empty and I didn't see any report from the right time in the errors webpage. After applying the change to add "Crash" to the crashdb.conf, I still don't see a crash dump in /var/crash after repro. However, I did find that the problem only repros in NVIDIA PRIME mode, not Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899766 Title: Xorg freeze after selecting large cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899913] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899913 Title: touchpad not detected lenovo yoga slim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898419] Re: Webcamoid should not notify user about new version if installed from universe pocket as deb package
** Also affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate-settings (Ubuntu) Status: New => Fix Released ** Changed in: webcamoid (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898419 Title: Webcamoid should not notify user about new version if installed from universe pocket as deb package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1898419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi, i now am boss of my mainboard ASUS ProWS C246-ACE EFI firmware 1401, at least as long i do not want to disable Secure Boot. The hardware provider was of not of help with USB sticks, but remembers to have inserted Debian 10.4.0 netinst on CD-RW when SSD and HDD were still without bootable system. The EFI confused me old BIOS owner by not attributing external devices a high boot priority. I have to go into the EFI setup and move the offered drive (USB stick or CD reader) to the top of the list. Then it boots. This setting gets forgotten as soon as i boot again. Next stumblestone was that my large 128 GB stick causes a long delay with booting, is then not presented as boot device, and does not show up in a booted Debian 10, if i plug it into a blue USB socket. In a black socket it works for Linux and is recognized by EFI after i powered down the machine after unplugging from blue and plugging into black. (An old 2 GB stick with Debian 10.4.0 netinst on it works at blue USB sockets.) I tested from USB stick successfully up to the GRUB menu: groovy-desktop-amd64.iso 20201007.1 MBR-only groovy-desktop-amd64.iso 20201010 GPT without boot flag groovy-desktop-amd64.iso 20201015 GPT with boot flag The 20201010 version was also tested from DVD+RW. (There is no difference between the three ISO as far as the El Torito catalog is concerned.) Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898419] Re: Webcamoid should not notify user about new version if installed from universe pocket as deb package
Marked as fixed in ubuntu-mate-settings 20.10.1 as per https://launchpad.net/ubuntu/+source/ubuntu-mate-settings/20.10.1 . The webcamoid package itself is untouched. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898419 Title: Webcamoid should not notify user about new version if installed from universe pocket as deb package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1898419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi @sudodus (1) The HP desktop have AMD radeon 290X graphics card. (2) Ubuntu MATE Focal 20.04 with kernel 5.9.0 and 5.8.14 runs just fine on the same HP PVILION eLITE DESKTOP. (3) Yes, as described in my previous post, when I try to boot the system from Ubuntu MATE Groovy desktop Oct 14, 2020 Live USB (prepared either with Etcher or MultiBootUSB), I do NOT get Grub from Live USB at all. Cursor blinks once or twice and immediately I get "installed version" of the Grub from Ubunbtu MATE Focal 20.04 (4) Regarding the "mkusb". Is this the correct PPA to install it from? https://launchpad.net/~mkusb/+archive/ubuntu/ppa Because I just added the PPA (and added the signing key / fingerprint) but afterwards I only get "mkusb" in Synaptic. I can not find "mkusb-dus". Or are they one and same package? (5) I will try once again with mkusb with the settings you've suggested. Thanks alot. - Jags -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899893] Re: [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements
In future please be careful to only report one issue per bug. Let's start by making this just about a moveable keyboard... ** Tags added: osk ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements + Ubuntu default screen keyboard to be movable ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899893 Title: Ubuntu default screen keyboard to be movable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Hi Jags Desai, Yes, mkusb-dus (alias dus) is part of the mkusb package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867118] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-15 03:37 EDT---
@Canonical: Where is this commit currently integrated
commit 709192d531e5 ("s390/dasd: Fix zero write for FBA devices").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867118
Title:
dasd_fba io error and kernel panic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
You need the package 'usb-pack-efi' too. sudo add-apt-repository ppa:mkusb/ppa # and press Enter sudo apt update sudo apt install mkusb usb-pack-efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538234] Re: Right-clicking on an application in the Activities Overview list should give you options but also display program information
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Tags added: focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538234 Title: Right-clicking on an application in the Activities Overview list should give you options but also display program information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1538234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896638] Re: Path to swapfile doesn't use a static device path
This bug was fixed in the package ec2-hibinit-agent - 1.0.0-0ubuntu11 --- ec2-hibinit-agent (1.0.0-0ubuntu11) groovy; urgency=medium * Disable suspending the system (LP: #1898087) * Always set resume device by PARTUUID instead of by device name. Based on patch by Francis Ginther. (LP: #1896638) -- Balint Reczey Wed, 14 Oct 2020 20:49:52 +0200 ** Changed in: ec2-hibinit-agent (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896638 Title: Path to swapfile doesn't use a static device path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Same for me. Also Alt + F2 and executing "r" resolved it... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
@sudodus/Nio - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) thumb-drive was created as requested by @sudodus comment #41 Ubuntu 2020-10-14 groovy daily ISO (same as comment #40) (1) wiped thumb-drive (2) `mkusb-plug groovy-desktop-amd64.iso` (option N or non-persistent was selected) It's been booted TWICE successfully on the box. I'm out of time so will have to continue testing later. Of note on shutdown: IO errors on shutdown, sdb . async page read Are those (now) errors what corrupts the normal written `dus groo` ISO? data is written to device? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899897] Re: package nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899897 Title: package nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-450 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1899897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
We did the same seed changes in xubuntu now as in other flavors, don't think there's much more we can do. Can someone test the 20201015 xubuntu image (or newer)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Description changed: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data -stream" on z15. + stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware -compression state and returns an incorrect result. + compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. -The hardware does not provide enough information in order to -implement this function. + The hardware does not provide enough information in order to + implement this function. + + + [Impact] + + * Certain rsync builds fail with "error in rsync protocol data stream" + on z15. + + * rsync with non-default zlib compression (-z flag) uses + inflateSyncPoint() API. + + * inflateSyncPoint() does not take into account the hardware + compression state and returns an incorrect result. + + * Make inflateSyncPoint() fail if the hardware compression is on. The + hardware does not provide enough information in order to implement this + function. + + * Above makes rsync to succeed, when zlib uses hardware compression. + + [Test Case] + Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 + + [Regression Potential] + + * inflateSyncPoint API is rarely used. Scanning codesearch, there is a + lot of false positives due to embedded copies of zlib in all the things. + I do see that both rsync and backuppc-rsync use it. It used during a + safety check to ensure that algorithm is not at a sync point (or that + cannot be determined). Nonetheless, returning error is a safer + implementation for this API call. + + [Other Info] + + * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. ** Description changed: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. + [Impact] - [Impact] - - * Certain rsync builds fail with "error in rsync protocol data stream" + * Certain rsync builds fail with "error in rsync protocol data stream" on z15. - * rsync with non-default zlib compression (-z flag) uses - inflateSyncPoint() API. + * On ubuntu, rsync normally uses zstd or lz4. But when rsync is forced + to use non-default zlib compression (-z flag) it uses inflateSyncPoint() + API. This can also happen when rsync on the the other end doesn't + support zstd & lz4. - * inflateSyncPoint() does not take into account the hardware + * inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. - * Make inflateSyncPoint() fail if the hardware compression is on. The + * Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. - * Above makes rsync to succeed, when zlib uses hardware compression. + * Above makes rsync to succeed, when zlib uses hardware compression. [Test Case] Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 [Regression Potential] - * inflateSyncPoint API is rarely used. Scanning codesearch, there is a + * inflateSyncPoint API is rarely used. Scanning codesearch, there is a lot of false positives due to embedded copies of zlib in all the things. I do see that both rsync and backuppc-rsync use it. It used during a safety check to ensure that algorithm is not at a sync point (or that cannot be determined). Nonetheless, returning error is a safer implementation for this API call. [Other Info] - - * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. + + * This is a regression introduced by adding & enabling zlib hw + acceleration by default on z15; and discovering using rsync that one API + is implemented incorrectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions -- ubuntu-bugs mailing list
[Bug 1898087] Re: Please disable suspend when the package is installed
This bug was fixed in the package ec2-hibinit-agent - 1.0.0-0ubuntu11 --- ec2-hibinit-agent (1.0.0-0ubuntu11) groovy; urgency=medium * Disable suspending the system (LP: #1898087) * Always set resume device by PARTUUID instead of by device name. Based on patch by Francis Ginther. (LP: #1896638) -- Balint Reczey Wed, 14 Oct 2020 20:49:52 +0200 ** Changed in: ec2-hibinit-agent (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898087 Title: Please disable suspend when the package is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1898087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899851] Re: Intel Media Q3 release integration into Ubuntu 20.10
** Package changed: ubuntu => intel-media-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899851 Title: Intel Media Q3 release integration into Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1899851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899946] [NEW] update to 20.04 fails
Public bug reported: 2020-10-15 12:13:12,549 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' 2020-10-15 12:13:12,550 DEBUG abort called 2020-10-15 12:13:12,586 DEBUG openCache() 2020-10-15 12:13:14,742 DEBUG Comparing 4.15.0-118 with 2020-10-15 12:13:14,743 DEBUG Comparing 4.15.0-121 with 4.15.0-118 2020-10-15 12:13:14,950 DEBUG /openCache(), new cache size 100372 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 12:13:50 2020 InstallationDate: Installed on 2016-04-08 (1651 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-15 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899946 Title: update to 20.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899962] [NEW] Wrong audio output device selected on Raspberry Pi Desktop
Public bug reported: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. ** Affects: pulseaudio (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/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda
@Łukasz Zemczak (sil2100) Xubuntu 20201015 still fails on QuickEMU legacy. ** Attachment added: "xubuntu-20201015-fail.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+attachment/5422578/+files/xubuntu-20201015-fail.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885414 Title: on flavours ubiquity: bootloader failed on /dev/vda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1885414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
@ Thomas, 1. I know that it can improve things to start from a wiped drive, but I don't know why. I know that before you got involved and started to improve the booting, the systems could not create the ext4 partition in my computers, unless the USB drive was wiped, and I *think* this was independent of what was at the end of the drive. Maybe I am wrong there. Anyway see https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895329 and for example comment #4. Earlier today I tested drives *with 'nopersistent' without prior wiping*, and if I understood correctly it made a difference when booting the HP Elitebook 8560p. But the behaviour of cloned drives was flaky, so it is not easy to be sure what happens by chance and what is really reproducible. I think we should do some more tests before we can be sure of what happens. That way we can find out if the backup partition table at the end of the drive makes a difference in this case. 2. I think USB pendrives are not well standardized. They are tested to work as data storage devices with Windows and MacOS. Booting is not important enough for the manufacturers of USB pendrives to do thorough tests. Maybe the same is true for the USB systems in computers. Anyway most computers can be booted by most USB pendrives, but I have seen and read about many exceptions. I had an own case when a USB drive did not boot when connected directly to the computer, but was happy to boot the same computer when connected via an external USB hub. It is also my experience that booting is more likely to succeed via USB2 ports than via USB3 ports, and it was a trial and error adventure to find a USB3 hub, that works well with booting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
** Changed in: autofs (Ubuntu) Status: Incomplete => Invalid ** Changed in: autofs (Ubuntu Focal) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897744] Re: VerifyHostKeyDNS not working due to missing trust-ad flag
** Description changed: [impact] without trust-ad resolv.conf option, glibc will strip AD from systemd- resolved responses. one thing this will prevent working is ssh VerifyHostKeyDNS [test case] - setup a target system to ssh into, and create a SSHFP DNS record for its - public key. on a different source system, setup dns to enable DNSSEC, - and attempt to ssh to the target system using the VerifyHostKeyDNS=yes - option. - - setup of the SSHFP is out of scope for this bug, but e.g.: - https://en.wikipedia.org/wiki/SSHFP_record - https://tools.ietf.org/html/rfc4255 + see + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1898590/comments/7 [regression potential] regressions would likely involve DNS lookup failures, probably if DNSSEC is enabled but possibly even without, and likely when the application requesting the dns lookup processes the response AD. [scope] this is needed only in focal. glibc first stripped the AD in version 2.31, so this is not needed in bionic or earlier. this was added upstream in commit a742f9828ea which was included in v246, so this is fixed already in groovy. [original description] Hi, 1) Description: Ubuntu 20.04.1 LTS Release: 20.04 2) systemd:245.4-4ubuntu3.2 3) I set VerifyHostKeyDNS to YES and hosts are automatically verified via sshfp. 4) I still get the security question Matching host key fingerprint found in DNS. Are you sure you want to continue connecting (yes/no/[fingerprint])? The issue is known and fixed in systemd v246. https://github.com/systemd/systemd/pull/16072 Best regards Daniel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899973] [NEW] package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
Public bug reported: Error after reinstall ProblemType: Package DistroRelease: Ubuntu 20.04 Package: snapd 2.46.1+20.04 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 15 09:38:24 2020 DpkgTerminalLog: dpkg: ошибка при обработке пакета snapd (--configure): пакет абсолютно неработоспособен; перед настройкой его следует переустановить ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2020-10-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: snapd Title: package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899973 Title: package snapd 2.46.1+20.04 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1899973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899982] Re: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899982 Title: package linux-image-5.4.0-51-generic 5.4.0-51.56 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1899982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
https://twistedmatrix.com/trac/ticket/9410 ** Also affects: twisted (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/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
It also seems like this has the effect for the impacted user I'm currently helping to always have this message in the UI: "X rack controllers are not yet connected to the region. Visit the rack controllers page for more information". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741913] Re: [master] Twisted seems to not handle disconnect from client correctly
https://github.com/twisted/twisted/commit/169fd1d93b7af06bf0f6893b193ce19970881868 # git describe --contains 169fd1d93b twisted-19.7.0~20^2~13 # rmadison python3-twisted | 17.9.0-2ubuntu0.1 | bionic-updates | all python3-twisted | 18.9.0-11 | focal | all python3-twisted | 18.9.0-11 | groovy | all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741913 Title: [master] Twisted seems to not handle disconnect from client correctly To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1741913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
Thanks but The mute led is still not working. No it has just The audio mute led, no mic one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
Hello Michael, thanks for the followup and for filing the bug in the first place. For the moment I'm changing the status of this report to Incomplete across the packages/series it targets. If this specific issue can't be reproduced anymore please set the statuses to Invalid (I'd prefer it to Fix Released as we didn't identify what actually fixed it), and go ahead filing a new bug for the remaining issues you're facing. On the other hand if you still think this should be investigated please comment back with your findings, change the bug status back to New and we'll look at it again. Thanks! ** Changed in: autofs (Ubuntu) Status: Triaged => Incomplete ** Changed in: autofs (Ubuntu Focal) Status: Triaged => Incomplete ** Changed in: systemd (Ubuntu) Status: Triaged => Incomplete ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880193 Title: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899964] [NEW] Failover of loadbalancer fails when Amphora master is missing
Public bug reported: Tried to failover a loadbalancer that has missing entries of amphora master. The loadbalancer went to ERROR state. OpenStack version: Train The fix is available in upstream as part of the Octavia Failover refactor patches in Train https://review.opendev.org/#/q/status:merged+project:openstack/octavia+branch:stable/train+topic:failover-refactor Verified with the upstream patches and it worked. ** Affects: octavia (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/1899964 Title: Failover of loadbalancer fails when Amphora master is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/1899964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899964] Re: Failover of loadbalancer fails when Amphora master is missing
** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Also affects: cloud-archive/train Importance: Undecided Status: New ** Also affects: cloud-archive/victoria Importance: Undecided Status: New ** Changed in: cloud-archive/victoria Status: New => Fix Committed ** Changed in: octavia (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899964 Title: Failover of loadbalancer fails when Amphora master is missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1899964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899965] [NEW] AVHWDeviceContext: Failed to query surface attributes
Public bug reported: Hi, using mpv to view a h264 video displays the following error message: $ mpv foo.mkv (+) Video --vid=1 (*) (h264 1440x924 25.000fps) [ffmpeg] AVHWDeviceContext: Failed to query surface attributes: 20 (the requested function is not implemented). [vo/gpu/vaapi-egl] failed to retrieve libavutil frame constraints Using hardware decoding (vaapi). [...] The video is correctly displayed, though. There are 2 drivers, a free (i915) and a non-free (iHD): -rw-r--r-- 1 root root 8098968 Feb 6 2020 /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so -rw-r--r-- 1 root root 35102696 Apr 21 08:50 /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so Using the free driver with LIBVA_DRIVER_NAME=i965 mpv foo.mkv gives no error, whereas using the non-free driver with LIBVA_DRIVER_NAME=iHD mpv foo.mkv leads to the above error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: intel-media-va-driver-non-free 20.1.1+ds1-1build1 Uname: Linux 5.8.15-050815-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Oct 15 14:11:45 2020 SourcePackage: intel-media-driver-non-free UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: intel-media-driver-non-free (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899965 Title: AVHWDeviceContext: Failed to query surface attributes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver-non-free/+bug/1899965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (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/1899878 Title: Python's test_ssl fails starting from Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
@ everybody, In the light of the lasts findings, questions and suggestions, I did some more tests, this time with yesterday's Xubuntu Groovy iso file, that failed booting yesterday. I think I started testing the cloned USB drive in the Lenovo V130 (which worked), and continued testing in the HP Elitebook 8560p. Anyway, today I started with a cloned drive (without prior wiping) and testing booting in the HP Elitebook 8560p. - Successful boot first time, and an ext4 partition was created - Failed boot after that: the drive was not recognized (could be repeated) Then I created a 'nopersistent' drive with mkusb-plug in the same drive (without prior wiping) and testing booting in the HP Elitebook 8560p. - Successful boot first time. No ext4 partition was created - Successful boot after that (could be repeated) I conclude that the crucial thing is the existence of the ext4 partition (and maybe other things associated with it - corruption, backup gpt table at the tail end of the drive ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881762] Re: resource timeout not respecting units
After testing I can confirm that this new version by all accounts fixes the reported bug. Stopping and starting a systemd resource with timeout = "10s" does not fail with timeouts I tested this by installing the original 2.0.3-3ubuntu3, and reproducing the bug. then I upgraded to 2.0.3-3ubuntu4 (the proposed) and cannot reproduce the bug. Marking this as resolved ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881762 Title: resource timeout not respecting units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1881762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888765] Re: [MIR] oem-sutton.simon-camellia-meta
** Patch added: "oem-sutton.simon-camellia-meta.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1888765/+attachment/5422517/+files/oem-sutton.simon-camellia-meta.debdiff ** Attachment removed: "camellia.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1888765/+attachment/5399511/+files/camellia.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888765 Title: [MIR] oem-sutton.simon-camellia-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1888765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899853] Re: Screen freezing
It fixed a lot of it but there is still a bit of lag/buffering when watching streams. I am new to ubuntu and used windows before so I never really experienced anything like this on WIndows 10. I attached the journal.txt file ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+bug/1899853/+attachment/5422521/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899853 Title: Screen freezing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899955] [NEW] New Freeze Exception: Exceptional circumstance
Public bug reported: A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution: Changing the default wallpaper from the existing Groovy Gorilla illustration to the Raspberry Pi specific one with the Raspberry in his sunglasses. "We'll basically need to revert https://launchpad.net/ubuntu/+source /ubuntu-settings/20.10.2 and https://launchpad.net/ubuntu/+source /ubuntu-wallpapers/20.10.2-0ubuntu1 and update the warty-final- ubuntu.png" A rationale for the exception, explaining the benefit of the change: The benefit is to pay homage to the work various teams have been doing with the Raspberry Pi foundation and to their product. It's a way to signal our commitment to making their platform great and deepen our relationship with the Pi foundation. Any additional information which would be helpful in considering the decision The concerns people have are of product placement and forcing something onto peoples machines. There are several arguments against this, the option to change to the default easily, that there is not direct link to Raspberry Pi anything and its quite subtle. But ultimately the reason is we want to make a splash with the Raspberry Pi and arm in general and this is a very good way to do it. ** Affects: ubuntu-wallpapers (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/1899955 Title: New Freeze Exception: Exceptional circumstance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1899955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899954] [NEW] SRU: backport Python 3.9.0 to 20.04 LTS
Public bug reported: Backport python 3.9.0 to focal, updating from the first release candidate. Regression potential: 3.9 is not used by default, and not used as any build dependency. Therefore the potential is very low. Validation: python3.9's Test results show no regressions, and the packages are successfully built. ** Affects: python3.9 (Ubuntu) Importance: Undecided Status: New ** Description changed: - Backport python 3.9.0 to focal. + Backport python 3.9.0 to focal, updating from the first release + candidate. Regression potential: 3.9 is not used by default, and not used as any build dependency. Therefore the potential is very low. Validation: python3.9's Test results show no regressions, and the packages are successfully built. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899954 Title: SRU: backport Python 3.9.0 to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1899954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877844] Re: [SRU] data corruption issue in all versions before 1.1.11
xenial 16.04: upgrade from the current 1.0.12 to 1.0.13-0ubuntu1.16.04.1 (a.k.a. stock 1.0.13 + this fix cherry-picked from 1.0 maint branch) bionic 18.04: upgrade to 1.1.14-2ubuntu18.04.1 (sorry, just the versioning in changelog was wrong!) focal 20.04: upgrade to 1.1.14-2ubuntu20.04.1 I fixed the changelog, changed from 20 to 18 and reuploaded to bionic (and uploaded the focal version too) ** Changed in: borgbackup (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: borgbackup (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877844 Title: [SRU] data corruption issue in all versions before 1.1.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1877844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899953] [NEW] Crackling audio on Raspberry Pi Desktop
Public bug reported: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. ** Affects: pulseaudio (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/1899953 Title: Crackling audio on Raspberry Pi Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Fix on #211 Another header file hid-ids.h is required to build i2c-hid module. Attached is the updated zip file. ** Attachment added: "i2c-hid_standalone.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5422562/+files/i2c-hid_standalone.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899951] [NEW] Problemi nell'aggiornamento a Ubuntu 20.04
Public bug reported: Si è verificato un problema irresolubile durante il calcolo dell'avanzamento. Ciò può essere causato da: * Pacchetti software non ufficiali non forniti da Ubuntu Utilizzare lo strumento «ppa-purge» incluso nel pacchetto ppa-purge per rimuovere software installato via un PPA Launchpad PPA e riprovare l'avanzamento. Nel caso fosse un altro problema, segnalare un bug eseguendo in un terminale il seguente comando: «ubuntu-bug ubuntu-release-upgrader- core». Per investigare il problema consultare i file di registro in «/var/log/dist-upgrade» che possono contenere maggiori dettagli riguardo all'avanzamento. In particolare, consultare i file «main.log» e «apt.log». Da main log 2020-10-15 11:24:23,312 DEBUG Marking 'ubuntu-desktop' for upgrade 2020-10-15 11:24:23,519 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati.) 2020-10-15 11:25:48,252 ERROR Dist-upgrade failed: 'Broken packages after upgrade: ubuntu-desktop' 2020-10-15 11:25:48,253 DEBUG abort called 2020-10-15 11:25:48,257 DEBUG openCache() 2020-10-15 11:25:51,367 DEBUG Comparing 4.15.0-117 with 2020-10-15 11:25:51,367 DEBUG Comparing 4.15.0-118 with 4.15.0-117 2020-10-15 11:25:51,368 DEBUG Comparing 4.15.0-121 with 4.15.0-118 2020-10-15 11:25:51,600 DEBUG /openCache(), new cache size 96112 oppure 2020-10-15 11:38:42,245 DEBUG Marking 'ubuntu-desktop' for upgrade 2020-10-15 11:38:42,450 WARNING Can't mark 'ubuntu-desktop' for upgrade (E:Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati.) Da apt.log Broken ubuntu-desktop:amd64 Dipende on xorg:amd64 < 1:7.7+19ubuntu7.1 @ii mR > Considering xorg:amd64 1 as a solution to ubuntu-desktop:amd64 1 Done Log time: 2020-10-15 11:25:51.588345 Io ho rimosso le PPA che avevano problemi: ho lasciato quelle per wine, libreoffice e google. Distinti saluti Carlo Sarti ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 12:40:36 2020 InstallationDate: Installed on 2017-11-26 (1053 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-15 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899951 Title: Problemi nell'aggiornamento a Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899952] [NEW] onionshare should not be in multiverse
Public bug reported: Hello! As per package info[0] onionshare is in multiverse. But since this[1] Ubuntu help page says that "Multiverse - Software restricted by copyright or legal issues" and onionshare is released under GPL[2], oninshare should not be in multiverse. It should be in Universe IMHO. Thanks! [0] https://packages.ubuntu.com/focal/onionshare [1] https://help.ubuntu.com/community/Repositories/Ubuntu [2] https://github.com/micahflee/onionshare/blob/develop/LICENSE ** Affects: onionshare (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/1899952 Title: onionshare should not be in multiverse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onionshare/+bug/1899952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899963] [NEW] package kicad-demos (not installed) failed to install/upgrade: trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', which is also in package kicad-demo 5.0.
Public bug reported: Recevied error message failed to apply Start Kernel modules at log in ProblemType: Package DistroRelease: Ubuntu 20.04 Package: kicad-demos (not installed) ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 7 22:24:51 2020 ErrorMessage: trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', which is also in package kicad-demo 5.0.2-stable-201811280959+bee76a0~70~ubuntu18.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: kicad Title: package kicad-demos (not installed) failed to install/upgrade: trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', which is also in package kicad-demo 5.0.2-stable-201811280959+bee76a0~70~ubuntu18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kicad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-hook-error apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899963 Title: package kicad-demos (not installed) failed to install/upgrade: trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', which is also in package kicad-demo 5.0.2-stable-201811280959+bee76a0~70~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kicad/+bug/1899963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898200] Re: [SRU] ceph 15.2.5
Uploaded to focal UNAPPROVED for SRU team review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898200 Title: [SRU] ceph 15.2.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1898200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899832] Re: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (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/1899832 Title: CONFIG options for (ipip, sit) should not be built-in to the KVM kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1899832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863498] Re: raise ValueError('malformed node or string: ' + repr(node)) ValueError: malformed node or string: b"['$HOME']\n"
** Changed in: ubuntu-mate
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863498
Title:
raise ValueError('malformed node or string: ' + repr(node))
ValueError: malformed node or string: b"['$HOME']\n"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup-caja/+bug/1863498/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] [NEW] samba SMB share certain operations fail
Public bug reported: Samba SMB shares accessed from Windows or Mac OS don't work as expected when using tools like Git or npm (node package manager). Expected: For example, Git clones to a folder mounted via SMB, as it did with previous ubuntu versions What happened: When using git clone in an smb mounted directory, git throws the following errors: warning: unable to unlink 'images': Directory not empty fatal: cannot create directory at 'images': Directory not empty The errors vary a bit every run (stops at different files/dirs) when extracting or doing other operations. Copying and writing from files via the file browser works without a problem. I could reproduce the error in the following environment with the latest updates applied: Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-51.56-generic 5.4.65) Ubuntu 20.04.1 LTS (Ubuntu 5.4.0-48.52-generic 5.4.60) Samba version 4.11.6-Ubuntu Clients: Windows 10 Version 10.0.18363 Build 18363, Mac OS 10.13.6 On a fresh install with Ubuntu 18.04 (Samba 4.7.6) and CentOS 7 (Samba 4.11) as SMB servers the error does NOT occur, with the same standard smb.conf. Also, setting the following options in smb.conf did NOT help: mangled names = Yes oplocks = False level2 oplocks = False I will happily provide any information/testing that is necessary. Thank you ** Affects: samba (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/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864306] Re: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
I have two instances running with the same provider (Linode). One upgraded fine about a month ago. The other has this grub-pc error. The only differences I noted in the /boot/grub folder was that the one that is not working has the default and menu.lst files present. Not sure if it is related but it would appear (anecdotally) that something changed between my upgrading of the two instances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864306 Title: package grub-pc 2.04-1ubuntu12.1 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1864306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Still occurring on 20.04.1 LTS. Laptop (Lenovo E490) has power connected, lid is closed, Automatic suspend when plugged in is disabled; still suspends after a while. I'll now try messing with logind.conf and see if I can get it to behave the way I want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890815] Re: vainfo requires a nvidia sofile not in repositories
I'm facing same issue. This is not the only package missing in 20.04 I has issues install some other packages too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890815 Title: vainfo requires a nvidia sofile not in repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva-utils/+bug/1890815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898904] Re: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel'
Patch applied. Thanks! Hope the package in the repository will be fixed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898904 Title: Calibre crashes at startup with AttributeError: 'NoneType' object has no attribute 'cancel' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1898904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899968] Re: samba SMB share certain operations fail
Can you clarify one scenario that reproduces the problem, being explicit about what the server is, and the client? cifs-utils (and the kernel?) could very well be involved here. Also the server share config please. Or can you show the bad/good behavior by just by switching servers, and keeping the same client? It also may matter which SMB protocol was used for the mount, as defaults have changed. To be honest, I'm suspecting it's unix extensions that are not being used, since the default cifs mount option changed from SMB1 (deprecated nowadays) to SMB2 and higher, and unix extensions are not yet available for these higher protocol versions. To see which version was selected, you can type "mount -t cifs" or check dmesg right after a mount was done. ** Changed in: samba (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/1899968 Title: samba SMB share certain operations fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1899968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
