[Bug 2081172] Re: dracut generated initramfs doesn't contain necessary files for iscsi boot
Yes, it is installed. This is from the instance that I used to create the image that later on boots from iscsi: ubuntu@oracular-dracut:~$ sudo dpkg -l dracut-network Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==--- ii dracut-network 103-1ubuntu2 all dracut is an event driven initramfs infrastructure (network modules) I noticed that, when regenerating the initramfs, we get an error that says: dracut[I]: *** Including module: iscsi *** Failed to enable unit: Unit iscsiuio.socket does not exist Not sure if its related. Full output: https://pastebin.ubuntu.com/p/HFmCD9s4WZ/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081172 Title: dracut generated initramfs doesn't contain necessary files for iscsi boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2081172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081172] [NEW] dracut generated initramfs doesn't contain necessary files for iscsi boot
Public bug reported: When running Ubuntu 24.10 (Oracular Oriole) and switching from initramfs to dracut (by installing dracut packages and following instructions in /usr/share/doc/dracut-core/README.Debian), the initramfs generated by dracut won't include the necessary files to allow an instance to boot from iscsi. The following packages were installed: ii dracut 103-1ubuntu2 all Initramfs generator using udev ii dracut-core103-1ubuntu2 amd64dracut is an event driven initramfs infrastructure (core tools) ii dracut-install 103-1ubuntu2 amd64dracut is an event driven initramfs infrastructure (dracut-install) ii dracut-network 103-1ubuntu2 all dracut is an event driven initramfs infrastructure (network modules) When trying to boot from iscsi by adding the following cmdline to grub (booting from ISCSI in an Oracle Cloud instance): BOOT_IMAGE=/vmlinuz-6.8.0-1005-oracle root=UUID=f692dbf6-c1a4-4a31-8585-2571fbbd2f7e ro console=tty1 console=ttyS0 nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1 crash_kexec_post_notifiers rd.luks=0 rd.md=0 rd.dm=0 rd.net.timeout.carrier=5 rd.iscsi.param=node.session.timeo.replacement_timeout=6000 net.ifnames=1 ipmi_si.tryacpi=0 ipmi_si.trydmi=0 libiscsi.debug_libiscsi_eh=1 loglevel=4 rd.net.timeout.dhcp=10 ip=dhcp netroot=iscsi:169.254.0.2:::1:iqn.2015-02.oracle.boot:uefi The boot fails with: [ OK ] Reached target network-online.target - Network is Online. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. Starting iscsid.service - iSCSI initiator daemon (iscsid)... [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. [6.891677] dracut-initqueue[582]: iscsiadm: read error (-1/104), daemon died? [ OK ] Listening on iscsid.socket - Open-iSCSI iscsid Socket. [FAILED] Failed to start iscsid.service - iSCSI initiator daemon (iscsid). See 'systemctl status iscsid.service' for details. [7.909211] dracut-initqueue[582]: iscsiadm: read error (-1/104), daemon died? [7.910096] dracut-initqueue[582]: iscsiadm: Cannot perform discovery. Initiatorname required. [7.911164] dracut-initqueue[582]: iscsiadm: Could not perform SendTargets discovery: could not communicate to iscsid [7.913629] dracut-initqueue[521]: Warning: Target discovery to 169.254.0.2:3260 failed Eventually the instance will drop to an emergency shell and we can check the error in details: # journalctl -u iscsid --no-pager Sep 18 19:58:40 localhost systemd[1]: Starting iscsid.service - iSCSI initiator daemon (iscsid)... Sep 18 19:58:40 localhost (hecks.sh)[584]: iscsid.service: Unable to locate executable '/usr/lib/open-iscsi/startup-checks.sh': No such file or directory Sep 18 19:58:40 localhost (hecks.sh)[584]: iscsid.service: Failed at step EXEC spawning /usr/lib/open-iscsi/startup-checks.sh: No such file or directory Sep 18 19:58:40 localhost systemd[1]: iscsid.service: Control process exited, code=exited, status=203/EXEC Sep 18 19:58:40 localhost systemd[1]: iscsid.service: Failed with result 'exit-code'. Sep 18 19:58:40 localhost systemd[1]: Failed to start iscsid.service - iSCSI initiator daemon (iscsid). Extracting the initramfs generated by dracut, we can see that /usr/lib/open-iscsi/startup-checks.sh is not included: ubuntu@oracular-dracut:~/initrd$ ls -l usr/lib/ total 636 drwxr-xr-x 2 ubuntu ubuntu 4096 Sep 18 22:13 dracut -rwxr-xr-x 1 ubuntu ubuntu 8177 Jul 25 03:45 dracut-crypt-lib.sh -rwxr-xr-x 1 ubuntu ubuntu 4078 Jul 25 03:45 dracut-dev-lib.sh -rwxr-xr-x 1 ubuntu ubuntu 29345 Jul 25 03:45 dracut-lib.sh drwxr-xr-x 2 ubuntu ubuntu 4096 Sep 18 22:13 firmware -rwxr-xr-x 1 ubuntu ubuntu 6552 Dec 6 2023 fs-lib.sh -rw-r--r-- 1 ubuntu ubuntu510 Sep 6 14:20 initrd-release -rw-r--r-- 1 ubuntu ubuntu 14648 Jul 23 13:41 libmpathcmd.so.0 -rw-r--r-- 1 ubuntu ubuntu 39224 Jul
[Bug 2080770] [NEW] I can´t upgrade from 24.04 to 24.04.1 distribution
Public bug reported: During update, update manager is marked to remove, but is also in list they should not remove ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 5.15.0-121.131-generic 5.15.163 Uname: Linux 5.15.0-121-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Sun Sep 15 10:01:00 2024 InstallationDate: Installed on 2021-04-02 (1262 days ago) InstallationMedia: Ubuntu-MATE 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-15 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080770 Title: I can´t upgrade from 24.04 to 24.04.1 distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr
Based on discussions at https://github.com/nfs-ganesha/nfs- ganesha/issues/1123, it seems this is something released with nfs- ganesha V4, so IIUC, this is something that will only be available to an Openstack + Manila + Ceph + NFS Ganesha in Noble Numbat, since it offers nfs-ganesha 4.3-8ubuntu1 ** Changed in: nfs-ganesha (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064657 Title: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr
This is also being discussed upstream: https://github.com/nfs- ganesha/nfs-ganesha/issues/1123 ** Bug watch added: github.com/nfs-ganesha/nfs-ganesha/issues #1123 https://github.com/nfs-ganesha/nfs-ganesha/issues/1123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064657 Title: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr
Hi Peter, The NFS client is a Jammy VM running nfs-common 1:2.6.1-1ubuntu1.2 and kernel 5.15.0-102-generic. I'm running a sosreport and will attach it here soon. Regards, Fabio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064657 Title: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064657] Re: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr
** Attachment added: "sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz" https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+attachment/5781410/+files/sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064657 Title: Add support for CEPH ceph.file.layout and ceph.dir.layout xattr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream
UPGRADE pdfarranger via SNAP: I'm on Ubuntu 22.04.04 and I was facing the same issue, having installed pdfarranger 1.8.2 via command line apt install. Removing it (with sudo apt remove --purge pdfarranger) and reinstalling via snap (sudo snap install pdfarranger) I got version 1.10.1 and fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047758 Title: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfarranger/+bug/2047758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047758] Re: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream
Hi, I would like to say that I'm facing the same problem. Hope it's ok to add this comment into this bug report. I recently made a fresh install of ubuntu 22.04-04. And when trying to combine 2 pdfs, PDF-Arranger gives me this error: "use pikepdf.PDF.pages interface to copy pages from one PDF to another" Installed versions are: pdfarranger 1.8.2-1 libqpdf28 10.6.3-1 I don't know to tell if pdfarranger is using this libqpdf or another version, but if someone could explain I'm willing to do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047758 Title: Cannot save PDFs due to PikePDF incompatibility, solved & patched upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfarranger/+bug/2047758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054343] Re: arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039 still open)
** Tags added: rls-ff-incoming rls-jj-incoming rls-mm-incoming rls-nn- incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054343 Title: arm64 build of gcc-10 10.5.0-3ubuntu1 still broken (CVE-2023-4039 still open) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2054343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1992187] Re: hplip not working after install in 22.04, python error
Could not understand how to implement the workaround suggested by Alterbo Donato #4. I would appreciate if you could clarify. But uninstalling the package available at Ubuntu 22.04 repository and installing the package downloaded from HP Developers (https://developers.hp.com/hp-linux-imaging-and-printing/gethplip) worked fine for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1992187 Title: hplip not working after install in 22.04, python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1992187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056187] Re: fails to configure BOOTIF when using iscsi
It seems 0.142ubuntu19 would be exposed to the bug. To test whether or not my use case would be affected by it, I've booted a Jammy instance with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is booting well through iscsi. My cmdline is as below, so it might not be exposed to the issue (and hence, please ignore my comment above as a valid test for the patch, given that I wasn't exposed to it to begin with): BOOT_IMAGE=/boot/vmlinuz-6.5.0-1018-oracle root=UUID=2792ceda-655f-4995-bf29-6a714f9a200b ro console=tty1 console=ttyS0 nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1 crash_kexec_post_notifiers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056460] [NEW] cloud-init in degraded state on Oracle instance with "Invalid network-config provided"
Public bug reported:
When booting a Noble Numbat (Ubuntu 24.04) instance on Oracle Cloud,
clout-init ends up in a degraded state reporting "Invalid network-config
provided". Details are displayed below:
ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init status -l
status: done
extended_status: degraded done
boot_status_code: enabled-by-generator
last_update: Thu, 07 Mar 2024 14:42:12 +
detail: DataSourceOracle
errors: []
recoverable_errors:
WARNING:
- Invalid network-config provided: Please run 'sudo cloud-init schema
--system' to see the schema errors.
ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init schema --system
Found cloud-config data types: user-data, network-config
1. user-data at
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/cloud-config.txt:
Empty 'cloud-config' found at
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/cloud-config.txt.
Nothing to validate.
2. network-config at
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json:
Invalid network-config
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json
Error: Cloud config schema errors: config.0.subnets.0: Additional properties
are not allowed ('broadcast' was unexpected)
Error: Invalid schema: network-config
ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo jq .
/var/lib/cloud/instances/ocid1.instance.oc1.sa-saopaulo-1.antxeljrniwq6syclo77iwfs2fznvqcipuenlp4bkdjw2aqocj65dvmdmnkq/network-config.json
{
"config": [
{
"mac_address": "b8:3f:d2:c3:fd:7c",
"name": "ens300f0np0",
"subnets": [
{
"broadcast": "10.0.0.255",
"control": "manual",
"dns_nameservers": [
"169.254.169.254"
],
"gateway": "10.0.0.1",
"netmask": "255.255.255.0",
"type": "dhcp"
}
],
"type": "physical"
}
],
"version": 1
}
ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init --version
/usr/bin/cloud-init 24.1-0ubuntu1
Attaching the logs.
** Affects: cloud-init (Ubuntu)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056460
Title:
cloud-init in degraded state on Oracle instance with "Invalid network-
config provided"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056460] Re: cloud-init in degraded state on Oracle instance with "Invalid network-config provided"
** Attachment added: "cloud-init.tar.gz" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+attachment/5753817/+files/cloud-init.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056460 Title: cloud-init in degraded state on Oracle instance with "Invalid network- config provided" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056187] Re: fails to configure BOOTIF when using iscsi
I've tested launching a Oracle Cloud baremetal instance (which boots from iSCSI) using such patch, and all worked well: https://pastebin.ubuntu.com/p/3cdFdYBVFG/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056194] Re: Networking broken in early boot on Oracle Native instances
I've tested the patch and it fixes the issue. I can confirm the MTU settings are now correct and curl works fine. I also confirmed it allowed cloud-init to run and fully complete the boot process: https://pastebin.ubuntu.com/p/KfcP7wmjjV/ There are no cloud-init errors: https://pastebin.ubuntu.com/p/jtkTWkDGVN/ https://pastebin.ubuntu.com/p/vZSyTJ3RsH/ All I noticed was a delay / hang during dhcp probe, followed by a timeout and it worked in the first retry: https://pastebin.ubuntu.com/p/hXWKYCypXM/ Overall, everything worked well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056194 Title: Networking broken in early boot on Oracle Native instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056194] Re: Networking broken in early boot on Oracle Native instances
Between initramfs-tools 0.142ubuntu8 and 0.142ubuntu9, we've Replaced dhclient by dhcpcd (LP: #2024164). When a DHCP server provides MTU settings to dhcpcd, it configures the routes with the appropriate mtu value (due to "option interface_mtu" in /etc/dhcpcd.conf), but it does not configure the MTU setting in the interface. So, we end up having a mismatch between interface and route MTU setting, as observed below: root@(none):/# ip a 1: lo: mtu 65536 qdisc noop state DOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:00:17:05:ee:5a brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.0.0.21/24 brd 10.0.0.255 scope global dynamic noprefixroute ens3 valid_lft 86048sec preferred_lft 75248sec inet6 fe80::17ff:fe05:ee5a/64 scope link valid_lft forever preferred_lft forever root@(none):/# ip route show default via 10.0.0.1 dev ens3 proto dhcp src 10.0.0.21 metric 1002 mtu 9000 10.0.0.0/24 dev ens3 proto dhcp scope link src 10.0.0.21 metric 1002 mtu 9000 169.254.0.0/16 dev ens3 proto dhcp scope link src 10.0.0.21 metric 1002 mtu 9000 If we go back to initramfs-tools 0.142ubuntu8 (and, consequently to dhclient), the MTU settings will match: root@(none):/# ip a 1: lo: mtu 65536 qdisc noop state DOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 9000 qdisc mq state UP group default qlen 1000 link/ether 02:00:17:05:ee:5a brd ff:ff:ff:ff:ff:ff altname enp0s3 inet 10.0.0.21/24 brd 10.0.0.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::17ff:fe05:ee5a/64 scope link valid_lft forever preferred_lft forever root@(none):/# ip route show default via 10.0.0.1 dev ens3 10.0.0.0/24 dev ens3 proto kernel scope link src 10.0.0.21 169.254.0.0/16 dev ens3 scope link Due to this mismatch when using dhcpcd, certain network activities might fail. For example, in Oracle instances, a curl to the DataSource will just hang: curl --connect-timeout 10 --max-time 15 -H "Authorization: Bearer Oracle" -L http://169.254.169.254/opc/v2/instance/ If you either reduce the route MTU setting down to 1500 OR increase the interface MTU setting to 9000, curl works: option 1 - Reduce route setting: ip route delete 169.254.0.0/16 dev ens3 proto dhcp scope link src 10.0.0.21 metric 1002 mtu 9000 ip route add 169.254.0.0/16 dev ens3 scope link option 2 - Increase interface setting: ip link set mtu 9000 ens3 The correct MTU setting here is 9000. When you fully boot the instance, the MTU gets configured appropriately (outside of initramfs) I also checked the Paravirtualized instances (uses virtio_net interfaces instead of mlx5_core) and the mismatch is also there, but curl still works, so the Paravirtualized instance is also exposed to the bug but more resistant to it. While investigating this, I noticed that in past releases of dhcpcd, we had a hook 10-mtu, that would automatically configure the mtu setting based on information it received from the dhcp server. This file was removed by the following commit: https://github.com/NetworkConfiguration/dhcpcd/commit/ca6cdf5847cda720b65793ea6827b1b373c62382 There are some discussion around why this was removed here: https://github.com/NetworkConfiguration/dhcpcd/issues/67 Anyway, this causes such mismatch between interface and route settings, which cause curl to the IMDS to hang and cloud-init to fail. ** Bug watch added: github.com/NetworkConfiguration/dhcpcd/issues #67 https://github.com/NetworkConfiguration/dhcpcd/issues/67 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056194 Title: Networking broken in early boot on Oracle Native instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04
Hi Brian, Thanks for that. I've tested and validated that ec2-instance-connect from jammy-proposed fixes the issue. Here are the evidences: https://pastebin.ubuntu.com/p/dPD6vyS6g4/ Cheers, Fabio Martins -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973114 Title: Key trust verification fails on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973114] Re: Key trust verification fails on Ubuntu 22.04
I also tested with mssh to make it works well: When running ec2-instance-connect 1.1.14-0ubuntu1 (from Jammy) and trying to connect with mssh: fabio@fabio-canonical:~/.aws$ mssh ubuntu@i-0af3232b4fb6ed642 ubuntu@3.91.56.142: Permission denied (publickey). Due to the bug, we can see the key being pushed, but then the client denying the connection: https://pastebin.ubuntu.com/p/7StqsfQdJp/ Back in the instance, I've changed the sources.list to point to kinetic repos and upgraded ec2-instance-connect to kinetic's version: ubuntu@ip-10-0-1-226:~$ sudo apt-cache policy ec2-instance-connect ec2-instance-connect: Installed: 1.1.14-0ubuntu2 Candidate: 1.1.14-0ubuntu2 Version table: *** 1.1.14-0ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status And now mssh works fine: fabio@fabio-canonical:~/.aws$ mssh ubuntu@i-0af3232b4fb6ed642 Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1004-aws x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage System information as of Fri May 13 14:16:20 UTC 2022 System load: 0.2421875 Processes: 128 Usage of /: 21.1% of 7.58GB Users logged in: 1 Memory usage: 1%IPv4 address for eth0: 10.0.1.226 Swap usage: 0% 74 updates can be applied immediately. To see these additional updates run: apt list --upgradable Last login: Fri May 13 13:47:05 2022 from 189.19.160.174 ubuntu@ip-10-0-1-226:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973114 Title: Key trust verification fails on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've also updated the [Test Plan] section of the bug description
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
+
+ - Check that the ipconfig utility is able to obtain an IP through dhcp:
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig ens9; date
+
+ - Check if it respects the timeout (i.e. 2 seconds in the example
+ below):
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+
+ - The original issue is that timeout is being ignored when not receiving
+ any reply from a DHCP Server, so for this test you have to stop your
+ DHCP Server (i.e. dnsmasq) and then test the timeouts:
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date
+
+ Make sure it times out respectivelly in 2 and 5 seconds.
[racb: pending agreement with the SRU team; please see comment 37]
Any situation where ipconfig encounters an error sending the DHCP
packet, it will automatically set a delay of 10 seconds, which could be
longer than the user-specified timeout. It can be reproduced by creating
a dummy interface and attempting to run ipconfig on it with a timeout
value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(&now, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually used
never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer (setting the timeout to 10 would keep the existing
behaviour). 2) I think it is unlikely that such a scenario exists at all. The
10-second timeout problem happens w
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hello Robie, I've validated that the package from -proposed works well, testing in my VM based environment. I haven't tested it on Oracle bare metal (where the original issue happened) as that is a type of instance hard to get access to. Given that the test packages had proven to fix the original problem that we were targetting to address, I believe the package from -proposed should also work well. Let me know if it is necessary to also test that it addresses the original issue with Oracle BM host and I'll get access to one and validate. Regarding your question below: > ...would it be practical and/or useful to verify that, with a timeout of 2s, a DHCP reply sent after 1.5s works, but a DHCP reply sent after 2.5s does not? That has been addressed in comment #30 (and now also in #39 with the package from -proposed). Regarding your question if upstream had accepted the patch, I would have to defer that to Khaled, but I also agree that it seems a deliberate upstream design decision not to accept it. Regarding your comment below: > In Ubuntu, we might decide to maintain the patch as a delta but then drop that delta in subsequent releases when we no longer need that functionality. That is indeed just needed for Bionic. To confirm/clarify my understanding, if this moves to -updates, in theory this is not going to be reverted (from Bionic) in the future, right? Once it lands there, it is expected that any newer klibc-utils packages that gets released to Bionic will continue to carry this patch? Thank you in advance! Regards, Fabio Martins -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the package from -proposed and I can confirm it fixes the problem: Installed from -proposed: root@ubuntu:~# apt-cache policy klibc-utils klibc-utils: Installed: 2.0.4-9ubuntu2.2 Candidate: 2.0.4-9ubuntu2.18.04.1 Version table: 2.0.4-9ubuntu2.18.04.1 500 500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64 Packages *** 2.0.4-9ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.0.4-9ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.0.4-9ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Working well without timeout: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig ens9; date Thu May 12 12:54:48 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Thu May 12 12:55:01 UTC 2022 Timeout being honored: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date Thu May 12 12:55:44 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (2 s) IP-Config: no response after 2 secs - giving up Thu May 12 12:55:46 UTC 2022 Testing the original issue (timeout being ignored when not receiving any reply from a DHCP Server), which is now also getting honored: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date Thu May 12 12:56:32 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (2 s) IP-Config: no response after 2 secs - giving up Thu May 12 12:56:34 UTC 2022 root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date Thu May 12 12:56:43 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (5 s) IP-Config: no response after 5 secs - giving up Thu May 12 12:56:48 UTC 2022 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Should this bug be changed to Fix Committed at this point? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972855] [NEW] lldb malfunctions due to faulty python path (ModuleNotFoundError: No module named 'lldb.embedded_interpreter')
Public bug reported: Starting lldb causes the following to happen: $ lldb Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'lldb.embedded_interpreter' (lldb) This causes issues with, for instance, QtCreator, which stalls when trying to debug anything with lldb. lldb -P gives the following path: /usr/lib/local/lib/python3.10/dist-packages However, that path doesn't exist: $ ls -l /usr/lib/local/lib/python3.10/dist-packages ls: cannot access '/usr/lib/local/lib/python3.10/dist-packages': No such file or directory The package python3-lldb-14 provides this path, though: /usr/lib/llvm-14/lib/python3.10/dist-packages/ Creating a symbolic link from /usr/lib/llvm-14/lib/python3.10/dist- packages/ to /usr/lib/local/lib/python3.10/dist-packages makes things work as expected: $ ls -l /usr/lib/local/lib/python3.10/dist-packages && lldb lrwxrwxrwx 1 root root 45 May 10 15:23 /usr/lib/local/lib/python3.10/dist-packages -> /usr/lib/llvm-14/lib/python3.10/dist-packages (lldb) Now QtCreator functions fine with lldb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lldb 1:14.0-55~exp2 ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30 Uname: Linux 5.15.0-27-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue May 10 15:18:41 2022 InstallationDate: Installed on 2015-02-26 (2630 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: llvm-defaults UpgradeStatus: Upgraded to jammy on 2022-05-02 (7 days ago) ** Affects: llvm-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - == Ubuntu release info == - Description: Ubuntu 22.04 LTS - Release: 22.04 - = - Package version: lldb 1:14.0-55~exp2 - = - - Starting lldb causes the following to happen: $ lldb Traceback (most recent call last): - File "", line 1, in + File "", line 1, in ModuleNotFoundError: No module named 'lldb.embedded_interpreter' (lldb) lldb -P gives the following path: /usr/lib/local/lib/python3.10/dist-packages However, that path doesn't exist: $ ls -l /usr/lib/local/lib/python3.10/dist-packages ls: cannot access '/usr/lib/local/lib/python3.10/dist-packages': No such file or directory The package python3-lldb-14 provides this path, though: /usr/lib/llvm-14/lib/python3.10/dist-packages/ Creating a symbolic link from /usr/lib/llvm-14/lib/python3.10/dist- packages/ to /usr/lib/local/lib/python3.10/dist-packages makes things work as expected: $ ls -l /usr/lib/local/lib/python3.10/dist-packages && lldb lrwxrwxrwx 1 root root 45 May 10 15:23 /usr/lib/local/lib/python3.10/dist-packages -> /usr/lib/llvm-14/lib/python3.10/dist-packages (lldb) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lldb 1:14.0-55~exp2 ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30 Uname: Linux 5.15.0-27-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Tue May 10 15:18:41 2022 InstallationDate: Installed on 2015-02-26 (2630 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: llvm-defaults UpgradeStatus: Upgraded to jammy on 2022-05-02 (7 days ago) ** Summary changed: - lldb cannot startup due to faulty python path + lldb malfunctions due to faulty python path ** Description changed: Starting lldb causes the following to happen: $ lldb Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'lldb.embedded_interpreter' (lldb) + + This causes issues with, for instance, QtCreator, which stalls when + trying to debug anything with lldb. lldb -P gives the following path: /usr/lib/local/lib/python3.10/dist-packages However, that path doesn't exist: $ ls -l /usr/lib/local/lib/python3.10/dist-packages ls: cannot access '/usr/lib/local/lib/python3.10/dist-packages': No such file or directory The package python3-lldb-14 provides this path, though: /usr/lib/llvm-14/lib/python3.10/dist-packages/ Creating a symbolic link from /usr/lib/llvm-14/lib/python3.10/dist- packages/ to /usr/lib/local/lib/python3.10/dist-packages makes things work as expected: $ ls -l /usr/lib/local/lib/python3.10/dist-packages && lldb lrwxrwxrwx 1 root root 45 May 10 15:23 /usr/lib/local/lib/python3.10/dist-packages -> /usr/lib/llvm-14/lib/python3.10/dist-packages (lldb) + Now QtCreator functions fine with lldb. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lldb 1:14.0-55~exp2 ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30 Uname: Linux 5.15.0-27-lowlatency x86_64 ApportVersion: 2.20
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the new patch from ppa:mfo/lp1947099v2 and I can confirm it resolves the problem: - Without the patch: https://pastebin.ubuntu.com/p/RksNcBGSzn/ It took 396,940865−220,447147 = 176,493718 seconds in the IP-Config section. Total boot time: ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time Startup finished in 4min 1.355s (firmware) + 2min 24.433s (loader) + 6min 8.464s (kernel) + 41.466s (userspace) = 13min 15.719s graphical.target reached after 41.068s in userspace - With the patch: https://pastebin.ubuntu.com/p/46nVYCYyDZ/ It took 246,556749−212,019368 = 34,537381 seconds in the IP-Config section. Total boot time: ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time Startup finished in 4min 1.246s (firmware) + 2min 24.170s (loader) + 3min 42.915s (kernel) + 39.010s (userspace) = 10min 47.343s graphical.target reached after 38.634s in userspace ubuntu@gpu48-ubuntu18:~$ sudo apt-cache policy klibc-utils klibc-utils: Installed: 2.0.4-9ubuntu2.18.04.1 Candidate: 2.0.4-9ubuntu2.18.04.1 Version table: *** 2.0.4-9ubuntu2.18.04.1 500 500 http://ppa.launchpad.net/mfo/lp1947099v2/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 2.0.4-9ubuntu2.1 500 500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.0.4-9ubuntu2 500 500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Thank you, Mauricio, for the build process details and for adding the update here. I'm including some evidence of my tests showing that the patch you suggested did work well: Details of the build process: https://pastebin.ubuntu.com/p/dmVWH2fxpy/ Test package installed: https://pastebin.ubuntu.com/p/qxyWBGrm3P/ Working well without specifying a timeout: https://pastebin.ubuntu.com/p/byftnFk33C/ Timeout is also being honored: https://pastebin.ubuntu.com/p/spFsTRhXTz/ Testing the original issue (timeout being ignored when not receiving any reply from a DHCP Server), which is now also getting honored: https://pastebin.ubuntu.com/p/KHVRj7BdRw/ I'm working to get access to another instance to test that the boot time optimiizations are still fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
@Łukasz / @Robie, do you think the above comments are enough to proceed with this SRU? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the klibc-utils patch using Mauricio's ppa: sudo add-apt-repository ppa:mfo/lp1947099 sudo apt install klibc-utils sudo update-initramfs -u -k all And I can confirm that it does improve the boot time in more than 3 minutes, without causing any noticeable issues. - Without the patch: https://pastebin.ubuntu.com/p/6M7M2FfCGQ/ root@ubuntu1804:~# sudo systemd-analyze time Startup finished in 4min 2.098s (firmware) + 2min 23.684s (loader) + 6min 226ms (kernel) + 38.766s (userspace) = 13min 4.776s graphical.target reached after 38.374s in userspace We can see it spent 6min 226ms in kernel, and looking through the serial console (or dmesg) it was running the ipconfig commands for each of the Mellanox NICs from 211.972259 up to 386.155116 = 174.182857 seconds - With the patch: https://pastebin.ubuntu.com/p/JxDs8WPqc4/ root@ubuntu1804:~# sudo systemd-analyze time Startup finished in 4min 890ms (firmware) + 2min 23.278s (loader) + 3min 46.413s (kernel) + 40.734s (userspace) = 10min 51.317s graphical.target reached after 40.354s in userspace We can see the kernel time decreased to a bit more than 3 minutes and we spent only 41 seconds (as opposed to 174 seconds) in the ipconfig commands: 210.675050 to 252.432441 = 41.757391 seconds That definitely has helped to resolve the issue we are chasing here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I tried using klibc-utils from the ppa (containing the patch): root@ubuntu:~# sudo apt-cache policy klibc-utils klibc-utils: Installed: 2.0.4-9ubuntu2.18.04.1 Candidate: 2.0.4-9ubuntu2.18.04.1 Version table: *** 2.0.4-9ubuntu2.18.04.1 500 500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 2.0.4-9ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1] But now when I try to obtain an IP using dhcp without specifying any timeout, it dumps lots of "Lowered timeout to match user request" messages. Is that expected? https://pastebin.ubuntu.com/p/5Tpc5Rwdkq/ [2] Other than that, it worked well. We can see from the pastebin below that the timeout is getting respected: https://pastebin.ubuntu.com/p/TJbCzx7hFC/ [3] And also the main issue was the timeout being ignored when not receiving any reply from a DHCP Server, which is now also getting honored: https://pastebin.ubuntu.com/p/BvKk6fJJDc/ I will try to test this package in a OCI BM.GPU4.8 instance to see the improvements with the main optimization, but it would be good to get clarification on [1] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944574] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
I believe the "EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary" that was reported on this bug is not what is preventing the VM from booting. If you look into the full log you provided, that message is logged both on the boot that succeeded and in the one that got stuck. I believe whatever was done in the VM in between these reboots, might have caused the problem you are observing. There's also a known problem on linux-oracle kernel that prevents you from seeing the serial console. That is being fixed for Focal images on the linux-oracle 5.13.0.1023.28~20.04.1 kernel, which is currenlty in focal-proposed. If this is something you can reproduce with Focal images, using the kernel from proposed might help you see what is really preventing the VM from starting. We'll review the 'kernel image not aligned on 64k boundary' error anyway to assess what might be causing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944574 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1944574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've setup a Lab with dnsmasq acting as DHCP Server, which I can use the dhcp-reply-delay option to introduce a delay between the DHCPDISCOVER and DHCPOFFER, as in the example below: Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPDISCOVER(ens3) 52:54:00:d7:10:13 Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: 4195928115 reply delay: 3 Mar 30 18:26:37 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPOFFER(ens3) 192.168.150.119 52:54:00:d7:10:13 Just minor note that the delay only happens between DHCPDISCOVER and DHCPOFFER, but not between DHCPREQUEST and DHCPACK: Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPREQUEST(ens3) 192.168.150.119 52:54:00:d7:10:13 Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPACK(ens3) 192.168.150.119 52:54:00:d7:10:13 ubuntu So, if this is a new interface (new mac) looking for an IP, the delay will be added, but if this is an interface which was previously configured and is asking to re-use the same IP (DHCPREQUEST), there won't be any delays. I believe this Lab will help reproducing the issue with and without the proposed patch. 1. In a ideal scenario, where no delays were added (dhcp-reply-delay is commented out), ipconfig will take approximately to do its job: it sends a DHCPREQUEST, then DHCPDISCOVER and then another DHCPREQUEST in this process: - From the ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date Wed Mar 30 19:25:44 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Wed Mar 30 19:25:54 UTC 2022 - From the dhcp server perspective: Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e ubuntu Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e 2. Adding a 5 seconds delay in dnsmasq (dhcp-reply-delay=5) and without enforcing a timeout in ipconfig: - From ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date Wed Mar 30 19:34:09 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Wed Mar 30 19:34:27 UTC 2022 - From the dhcpserver perspective: Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e ubuntu Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e It takes 18 seconds for the process to complete, as dnsmasq adds 3x 5 seconds delay in the process 3. Using the -t to specify a 15 seconds timeout (when the actual process takes 18 seconds): - From the ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig -t 15 ens9; date Wed Mar 30 19:37:11 UTC 2
[Bug 1967001] Re: Wrong message "Check your Internet connection."
Sorry, perhaps I was not clear. I know my sources.list.d is wrong but what I mean is that the message "check your internet connection" is wrong because the internet connection is working. Just a graphical issue, I suggest to remove the "Check your internet connection" written. Thanks and BR ** Changed in: update-manager (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967001 Title: Wrong message "Check your Internet connection." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1967001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967001] Re: Wrong message "Check your Internet connection."
Confirmed by screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967001 Title: Wrong message "Check your Internet connection." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1967001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967001] [NEW] Wrong message "Check your Internet connection."
Public bug reported: Hi everytime it runs it ends showing the box "Failed to download repository information. Check your internet connection". It instead works as expected. The error probably is here: Err:7 https://download.docker.com/linux/ubuntu \ Release 404 Not Found [IP: 108.138.199.73 443] Reading package lists... Done E: The repository 'https://download.docker.com/linux/ubuntu \ Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. njin@Fluid:~$ So it is just a wrong message in that box, screenshot attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: update-manager 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 22:04:44 2022 ExecutablePath: /usr/bin/update-manager GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-count' b'383' b'com.ubuntu.update-manager' b'launch-time' b'int64 1648584138' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-width' b'645' InstallationDate: Installed on 2021-04-18 (345 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonDetails: N/A SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-03-29 22-08-19.png" https://bugs.launchpad.net/bugs/1967001/+attachment/5574421/+files/Screenshot%20from%202022-03-29%2022-08-19.png ** Changed in: update-manager (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/1967001 Title: Wrong message "Check your Internet connection." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1967001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965104] Re: do-release-upgrade crashed with FileNotFoundError in getListFromFile(): [Errno 2] No such file or directory: '/usr/share/ubuntu-release-upgrader/removal_blacklist.cfg'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965104 Title: do-release-upgrade crashed with FileNotFoundError in getListFromFile(): [Errno 2] No such file or directory: '/usr/share/ubuntu-release-upgrader/removal_blacklist.cfg' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1965104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 959700] Re: duplicate sources.list entry after upgrade lucid2precise
closed EOL ** Changed in: update-manager (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959700 Title: duplicate sources.list entry after upgrade lucid2precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/959700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964465] [NEW] kazam crashed with gi.repository.GLib.GError in save(): g-file-error-quark: Failed to open “/home/username/None/Kazam_screenshot_00000.png” for writing: No such file or directory (
Public bug reported: taking screenshot after selecting path to save ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: kazam 1.4.5-5 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:26:27 2022 ExecutablePath: /usr/bin/kazam InstallationDate: Installed on 2021-04-18 (326 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/kazam Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/kazam'] PythonDetails: N/A SourcePackage: kazam Title: kazam crashed with gi.repository.GLib.GError in save(): g-file-error-quark: Failed to open “/home/username/None/Kazam_screenshot_0.png” for writing: No such file or directory (4) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Affects: kazam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash jammy need-duplicate-check ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964465 Title: kazam crashed with gi.repository.GLib.GError in save(): g-file-error- quark: Failed to open “/home/username/None/Kazam_screenshot_0.png” for writing: No such file or directory (4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kazam/+bug/1964465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963800] Re: pitivi crashed with AttributeError in add_limited_log_handler(): module 'collections' has no attribute 'Callable'
Checked now, fix confirmed. sorry late but had a hand surgery. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963800 Title: pitivi crashed with AttributeError in add_limited_log_handler(): module 'collections' has no attribute 'Callable' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1963800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963800] [NEW] pitivi crashed with AttributeError in add_limited_log_handler(): module 'collections' has no attribute 'Callable'
Public bug reported:
Crash at start
Missing soft dependency:
- GSound not found on the system
-> enables sound notifications when rendering is complete
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
135, in do_startup
loggable.init('PITIVI_DEBUG', enable_color, enable_crack_output)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/utils/loggable.py", line
651, in init
add_limited_log_handler(print_handler)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/utils/loggable.py", line
738, in add_limited_log_handler
if not isinstance(func, collections.Callable):
AttributeError: module 'collections' has no attribute 'Callable'
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
203, in do_activate
self.create_main_window()
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
209, in create_main_window
self.gui = MainWindow(self)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/mainwindow.py", line
108, in __init__
self.app.settings.connect("useDarkThemeChanged",
AttributeError: 'NoneType' object has no attribute 'connect'
njin@Fluid:~/UWBridge/Network$
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: pitivi 2021.05-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 6 10:40:50 2022
ExecutablePath: /usr/bin/pitivi
InstallationDate: Installed on 2021-04-18 (322 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
InterpreterPath: /usr/bin/python3.10
ProcCmdline: /usr/bin/python3 /usr/bin/pitivi
Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal,
3.10.1-0ubuntu1
PythonArgs: ['/usr/bin/pitivi']
PythonDetails: N/A
SourcePackage: pitivi
Title: pitivi crashed with AttributeError in add_limited_log_handler(): module
'collections' has no attribute 'Callable'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
** Affects: pitivi (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-crash jammy need-duplicate-check
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963800
Title:
pitivi crashed with AttributeError in add_limited_log_handler():
module 'collections' has no attribute 'Callable'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1963800/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hi Robie, The user story here is about improving the time it takes to boot a Bionic instance on Oracle Cloud in a specific bare metal shape, called BM.GPU4.8. This is a pretty large instance, with 18x Ethernet controller [0200]: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] [15b3:1019]: https://www.oracle.com/uk/cloud/compute/gpu.html Comparing the time it takes to boot Bionic with a CentOS instance we can see a big delta both in kernel and userspace: CentOS: Startup finished in 4min 3.548s (firmware) + 2min 23.525s (loader) + 3min 17.984s (kernel) + 1min 37.825s (initrd) + 38.723s (userspace) = 12min 1.608s multi-user.target reached after 38.714s in userspace Ubuntu: Startup finished in 4min 621ms (firmware) + 2min 23.174s (loader) + 7min 34.767s (kernel) + 5min 48.219s (userspace) = 19min 46.782s graphical.target reached after 5min 47.854s in userspace The userspace difference is a cloud-init problem that is being handled by other launchpad bugs. Here we are trying to focus on the kernel difference, which further was narrowed down to be related to klibc and it is what we are trying to address with this bug. Some details: Looking into details, here are the dmesg output from CentOS and Ubuntu, for kernel comparison: Ubuntu: https://pastebin.canonical.com/p/X7GFVjdV3b/ CentOS: https://pastebin.canonical.com/p/gNhFwJjyjw/ Looking there, one area that looks promising is around mlx5_core driver, where Ubuntu spends 218 seconds, while CentOS spends 44 seconds Khalid did a nice job investigating and found that the problem came from ipconfig from initramfs. Here are the details: The delay from the kernel side is due to the fact that every interface (18 in total) takes over 10 seconds each to initialize. The interfaces are brought up and used for DHCP as part of the iscsi initialization, during the initramfs stage. Specifically the script ```/usr/share/initramfs-tools/scripts/local-top/iscsi``` which is included in the initramfs and is installed as part of open-iscsi To initialize the network interfaces this script calls other helper functions that are part of the initramfs, specifically "configure_networking" in ```/usr/share/initramfs- tools/scripts/functions``` which is installed as part of initramfs- tools-core. The configure_networking function initializes networking by looping over all interfaces and issuing this call: ``` ipconfig -t 2 ``` where it is calling the ipconfig utility (part of klibc-utils) which also gets bundled in the initramfs. The -t 2 specifies a timeout of 2 seconds. This ipconfig tool attempts to perform DHCP on the given interface, within the specified timeout (always 2 seconds for each interface) Normally, ipconfig does not perform only one DHCP attempt - it performs multiple DHCP attempts, each attempt waiting for an exponentially increasing amount of time (1s, 2s, 4s, ..etc) up until the total amount of time has passed that is equal the user-specified timeout (2 in this case, so it should wait 1 second, followed by 1 second, for a total of 2 seconds). However, it appears ipconfig has a bug. In case it encounters an error sending a DHCP request on an interface (which is the case for 17 out of the 18 interfaces on this instance), it attempts to "try again later" and sets a timer of 10 seconds for the next attempt - ignoring completely the user-specified value (2 seconds). I believe this is a bug in ipconfig and have a working fix to limit the delay to the user- specified timeout so each interface actually takes a maximum of 2 seconds for initialization, even in error cases. The above is for bionic, which has the reported problem. In focal, even though the kernel and klibc-utils are identical to bionic, the version of initramfs-tools-core is different. In the focal version, configure_networking() has been reworked to avoid using ipconfig entirely. Instead, it uses ```dhclient```. And instead of doing that 18 times, dhclient is called only once with the full list of interfaces, as such: ``` dhclient -v -1 -cf /etc/dhcp/dhclient.conf.2 -pf /tmp/dhclient.pid.2 -4 enp12s0f0np0 enp12s0f1np1 enp138s0f0np0 enp138s0f1np1 enp148s0f0np0 enp148s0f1np1 enp195s0f0np0 enp195s0f1np1 enp209s0f0np0 enp209s0f1np1 enp22s0f0np0 enp22s0f1np1 enp45s0f0np0 enp45s0f1np1 enp72s0f0np0 enp72s0f1np1 enp76s0f0np0 enp76s0f1np1 ``` dhclient does DHCP on all those interfaces at the same time, asynchronously, and it daemonizes (goes in the background) as soon as it gets a DHCP response which happens relatively quickly (on interface enp45s0f0np0 usually) and so the boot-up continues *much* faster compared to bionic (180+ seconds are reduced to just 5-10 seconds). I'm sure there might be other use cases, but this is what we have been reported and are trying to work with. I hope this helps clarifying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not hono
[Bug 474687] Re: Gthumb needs a way to edit keyboard shortcuts
+1 I wish I could use CTRL+C to copy the image while viewing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/474687 Title: Gthumb needs a way to edit keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gthumb/+bug/474687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958626] Re: Trackpad is not detected for Dell Precision 5550
Also, it correctly works with a live Pop!_OS installation USB; `uname -a` there yields: Linux pop-os 5.13.0-7614-generic #14~1631647151~21.04~930e87c-Ubuntu SMP Fri Sep 17 00:24:58 UTC 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/1958626 Title: Trackpad is not detected for Dell Precision 5550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958626] [NEW] Trackpad is not detected for Dell Precision 5550
Public bug reported: It doesn't appear in /proc/bus/input/devices: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys= S: Sysfs=/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=8000 0 0 1500b0c00 40020030 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=0bda Product=5510 Version=9179 N: Name="Integrated_Webcam_HD: Integrate" P: Phys=usb-:00:14.0-11/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-11/1-11:1.0/input/input17 U: Uniq= H: Handlers=kbd event17 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=0bda Product=5510 Version=9179 N: Name="Integrated_Webcam_HD: Integrate" P: Phys=usb-:00:14.0-11/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-11/1-11:1.2/input/input18 U: Uniq= H: Handlers=kbd event18 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=0203 Product=145f Version=0100 N: Name="AUKEY PC-LM1 USB Camera: AUKEY " P: Phys=usb-:00:14.0-4.1.1/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4.1/1-4.1.1/1-4.1.1:1.0/input/input26 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=1532 Product=0020 Version=0111 N: Name="Razer Razer Abyssus 1800" P: Phys=usb-:00:14.0-4.1.2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4.1/1-4.1.2/1-4.1.2:1.0/0003:1532:0020.000A/input/input27 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=1532 Product=0020 Version=0111 N: Name="Razer Razer Abyssus 1800" P: Phys=usb-:00:14.0-4.1.2/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4.1/1-4.1.2/1-4.1.2:1.1/0003:1532:0020.000B/input/input28 U: Uniq= H: Handlers=sysrq kbd event7 B: PROP=0 B: EV=100013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 I: Bus=0003 Vendor=1b1c Product=1b20 Version=0111 N: Name="Corsair Corsair STRAFE RGB Gaming Keyboard" P: Phys=usb-:00:14.0-4.1.3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4.1/1-4.1.3/1-4.1.3:1.0/0003:1B1C:1B20.000C/input/input29 U: Uniq=16013037AF0CA4A7592515EAF5001941 H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=12001f B: KEY=3f000
[Bug 1946211] Re: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries)
Hi, I've verified that the package from ussuri-proposed fixes the issue. Without the patch: https://pastebin.ubuntu.com/p/PFrkX7BkCT/ With the patch: https://pastebin.ubuntu.com/p/yytzD3sjV9/ Cheers and thank you for fixing it. - Fabio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946211 Title: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1946211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946211] Re: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries)
Hi, I can confirm that the packages from -propose will resolve the issue. See evidences bellow: - While using 15.2.12, we can see the bug: https://pastebin.ubuntu.com/p/jYg8x4Q7vR/ - After installing 15.2.14 from -proposed, the bug is resolved: https://pastebin.ubuntu.com/p/mKFrTjddX7/ Thank you for your help addressing this issue. Regards, Fabio Martins ** 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/1946211 Title: [SRU] "radosgw-admin bucket limit check" has duplicate entries if bucket count exceeds 1000 (max_entries) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1946211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947577] [NEW] package libapache2-mod-wsgi-py3 4.7.1-3build2 failed to install/upgrade: o subprocesso instalado, do pacote libapache2-mod-wsgi-py3, o script post-installation retornou erro do sta
Public bug reported: i can't using snap store and aptitude ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libapache2-mod-wsgi-py3 4.7.1-3build2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 15 17:29:19 2021 ErrorMessage: o subprocesso instalado, do pacote libapache2-mod-wsgi-py3, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-06-09 (130 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: mod-wsgi Title: package libapache2-mod-wsgi-py3 4.7.1-3build2 failed to install/upgrade: o subprocesso instalado, do pacote libapache2-mod-wsgi-py3, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.mods-available.wsgi.conf: [deleted] modified.conffile..etc.apache2.mods-available.wsgi.load: [deleted] ** Affects: mod-wsgi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish 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/1947577 Title: package libapache2-mod-wsgi-py3 4.7.1-3build2 failed to install/upgrade: o subprocesso instalado, do pacote libapache2-mod- wsgi-py3, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1947577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945913] [NEW] package mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127
Public bug reported: Bug reportered during the SO automatic upgrade. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 3 12:14:44 2021 DuplicateSignature: package:mysql-server-8.0:8.0.26-0ubuntu0.20.04.3 Setting up mysql-server-8.0 (8.0.26-0ubuntu0.20.04.3) ... /var/lib/dpkg/info/mysql-server-8.0.postinst: linha 191: /usr/share/mysql-common/configure-symlinks: Arquivo ou diretório inexistente dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links simbólicos: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['#ib_16384_0.dblwr', 'ib_logfile1', '#ib_16384_1.dblwr', 'public_key.pem', 'client-key.pem', 'auto.cnf', 'mysql.ibd', 'datacenter', 'ibdata1', 'private_key.pem', 'binlog.01', 'ib_logfile0', 'phpmyadmin', '#innodb_temp', 'binlog.02', 'performance_schema', 'ca.pem', 'server-key.pem', 'ca-key.pem', 'debian-5.7.flag', 'mysql', 'undo_001', 'ib_buffer_pool', 'undo_002', 'client-cert.pem', 'sys', 'binlog.03', 'binlog.05', 'binlog.index', 'binlog.04', 'server-cert.pem', 'contabilidade'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=edf77657-1d5c-4a17-addb-efa77e47ae8f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check 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/1945913 Title: package mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944468] Re: Electron applications all crash upon launch
I can confirm @mwhudson's glibc build from https://launchpad.net/~mwhudson/+archive/ubuntu/devirt fixed the issue for me with VSCode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940739] [NEW] package libnvidia-compute-460-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340
Public bug reported: I installed on ubuntu 20.04 drivers nvidia for GT230M: sudo add-apt-repository ppa:kelebek333/nvidia-legacy sudo apt-get update sudo apt-get install nvidia-340 But I tried install sudo apt install nvidia-cuda-toolkit and show me this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-460-server (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 21 08:49:24 2021 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-4lmtrfocal1 InstallationDate: Installed on 2021-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460-server Title: package libnvidia-compute-460-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-4lmtrfocal1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460-server (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/1940739 Title: package libnvidia-compute-460-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/libnvidia-ml.so', which is also in package nvidia-340 340.108-4lmtrfocal1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1940739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937844] [NEW] arm-linux-gnueabi-gcc pgo build fails
Public bug reported: These are the errors made by the compiler. /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: /tmp/Prova_linuxarmv7.IKA0IY.ltrans0.ltrans.o: in function `Func1.constprop.0': :(.text+0xfdc): undefined reference to `__gcov_one_value_profiler_atomic' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: /tmp/Prova_linuxarmv7.IKA0IY.ltrans0.ltrans.o: in function `Func2.lto_priv.0': :(.text+0x1364): undefined reference to `__gcov_one_value_profiler_atomic' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: :(.text+0x1878): undefined reference to `__gcov_one_value_profiler_atomic' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: :(.text+0x2004): undefined reference to `__gcov_one_value_profiler_atomic' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: :(.text+0x2134): undefined reference to `__gcov_one_value_profiler_atomic' /usr/lib/gcc-cross/arm-linux-gnueabi/9/../../../../arm-linux-gnueabi/bin/ld: /tmp/Prova_linuxarmv7.IKA0IY.ltrans1.ltrans.o::(.text+0x37c): more undefined references to `__gcov_one_value_profiler_atomic' follow collect2: error: ld returned 1 exit status This is the compilation command: arm-linux-gnueabi-gcc ./main.c -s -static -pthread -O3 -flto -std=gnu11 -DNDEBUG -Wall -Wextra -lm -march=armv7-a -mfpu=neon -mfloat-abi=softfp -DNEON -o ./Prova_linuxarmv7 -fprofile-generate -lgcov The same command without "-fprofile-generate -lgcov" works well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gcc-9-arm-linux-gnueabi 9.3.0-17ubuntu1~20.04cross2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 17:04:24 2021 InstallationDate: Installed on 2020-05-01 (448 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gcc-9-cross UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-9-cross (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/1937844 Title: arm-linux-gnueabi-gcc pgo build fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9-cross/+bug/1937844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931312] Re: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04
First, sorry for the noise in opening this issue. Due to confusion trying to figure out the cause of the problem, I ended up discovering the optional environment variable STEAM_RUNTIME=0 and erroneously assuming this was the correct way. (Steam doesn't have a --help and I couldn't find any documentation. https://github.com/ValveSoftware/steam-for-linux/issues/7849 ) One of the Steam maintainers pointed out to me that Steam sends the 32-bit and 64-bit versions of several libraries and that in short STEAM_RUNTIME=0 will make Steam not use the libraries sent by Steam but try to check them directly in the libraries installed at OS level. The full explanation can be seen in https://github.com/ValveSoftware/steam-for-linux/issues/7813#issuecomment-857851359 https://github.com/ValveSoftware/steam-for- linux/issues/7847#issuecomment-857863961 I believe this issue can be CLOSED WITHOUT A FIX since running STEAM_RUNTIME=0 steam generates a 'missing library' false positive, and Valve does not officially support this option. ### Steam users who read this topic: >> The comments below are only valid for the >> Steam Client build: Jun 8 2021, at 22:23:41 >> Steam API v020. >> Steam Package versions: 1623193086 In my case, Steam wouldn't open due to a bug that occurs when the option to save Steam password is checked. To solve this, run: steam --reset Open Steam again, and make sure you don't check the option to save the password. The above command will force Steam to delete the entire steam-runtime and download and install it again. Note: The --reset command does not affect installed games. Another way to have the same fix without reinstall steam-runtime is to open ~/.steam/registry.vdf and change Registry.HKCU.Software.Valve.Steam.RememberPassword from "1" to "0" ** Bug watch added: github.com/ValveSoftware/steam-for-linux/issues #7849 https://github.com/ValveSoftware/steam-for-linux/issues/7849 ** Bug watch added: github.com/ValveSoftware/steam-for-linux/issues #7813 https://github.com/ValveSoftware/steam-for-linux/issues/7813 ** Bug watch added: github.com/ValveSoftware/steam-for-linux/issues #7847 https://github.com/ValveSoftware/steam-for-linux/issues/7847 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931312 Title: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931312] [NEW] i386 version of libpipewire-0.3 for Ubuntu Focal 20.04
Public bug reported: Hi, I updated the packages today and one of them was Steam. When trying to open Steam, it is reported missing to install 32-bit version of libpipewire-0.3.so.0 luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam Running Steam on focal 20.04 64-bit STEAM_RUNTIME is disabled by the user Error: You are missing the following 32-bit libraries, and Steam may not run: libpipewire-0.3.so.0 I did a brief search and saw that there is no 32bit version of pipewire 0.3 release. https://packages.ubuntu.com/search?arch=i386&keywords=pipewire luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386 [sudo] senha para luzfcb: Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto E: Impossível encontrar o pacote libpipewire-0.3-0:i386 E: Couldn't find any package by glob 'libpipewire-0.3-0' E: Não foi possível encontrar o pacote através da expressão regular 'libpipewire-0.3-0' Are there any plans to fix this and make life for the few people still trying to play games using Linux less difficult? Yes or no, thanks for your hard work. ** Affects: pipewire (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/1931312 Title: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928373] Re: mariadb-server-10.3 upgrade doesn't complete configuration
Hi, I was dist-upgrading in version 20.04.2, no version changes. Just a normal dist-upgrade as I do periodically. I have fixed the issue completely removing mariadb* and reinstalling. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928373 Title: mariadb-server-10.3 upgrade doesn't complete configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1928373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928373] [NEW] mariadb-server-10.3 upgrade doesn't complete configuration
Public bug reported: I have just performed a dist-upgrade on ubuntu 20.04.2 server and got stuck on mariadb-server-10.3 The apt process hung on this package and after 20 minutes waiting I have killed the process. After that, I checked mariadb and it was running with v. 10.3 but apt is still claiming for configuration: dpkg --configure -a Setting up mariadb-server-10.3 (1:10.3.29-0ubuntu0.20.04.1) Hanging forever. But if I check installed packages, I get this: dpkg -l | grep maria* ii mariadb-client-10.3 1:10.3.29-0ubuntu0.20.04.1 amd64MariaDB database client binaries ii mariadb-client-core-10.3 1:10.3.29-0ubuntu0.20.04.1 amd64MariaDB database core client binaries ii mariadb-common 1:10.3.29-0ubuntu0.20.04.1 all MariaDB common metapackage iU mariadb-server 1:10.3.29-0ubuntu0.20.04.1 all MariaDB database server (metapackage depending on the latest version) iF mariadb-server-10.3 1:10.3.29-0ubuntu0.20.04.1 amd64MariaDB database server binaries ii mariadb-server-core-10.3 1:10.3.29-0ubuntu0.20.04.1 amd64MariaDB database core server files >From now on, every time I need to update a package/system I going through this >hanging problem: dpkg: dependency problems prevent configuration of mariadb-server: mariadb-server depends on mariadb-server-10.3 (>= 1:10.3.29-0ubuntu0.20.04.1); however: Package mariadb-server-10.3 is not configured yet. dpkg: error processing package mariadb-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: mariadb-server-10.3 mariadb-server How to fix this? ** Affects: mariadb-10.3 (Ubuntu) Importance: Undecided Status: New ** Tags: mariadb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928373 Title: mariadb-server-10.3 upgrade doesn't complete configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1928373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928136] [NEW] Desktop crashes when i press the start(windows) button
Public bug reported: Usually when i press the start button the desktop crashes and i can´t do anything with my pc, so I have to restart it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 11 22:02:33 2021 InstallationDate: Installed on 2021-05-02 (9 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928136 Title: Desktop crashes when i press the start(windows) button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921104] Re: net/mlx5e: Add missing capability check for uplink follow
Another customer has provided positive feedback that it fixes the issue on Focal: 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921104 Title: net/mlx5e: Add missing capability check for uplink follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923115] Re: Networkd vs udev nic renaming race condition
Customer has provided a positive feedback that the package in -proposed fixed this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923115 Title: Networkd vs udev nic renaming race condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920988] [NEW] gcc mingw gives errors when compiling with profiler guided optimizations
Public bug reported: When I compile a program with gcc mingw with -fprofile-generate -lgcov I get the following errors: /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x7f2): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x874): undefined reference to `__gcov_indirect_call_profiler_v3' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x993): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9b7): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9d7): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9fe): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xcf6): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xd1a): more undefined references to `__gcov_one_value_profiler_atomic' follow /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xfe3): undefined reference to `__gcov_indirect_call_profiler_v3' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x3841): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x69e5): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9742): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9751): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9760): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x97b9): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x97c8): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x97d7): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0x9b85): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa1dd): undefined reference to `__gcov_indirect_call_profiler_v3' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa955): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa964): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa977): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa9c0): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa9cf): undefined reference to `__gcov_average_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xa9e2): undefined reference to `__gcov_ior_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xaa3e): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xaed5): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xb3b9): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xb3f0): undefined reference to `__gcov_one_value_profiler_atomic' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.text+0xd2aa): undefined reference to `__gcov_indirect_call_profiler_v3' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.data+0x29f0): undefined reference to `__gcov_merge_ior' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.data+0x29f8): undefined reference to `__gcov_merge_time_profile' /usr/bin/x86_64-w64-mingw32-ld: /tmp/test.exe.OUuwZB.ltrans0.ltrans.o::(.rdata$.refptr.__gcov_indirect_call[.refptr.__gcov_indirect_call]+0x0): undefined reference to `__gcov_indirect_call' /usr/bin/x86_64-w64-mingw32-ld:
[Bug 1919261] [NEW] Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed
Public bug reported: In a host where ceph-mds is installed, upgrading from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails with: dpkg: error processing archive /tmp/apt-dpkg-install-Zen6uw/9-ceph-common_15.2.8-0ubuntu0.20.04.1~cloud0_amd64.deb (--unpack): trying to overwrite '/usr/bin/cephfs-data-scan', which is also in package ceph-mds 14.2.11-0ubuntu0.19.10.1~cloud4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-Zen6uw/9-ceph-common_15.2.8-0ubuntu0.20.04.1~cloud0_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The problem happens because /usr/bin/cephfs-data-scan is provided by ceph-mds in 14.2.11-0ubuntu0.19.10.1~cloud4: # dpkg -S /usr/bin/cephfs-data-scan ceph-mds: /usr/bin/cephfs-data-scan However in 15.2.8-0ubuntu0.20.04.1~cloud0 it is provided by ceph-common: # dpkg -S /usr/bin/cephfs-data-scan ceph-common: /usr/bin/cephfs-data-scan A quick workaround is to temporarily remove ceph-mds before the upgrade (dpkg -r ceph-mds) and then perform the upgrade process using apt install. It will upgrade all packages and reinstall ceph-mds. ** Affects: ceph (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/1919261 Title: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1919261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918874] Re: Application icons superposed to open windows
Same problem here! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918874 Title: Application icons superposed to open windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917077] [NEW] package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: o subprocesso instalado, do pacote grub-efi-amd64-signed, o script post-installation retornou erro
Public bug reported: fresh install ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 26 14:50:25 2021 ErrorMessage: o subprocesso instalado, do pacote grub-efi-amd64-signed, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-02-26 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: o subprocesso instalado, do pacote grub-efi-amd64-signed, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917077 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: o subprocesso instalado, do pacote grub-efi- amd64-signed, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1917077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906127] [NEW] Upgrade to Ubuntu 20.04.1 crashes
Public bug reported: I paste here content of /var/log/dist-upgrade/main.log. I also attach the file var/log/dist-upgrade/apt.log 2020-11-28 23:49:36,331 INFO Using config files '['./DistUpgrade.cfg.bionic']' 2020-11-28 23:49:36,331 INFO uname information: 'Linux marroni-Lenovo-G50-70 4.15.0-124-generic #127-Ubuntu SMP Fri Nov 6 10:54:43 UTC 2020 x86_64' 2020-11-28 23:49:36,745 INFO apt version: '1.6.12ubuntu0.1' 2020-11-28 23:49:36,746 INFO python version: '3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0]' 2020-11-28 23:49:36,749 INFO release-upgrader version '20.04.29' started 2020-11-28 23:49:36,802 INFO locale: 'en_US' 'UTF-8' 2020-11-28 23:49:36,961 DEBUG Using 'DistUpgradeViewGtk3' view 2020-11-28 23:49:37,008 DEBUG enable dpkg --force-overwrite 2020-11-28 23:49:37,026 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' 2020-11-28 23:49:40,248 DEBUG lsb-release: 'bionic' 2020-11-28 23:49:40,248 DEBUG _pythonSymlinkCheck run 2020-11-28 23:49:40,249 DEBUG openCache() 2020-11-28 23:49:40,249 DEBUG quirks: running PreCacheOpen 2020-11-28 23:49:40,249 DEBUG running Quirks.PreCacheOpen 2020-11-28 23:49:41,230 DEBUG Comparing 4.15.0-122 with 2020-11-28 23:49:41,230 DEBUG Comparing 4.15.0-123 with 4.15.0-122 2020-11-28 23:49:41,230 DEBUG Comparing 4.15.0-124 with 4.15.0-123 2020-11-28 23:49:41,465 DEBUG /openCache(), new cache size 100981 2020-11-28 23:49:41,465 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop') 2020-11-28 23:49:41,466 DEBUG checkViewDepends() 2020-11-28 23:49:41,467 DEBUG running doUpdate() (showErrors=False) 2020-11-28 23:49:44,692 DEBUG openCache() 2020-11-28 23:49:46,008 DEBUG Comparing 4.15.0-122 with 2020-11-28 23:49:46,009 DEBUG Comparing 4.15.0-123 with 4.15.0-122 2020-11-28 23:49:46,009 DEBUG Comparing 4.15.0-124 with 4.15.0-123 2020-11-28 23:49:46,272 DEBUG /openCache(), new cache size 100981 2020-11-28 23:49:46,272 DEBUG doPostInitialUpdate 2020-11-28 23:49:46,272 DEBUG quirks: running focalPostInitialUpdate 2020-11-28 23:49:46,272 DEBUG running Quirks.focalPostInitialUpdate 2020-11-28 23:49:48,631 DEBUG Snap core18 is installed 2020-11-28 23:49:48,777 DEBUG Snap gnome-3-34-1804 is installed 2020-11-28 23:49:48,777 DEBUG Snap gnome-3-34-1804 is not tracking the release channel 2020-11-28 23:49:48,992 DEBUG Snap gtk-common-themes is installed 2020-11-28 23:49:49,309 DEBUG Snap gnome-3-28-1804 is installed 2020-11-28 23:49:49,309 DEBUG Snap gnome-3-28-1804 is not tracking the release channel 2020-11-28 23:49:49,467 DEBUG Snap gnome-calculator is installed 2020-11-28 23:49:49,806 DEBUG Snap gnome-characters is installed 2020-11-28 23:49:49,959 DEBUG Snap gnome-logs is installed 2020-11-28 23:49:52,494 DEBUG MetaPkgs: ubuntu-desktop 2020-11-28 23:49:55,478 DEBUG Foreign: 2020-11-28 23:49:55,478 DEBUG Obsolete: cnijfilter2 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libpng12-0 libsane rstudio scangearmp2 skype:i386 skypeforlinux teams 2020-11-28 23:49:55,479 DEBUG updateSourcesList() 2020-11-28 23:49:55,485 DEBUG rewriteSourcesList() with mirror_check 2020-11-28 23:49:55,486 DEBUG ['ubuntu-minimal', 'ubuntu-standard'] 2020-11-28 23:49:55,486 DEBUG Checking pkg: ubuntu-minimal 2020-11-28 23:49:55,486 DEBUG Checking pkg: ubuntu-standard 2020-11-28 23:49:55,487 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic main restricted' 2020-11-28 23:49:55,487 DEBUG verifySourcesListEntry: deb http://it.archive.ubuntu.com/ubuntu/ focal main restricted 2020-11-28 23:49:55,487 DEBUG url_downloadable: http://it.archive.ubuntu.com/ubuntu//dists/focal/Release 2020-11-28 23:49:55,487 DEBUG s='http' n='it.archive.ubuntu.com' p='/ubuntu//dists/focal/Release' q='' f='' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal main restricted' updated to new dist 2020-11-28 23:49:55,555 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic-updates main restricted' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal-updates main restricted' updated to new dist 2020-11-28 23:49:55,555 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic universe' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal universe' updated to new dist 2020-11-28 23:49:55,555 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic-updates universe' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal-updates universe' updated to new dist 2020-11-28 23:49:55,555 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic multiverse' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal multiverse' updated to new dist 2020-11-28 23:49:55,555 DEBUG examining: 'deb http://it.archive.ubuntu.com/ubuntu/ bionic-updates multiverse' 2020-11-28 23:49:55,555 DEBUG entry 'deb http://it.archive.ubuntu.com/ubuntu/ focal-updates multiverse' updated t
[Bug 1904050] [NEW] Title bar detached from window
Public bug reported: The title bar is detached and not aligned to the window. See attached photos. BR and thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 20:34:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-30 (1474 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade hirsute third-party-packages ** Attachment added: "Screenshot from 2020-11-12 20-33-53.png" https://bugs.launchpad.net/bugs/1904050/+attachment/5433850/+files/Screenshot%20from%202020-11-12%2020-33-53.png ** Changed in: ubuntu-release-upgrader (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/1904050 Title: Title bar detached from window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1904050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904050] Re: Title bar detached from window
confirmed by screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904050 Title: Title bar detached from window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1904050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903593] [NEW] rhythmbox-metadata assert failure: rhythmbox-metadata: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
Public bug reported: Nothing to add, the player worked correctly. B.R. & thanks ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: rhythmbox 3.4.4-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 AssertionMessage: rhythmbox-metadata: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 22:04:33 2020 EcryptfsInUse: Yes ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata InstallationDate: Installed on 2016-10-30 (1471 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp Signal: 6 SourcePackage: rhythmbox StacktraceTop: __assert_fail_base (fmt=0x7fdf7311a458 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 "../nouveau/pushbuf.c", line=723, function=) at assert.c:92 __GI___assert_fail (assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 "../nouveau/pushbuf.c", line=723, function=0x7fdf61e471a0 "nouveau_pushbuf_data") at assert.c:101 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 nouveau_pushbuf_data () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 Title: rhythmbox-metadata assert failure: rhythmbox-metadata: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo separator: ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute third-party-packages ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903593/+attachment/5432754/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903593 Title: rhythmbox-metadata assert failure: rhythmbox-metadata: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903455] [NEW] package libpython3.9-stdlib 3.9.0-1+bionic2 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py', que também está no pa
Public bug reported: Estou tentando realizar instalações de programas que indicam pendências inviabilizadas por esses erros. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpython3.9-stdlib 3.9.0-1+bionic2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: libpython3.9-stdlib:amd64: Install libpython3.9-minimal:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 8 14:36:52 2020 DpkgHistoryLog: Start-Date: 2020-11-08 14:36:51 Commandline: apt --fix-broken install Requested-By: fabio (1000) Upgrade: libpython3.9-minimal:amd64 (3.9.0-1+bionic2, 3.9.0-5~20.04), libpython3.9-stdlib:amd64 (3.9.0-1+bionic2, 3.9.0-5~20.04) DpkgTerminalLog: A preparar para desempacotar .../libpython3.9-stdlib_3.9.0-5~20.04_amd64.deb ... A descompactar libpython3.9-stdlib:amd64 (3.9.0-5~20.04) sobre (3.9.0-1+bionic2) ... [1mdpkg:[0m erro ao processar o arquivo /var/cache/apt/archives/libpython3.9-stdlib_3.9.0-5~20.04_amd64.deb (--unpack): a tentar sobre-escrever '/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py', que também está no pacote libpython3.9-minimal:amd64 3.9.0-1+bionic2 ErrorMessage: a tentar sobre-escrever '/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py', que também está no pacote libpython3.9-minimal:amd64 3.9.0-1+bionic2 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: python3.9 Title: package libpython3.9-stdlib 3.9.0-1+bionic2 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py', que também está no pacote libpython3.9-minimal:amd64 3.9.0-1+bionic2 UpgradeStatus: Upgraded to focal on 2020-10-17 (22 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal 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/1903455 Title: package libpython3.9-stdlib 3.9.0-1+bionic2 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/python3.9/_sysconfigdata__linux_x86_64-linux-gnu.py', que também está no pacote libpython3.9-minimal:amd64 3.9.0-1+bionic2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1903455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903339] Re: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1
Fixed in version 5.09-1 Closing report ** Changed in: manpages (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903339 Title: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages- dev 5.08-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1903339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903339] Re: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1
See also bug #1903243 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903339 Title: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages- dev 5.08-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1903339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903339] Re: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1
confirmed by similar bug 1903243 ** Changed in: manpages (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/1903339 Title: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages- dev 5.08-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1903339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903243] Re: package manpages 5.09-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1
Even pkg manpages 5.08-1 is affected, see bug #1903339 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903243 Title: package manpages 5.09-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages- dev 5.08-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1903243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903339] [NEW] package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1
Public bug reported: 06/11/2020 upgrade ProblemType: Package DistroRelease: Ubuntu 21.04 Package: manpages 5.08-1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 6 19:05:33 2020 Dependencies: DuplicateSignature: package:manpages:5.08-1 Unpacking manpages (5.09-1) over (5.08-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-KfgXY7/04-manpages_5.09-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1 ErrorMessage: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1 InstallationDate: Installed on 2016-10-30 (1468 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.11 SourcePackage: manpages Title: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages-dev 5.08-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: manpages (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903339 Title: package manpages 5.08-1 failed to install/upgrade: trying to overwrite '/usr/share/man/man3/queue.3.gz', which is also in package manpages- dev 5.08-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1903339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903159] [NEW] package gparted 1.0.0-0.1build1 failed to install/upgrade: trying to overwrite '/usr/share/metainfo/gparted.appdata.xml', which is also in package gparted-common 1.0.0-0.1build1
Public bug reported: performing dist-upgrade ProblemType: Package DistroRelease: Ubuntu 21.04 Package: gparted 1.0.0-0.1build1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 5 18:52:51 2020 ErrorMessage: trying to overwrite '/usr/share/metainfo/gparted.appdata.xml', which is also in package gparted-common 1.0.0-0.1build1 InstallationDate: Installed on 2016-10-30 (1467 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.11 SourcePackage: gparted Title: package gparted 1.0.0-0.1build1 failed to install/upgrade: trying to overwrite '/usr/share/metainfo/gparted.appdata.xml', which is also in package gparted-common 1.0.0-0.1build1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gparted (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute 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/1903159 Title: package gparted 1.0.0-0.1build1 failed to install/upgrade: trying to overwrite '/usr/share/metainfo/gparted.appdata.xml', which is also in package gparted-common 1.0.0-0.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1903159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435]
This issue is reproducible (but more rarely) also when using -g0 , see the full build log here: https://launchpadlibrarian.net/501972023/buildlog_ubuntu-groovy-armhf.mesa_20.3~git2010140730.775866~oibaf~g_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435]
*** Bug 97368 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898774] [NEW] package libfaudio0 19.07-0~bionic failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfaudio0/changelog.Debian.gz' partilhado, que é diferente de outras instâncias
Public bug reported: tentei apt --fix-broken install mas nao resolveu ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libfaudio0 19.07-0~bionic ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: libfaudio0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 6 14:40:24 2020 DpkgTerminalLog: A preparar para desempacotar .../libfaudio0_20.04-2_amd64.deb ... A descompactar libfaudio0:amd64 (20.04-2) sobre (19.07-0~bionic) ... [1mdpkg:[0m erro ao processar o arquivo /var/cache/apt/archives/libfaudio0_20.04-2_amd64.deb (--unpack): a tentar sobreescrever '/usr/share/doc/libfaudio0/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libfaudio0:amd64 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libfaudio0/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libfaudio0:amd64 InstallationDate: Installed on 2020-09-22 (13 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: faudio Title: package libfaudio0 19.07-0~bionic failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfaudio0/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libfaudio0:amd64 UpgradeStatus: Upgraded to focal on 2020-10-04 (1 days ago) ** Affects: faudio (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/1898774 Title: package libfaudio0 19.07-0~bionic failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfaudio0/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libfaudio0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/faudio/+bug/1898774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894371] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 5 15:03:23 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, 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.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-05 (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/1894371 Title: package initramfs-tools 0.136ubuntu6.2 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/1894371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85048] Re: rovoked certificates are shown as valid
I'm using tinyca2 version 7.5.6 and this behavior of revoked certificates shown as valids are happening again. In the same way I create certificates, revoke them and they still appear as valid ones. If I try to remove it raises the error "already revoked". I can confirm they are being revoked by inspecting the index.txt file in the CA folder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/85048 Title: rovoked certificates are shown as valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinyca/+bug/85048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852002] Re: Desktop frozen for 30 seconds after Nvidia driver crash
PS: just tested with latest vanilla kernel 5.7.9-050709-generic from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D, things work. It seems there's some issue with 5.4.0-40-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852002] Re: Desktop frozen for 30 seconds after Nvidia driver crash
I'm having the same issue with Ubuntu Focal, kernel 5.4.0-40-generic and latest Nvidia 450.57 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa. I started having this issue when I update Chrome **after** 81.0.4044.138. Up to this version, things work. From this Chrome version on, whenever I open any OpenGL site (eg: onshape.com), everything freezes for a good 30s, I get a message on "OpenGL not working" from the website, and kernel spits this: [ 80.762915] NVRM: GPU at PCI::09:00: GPU-824bae61-b6cb-f859-5c4b-531553afa61b [ 80.762918] NVRM: GPU Board Serial Number: [ 80.762922] NVRM: Xid (PCI::09:00): 31, pid=5024, Ch 0016, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_01a8e000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same error with me. Lenovo Thinkpad Yoga X380 with Ubuntu 20.04. I installed ubuntu on today's date and realized this flaw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878637] [NEW] hxselect crash over not-closed tag
Public bug reported: Hello I can't parse any html page anymore because hxselect crash when ecountering a tag that was not closed. For example http://coincapital.live | hxnormalize | hxselect '#BTC_DTCO' % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 37821 100 378210 0 22182 0 0:00:01 0:00:01 --:--:-- 22182 End tag doesn't match start tag < Thank you ** Affects: html-xml-utils (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/1878637 Title: hxselect crash over not-closed tag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/html-xml-utils/+bug/1878637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873077] Re: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone()
Yes! Fixes this bug for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873077 Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-clocks/+bug/1873077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "co
Ubuntu 19.10, mutter-3.34.3-1ubuntu1~19.10.1 and still crash sometimes with IntelliJ -- apr 17 16:40:45 delphy gnome-shell[2612]: ** apr 17 16:40:45 delphy gnome-shell[2612]: mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL apr 17 16:40:45 delphy gnome-shell[2612]: Bail out! mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should be NULL apr 17 16:40:45 delphy gnome-shell[2612]: GNOME Shell crashed with signal 6 apr 17 16:40:45 delphy gnome-shell[2612]: == Stack trace for context 0x56084b40d3b0 == apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Failed with result 'core-dump'. apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Service has no hold-off time (RestartSec=0), scheduling restart. apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1. apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session (session: ubuntu). apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session (session: ubuntu). apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session. apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session. apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Stopped GNOME Shell on X11. apr 17 16:40:45 delphy systemd[2342]: Starting GNOME Shell on X11... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873077] Re: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone()
** Bug watch added: gitlab.gnome.org/GNOME/gnome-clocks/-/issues #97 https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/97 ** Also affects: gnome-clocks via https://gitlab.gnome.org/GNOME/gnome-clocks/-/issues/97 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873077 Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-clocks/+bug/1873077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873077] [NEW] gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone()
Public bug reported: after view the world clock ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-clocks 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Apr 15 16:37:26 2020 ExecutablePath: /usr/bin/gnome-clocks ExecutableTimestamp: 1583690450 InstallationDate: Installed on 2020-03-20 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: /usr/bin/gnome-clocks --gapplication-service ProcCwd: /home/fabio SegvAnalysis: Segfault happened at: 0x7f35030f3300 : mov 0x10(%rdi),%esi PC (0x7f35030f3300) ok source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-clocks StacktraceTop: g_date_time_to_instant (datetime=0x0) at ../../../glib/gdatetime.c:2709 g_date_time_to_timezone (datetime=datetime@entry=0x0, tz=0x561a2dbb4220) at ../../../glib/gdatetime.c:2709 clocks_world_item_calculate_riseset (self=0x561a2d9f6620 [ClocksWorldItem]) at src/25a6634@@gnome-clocks@exe/world.c:1341 clocks_world_item_real_tick (self=0x561a2d9f6620 [ClocksWorldItem]) at src/25a6634@@gnome-clocks@exe/world.c:2068 (instance=instance@entry=0x561a2d9f6620, signal_id=, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554 Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_instant() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: ** Affects: gnome-clocks Importance: Unknown Status: Unknown ** Affects: gnome-clocks (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash focal ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873077 Title: gnome-clocks crashed with SIGSEGV in g_date_time_to_timezone() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-clocks/+bug/1873077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
The commit was send https://gitlab.gnome.org/GNOME/geary/-/commit/770762055ae8a6aa8e883e198cb2d424db35882c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
** Bug watch added: gitlab.gnome.org/GNOME/geary/-/issues #747 https://gitlab.gnome.org/GNOME/geary/-/issues/747 ** Also affects: geary via https://gitlab.gnome.org/GNOME/geary/-/issues/747 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868152 Title: geary won't start after upgrading to 3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1868152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868152] Re: geary won't start after upgrading to 3.36
Here a better trace
(gdb) bt full
#0 0x723999bf in __GI___poll (fds=0x55af2d30, nfds=1,
timeout=25000) at ../sysdeps/unix/sysv/linux/poll.c:29
resultvar = 18446744073709551100
sc_cancel_oldtype = 0
sc_ret =
#1 0x77d301ae in g_main_context_poll (priority=,
n_fds=1, fds=0x55af2d30, timeout=,
context=0x55af3590) at ../../../glib/gmain.c:4346
ret =
errsv =
poll_func = 0x77d3ff10
poll_func =
ret =
errsv =
#2 g_main_context_iterate (context=0x55af3590, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at ../../../glib/gmain.c:4042
max_priority = 2147483647
timeout = 25000
some_ready =
nfds = 1
allocated_nfds =
fds = 0x55af2d30
#3 0x77d30533 in g_main_loop_run (loop=0x55af2d10) at
../../../glib/gmain.c:4241
self =
__func__ = "g_main_loop_run"
#4 0x778df415 in g_dbus_connection_send_message_with_reply_sync
(connection=connection@entry=0x55ac6020,
message=message@entry=0x55ad24a0,
flags=flags@entry=G_DBUS_SEND_MESSAGE_FLAGS_NONE,
timeout_msec=timeout_msec@entry=-1,
out_serial=out_serial@entry=0x0, cancellable=cancellable@entry=0x0,
error=0x7fffdc90) at ../../../gio/gdbusconnection.c:2164
data = {res = 0x0, context = 0x55af3590, loop = 0x55af2d10}
reply =
__func__ = "g_dbus_connection_send_message_with_reply_sync"
#5 0x778df80f in g_dbus_connection_call_sync_internal
(connection=0x55ac6020, bus_name=0x55aeed80 "org.gnome.Geary",
object_path=0x55af0f40 "/org/gnome/Geary",
interface_name=interface_name@entry=0x7793b231 "org.gtk.Actions",
method_name=method_name@entry=0x7793b259 "DescribeAll",
parameters=parameters@entry=0x0, reply_type=0x7793b265,
flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1, fd_list=0x0,
out_fd_list=0x0, cancellable=0x0, error=0x7fffde60)
at ../../../gio/gdbusconnection.c:5989
message = 0x55ad24a0
reply = 0x0
result = 0x0
local_error = 0x0
send_flags = G_DBUS_SEND_MESSAGE_FLAGS_NONE
__func__ = "g_dbus_connection_call_sync_internal"
#6 0x778e17f7 in g_dbus_connection_call_sync (connection=, bus_name=, object_path=,
interface_name=interface_name@entry=0x7793b231 "org.gtk.Actions",
method_name=method_name@entry=0x7793b259 "DescribeAll",
parameters=parameters@entry=0x0, reply_type=0x7793b265,
flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1, cancellable=0x0,
error=0x7fffde60)
at ../../../gio/gdbusconnection.c:6219
No locals.
#7 0x778b8bf9 in g_dbus_action_group_sync
(group=group@entry=0x55ad2400, cancellable=cancellable@entry=0x0,
error=error@entry=0x7fffde60) at ../../../gio/gdbusactiongroup.c:530
reply =
__func__ = "g_dbus_action_group_sync"
#8 0x778b4a6b in g_application_impl_register
(application=application@entry=0x55ab2160, appid=0x55ae2410
"org.gnome.Geary",
flags=, exported_actions=,
remote_actions=remote_actions@entry=0x55ab2108,
cancellable=cancellable@entry=0x0,
error=0x7fffde60) at ../../../gio/gapplicationimpl-dbus.c:646
actions = 0x55ad2400
impl =
__func__ = "g_application_impl_register"
#9 0x778b166c in g_application_register (error=0x7fffde60,
cancellable=0x0, application=0x55ab2160)
at ../../../gio/gapplication.c:2187
__func__ = "g_application_register"
_g_boolean_var_ =
__inst =
__t =
__r =
#10 g_application_register (application=0x55ab2160, cancellable=0x0,
error=0x7fffde60) at ../../../gio/gapplication.c:2176
__func__ = "g_application_register"
#11 0x778b1aee in g_application_real_local_command_line
(application=0x55ab2160, arguments=0x7fffdf18,
exit_status=0x7fffdeb4)
at ../../../gio/gapplication.c:1106
error = 0x0
options = 0x7fffe0001840
n_args =
#12 0x555fd38e in application_client_real_local_command_line
(base=, args=0x7fffdf18, exit_status=0x7fffdf14)
at
src/client/f537023@@geary-client@sta/application/application-client.c:1444
self = 0x55ab2160
_vala_exit_status = 0
_tmp0_ =
_tmp1_ =
current_path = 0x55ae47f0 "/usr/bin/geary"
_tmp2_ =
_tmp3_ =
_tmp4_ = 0x0
_tmp5_ =
_tmp6_ =
_tmp7_ =
_tmp10_ = 0x55ae47f0 "/usr/bin/geary"
_tmp11_ =
_tmp12_ =
_tmp13_ =
_tmp14_ = -1
_tmp15_ =
result = 0
#13 0x778b1e72 in g_application_run (application=0x55ab2160,
argc=, argv=)
at ../../../gio/gapplication.c:2528
arguments = 0x55ae2d80
status = 0
context = 0x55ac5be0
acquired_context = 1
[Bug 1866565] Re: Enabling the embedded terminal plugin crashes GEdit and subsequently prevents GEdit to start b/c of missing key in GSettings schema
The fix has been sent at gnome repository, but I still get the issues in Ubuntu. You can comment the line 147 at file /usr/lib/x86_64-linux- gnu/gedit/plugins/terminal.py and work again, meanwhile we'll wait the next update for gedit-plugins in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866565 Title: Enabling the embedded terminal plugin crashes GEdit and subsequently prevents GEdit to start b/c of missing key in GSettings schema To manage notifications about this bug go to: https://bugs.launchpad.net/gedit-plugins/+bug/1866565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "co
I recently reported the issue to jetbrains https://youtrack.jetbrains.com/issue/IDEA-233737 (with a screencast) All packages: mutter, mutter-common, gir1.2-mutter-5 and libmutter-5-50 are at version 3.34.1+git20191107-1ubuntu1~19.10.1 journalctl log --- feb 25 12:20:29 delphy gnome-shell[9183]: ** feb 25 12:20:29 delphy gnome-shell[9183]: mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached feb 25 12:20:29 delphy gnome-shell[9183]: Bail out! mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should not be reached feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 == feb 25 12:20:29 delphy gnome-shell[9183]: GNOME Shell crashed with signal 6 feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 0x55de5b4f1540 == Also attached the gdb.txt file produced with these instructions https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell Hope it helps ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/+attachment/5330843/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure
Hello! I am having the same issue. I have Windows 10 installed, and wanted to have Ubuntu as well. I followed the steps described on Ubuntu forums, however it cannot install Ubuntu because it requires an EFI partition, which is not possible to me since I have a legacy BIOS and that cannot be changed to UEFI. Last time I tried to "force" install Ubuntu, I ended up not being able to boot in any of the OS's. During the manual partitioning, I thought that creating a specific "/boot" partition would be enough to solve the problem, but it was not, unfortunately. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766945 Title: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1766945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852077] Re: Backport: bonding: fix state transition issue in link monitoring
Hi Po, IIUC this bug is related to commit 627450ac21f7f4a44b949c5d5e2c35829ff1784f, which is in 4.15.0-74, which I see now in -updates / -security. Isn't it completed yet? $ git tag --contains 627450ac21f7f4a44b949c5d5e2c35829ff1784f Ubuntu-4.15.0-73.82 Ubuntu-4.15.0-74.84 Ubuntu-raspi2-4.15.0-1053.57 Ubuntu-snapdragon-4.15.0-1070.77 $ rmadison linux-image-4.15.0-74-generic linux-image-4.15.0-74-generic | 4.15.0-74.83~16.04.1 | xenial-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-image-4.15.0-74-generic | 4.15.0-74.83~16.04.1 | xenial-updates | amd64, arm64, armhf, i386, ppc64el, s390x linux-image-4.15.0-74-generic | 4.15.0-74.84 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-image-4.15.0-74-generic | 4.15.0-74.84 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852077 Title: Backport: bonding: fix state transition issue in link monitoring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789656] Re: Complete system freeze happening sporadically when running chromium
This is the journal just before freeze. It does not seem to be referred to Chrome ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+attachment/5311974/+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/1789656 Title: Complete system freeze happening sporadically when running chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789656] Re: Complete system freeze happening sporadically when running chromium
Hello, I am using X11, as for: fabio@fabio-office:~$ env | grep x11 XDG_SESSION_TYPE=x11 I don't know how to use Wayland, but I will look how to. I will post the journal as soon as the problem appears again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789656 Title: Complete system freeze happening sporadically when running chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789656] Re: Complete system freeze happening sporadically when running chromium
UPDATE: it seems just to freeze mouse and keyboard input, since I am able to see desktop notifications and other stuff going on. UPDATE2: it does not only affect the Chromium browser, but also Electron (or similar) applications that use the same technology. Since the system doesn't actually freeze completely, I could be able to dump information / logs. Please, give me some command lines you want me to run on my system to further investigate. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789656 Title: Complete system freeze happening sporadically when running chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789656] Re: Complete system freeze happening sporadically when running chromium
It happens to me too. Same problem. Related to Chrome or Chromium. I can add that, if I use ssh to the freezed machine, SSH is active and everything works. I tried to restart X11, even with "runlevel 3" and then "runlevel 5", but once it has frozen, the GUI never comes up again. If I use Firefox, it never happens. I suspect it has something to do with NVidia drivers, but I don't know how to check. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789656 Title: Complete system freeze happening sporadically when running chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853510] Re: "*** buffer overflow detected" when running atop
** Package changed: tree (Ubuntu) => atop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853510 Title: "*** buffer overflow detected" when running atop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atop/+bug/1853510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829823] Re: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt-guests causing hang
Hello Corey and Matthew, I just want to confirm that I've installed libvirt-bin 1.3.1-1ubuntu10.28~cloud0 from mitaka-proposed in a Ubuntu Trusty and it fixes the issue. I'm tagging verification-done-mitaka here. Thank you very much. Regards, Fabio Martins ** Tags removed: verification-mitaka-needed ** Tags added: verification-done-mitaka -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829823 Title: libvirt-bin: during shutdown libvirt-bin is stopped before libvirt- guests causing hang To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797734] Re: slow calculator startup
Hi, Ubuntu 18.04.3 LTS running on SSD laptop with 16GB ram and i7 cpu here, i can confirm that startup was very slow and was solved doing: $ snap remove gnome-calculator $ sudo apt-get install gnome-calculator Before the "snap remove" startup time was as minimum 10 secs, now is 1 sec or less. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271487] Re: terminator need to highlight search string
+1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/271487 Title: terminator need to highlight search string To manage notifications about this bug go to: https://bugs.launchpad.net/terminator/+bug/271487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
