[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition
groovy has been released with 2.36 so I will mark this issue as fixed. ** Changed in: util-linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: util-linux-ng Importance: Unknown => Undecided ** Changed in: util-linux-ng Status: Unknown => New ** Changed in: util-linux-ng Remote watch: github.com/karelzak/util-linux/issues #824 => None ** Changed in: util-linux-ng Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition
At this moment, this issue is still present in focal. It would be nice if this can be fixed for an LTS release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition Status in Util-Linux-ng: Unknown Status in util-linux package in Ubuntu: Confirmed Bug description: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871176] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
I got this error after a few steps: * After upgrading from eoan to focal and rebooting, I was dropped into the initramfs shell. Exiting from the shell, I see the error message "/dev/mapper/ubuntu--vg-root does not exist". * After some searching online, I reboot using my previous kernel and reach the desktop. * I open Synaptic and see that lvm2 was removed. When I try to install it, I get the error in this issue. After some more searching online, I see https://askubuntu.com/questions/1049727/every-time-i-install-or- remove-a-package-i-get-lvm2-error/1085420 and try the suggested answer (purge lvm2 before reinstalling) - this worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858152] Re: fstrim.service no longer trims /home partition
Thanks Matt. Looks like the fix will be in the next upstream release (2.35). ** Also affects: util-linux-ng via https://github.com/karelzak/util-linux/issues/824 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition Status in Util-Linux-ng: Unknown Status in util-linux package in Ubuntu: Confirmed Bug description: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1858152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858152] [NEW] fstrim.service no longer trims /home partition
Public bug reported: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858152 Title: fstrim.service no longer trims /home partition Status in util-linux package in Ubuntu: New Bug description: When I was running disco, fstrim.service would trim all of my partitions: Oct 21 00:00:18 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 21 00:00:37 computer fstrim[9588]: /home: 25 GiB (26797150208 bytes) trimmed on /dev/mapper/ubuntu--vg-home Oct 21 00:00:37 computer fstrim[9588]: /boot: 805.4 MiB (844546048 bytes) trimmed on /dev/sda5 Oct 21 00:00:37 computer fstrim[9588]: /: 5.5 GiB (5929816064 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 21 00:00:37 computer systemd[1]: fstrim.service: Succeeded. Oct 21 00:00:37 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. After upgrading to eoan, my /home partition is no longer trimmed: Oct 28 00:00:21 computer systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab... Oct 28 00:00:32 computer fstrim[24667]: /boot: 781.1 MiB (819011584 bytes) trimmed on /dev/sda5 Oct 28 00:00:32 computer fstrim[24667]: /: 7.2 GiB (7696994304 bytes) trimmed on /dev/mapper/ubuntu--vg-root Oct 28 00:00:32 computer systemd[1]: fstrim.service: Succeeded. Oct 28 00:00:32 computer systemd[1]: Started Discard unused blocks on filesystems from /etc/fstab. Checking the unit file (/lib/systemd/system/fstrim.service), I noticed there is a "ProtectHome=yes" option. Removing this option caused my /home partition to be trimmed once again. I believe the "ProtectSystem=strict" option may also cause partitions in non-standard partition schemes to be skipped by fstrim.service (although I have not tested this). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615347] [NEW] Local DNS server not removed when connected to OpenVPN network, when connected by both Ethernet and Wi-Fi
Public bug reported: I'm using Ubuntu 16.04, connected to the same network by both Ethernet and Wi-Fi. When I query dnsmasq by running: dig +short chaos txt servers.bind I see only one set of DNS servers (one IPv4, one IPv6); not sure if it's NetworkManager or dnsmasq that is de-duping the servers from both connections. When I connect to an OpenVPN connection (configured through NM, IPv4-only, with no split-tunnelling) and query dnsmasq again, I see that the VPN DNS server is present, but the local IPv4 DNS server is also still used (dnsmasq reports two IPv4 servers, one IPv6 server). (I filed bug #1615343 regarding the local IPv6 DNS server not being removed.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1615347 Title: Local DNS server not removed when connected to OpenVPN network, when connected by both Ethernet and Wi-Fi Status in network-manager package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, connected to the same network by both Ethernet and Wi-Fi. When I query dnsmasq by running: dig +short chaos txt servers.bind I see only one set of DNS servers (one IPv4, one IPv6); not sure if it's NetworkManager or dnsmasq that is de-duping the servers from both connections. When I connect to an OpenVPN connection (configured through NM, IPv4-only, with no split-tunnelling) and query dnsmasq again, I see that the VPN DNS server is present, but the local IPv4 DNS server is also still used (dnsmasq reports two IPv4 servers, one IPv6 server). (I filed bug #1615343 regarding the local IPv6 DNS server not being removed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615343] [NEW] IPv6 DNS server not removed when connected to IPv4-only OpenVPN VPN
Public bug reported: I'm using Ubuntu 16.04 on a network where the DNS server is available on both IPv4 and IPv6 (managed by a router running OpenWrt). As mentioned in the dnsmasq manpage, I can see dnsmasq has both IPv4 and IPv6 entries by running: dig +short chaos txt servers.bind I also have an IPv4-only OpenVPN connection configured through NetworkManager (the VPN itself is IPv4-only, the NM connection is set to Automatic for both IPv4 and IPv6), with no split-tunnelling. When I connect to the VPN and query dnsmasq again, I see that the IPv4 entry has been replaced by the VPN IPv4 DNS server, but the (local network) IPv6 entry is still present. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1615343 Title: IPv6 DNS server not removed when connected to IPv4-only OpenVPN VPN Status in network-manager package in Ubuntu: New Bug description: I'm using Ubuntu 16.04 on a network where the DNS server is available on both IPv4 and IPv6 (managed by a router running OpenWrt). As mentioned in the dnsmasq manpage, I can see dnsmasq has both IPv4 and IPv6 entries by running: dig +short chaos txt servers.bind I also have an IPv4-only OpenVPN connection configured through NetworkManager (the VPN itself is IPv4-only, the NM connection is set to Automatic for both IPv4 and IPv6), with no split-tunnelling. When I connect to the VPN and query dnsmasq again, I see that the IPv4 entry has been replaced by the VPN IPv4 DNS server, but the (local network) IPv6 entry is still present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
