[Bug 2064184] [NEW] sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()" from upstream
Public bug reported: SRU Justification: [Impact] It shouldn't affect normal functionalities. With this fix, it'll remove a warning when unloading and loading the sdhci_of_dwcmshc kernel driver. [Fix] The fix unload the runtime PM when unloading the sdhci_of_dwcmshc driver. [Test Case] Normal regression; Unload and load sdhci_of_dwcmshc.ko again. [Regression Potential] Same behavior from user perspective. ** Affects: linux-bluefield (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/2064184 Title: sdhci_of_dwcmshc: sync up "disable PM runtime in dwcmshc_remove()" from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2064184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
> If you wish to undertake "Guest Customization" reliably then you must > interact correctly with the interfaces provided by the guest OS. These will > of course change from release to release of the guest OS, so in general it is > always necessary to adapt interactions as required by new guest OS releases. > Therefore your customers should not expect any new guest OS release to > function correctly with your Guest Customization feature prior to receiving > such an update from you. > It sounds like this problem will go away as soon as you release your fixed > vSphere update? Yes,this is reason we always test "Guest Customization" on new guest os daily/beta build before it's released to catch such failure due to guest os change. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and must upgrade to it to get the fix. While if guest side(at least in guest os GA build) can fix it, customer will not encounter the failure at all. Certainly, where the fix goes to is case by case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
> If you wish to undertake "Guest Customization" reliably then you must > interact correctly with the interfaces provided by the guest OS. These will > of course change from release to release of the guest OS, so in general it is > always necessary to adapt interactions as required by new guest OS releases. > Therefore your customers should not expect any new guest OS release to > function correctly with your Guest Customization feature prior to receiving > such an update from you. > It sounds like this problem will go away as soon as you release your fixed > vSphere update? When "Guest Customization" fails due to a guest os change, we will work with guest os team to see how to resolve it. The fix could be either on vSphere side or on guest os side. Such failure can be caught before guest os release since we always test new guest os daily/beta build before it's released. If the fix is on vSphere side, customer will have to wait for the next vSphere release which contains the fix and upgrade to it. If the fix is on guest side(at least in guest os GA build), then customer need NOT upgrade vSphere to get the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039206] Re: open-vm-tools "hwclock" needed for VM guest customization not available
Thanks Robie for the information, this is exactly the VMware guest customization updating in the next vSphere 8.0 update release which is "Using timedatectl command to set hardware clock since Ubuntu 23.10". However as Ubuntu 24.04 is LTS, it's widely supported on vSphere 8.x line, without hwclock command, customers who are using the current vSphere 8.0 - 8.0U2 releases will encounter this issue. Understood that timedatctl command shall be used with systemd, still if adding hwclock command back has no conflict, it will be great helpful for customers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039206 Title: open-vm-tools "hwclock" needed for VM guest customization not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2039206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055001] [NEW] Thunderbolt Device Activation Failure and DROM Data CRC Mismatch
Public bug reported: Description: Encountered multiple issues while attempting to connect and activate a Thunderbolt device. Initially, the device was recognized but then disconnected shortly after. System logs indicated a DROM data CRC mismatch, despite which, the system attempted to continue with the device activation. Subsequent log entries indicated failure in the device activation path, as well as a failed attempt to activate the PCIe tunnel, leading to an abort. Something may be useful: boltctl command can not find this eGPU. Error Messages: Device disconnected. DROM data CRC32 mismatch (expected vs. actual value discrepancy). New device recognized but subsequent activation path failure. PCIe tunnel activation failure and aborted attempt. Kernel warning pointing to the tb_path_activate function. System and Hardware Information Operating system version, kernel version (6.5.0-21-generic). Attempted Resolution Steps: Reconnecting the Thunderbolt device. Checking and updating the system kernel and firmware. Adjusting Thunderbolt-related settings in BIOS/UEFI setup. Expected Outcome: Expected the Thunderbolt device to connect successfully and be stably recognized by the system without encountering issues like DROM data mismatch or activation path failures. Actual Outcome Faced a series of issues including frequent device disconnections, DROM data checksum mismatches, activation path failures, and failed attempts to activate the PCIe tunnel. Additional Information Provide all relevant system log entries and outputs. Detailed information on any other attempted solutions or relevant setting adjustments should also be included. Output From: $dmesg | grep thunderbolt [ 1574.244690] thunderbolt 0-2: device disconnected [ 1598.743402] thunderbolt :75:00.5: 2: DROM data CRC32 mismatch (expected: 0x97552eeb, got: 0x8dd06782), continuing [ 1598.754439] thunderbolt 0-2: new device found, vendor=0x215 device=0xb [ 1598.754443] thunderbolt 0-2: XYJ-LINK XY Dock BX [ 1598.863476] thunderbolt :75:00.5: 2:1: hop deactivation failed for hop 1, index 8 [ 1598.863485] thunderbolt :75:00.5: path activation failed [ 1598.863526] WARNING: CPU: 10 PID: 18389 at drivers/thunderbolt/path.c:573 tb_path_activate+0x124/0x500 [thunderbolt] [ 1598.863643] iwlwifi crypto_simd snd_acp_config usbhid snd drm_kms_helper ecdh_generic cryptd nls_iso8859_1 snd_soc_acpi cfg80211 hid rapl ecc ccp i2c_algo_bit soundcore snd_pci_acp3x sch_fq_codel k10temp wmi_bmof mac_hid acpi_tad msr parport_pc ppdev lp parport drm efi_pstore ip_tables x_tables autofs4 nvme xhci_pci r8169 nvme_core video thunderbolt crc32_pclmul i2c_piix4 xhci_pci_renesas realtek nvme_common wmi [ 1598.863701] RIP: 0010:tb_path_activate+0x124/0x500 [thunderbolt] [ 1598.863767] ? tb_path_activate+0x124/0x500 [thunderbolt] [ 1598.863808] ? tb_path_activate+0x124/0x500 [thunderbolt] [ 1598.863825] ? tb_path_activate+0x124/0x500 [thunderbolt] [ 1598.863846] tb_tunnel_restart+0xd6/0x2b0 [thunderbolt] [ 1598.863864] tb_tunnel_activate+0x141/0x180 [thunderbolt] [ 1598.863885] tb_tunnel_pci+0xde/0x250 [thunderbolt] [ 1598.863902] tb_domain_approve_switch+0x3e/0x70 [thunderbolt] [ 1598.863920] authorized_store+0x250/0x290 [thunderbolt] [ 1598.864049] thunderbolt :75:00.5: 0:5 <-> 2:6 (PCI): activation failed [ 1598.864216] thunderbolt :75:00.5: 2:6: PCIe tunnel activation failed, aborting [ 1598.864418] thunderbolt 0-2: device disconnected ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055001 Title: Thunderbolt Device Activation Failure and DROM Data CRC Mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
Thank you Olivier The command resolved my problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
** Package changed: ubuntu => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I am on Ubuntu 22.04. It also freezes my Google chrome browser(Version 100.0.4896.127), if I try to upload any file from local. The page and the window become unresponsive. But I can create new window or close the browser using right click menu from the GNOME on the top and right sidebar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1970148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Hi @Nick Rosbrook (enr0n) Will any modification(regarding snapd udev rule) be included in the Ubuntu 22.04 release version? Thanks, Regards, Jiwei -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Yes, same here. I got the same good news with beta image. Christian, thanks for your help again. I think we can close this bug for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
Appreciate your help, Christian. I'm trying to find a way to reproduce this issue without vSphere, will post it here once get it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
VMware internal bug for this is 2928681. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
According to our investigation, I found that the issue is caused by the "mount" system call can not be allowed to execute. And after checking the upstream commit, the issue is introduced by the following patch, commit ee8f26180d01e3ddd4e5f20b03b81e5e737657ae Author: Lennart Poettering Date: Thu Apr 19 11:04:17 2018 +0200 units: switch from system call blacklist to whitelist This is generally the safer approach, and is what container managers (including nspawn) do, hence let's move to this too for our own services. This is particularly useful as this this means the new @system-service system call filter group will get serious real-life testing quickly. This also switches from firing SIGSYS on unexpected syscalls to returning EPERM. This would have probably been a better default anyway, but it's hard to change that these days. When whitelisting system calls SIGSYS is highly problematic as system calls that are newly introduced to Linux become minefields for services otherwise. Note that this enables a system call filter for udev for the first time, and will block @clock, @mount and @swap from it. Some downstream distributions might want to revert this locally if they want to permit unsafe operations on udev rules, but in general this shiuld be mostly safe, as we already set MountFlags=shared for udevd, hence at least @mount won't change anything. Before the patch,systemd-udevd.service has not set “SystemCallFilter=”,but after the patch,the “SystemCallFilter=@system- service @module @raw-io” was added diff --git a/units/systemd-udevd.service.in b/units/systemd-udevd.service.in index 2b9fa69d9b..6a3814e5d9 100644 --- a/units/systemd-udevd.service.in +++ b/units/systemd-udevd.service.in @@ -29,6 +29,8 @@ PrivateMounts=yes MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 +SystemCallFilter=@system-service @module @raw-io +SystemCallErrorNumber=EPERM SystemCallArchitectures=native LockPersonality=yes IPAddressDeny=any Because there is no "SystemCallFilter=@system-service @module @raw-io" in the /usr/lib/systemd/system/systemd-udevd.service on UBuntu20.04, we can not experience the same issue, but can reproduce the issue on UBuntu22.04. If we add "@mount" to "SystemCallFilter=" on UBuntu22.04, the issue can be fixed. Thanks, Regards, Jiwei -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962843] Re: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd-networkd.socket
This issue doesn't reproduce on 22.04 Live server image, its '/usr/lib/systemd/system/systemd-networkd.socket' is same with 22.04 Desktop image, so looks like shutdown.target in systemd-networkd.socket is not the root cause. I think the systemd dependence is quite different between Desktop and Server images, please systemd experts look into this. By running below command on Ubuntu 21.04 Desktop, Ubuntu 22.04 Desktop and Ubuntu 22.04 Server VMs, got some .svg files, attached them in svg_files.zip to this bug for your reference. 1. systemd-analyze plot > plot2104_desktop.svg 2. systemd-analyze plot > plot2204_desktop.svg 3. systemd-analyze plot > plot2204_server.svg 4. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2104_desktop.svg 5. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_desktop.svg 6. systemd-analyze dot 'systemd-networkd.service' | dot -Tsvg > dot2204_server.svg According to the plot output, systemd-networkd starts late only on Ubuntu 22.04 Desktop VM, this leads to customization command 'netplan apply' fail. ** Attachment added: "svg files" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+attachment/5566877/+files/svg_files.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962843 Title: Guest OS customization fail for ubuntu 22.04 desktop in vsphere due to adding 'shutdown.target' in file /usr/lib/systemd/system/systemd- networkd.socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
root@plis231v:~# ps -o cmd fp 1 CMD /sbin/init root@plis231v:~# sudo ls -lah /proc/1/exe lrwxrwxrwx 1 root root 0 Feb 11 22:51 /proc/1/exe -> /sbin/upstart root@plis231v:~# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.15.0-167-generic root=/dev/mapper/plis231v-root ro quiet root@plis231v:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
any suggestion to fix this? I had tried below command. root@plis231v:~# sudo dpkg -l | grep systemd ii libpam-systemd:amd64 229-4ubuntu21.31+esm1 amd64system and service manager - PAM mod ii libsystemd0:amd64 229-4ubuntu21.31+esm1 amd64systemd utility library ii python3-systemd231-2build1 amd64Python 3 bindings for systemd ii systemd229-4ubuntu21.31+esm1 amd64system and service manager rc systemd-services 204-5ubuntu20.31 amd64systemd runtime services ii systemd-shim 9-1bzr4ubuntu1 amd64shim for systemd root@plis231v:~# root@plis231v:~# root@plis231v:~# root@plis231v:~# apt-get install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/3,659 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 77423 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.31+esm1_amd64.deb ... Unpacking systemd (229-4ubuntu21.31+esm1) over (229-4ubuntu21.31+esm1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3.6+esm1) ... Processing triggers for ureadahead (0.100.0-19.1) ... ureadahead will be reprofiled on next reboot Setting up systemd (229-4ubuntu21.31+esm1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Operation failed: No such file or directory [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. root@plis231v:~# systemctl status Failed to read server status: Invalid argument root@plis231v:~# root@plis231v:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
root@plis231v:~# systemctl status Failed to read server status: Invalid argument root@plis231v:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
root@plis231v:~# apt show snapd Package: snapd Version: 2.54.3+16.04~esm2 Built-Using: apparmor (= 2.10.95-0ubuntu2.11), libcap2 (= 1:2.24-12), libseccomp (= 2.4.3-1ubuntu3.16.04.3) Priority: optional Section: devel Maintainer: Ubuntu Developers Installed-Size: 146 MB Depends: adduser, apparmor (>= 2.10.95-0ubuntu2.2), ca-certificates, openssh-client, squashfs-tools, systemd, udev, init-system-helpers (>= 1.18~), libc6 (>= 2.17), libfuse2 (>= 2.6), liblzma5 (>= 5.1.1alpha+20110809), liblzo2-2, libudev1 (>= 183), zlib1g (>= 1:1.1.4) Recommends: gnupg Suggests: zenity | kdialog Conflicts: snap (<< 2013-11-29-1ubuntu1) Breaks: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9) Replaces: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9) Download-Size: 33.3 MB APT-Manual-Installed: yes APT-Sources: https://esm.ubuntu.com/infra/ubuntu xenial-infra-security/main amd64 Packages Description: Daemon and tooling that enable snap packages Install, configure, refresh and remove snap packages. Snaps are 'universal' packages that work across many different Linux systems, enabling secure distribution of the latest apps and utilities for cloud, servers, desktops and the internet of things. . Start with 'snap list' to see installed snaps. N: There are 2 additional records. Please use the '-a' switch to see them. root@plis231v:~# root@plis231v:~# snap version snap2.54.3+16.04~esm2 snapd unavailable series - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
Hey Alberto Mardegan, This issue is blocking us to enable livepatch. root@plis231v:~# systemctl status snapd Failed to get properties: No such interface '' root@plis231v:~# systemctl status snapd.socket Failed to get properties: No such interface '' root@plis231v:~# journalctl -b -u snapd No journal files were found. -- No entries -- root@plis231v:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] [NEW] snap failed to run with '/usr/bin/snap wait system seed.loaded'
Public bug reported: I tried to enable livepatch without any success. ([Bug 1960689] ) support suggested me report a bug for snapd. root@plis231v:~# sudo ua enable livepatch One moment, checking your subscription first Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools >> logs 22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main return args.action(args, cfg=cfg) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f return f(args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f retval = f(*args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in action_enable ent_ret, reason = entitlement.enable() File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 197, in enable ret = self._perform_enable(silent=silent) File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", line 160, in _perform_ena [snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp out, err = _subp(args, rcs, capture, timeout, env=env) File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp stderr=err.decode("utf-8"), uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap wait system seed.loaded' [sage: error: cannot communicate with server: Get http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: connect: no such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 27.4.1~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-167-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 Date: Fri Feb 11 23:01:08 2022 InstallationDate: Installed on 2010-12-02 (4089 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1960689] Re: livepatch is not able to enabled
Snap doesn't seem work, any workaround? root@plis231v:~# systemctl status snapd Failed to get properties: No such interface '' root@plis231v:~# systemctl start snapd.service Failed to start snapd.service: Unknown unit: snapd.service See system logs and 'systemctl status snapd.service' for details. root@plis231v:~# -Original Message- From: nore...@launchpad.net On Behalf Of Lucas Albuquerque Medeiros de Moura Sent: Tuesday, February 15, 2022 8:11 AM To: Gene Sun Subject: [Bug 1960689] Re: livepatch is not able to enabled CAUTION: EXTERNAL EMAIL Hello Gene Sun, It seems there is something wrong if your snapd service. What is the output of running: $ systemctl status snapd And if the service is not running, can you run: $ systemctl start snapd.service And double check if snap services is now running as expected ? -- You received this bug notification because you are subscribed to the bug report. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1960689data=04%7C01%7Cgsun%40ipipeline.com%7C0dcfb69159a34629aeef08d9f085fae3%7C4adda90d810f42fc852f18ed6744d7b3%7C0%7C0%7C637805280526405489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=50KuzPBQWzrLLnk%2F2VLoKlgaC7wBoC4e0ZvO5vPcpS0%3Dreserved=0 Title: livepatch is not able to enabled Status in ubuntu-advantage-tools package in Ubuntu: New Bug description: I tried to enable livepatch without any success. root@plis231v:~# sudo ua enable livepatch One moment, checking your subscription first Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools >> logs 22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main return args.action(args, cfg=cfg) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f return f(args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f retval = f(*args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in action_enable ent_ret, reason = entitlement.enable() File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 197, in enable ret = self._perform_enable(silent=silent) File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", line 160, in _perform_ena [snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp out, err = _subp(args, rcs, capture, timeout, env=env) File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp stderr=err.decode("utf-8"), uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap wait system seed.loaded' [sage: error: cannot communicate with server: Get http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: connect: no such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 27.4.1~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-167-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 Date: Fri Feb 11 23:01:08 2022 InstallationDate: Installed on 2010-12-02 (4089 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago) To manage notifications about this bug go to: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fubuntu-advantage-tools%2F%2Bbug%2F1960689%2F%2Bsubscriptionsdata=04%7C01%7Cgsun%40ipipeline.com%7C0dcfb69159a34629aeef08d9f085fae3%7C4adda90d810f42fc852f18ed6744d7b3%7C0%7C0%7C637805280526405489%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=x0jwoiGYQsie0F3UBAHRFNmw6FBm7M0b1nWHWrUKLmQ%3Dreserved=0 This e-mail and any attachments, are pri
RE: [Bug 1960689] Re: livepatch is not able to enabled
Here is what I saw. (I had reinstalled snap) root@plis231v:~# snap services error: cannot communicate with server: Get http://localhost/v2/apps?select=service: dial unix /run/snapd.socket: connect: no such file or directory root@plis231v:~# -Original Message- From: nore...@launchpad.net On Behalf Of Grant Orndorff Sent: Monday, February 14, 2022 1:54 PM To: Gene Sun Subject: [Bug 1960689] Re: livepatch is not able to enabled CAUTION: EXTERNAL EMAIL Hello Gene Sun, thank you for taking the time to file a bug! The livepatch service is installed as a snap when you run `ua enable livepatch`. It looks like the `snap` command is failing because the snapd.socket isn't available. Can you verify that the snap service is working or not by running a snap command like `snap services`? -- You received this bug notification because you are subscribed to the bug report. https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1960689data=04%7C01%7Cgsun%40ipipeline.com%7C3e181dee376048827e9d08d9efec511f%7C4adda90d810f42fc852f18ed6744d7b3%7C0%7C0%7C637804620527924141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=XvcdaEP3%2BW9P5Xo01dtDrfknUZ0%2Fsj23FMZRDBeBEys%3Dreserved=0 Title: livepatch is not able to enabled Status in ubuntu-advantage-tools package in Ubuntu: New Bug description: I tried to enable livepatch without any success. root@plis231v:~# sudo ua enable livepatch One moment, checking your subscription first Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools >> logs 22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main return args.action(args, cfg=cfg) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f return f(args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f retval = f(*args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in action_enable ent_ret, reason = entitlement.enable() File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 197, in enable ret = self._perform_enable(silent=silent) File "/usr/lib/python3/dist- packages/uaclient/entitlements/livepatch.py", line 160, in _perform_ena [snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp out, err = _subp(args, rcs, capture, timeout, env=env) File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp stderr=err.decode("utf-8"), uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap wait system seed.loaded' [sage: error: cannot communicate with server: Get http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: connect: no such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 27.4.1~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-167-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 Date: Fri Feb 11 23:01:08 2022 InstallationDate: Installed on 2010-12-02 (4089 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago) To manage notifications about this bug go to: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fubuntu- advantage- tools%2F%2Bbug%2F1960689%2F%2Bsubscriptionsdata=04%7C01%7Cgsun%40ipipeline.com%7C3e181dee376048827e9d08d9efec511f%7C4adda90d810f42fc852f18ed6744d7b3%7C0%7C0%7C637804620527924141%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000sdata=6YcyNAQL3AP40ZCaW7kIt%2FomZUhIElMliXGA%2BqsFvYE%3Dreserved=0 This e-ma
[Bug 1960689] Re: livepatch is not able to enabled
root@plis231v:~# uname -a Linux plis231v 4.15.0-167-generic #175~16.04.1-Ubuntu SMP Mon Jan 17 16:44:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@plis231v:~# root@plis231v:~# root@plis231v:~# sudo ua enable livepatch One moment, checking your subscription first Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools root@plis231v:~# root@plis231v:~# root@plis231v:~# root@plis231v:~# ubuntu-bug ubuntu-advantage-tools *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 90% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+filebug/710f8fc2-8bb8-11ec-b78d-40a8f0308420? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960689 Title: livepatch is not able to enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1960689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960689] [NEW] livepatch is not able to enabled
Public bug reported: I tried to enable livepatch without any success. root@plis231v:~# sudo ua enable livepatch One moment, checking your subscription first Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools >> logs 22-02-11 22:27:00,410 - util.py:(429) [DEBUG]: Reading file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,410 - util.py:(700) [DEBUG]: Writing file: /var/lib/ubuntu-advantage/notices.json 2022-02-11 22:27:00,411 - cli.py:(1499) [ERROR]: Unhandled exception, please file a bug Traceback (most recent call last): File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1458, in wrapper return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 1544, in main return args.action(args, cfg=cfg) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 166, in new_f return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 189, in new_f return f(args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 147, in new_f retval = f(*args, cfg=cfg, **kwargs) File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 888, in action_enable ent_ret, reason = entitlement.enable() File "/usr/lib/python3/dist-packages/uaclient/entitlements/base.py", line 197, in enable ret = self._perform_enable(silent=silent) File "/usr/lib/python3/dist-packages/uaclient/entitlements/livepatch.py", line 160, in _perform_ena [snap.SNAP_CMD, "wait", "system", "seed.loaded"], capture=True File "/usr/lib/python3/dist-packages/uaclient/util.py", line 662, in subp out, err = _subp(args, rcs, capture, timeout, env=env) File "/usr/lib/python3/dist-packages/uaclient/util.py", line 619, in _subp stderr=err.decode("utf-8"), uaclient.util.ProcessExecutionError: Failed running command '/usr/bin/snap wait system seed.loaded' [sage: error: cannot communicate with server: Get http://localhost/v2/snaps/system/conf?keys=seed.load /run/snapd.socket: connect: no such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-advantage-tools 27.4.1~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-167.175~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-167-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30+esm3 Architecture: amd64 Date: Fri Feb 11 23:01:08 2022 InstallationDate: Installed on 2010-12-02 (4089 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-advantage-tools UpgradeStatus: Upgraded to xenial on 2017-01-21 (1847 days ago) ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960689 Title: livepatch is not able to enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1960689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954844] Re: lxqt-panel 0.17.1 is leaking memory, v1.0.0 fixed it
apport-collect reports much much more than I'm willing to share, and I believe what I've provided is sufficient. So I'll pass this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954844 Title: lxqt-panel 0.17.1 is leaking memory, v1.0.0 fixed it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1954844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954844] [NEW] lxqt-panel 0.17.1 is leaking memory, v1.0.0 fixed it
Public bug reported: The culprit might as well be the same as reported in https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1881397 The reason I'm opening this, according to upstream, where I initially reported the problem, https://github.com/lxqt/lxqt/issues/2154 is that the problem has been fixed in the newest version. So upgrading lxqt-panel from 0.17.1 to 1.0.0 should be able to fix the issue. Please upgrade lxqt-panel to 1.0.0. Duplicating my initially reported problem (at https://github.com/lxqt/lxqt/issues/2154) below: Reported by smem: PID User Command Swap USS PSS RSS 1465 myid /usr/bin/lxqt-panel 522704 763824 767644 786196 1224 root /usr/lib/xorg/Xorg -noliste 169692 828352 847767 874776 1461 myid /usr/bin/pcmanfm-qt --deskt97892218803214756488 % cat /proc/1465/smaps | grep -A10 'heap' 55672ef42000-55677beb rw-p 00:00 0 [heap] Size:1260984 kB KernelPageSize:4 kB MMUPageSize: 4 kB Rss: 749320 kB Pss: 749320 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 6576 kB Private_Dirty:742744 kB Referenced: 747880 kB It is surely leaking memory, otherwise, the heap won't be this big, 1.2G!! This is LUbuntu 21.10: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish ** Affects: lxqt-panel (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/1954844 Title: lxqt-panel 0.17.1 is leaking memory, v1.0.0 fixed it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1954844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950065] Re: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
> And I've just reinstalled them all. with, sudo apt install --reinstall fcitx fcitx-bin fcitx-config-common fcitx- config-gtk fcitx-data fcitx-frontend-all fcitx-frontend-gtk2 fcitx- frontend-gtk3 fcitx-frontend-qt5:amd64 fcitx-module-dbus fcitx-module- kimpanel fcitx-module-lua fcitx-module-x11 fcitx-modules fcitx-ui- classic fcitx5-module-quickphrase-editor:amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950065 Title: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1950065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950065] [NEW] GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Public bug reported: I'm getting the following error whenever I start GTK related programs, like meld, firefox etc: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed All search hits suggests that it is fcitx-module-dbus' problem, and removing it will solve the problem. However, I do want to keep fcitx- module-dbus. Any other alternatives? I asked in a developer group and they suggest to upgrade to fcitx5 instead, but so far I can only find fcitx-module-dbus in 21.10 impish's repo, but it does has fcitx5. Can fcitx5-module-dbus be packed and available in 21.10 impish please? $ date; meld Sat Nov 6 17:46:39 EDT 2021 2021-11-06 17:47:05,368 CRITICAL Gtk: (org.gnome.meld:26756): GLib-GIO-CRITICAL **: 17:47:05.368: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed 2021-11-06 17:47:05,368 CRITICAL Gtk: (org.gnome.meld:26756): GLib-GIO-CRITICAL **: 17:47:05.368: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed . . . Basically it is causing every GTK related programs, like meld, firefox etc, to have an extended delay in starting. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish $ sudo apt list fcitx* | grep installed fcitx-bin/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-config-common/impish,impish,now 0.4.10-3 all [installed,automatic] fcitx-config-gtk/impish,now 0.4.10-3 amd64 [installed,automatic] fcitx-data/impish,impish,now 1:4.2.9.8-3 all [installed,automatic] fcitx-frontend-all/impish,impish,now 1:4.2.9.8-3 all [installed,automatic] fcitx-frontend-gtk2/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-frontend-gtk3/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-frontend-qt5/impish,now 1.2.5-1ubuntu2 amd64 [installed,automatic] fcitx-module-dbus/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-module-kimpanel/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-module-lua/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-module-x11/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-modules/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx-ui-classic/impish,now 1:4.2.9.8-3 amd64 [installed,automatic] fcitx5-module-quickphrase-editor/impish,now 1.2.5-1ubuntu2 amd64 [installed,automatic] fcitx/impish,impish,now 1:4.2.9.8-3 all [installed,automatic] And I've just reinstalled them all. ** Affects: fcitx (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/1950065 Title: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1950065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950065] Re: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
So far I can only find fcitx-module-dbus *version 4* in 21.10 impish's repo, but it does has fcitx5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950065 Title: GLib-GIO-CRITICAL **: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1950065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950001] [NEW] [BPO] Backport for ubuntu 20.04
Public bug reported: [Impact] * Update bpftrace to latest version 0.14.0 [Scope] * 20.04 ** Affects: bpftrace (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/1950001 Title: [BPO] Backport for ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/1950001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948364] [NEW] Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot
Public bug reported: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl log about static IP" https://bugs.launchpad.net/bugs/1948364/+attachment/5534988/+files/Static_IP_loss_2021-10-22_10-27-30.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948364 Title: Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
terraform is new to me, but if it's using https://github.com/vmware /cloud-init-vmware-guestinfo, it won't work unless the installation has been done in VM. See https://github.com/vmware/cloud-init-vmware- guestinfo/blob/master/README.md So you have to power-on the VM firstly, have you tried to modify OVF file extracted from OVA file, it contains a password property which is "Default User's password", the default user is ubuntu. Once you get into the VM, you can install cloud-init-vmware-guestinfo and then save the VM as source VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Hello Lukáš, You mentioned "initiate it with cloud-init (userdata + metadata)", may I know how did you initiate userdata and metadata? also you mentioned guestinfo.userdata and guestinfo.metadata, did you use the way described here: https://github.com/vmware/cloud-init-vmware-guestinfo ? Another question: did you trigger guest customization on the VM? if not, you needn't disable guest customization from the vmware-toolbox-cmd. There should be a default user 'ubuntu' which is configured in /etc/cloud/cloud.cfg, I think you will be asked to set password for this user when you deploy focal-server-cloudimg-amd64.ova on ESXi(I'm not sure what free version means, were you using vCenter server?) At last, we need cloud-init logs to see what really happened in VM, command 'sudo cloud-init collect-logs' should help to collect them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927263] [NEW] mlx-bootctl: rshim logging display from linux sysfs
Public bug reported: This one is opened to track the merge of the mlx-bootctl driver fix to support rshim logging display from linux sysfs. SRU Justification: [Impact] * N/A. [Fix] * Add support to display rshim logging bufferthe check properly to make sure the buffer won't wrap-around. [Test Case] * cat /sys/bus/platform/drivers/mlx-bootctl/rsh_log. Example: cat /sys/bus/platform/drivers/mlx-bootctl/rsh_log INFO[BL2]: start INFO[BL2]: DDR POST passed INFO[BL2]: UEFI loaded INFO[BL31]: start INFO[BL31]: runtime ... [Regression Potential] * SQA has regressioned the driver with this change and didn't find any new issues. [Other] * N/A ** Affects: linux-bluefield (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/1927263 Title: mlx-bootctl: rshim logging display from linux sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927262] [NEW] tmfifo: Fix a memory barrier issue
Public bug reported: This one is used to track a code merge of the tmfifo driver. SRU Justification: [Impact] * The virtio framework uses wmb() when updating avail->idx. It guarantees the write order, but not necessarily loading order for the code accessing the memory. So potentially it could cause traffic stuck which has been observed in the field. [Fix] * This commit adds a load barrier after reading the avail->idx to make sure all the data in the descriptor is visible. It also adds a barrier when returning the packet to virtio framework to make sure read/writes are visible to the virtio code. [Test Case] * Just normal test. This change doesn't affect any functionality. [Regression Potential] * SQA team has been running test with this fix for quite some time (several months). No issue as observed. [Other] * N/A ** Affects: linux-bluefield (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/1927262 Title: tmfifo: Fix a memory barrier issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927253] [NEW] mlxbf-tmfifo: Add ctrl message and MAC configuration
Public bug reported: THis one is created to track the commit merge of the mlxbf-tmfifo driver to support ctrl message and MAC configuration. SRU Justification: [Impact] * N/A. [Fix] * N/A. [Test Case] * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' from external rshim driver. The rshim MAC address will show up. # cat /dev/rshim0/misc DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log) BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap) BOOT_TIMEOUT100 (seconds) DROP_MODE 0 (0:normal, 1:drop) SW_RESET0 (1: reset) DEV_NAMEusb-1-1.1 DEV_INFOBlueField-2(Rev 0) OPN_STR MBF2M516A-EEEO BOOT_RESET_SKIP 0 (1: skip) PEER_MAC00:1a:ca:ff:ff:01 (rw) PXE_ID 0x (rw) VLAN_ID 0 0 (rw) * echo "PEER_MACxx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC address, which will take effect in next boot. [Regression Potential] * This is a new enhancement and is backward-compatible with previous behavior. [Other] * N/A ** Affects: linux-bluefield (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/1927253 Title: mlxbf-tmfifo: Add ctrl message and MAC configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
I think the network disconnection is a result of guest-customization task, although the vm side customization has been disabled according to the tools configuration. You can try connect the vm network right before power-on VM by gosv, then the vm network can be available automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Yes, exactly. I wonder how the network-config file is applied in your current workflow. Yes, guest customization can be turned off if VM's open-vm-tools version is 11.1.0 or above, see KB https://kb.vmware.com/s/article/78903. I just checked open-vm-tools version in https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.ova, it's 11.0.5. So you have to upgrade to 11.1.0+ to disable guest-customization. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919847] Re: rshim logging buffer could overflow and get lost
Verified that the same fix has been available in the master-next branch. ** Tags removed: verification-needed-focal ** Tags added: 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/1919847 Title: rshim logging buffer could overflow and get lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1919847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Understood. I think you are using vSphere7, guest-customization does support netplan from vSphere 6.7U3g, so network-config can be set. Guest-customization has 2 engines: one is perl scripts, the other is cloud-init. Unfortunately, neither of them can work with cloud-init to set userdata guest-config at the same boot. For perl script based guest-customization, it has dependency on dbus, due to the reason in comment #28, it fails with cloud-init running. For cloud-init based guest-customization, it uses the same cloud-init datasource OVF with ISO file, but different seed. Cloud-init can only apply either guest-customization or ISO userdata guest-config. Good news is if you are using vSphere7, you can use customization post- customization script to finish your workflow, need below steps: 1. Power-on VM which deploy from ova. 2. Disable cloud-init by running the command “sudo touch /etc/cloud/cloud-init.disabled” 3. Enable customization script by running the command "vmware-toolbox-cmd config set deployPkg enable-custom-scripts true" 3. Power-off VM and convert it to template. 4. Create a new guest-customization specification which includes network-configs and customization script, the script looks like: #!/bin/sh if [ x$1 == x"postcustomization" ]; then rm /etc/cloud/cloud-init.disabled systemctl reboot fi 5. Generate the cloud-init configurations for guest-config dynamically and create a cloud-init.iso file 6. The rest steps you did Related document and KB: a. Create a Customization Specification for Linux https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-9A5093A5-C54F-4502-941B-3F9C0F573A39.html b. Setting the customization script for virtual machines in vSphere 7.0 https://kb.vmware.com/s/article/74880 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Yes, let me understand your case more clearly, I thought cloud-init is only needed at step1. Attach an iso to set up user, ssk-key, is this a one time job or you want it happen for all cloned new VMs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@Florian The issue is a bit of different with the one reported at the beginning of this bug. Let me explain the details and provide a workaround for you. The key is when dbus.service is running at booting. With ova, cloud-init will be enabled and run, when it's running, it blocks dbus, see reason at comment #8. So dbus is running too late to make customization work even with the fix in 6.7U3. In your case, I suggest you create a new template but turn ova into template directly. Steps: 1. Power-on VM which deploy from ova. 2. Disable cloud-init by by running the command “sudo touch /etc/cloud/cloud-init.disabled” 3. Power-off VM and convert it to template. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919847] Re: rshim logging buffer could overflow and get lost
** Description changed: On Bluefield platforms, the 'bfrshlog' script can be used to write a string into the internal rshim logging buffer which has size 1KB. When the buffer is full, the intention is to drop the new data. However, due to a bug, the buffer could be overwritten and wrap-around when full. SRU Justification: [Impact] - * When 'cat /dev/rshim/misc' with DISPLAY_LEVEL set to 2, the logging buffer could be potentially displayed as empty when it's full. + * When 'cat /dev/rshim0/misc' with DISPLAY_LEVEL set to 2, the logging buffer could be potentially displayed as empty when it's full. [Fix] * Add the check properly to make sure the buffer won't wrap-around. [Test Case] - * Run "bfrshlog " repeatedly and check the /dev/rshim/misc with DISPLAY_LEVEL set to 2 in this file. The buffer shouldn't be overwritten or wrap-around. - + * Run "bfrshlog " repeatedly and check the /dev/rshim0/misc with DISPLAY_LEVEL set to 2 in this file. The buffer shouldn't be overwritten or wrap-around. [Regression Potential] - * Yes, it should be easy to add regression. + * The rshim log can be displayed by setting "DISPLAY_LEVEL 2" in /dev/rshim0/misc, then "cat /dev/rshim0/misc" to see the log messages. The log should contains ATF/UEFI booting progress and user logs from Linux applications by using the bfrshlog script. In any case, the log should always start from ATF logging, not overwritten or wrap-around. When the buffer is full, new data will be dropped. [Other] * N/A -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919847 Title: rshim logging buffer could overflow and get lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1919847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919847] [NEW] rshim logging buffer could overflow and get lost
Public bug reported: On Bluefield platforms, the 'bfrshlog' script can be used to write a string into the internal rshim logging buffer which has size 1KB. When the buffer is full, the intention is to drop the new data. However, due to a bug, the buffer could be overwritten and wrap-around when full. SRU Justification: [Impact] * When 'cat /dev/rshim/misc' with DISPLAY_LEVEL set to 2, the logging buffer could be potentially displayed as empty when it's full. [Fix] * Add the check properly to make sure the buffer won't wrap-around. [Test Case] * Run "bfrshlog " repeatedly and check the /dev/rshim/misc with DISPLAY_LEVEL set to 2 in this file. The buffer shouldn't be overwritten or wrap-around. [Regression Potential] * Yes, it should be easy to add regression. [Other] * N/A ** Affects: linux-bluefield (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/1919847 Title: rshim logging buffer could overflow and get lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1919847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897491] Re: greeter hang with 100% CPU with black display
I have encountered this problem in the armhf board too. I employed Xubuntu 20.04 on both RK3399(aarch64) and RK3288(armhf). Then I found that the lightdm-greater cannot work in RK3288. The log is the same as Steve said. I attempted to avoid this problem by logging in automatically. It's a trick to use Xubuntu with a problematic greeter since it still goes to a black screen if I want to change users or reactiong. Do you find any solutions to resolve this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897491 Title: greeter hang with 100% CPU with black display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1897491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
actually, the shell extension(in ubuntu software) Multi Monitors Add-On works, although it is not perfect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
When I am in the full-screen on the primary monitor, the top bar is blocked, so it is necessary for me to show the top bar in another monitor. It is truely a bug to be fixed, but the Linux seems not to be aware of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903915] [NEW] OC RAM hardware Error and auto reboot
Public bug reported: OC RAM results in hardware Error in dmesg, and auto-reboot from time to time. The same BIOS setting OC RAM worked just fine on Windows 10 2004, and also passed RAM TEST 86. error log: [ 316.850589] [Hardware Error]: Corrected error, no action required. [ 316.850593] [Hardware Error]: CPU:0 (17:71:0) MC25_STATUS[-|CE|MiscV|-|-|-|-|CECC|-|-|-]: 0x9800403e [ 316.850597] [Hardware Error]: IPID: 0x000100ff03830400 [ 316.850599] [Hardware Error]: Platform Security Processor Ext. Error Code: 62 [ 316.850599] [Hardware Error]: cache level: RESV, tx: INSN [ 628.157254] mce: [Hardware Error]: Machine check events logged [ 628.157256] [Hardware Error]: Corrected error, no action required. [ 628.157259] [Hardware Error]: CPU:0 (17:71:0) MC27_STATUS[-|CE|MiscV|-|-|-|SyndV|-|-|-]: 0x9822080b [ 628.157262] [Hardware Error]: IPID: 0x0001002e0500, Syndrome: 0x5a020001 [ 628.157264] [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error. [ 628.157265] [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xuhui 2030 F pulseaudio /dev/snd/controlC3: xuhui 2030 F pulseaudio /dev/snd/controlC1: xuhui 2030 F pulseaudio /dev/snd/controlC2: xuhui 2030 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 13:11:07 2020 InstallationDate: Installed on 2019-12-26 (321 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=63d433f9-bac8-44c0-8a5b-094c4bfaff86 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2311 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2311:bd10/16/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Description changed: OC RAM results in hardware Error in dmesg, and auto-reboot from time to time. The same BIOS setting OC RAM worked just fine on Windows 10 2004, and also passed RAM TEST 86. + + error log: + [ 316.850589] [Hardware Error]: Corrected error, no action required. + [ 316.850593] [Hardware Error]: CPU:0 (17:71:0) MC25_STATUS[-|CE|MiscV|-|-|-|-|CECC|-|-|-]: 0x9800403e + [ 316.850597] [Hardware Error]: IPID: 0x000100ff03830400 + [ 316.850599] [Hardware Error]: Platform Security Processor Ext. Error Code: 62 + [ 316.850599] [Hardware Error]: cache level: RESV, tx: INSN + [ 628.157254] mce: [Hardware Error]: Machine check events logged + [ 628.157256] [Hardware Error]: Corrected error, no action required. + [ 628.157259] [Hardware Error]: CPU:0 (17:71:0) MC27_STATUS[-|CE|MiscV|-|-|-|SyndV|-|-|-]: 0x9822080b + [ 628.157262] [Hardware Error]: IPID: 0x0001002e0500, Syndrome: 0x5a020001 + [ 628.157264] [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error. + [ 628.157265] [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout) + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: xuhui 2030 F pulseaudio - /dev/snd/controlC3: xuhui 2030 F
Re: [Bug 1901671] Re: Installing ubuntu crashes with input/output error while creating a user
I created the install media using rufus in DD mode (instead of ISO) and it worked. sun On Tue, Oct 27, 2020 at 10:10 PM Sunil S Kulkarni (सुनील सुरेश कुलकर्णी) < sunil...@gmail.com> wrote: > I have checked the ISO using the sha. But I still experience the error. > I am burning again with universal USB installer. I'll try with that and > I'll report again. > > sun > > On Tue, Oct 27, 2020 at 4:00 PM Chris Guiver <1901...@bugs.launchpad.net> > wrote: > >> I see a "CasperMD5CheckResult: pass" in your top details... yet the >> report still shows IO errors on your install media? >> >> If this was a VM, the problem is often a lack of memory allocated to the >> virtual machine. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1901671 >> >> Title: >> Installing ubuntu crashes with input/output error while creating a >> user >> >> Status in Ubuntu: >> Incomplete >> >> Bug description: >> Installing 20.04 LTS on a samsung pro SSD and on I5 10400. Hyper- >> threading and TPM are disabled. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.04 >> Package: ubiquity 20.04.15.2 >> ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 >> Uname: Linux 5.4.0-42-generic x86_64 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> ApportVersion: 2.20.11-0ubuntu27.4 >> Architecture: amd64 >> CasperMD5CheckResult: pass >> CasperVersion: 1.445.1 >> CurrentDesktop: ubuntu:GNOME >> Date: Tue Oct 27 15:25:23 2020 >> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz >> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- >> LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 >> (20200731) >> ProcEnviron: >>LANGUAGE=en_IN >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_IN >>LC_NUMERIC=C.UTF-8 >> SourcePackage: ubiquity >> UpgradeStatus: No upgrade log present (probably fresh install) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+bug/1901671/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901671 Title: Installing ubuntu crashes with input/output error while creating a user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1901671] Re: Installing ubuntu crashes with input/output error while creating a user
I have checked the ISO using the sha. But I still experience the error. I am burning again with universal USB installer. I'll try with that and I'll report again. sun On Tue, Oct 27, 2020 at 4:00 PM Chris Guiver <1901...@bugs.launchpad.net> wrote: > I see a "CasperMD5CheckResult: pass" in your top details... yet the > report still shows IO errors on your install media? > > If this was a VM, the problem is often a lack of memory allocated to the > virtual machine. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1901671 > > Title: > Installing ubuntu crashes with input/output error while creating a > user > > Status in Ubuntu: > Incomplete > > Bug description: > Installing 20.04 LTS on a samsung pro SSD and on I5 10400. Hyper- > threading and TPM are disabled. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubiquity 20.04.15.2 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > CasperMD5CheckResult: pass > CasperVersion: 1.445.1 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 27 15:25:23 2020 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- > LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > ProcEnviron: >LANGUAGE=en_IN >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >LC_NUMERIC=C.UTF-8 > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1901671/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901671 Title: Installing ubuntu crashes with input/output error while creating a user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901671] [NEW] Installing ubuntu crashes with input/output error while creating a user
Public bug reported: Installing 20.04 LTS on a samsung pro SSD and on I5 10400. Hyper- threading and TPM are disabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 15:25:23 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901671 Title: Installing ubuntu crashes with input/output error while creating a user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Thanks Robert for the quick confirmation, so I assume that the bionic, focal, and groovy images will be updated to include VMTools version info. We will let customer to retry once the new images are available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
To include VMTools version info to ova template, write 'ddb.toolsVersion=2147483647' to the VMDK file before create the template. VDDK SDK VixDiskLib_WriteMetadata API can be used to write "ddb.toolsVersion" metadata - https://code.vmware.com/docs/11750/virtual-disk-development-kit-programming-guide/GUID-C13FE900-6B19-4082-A040-354FB1F60BCB.html VDDK SDK: https://code.vmware.com/web/sdk/7.0/vddk Here is an example: https://github.com/vmware/photon/blob/master/support /image-builder/ovagenerator.py#L53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Verified no such issue on 20.04 cloud image (OVA). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893722] [NEW] ddclient FAILED: Could not get freedns update URLs from freedns.afraid.org
Public bug reported: The ddclient needs upgrade for Ubuntu 20.04 LTS, or at least put ddclient (3.9.1-5) into focal-backports. My /etc/ddclient.conf has been working for years, but recently it is broken: rm /var/cache/ddclient/ddclient.cache $ sudo ddclient -daemon=0 -force FAILED: Could not get freedns update URLs from freedns.afraid.org $ sudo ddclient -daemon=0 -force WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = '' FAILED: Could not get freedns update URLs from freedns.afraid.org $ apt-cache policy ddclient ddclient: Installed: 3.8.3-1.1ubuntu1 Candidate: 3.8.3-1.1ubuntu1 Version table: *** 3.8.3-1.1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal ** Affects: ddclient (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/1893722 Title: ddclient FAILED: Could not get freedns update URLs from freedns.afraid.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/1893722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892447] Re: Why ignore new name server if 3 name servers exists
emm...I see the new name servers are appended to the current name servers list. https://github.com/canonical/cloud- init/blob/master/cloudinit/distros/parsers/resolv_conf.py#L79 So the new name servers are always in the tail, if there are already 3 current name servers exist, then any new name servers will be discarded. In our scenario, new name servers sent to cloud-init by OVF datasource, but the result is inconsistent, depends on how many name servers exist before power-on. If change the implementation to append the current name servers to the new name servers, then the current name servers are in the tail, then keep the first 3 of the list. In such way, new name servers can be always set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892447 Title: Why ignore new name server if 3 name servers exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1892447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892447] [NEW] Why ignore new name server if 3 name servers exists
Public bug reported: Hi team, This might be a question which has been asked by someone else, but I did NOT find related bugs by searching. See https://github.com/canonical/cloud- init/blob/master/cloudinit/distros/parsers/resolv_conf.py#L83, new name server(s) will be ignored if 3 name servers already exists, I know the max number is 3 for name servers. But why not replace the existing name servers by new ones? Thanks, Pengpeng ** Affects: cloud-init (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/1892447 Title: Why ignore new name server if 3 name servers exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1892447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Hi team, Could you please share some info on this, when and how this issue is going to be fixed? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Hi team, Any updates on this, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Thanks Richard for the updates. As far as I know, Ubuntu 20.04 has been GAed at Apr.24, 2020. So the change is not included in GA version(please correct me if I'm wrong), could you please let us know when the change will probably be shipped to Ubuntu 20.04 Live server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Hi Dan, Paride, Any updates on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Sure, list the use case step by step as below: 1. Customer create a Ubuntu VM on vSphere 2. Customer attach Live Server installer ISO to VM's CD-ROM 3. Customer power-on the VM and go through installation wizard to install Ubuntu Live Server (subiquity works here) 4. Customer want to create more Ubuntu Live Server VMs, so he clone the step3 created VM and Customize the new VMs network (cloud-init works here, using OVF datasource) to have different IP addresses. 5. Since the subiquity-disable-cloudinit-networking.cfg exists, cloned VMs fail to configure Netplan network configuration by cloud-init. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
I mean the subiquity-disable-cloudinit-networking.cfg is deleted automatically, not by Customer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Thanks for the explanation. On VMware vSphere platform, Customer can install Ubuntu Live Server system through ISO image on a Virtual Machine, then the Live Server Ubuntu VM will contain subiquity-disable-cloudinit-networking.cfg. This leads to cloud-init can NOT manage network on this VM by default. If the Subiquity works one time, is it possible that subiquity-disable- cloudinit-networking.cfg is deleted after installation. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871975] Re: network configuration is disabled by default in cloud-init for ubuntu live server beta
Hi, When does subiquity write netplan configuration? At installation? Will it run again on an installed system? If no, can we remove subiquity- disable-cloudinit-networking.cfg after installation done? The problem is cloud-init can never write netplan configuration with subiquity-disable-cloudinit-networking.cfg exists. This prevents some user scenarios working which I'm sure they are working on Ubuntu 18.04: For ex: On VMware vSphere platform, an Ubuntu system network can be customized to different netplan configuration by cloud-init. I believe public clouds such as AWS and Azure are using cloud-init to configure network for new instance. Please share more information on how subiquity works with cloud-init, change the status back to New. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871975 Title: network configuration is disabled by default in cloud-init for ubuntu live server beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1871975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774944] Re: shc problems after server upgrade
latest version 4.0.3-0.1 is in Ubuntu now (https://launchpad.net/ubuntu/+source/shc), thus closing this old bug. Please reopen if problem persists. ** Changed in: shc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774944 Title: shc problems after server upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shc/+bug/1774944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@Balint, thanks a lot for the information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537056] Re: apt-add-repository always returns "user or team does not exist." for ppa repos
Hi,How did you finally solve this problem? i am in add sudo -E add-apt-repository ppa:mosquitto-dev/mosquitto-ppa exception message: Cannot add PPA: 'ppa:~mosquitto-dev/ubuntu/mosquitto-ppa'. ERROR: '~mosquitto-dev' user or team does not exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537056 Title: apt-add-repository always returns "user or team does not exist." for ppa repos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1537056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@Dan, could you please confirm if your fix will be patched on Ubuntu19.10? If yes, when it will happen? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
@Dan, The issue is resolved by your fix. Instead of only changing /etc/dhcp/dhclient-enter-hooks.d/resolved script, I added your repository "ppa:ddstreet/systemd" and updated/upgraded systemd, then the issue was NOT reproducing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
Thanks @Dan, I applied the patch https://launchpadlibrarian.net/448207988/resolved.patch to my VM, but the issue is still reproducing. The md5sum line is before creating "$statedir/isc-dhcp-v4-$interface.conf", while I can see the isc-dhcp-v4-$interface.conf file is created on my VM. I think the root cause is not same with bug 1849608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] Re: DNS info is not loaded by dhclient
Thanks Till, which systemd service's dependency got changed? I compared /lib/systemd/system/systemd-resolved.conf between 18.04 and 19.10, they are same. There is "After=systemd-sysusers.service systemd- networkd.service". I do NOT know when and who triggers /etc/dhcp/dhclient-enter- hooks.d/resolved script at boot, but it's possible that when this script executed, systemd-resolved.service is not ready for reload or restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850775] [NEW] DNS info is not loaded by dhclient
Public bug reported: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: cloud-init (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Thanks for the confirmation! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi Joshua, Thanks for your reply. Could you please confirm if all Ubuntu types uses Netplan from 19.10, I noticed from 17.10 to 19.04, Desktop type has ifupdown, Server and Live Server are using Netplan. Thanks, Pengpeng ** Changed in: network-manager (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Re-new this bug for requesting above confirmation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845745] Re: Cannot change login user for SDDM under Lubuntu 18.04
> This bug report will be marked for expiration in 59 days I'll wait for it to close itself then, if nobody else can confirm it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845745 Title: Cannot change login user for SDDM under Lubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1845745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845745] Re: Cannot change login user for SDDM
> Lubuntu didn't support sddm until 18.10 Ah, that might explains it. I'm using the Lubuntu 18.04 without much upgrade. I.e., my system being 18.04 and not fully updated might be the cause. ** Summary changed: - Cannot change login user for SDDM + Cannot change login user for SDDM under Lubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845745 Title: Cannot change login user for SDDM under Lubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1845745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845745] [NEW] Cannot change login user for SDDM
Public bug reported: I have more than one user set up but the login screen only shows the initial (original) user with SDDM. Using LightDM allows me to type in (thus change to) the other users, and they are able to login just fine. I.e., my SDDM login screen always stuck with the original user created when the system was first installed -- the left and right arrow that is supposed to change the login user doesn't work for me. This is LUbuntu 18.04.02. ** Affects: sddm (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/1845745 Title: Cannot change login user for SDDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1845745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi team, Please let us know if this is as-designed or not, Ubuntu desktop version was using /etc/network/interfaces to configure static IP address and etc... Best regards, Pengpeng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833192] Re: VMware: post custom script isn't run correctly
Verified VMware post customization script worked fine with cloud-init 19.2-24 on Ubuntu16.04.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833192 Title: VMware: post custom script isn't run correctly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1833192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
@Maher AlAsfar (malasfar) What's cloud-init version on the Ubuntu16.04? The version need be greater or equal to 18.2 to make customization work. What's open-vm-tools version on the Ubuntu16.04? If you customize Ubuntu with cloud-init, please do NOT add any "After=dbus.x" to open-vm-tools.service file, since it will create dependency cycle during booting. And If it's possible, I suggest use Ubuntu18.04, not Ubuntu16.04 to work with cloud-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834779] Re: equivs-build: fatal error occurred while parsing debian/changelog
Thanks for the comment. The input file is almost identical to that of the original package. I checked https://bugs.debian.org/219188, and found that it only talks about the warning of can't parse dependency, not this fatal error on debian/changelog. Moreover, the package has been created in that case, but not in this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834779 Title: equivs-build: fatal error occurred while parsing debian/changelog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1834779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834779] [NEW] equivs-build: fatal error occurred while parsing debian/changelog
Public bug reported: There is no debian/changelog file involved when using equivs-build, so would the "fatal error occurred while parsing debian/changelog" error be a bug? Here are the details: $ cat ttf-ubuntu-font-family Package: ttf-ubuntu-font-family Architecture: all Version: 91:0.83-2 Multi-Arch: foreign Priority: optional Section: universe/oldlibs Source: fonts-ubuntu (0.83-2) Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Fonts Task Force Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 40 Depends: fonts-ubuntu Homepage: https://design.ubuntu.com/font/ Description: sans-serif font set from Ubuntu (transitional package) (equ-dummy) Task: kubuntu-desktop, kubuntu-full, lubuntu-live-share, core-share, lubuntu-gtk-core, lubuntu-desktop-share, lubuntu-core, lubuntu-live, lubuntu-qt-core, lubuntu-live-qt, lubuntu-live-gtk $ equivs-build ttf-ubuntu-font-family dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_installchangelogs: warning: debian/changelog(l2): found end of file where expected first heading dh_installchangelogs: error: fatal error occurred while parsing debian/changelog debian/rules:20: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 255 Error in the build process: exit status 2 $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy equivs equivs: Installed: 2.1.0 Candidate: 2.1.0 Version table: *** 2.1.0 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: equivs (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/1834779 Title: equivs-build: fatal error occurred while parsing debian/changelog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1834779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834730] [NEW] Segmentation fault when using xz compression
Public bug reported: Just like reported (twice) at https://bugzilla.redhat.com/show_bug.cgi?id=1350122, dar will Segmentation fault when using the xz compression: $ /usr/bin/dar -zxz -R . -c /path/to/my-dar-full Segmentation fault Mainly because `xz` support is actually disabled from libdar at compile time; i.e. $ dar -V | fgrep xz Liblzma compression (xz) : NO $ apt-cache policy dar dar: Installed: 2.5.14+bis-1 Candidate: 2.5.14+bis-1 Version table: *** 2.5.14+bis-1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 ** Affects: dar (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/1834730 Title: Segmentation fault when using xz compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dar/+bug/1834730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834092] [NEW] Unable to install selected kernel package
Public bug reported: My simple Netboot install configuration file doesn't have any kernel specification, except a commented out line of: #d-i base-installer/kernel/image string linux-generic It worked all the way up to 18.04, but when I'm trying 19.04 just now, I'm getting: in-target: Setting up linux-header-5.0.0-13-generic (5.0.0-13.14) ... in-target: Setting up linux-header-generic (5.0.0-13.14) ... base-install error: exiting on error base-installer/kernel/failed-install I'm seeing some related bug reports, e.g., https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755 https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1820419/ But reading through them, I'm still not too sure what's the cause for mine and what's the fix. I'm not sure which package to report the error too, and I can't even find any normal linux kernel packages from https://packages.ubuntu.com/search?suite=disco=names=linux which only returns two Package linux-aws & linux-aws-cloud- tools-5.0.0-1004 as of writing. ** Affects: linux-base (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/1834092 Title: Unable to install selected kernel package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1834092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774944] Re: shc problems after server upgrade
There is a long story why shc hasn't been updated which I won't get into details. But I've waited long enough and finally decided that I should take up packing shc again. The newest version has just been packaged and uploaded to to mentors.debian.net. The URL is: https://mentors.debian.net/package/shc Due to Debian deep-freeze, there will be some time for it to get into Debian then eventually into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774944 Title: shc problems after server upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shc/+bug/1774944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Hi Christian, According to #15, please do NOT make "After=dbus.socket" as a part of open-vm-tools package. While we will update VMware KBs to change from "After=dbus.service" to "After=dbus.socket" for (B). A) For Set cloud-init as the customization engine: B) For Set perl script as the customization engine: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Yes, I just tried 'After=dbus.socket' on my Ubuntu18.10, it works. We need do some verifications and then update our KB if it works on the other Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Thanks for the suggestion! Actually we are working on using (A) only and by default. Before that happens, (B) needs be kept. Instead of splitting vmtoolsd/open-vm-tools services, we might fix this issue in scripts, make sure when 'hostnamectl' cmd executes, the dbus.service is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Thanks a lot for the info, Christian. Let me answer your questions firstly: - are your scripts triggered by cloud init NO. - if so in which config module/phase as I'm sure I have done cloud-init driven hostname changed? - OR are your scripts triggered by open-vm-tools directly? VMware Guest OS Customization works with either pure 'perl' scripts or cloud-init as the customization engine. For 'perl' scripts customization, scripts are triggered by open-vm-tools.service, the 'hostnamectl' is the cmd in scripts to set hostname. And 'hostnamectl' has dependency on 'dbus.service'. For 'cloud-init' customization, only 2 config files are copied to a folder by open-vm-tools.service, and then cloud-init-local.service read the config file from that folder to do the customization. This is the reason of "bug 1667831 to have open-vm-tools before cloud-init-local was by Sankar from VMWare". And AFAIK, cloud-init is not using 'hostnamectl' to set hostname for Ubuntu distro. so when do the 'cloud-init' customization on Ubuntu, there is no dependency on 'dbus.service'. And Yes, I also noticed the cycle dependency was introduced if add 'After=dbus.service' to 'open-vm-tools.service' when cloud-init*.services are also enabled.(https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/comments/8) So the 'after=dbus.service' should only be added when using perl scripts as customization engine. see details in the workaround KB for Ubuntu18.04 Live Server https://kb.vmware.com/s/article/54986 For Set cloud-init as the customization engine: no need add 'after=dbus.service' to open-vm-tools.service For Set perl script as the customization engine: need add 'after=dbus.service' to open-vm-tools.service and also disable or remove cloud-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766538] Re: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server
Hi Matti, With "disable_vmware_customization: false" entry added, its enabling Guest OS Customization with Cloud-Init. Was the bionic installed on a VMware VM and did Guest OS Customization? Thanks, Pengpeng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766538 Title: network customization with cloud-init does not work on Ubuntu18.04 Beta2 Server To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1766538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793715] Re: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD
Hi Joshua, Sorry for the late response. Yes, adding "After=dbus.service" to open-vm-tools.service file is the workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793715 Title: VMWare Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1793715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810681] [NEW] 90% done with install on machine with windows 10, other linux already installed, says unrecoverable error
Public bug reported: it talks about attaching files, but there's nothing on this page to do so ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity 18.10.12 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CurrentDesktop: KDE Date: Mon Jan 7 03:04:10 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic kubuntu ubiquity-18.10.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810681 Title: 90% done with install on machine with windows 10, other linux already installed, says unrecoverable error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1810681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
Hi Christian, Thanks for your checking and quick response, and you are right. I double-checked my Ubuntu16.04 VM, it was configured with a local source on open-vm-tools indeed. After remove the local source and re-install open-vm-tools, it's 10.2.0 and has the dependency. Thanks, Pengpeng -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803939 Title: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] [NEW] cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
Public bug reported: Hi there, Found on version 10.3.5, the cloud-init.service dependency is NOT in open-vm-tools.service. Want to check with you if it’s removed on purpose? and what’s the reason of removing it. The cloud-init.service dependency was adding “Before=cloud-init-local.service” under [Unit] section of open-vm-tools.service file. Thanks, Pengpeng ** Affects: open-vm-tools (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/1803939 Title: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
$vmtoolsd -v VMware Tools daemon, version 10.3.5.6873 (build-9998599) $cat /lib/systemd/system/open-vm-tools.service [Unit] Description=Service for virtual machines hosted on VMware Documentation=http://github.com/vmware/open-vm-tools ConditionVirtualization=vmware Requires=vgauth.service After=vgauth.service [Service] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803939 Title: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803939] Re: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service
change to open-vm-tools package ** Package changed: linux (Ubuntu) => open-vm-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803939 Title: cloud-init.service dependency is missing on 10.3.5 open-vm-tools service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1803939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796875] Re: cloud-init and cloud-init-local services boot sequence does not obey dependency settings
Confirmed on Ubuntu18.10 GA build, the 'var/lib/cloud/instance' is back to a symbolic link. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796875 Title: cloud-init and cloud-init-local services boot sequence does not obey dependency settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1796875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs