[Touch-packages] [Bug 2064096] Re: rsyslog service timeout on noble numbat
Here's how to reproduce this in a LXD VM: Download Ubuntu 24.04 Desktop image into ~/Downloads Import the ISO $ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso 24.04-desktop --type=iso Prepare a LXD VM $ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c limits.cpu=4 -d root,size=32GiB $ lxc config device add lxd-noble-fde iso-volume disk pool=default source=24.04-desktop boot.priority=10 $ lxc config device add lxd-noble-fde tpm tpm $ lxc start --console=vga lxd-noble-fde Go through the manual install process but at the "Disk Setup" step, select "Erase disk and install Ubuntu" and click "Advanced features...". Select "Enable hardware-backed full disk encryption" then click "OK" Once the installation is done, force the LXD VM to stop $ lxc stop --force lxd-noble-fde Remove the ISO $ lxc config device remove lxd-noble-fde iso-volume Start the VM back $ lxc start lxd-noble-fde Once logged in, rsyslog should eventually fail to start and the same Apparmor denials should show up in `journalctl -k`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: rsyslog service timeout on noble numbat Status in rsyslog package in Ubuntu: Confirmed Bug description: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+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 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so
*** This bug is a duplicate of bug 2060676 *** https://bugs.launchpad.net/bugs/2060676 ** This bug has been marked a duplicate of bug 2060676 login: remove pam_lastlog.so from config -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2063257 Title: Noble: default pam config for login tries do load non-existent pam_lastlog.so Status in shadow package in Ubuntu: New Status in shadow source package in Noble: New Status in shadow package in Debian: New Bug description: pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there in the code, but not built by default. And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does. This does not prevent console logins, but generates an error in the logs: Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so Debian's shadow package is also still shipping this config[2]. If you think we should re-enable pam_lastlog, then this becomes a bug in the src:pam package, but keep in mind upstream is keen on removing it, and we might be better off switching to an alternative, perhaps pam_lastlog2[3]. 1. https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65 2. https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82 3. https://wiki.debian.org/PamLastlog2 4. https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063257/+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 2057927] Re: lxd vga console throws "Operation not permitted" error
I just tested 5.21/stable and couldn't reproduce as it properly disable the /proc/sys/kernel/apparmor_restrict_unprivileged_userns and /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined that would otherwise have caused those denials. Marking as incomplete until you can reproduce with 5.21/stable (5.20 being EOL). Thanks ** Changed in: lxd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2057927 Title: lxd vga console throws "Operation not permitted" error Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Incomplete Bug description: Since I upgraded to Noble the lxd vga console doesn't work anymore. I am using the lxd latest/stable snap (5.20-f3dd836). When trying to attach a vga console to an lxd vm I get: unshare: write failed /proc/self/uid_map: Operation not permitted It seems to be related to apparmor, I can see a matching DENIAL message in dmesg: [ 4735.233989] audit: type=1400 audit(1710419600.517:300): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=13157 comm="unshare" capability=21 capname="sys_admin" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2060965] Re: liblxc is missing in 24.04
Thanks for the follow-up! ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2060965 Title: liblxc is missing in 24.04 Status in lxc package in Ubuntu: Fix Released Bug description: For about a week liblxc is missing in 24.04 # apt search liblxc Sorting... Done Full Text Search... Done golang-gopkg-lxc-go-lxc.v2-dev/noble,noble 0.0+git20230621.be98af2-1 all Go bindings for liblxc lxc-dev/noble 1:5.0.1-0ubuntu8 all Transitional package - lxc-dev -> liblxc-dev # apt install lxc-dev The following packages have unmet dependencies: lxc-dev : Depends: liblxc-dev (>= 1:5.0.1-0ubuntu8) but it is not installable # apt-cache policy liblxc-dev liblxc-dev: Installed: (none) Candidate: (none) Version table: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2060965/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
@enr0n, yes, I did restart systemd-networkd after creating /etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf. If you want to reproduce, the steps outlined in the bug descriptions should provide you with a simple reproducer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
@enr0n, the proposal to add: bridges: br0: interfaces: [vlan1] To the network config defeats the purpose. The goal is to not have to do double configuration. The bridge is define in LXD, the vlan1 only in netplan. The other proposed fix of `KeepMaster=true` snippet in /etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf didn't work for me. I also tried putting it in 99-netplan-vlan1.network.d to match the name of my netplan .yaml but still didn't work. root@networkd-bug:~# cat /etc/netplan/99-vlan1.yaml network: version: 2 vlans: vlan1: id: 1 link: eth0 root@networkd-bug:~# cat /etc/systemd/network/99-netplan-vlan1.network.d/keep_master.conf [Network] KeepMaster=true root@networkd-bug:~# grep -n . /run/systemd/network/*vlan1* /run/systemd/network/10-netplan-vlan1.netdev:1:[NetDev] /run/systemd/network/10-netplan-vlan1.netdev:2:Name=vlan1 /run/systemd/network/10-netplan-vlan1.netdev:3:Kind=vlan /run/systemd/network/10-netplan-vlan1.netdev:5:[VLAN] /run/systemd/network/10-netplan-vlan1.netdev:6:Id=1 /run/systemd/network/10-netplan-vlan1.network:1:[Match] /run/systemd/network/10-netplan-vlan1.network:2:Name=vlan1 /run/systemd/network/10-netplan-vlan1.network:4:[Network] /run/systemd/network/10-netplan-vlan1.network:5:LinkLocalAddressing=ipv6 /run/systemd/network/10-netplan-vlan1.network:6:ConfigureWithoutCarrier=yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500
[Touch-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed
FYI, snapd is a "base-less" snap: $ lxc launch ubuntu-minimal-daily:22.04 c1 $ lxc shell c1 root@c1:~# snap list No snaps are installed yet. Try 'snap install hello-world'. root@c1:~# snap install snapd 2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart... snapd 2.61.1 from Canonical✓ installed root@c1:~# snap list Name Version RevTracking Publisher Notes snapd 2.61.1 20671 latest/stable canonical✓ snapd This is also visible by not having any `base:` while LXD currently uses core22: root@c1:~# snap info --verbose snapd | grep base: root@c1:~# snap info --verbose lxd | grep base: base:core22 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This was verified on Mantic with -proposed (1:5.0.1-0ubuntu8~23.10.1). Here's how: $ lxc launch ubuntu-daily:23.10 c2 Creating c2 Starting c2 $ lxc shell c2 root@c2:~# apt-get update ... root@c2:~# apt-get install -Vy liblxc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: ... liblxc-common (1:5.0.1-0ubuntu7) liblxc1 (1:5.0.1-0ubuntu7) ... lxcfs (5.0.3-1) .. root@c2:~# dpkg -l | grep liblxc-dev ii liblxc-dev 1:5.0.1-0ubuntu7 amd64Linux Containers userspace tools (development) root@c2:~# grep LXC_DEVEL /usr/include/lxc/version.h #define LXC_DEVEL 1 # enable -proposed root@c2:~# apt-get update ... root@c2:~# apt-get install -t mantic-proposed -Vy liblxc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: liblxc-common (1:5.0.1-0ubuntu8~23.10.1) liblxc1 (1:5.0.1-0ubuntu8~23.10.1) The following packages will be upgraded: liblxc-common (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1) liblxc-dev (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1) liblxc1 (1:5.0.1-0ubuntu7 => 1:5.0.1-0ubuntu8~23.10.1) 3 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Need to get 1804 kB of archives. ... root@c2:~# grep LXC_DEVEL /usr/include/lxc/version.h #define LXC_DEVEL 0 ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Committed Status in lxc source package in Mantic: Fix Committed Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
This was verified on Jammy with -proposed (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1). Here's how: $ lxc launch ubuntu-daily:22.04 c1 Creating c1 Starting c1 root@c1:~# apt-get update ... root@c1:~# apt-get install -Vy liblxc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libfuse2 (2.9.9-5ubuntu3) liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) lxcfs (5.0.0-0ubuntu2) uidmap (1:4.8.1-2ubuntu2.1) The following NEW packages will be installed: libfuse2 (2.9.9-5ubuntu3) liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) liblxc-dev (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1) lxcfs (5.0.0-0ubuntu2) uidmap (1:4.8.1-2ubuntu2.1) 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 1462 kB of archives. ... root@c1:~# dpkg -l | grep liblxc-dev ii liblxc-dev 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 amd64Linux Containers userspace tools (development) root@c1:~# grep LXC_DEVEL /usr/include/lxc/version.h #define LXC_DEVEL 1 # enable -proposed root@c1:~# apt-get update ... root@c1:~# apt-get install -Vy liblxc-dev ... The following packages will be upgraded: liblxc-common (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1) liblxc-dev (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1) liblxc1 (1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 => 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1) 3 upgraded, 0 newly installed, 0 to remove and 32 not upgraded. Need to get 1268 kB of archives. ... root@c1:~# grep LXC_DEVEL /usr/include/lxc/version.h #define LXC_DEVEL 0 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Fix Committed Status in lxc source package in Mantic: Fix Committed Status in lxc source package in Noble: Fix Released Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2051572] Re: Always preseed core and snapd snap in server seed
** Description changed: In removing the LXD snap from preseeding in the server seed for Ubuntu - 24.04 as part LP #2051346 [1] we also removed the snaps snap and the + 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. - - Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded + Time taken to install LXD snap using the lxd-installer package without + snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` - - Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. + Time taken to install LXD snap using the lxd-installer package with + snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce core22 and snaps snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 - [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 ** Description changed: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re-introduce - core22 and snaps snaps to our seed. + core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1]
[Touch-packages] [Bug 2047939] Re: Let tzdata not recommend tzdata-icu
@bdrung, I just noticed this package is now in universe in Noble. Is the demotion related to this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047939 Title: Let tzdata not recommend tzdata-icu Status in tzdata package in Ubuntu: Fix Released Bug description: tzdata-icu was split out of tzdata in 2022g-7ubuntu1 in lunar. Stop letting tzdata recommend tzdata-icu. All packages that need the files in /usr/share/zoneinfo-icu should directly depend on tzdata-icu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047939/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
Using a fast HTTPS server (same LAN as client), the `main.py` tests goes from ~8s to ~2.5s: # time python3 /tmp/main.py Distro: Ubuntu 22.04.3 LTS Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022 0 1 2 3 ... 99 real0m8.163s user0m16.041s sys 0m3.474s # apt-get install -t jammy-proposed libssl3 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: libssl3 1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded. Need to get 1,902 kB of archives. After this operation, 1,024 B of additional disk space will be used. # time python3 /tmp/main.py Distro: Ubuntu 22.04.3 LTS Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022 0 1 2 3 ... 99 real0m2.533s user0m9.188s sys 0m0.096s Upgrading the server side (NGINX) didn't make a measurable difference. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: Fix Committed Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) The SRU information has been added to the three bug reports and I am attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git-ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture-dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a
[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
In fact, the same but updated note was already on https://documentation.ubuntu.com/lxd/en/latest/installing/#install-lxd- from-source where it mentions that it affects 22.04 onward while the one you dug up says 23.04/23.10 are not affected ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Jammy: Confirmed Status in lxc source package in Mantic: Confirmed Status in lxc source package in Noble: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
** Summary changed: - liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic + liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases Status in lxc package in Ubuntu: Confirmed Bug description: [ Impact ] LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. [ Test Plan ] Install liblxc-dev package and check /usr/include/lxc/version.h file LXC_DEVEL should be 0 [ Where problems could occur ] Theoretically, build of a software which depends on liblxc-dev may start to fail if it assumes that LXC_DEVEL is 1. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
https://git.launchpad.net/ubuntu/+source/lxc/tree/debian/patches/0003-meson- Set-DEVEL-flag-post-release.patch is the patch that should be dropped by the SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2039873 Title: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic Status in lxc package in Ubuntu: New Bug description: Dear colleagues, As I can see from: - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/jammy - https://git.launchpad.net/ubuntu/+source/lxc/tree/configure?h=applied/ubuntu/kinetic LXC 5.0.0 was built with LXC_DEVEL=1 set. But for release build we should have LXC_DEVEL=0. LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h and then can be (and actually it is) used by other projects to detect if liblxc-dev is a development build or stable. Having LXC_DEVEL=1 makes problems for the users who want to build projects those are depend on liblxc from source (for example, LXD, go-lxc: https://github.com/canonical/lxd/pull/12420). Q: Why it was not a problem for so long? A: Because LXC API was stable for a long time, but recently we have extended liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc was updated too (https://github.com/lxc/go-lxc/pull/166). This change was developed properly to be backward compatible with the old versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro check VERSION_AT_LEAST (https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7) is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release build of LXC. And also, as I can see the source code that was used to build LXC 5.0.0 in Jammy/Kinetic is not precisely the same as in the official LXC 5.0.0 tag (https://github.com/lxc/lxc/tree/lxc-5.0.0). I understand that Jammy is a LTS release and making any changes is a problem and we should go through the SRU process. But I believe that we have to do something at least with LXC_DEVEL to make things work properly. Kind regards, Alex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2036127] [NEW] Restarting `systemd-networkd` looses unmanaged bridged parents
Public bug reported: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd-networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: New Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug
[Touch-packages] [Bug 1914839] Re: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically
This was fixed in ca-certificates version 20211016 which is what Jammy released with. As of today, all Ubuntu releases from Bionic onward ship 20230311 so marking as fix released. ** Changed in: ca-certificates (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914839 Title: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically Status in ca-certificates package in Ubuntu: Fix Released Status in ca-certificates package in Debian: Fix Released Bug description: While upgrading the ca-certificates package, a process got the error: SSL_ca_file /etc/ssl/certs/ca-certificates.crt does not exist This file should be replaced atomically, with no time gap where the file does not exist. (I am flagging this as a security vulnerability because, while I did not experience any security issue, I can imagine at least the possibility of this being exploitable in some way in some circumstances.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914839/+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 484786] Re: Better support for btrfs snapshots
Nowadays, btrfs snapshots can only be taken by the owner of the source subvol. https://btrfs.readthedocs.io/en/latest/ch-mount- options.html#btrfs-specific-mount-options: > Historically, any user could create a snapshot even if he was not owner of the source subvolume, the subvolume deletion has been restricted for that reason. The subvolume creation has been restricted ... I just tested this in a Jammy VM (FYI btrfsctl was replaced by `btrfs subvolume snapshot`): ``` ubuntu@bj:~$ uname -a Linux bj 5.15.0-75-generic #82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@bj:~$ dpkg -l| grep btrfs ii btrfs-progs 5.16.2-1 amd64Checksumming Copy on Write Filesystem utilities ubuntu@bj:~$ mount | grep btrfs /dev/sda3 on /home type btrfs (rw,noatime,space_cache=v2,subvolid=5,subvol=/) # Trying while /home is root owned ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo Create a snapshot of '/home' in './homefoo' ERROR: cannot snapshot '/home': Operation not permitted # Changing ownership of the source subvol ubuntu@bj:~$ sudo chown ubuntu: /home # Trying now that /home is owned by ubuntu: ubuntu@bj:~$ btrfs subvolume snapshot /home ./homefoo Create a snapshot of '/home' in './homefoo' ``` So I don't think it's a concern anymore but I won't fiddle with the bug status and leave that to others ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/484786 Title: Better support for btrfs snapshots Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: Binary package hint: apparmor I just realized that the btrfs snapshotting ioctl is usable by all users, not root as I previously assumed. This makes it concerningly easy for users on btrfs to defeat a path-based MAC framework like AppArmor. For example, consider the gdm-guest-session user. If I log into a gdm-guest-session on btrfs: (1) ls /home ==> Permission denied as expected, by AppArmor. (2) cd /tmp (3) btrfsctl -s test / (Make a snapshot of / in /tmp called test) (4) cd /tmp/test (5) Profit! Apparmor-unrestricted mirror of / in /tmp/test! As btrfs inevitably will become a mainstream filesystem, it's a good time to begin thinking about how to handle this situation. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/484786/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created
@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.
That same commit also seem to have a bogus error handling if `nm-online
-qs` fails:
```
nm-online -qs || (echo "SKIP: NetworkManager is not ready ..." 1>&2 && continue)
```
The `continue` will be run in the `()` subshell. I think this could be
fixed by using `{}` instead.
--
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/2010561
Title:
The Netplan Everywhere NetworkManager fails to supply Netplan with
networking information until a connection is deleted and re-created
Status in netplan:
Invalid
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce:
1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a
WiFi adapter. (I used Lubuntu Lunar.)
2. Connect to WiFi and install all updates.
3. Enable the Netplan Everywhere PPA and install the updated NetworkManager
from it (further details at
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
4. When the installation finishes, run "sudo netplan get".
Expected result: Networking information related to the WiFi connection
should appear in the "sudo netplan get" output.
Actual result: "sudo netplan get" returns the following:
** (process:4088): WARNING **: 12:41:41.394; Permissions for
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration
should NOT be accessible by others.
network:
version: 2
renderer: NetworkManager
End of output. Additionally, the /etc/netplan folder does not contain
files that I would expect to be there that would contain the
networking info.
Additional information:
If I disconnect from WiFi, then delete my WiFi connection entirely in
nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
get" returns the expected networking information. /etc/netplan is also
properly populated after doing this.
This bug seems like it will probably cause unintended behavior after
an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
(which is supposed to be using the Netplan Everywhere NetworkManager).
People probably won't know to entirely delete the WiFi and other
connections and then reconnect them in order for the netplan output to
be usable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+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 2009738] Re: no lxc manpage
Did I mentioned it was not convenient? :P $ d="$(mktemp -d)" $ lxc manpage "$d" $ ls -1 "$d" lxc.1 lxc.alias.1 lxc.alias.add.1 lxc.alias.list.1 lxc.alias.remove.1 lxc.alias.rename.1 lxc.cluster.1 lxc.cluster.add.1 ... $ ls -1 "$d" | wc -l 293 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2009738 Title: no lxc manpage Status in lxc package in Ubuntu: New Bug description: Hello, I don't have an lxc manpage on my focal system: $ man lxc No manual entry for lxc $ dpkg -l lxd | grep lxd ; snap info lxd | grep installed un lxd (no description available) installed: 5.11-ad0b61e (24483) 149MB - It looks a bit like none are packaged: $ find /snap/lxd -name '*.1.gz' -o -name '*.7.gz' -o -name '*.8.gz' $ While I appreciate the online --help output, I also like having longer-form documentation available on a system without needing to use a web browser. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc (not installed) ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 Uname: Linux 5.4.0-139-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 8 18:21:08 2023 SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-01-24 (1138 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2009738/+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 2009738] Re: no lxc manpage
I've been told that snaps can't ship man pages unfortunately: https://forum.snapcraft.io/t/support-for-man-pages/2299/24 https://bugs.launchpad.net/snapd/+bug/1575593 You can get something with `lxc manpage` which is basically the builtin --help formatted for man. However, that's not easy/convenient to access and looks weirder than the builtin --help stuff. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2009738 Title: no lxc manpage Status in lxc package in Ubuntu: New Bug description: Hello, I don't have an lxc manpage on my focal system: $ man lxc No manual entry for lxc $ dpkg -l lxd | grep lxd ; snap info lxd | grep installed un lxd (no description available) installed: 5.11-ad0b61e (24483) 149MB - It looks a bit like none are packaged: $ find /snap/lxd -name '*.1.gz' -o -name '*.7.gz' -o -name '*.8.gz' $ While I appreciate the online --help output, I also like having longer-form documentation available on a system without needing to use a web browser. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc (not installed) ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 Uname: Linux 5.4.0-139-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 8 18:21:08 2023 SourcePackage: lxc UpgradeStatus: Upgraded to focal on 2020-01-24 (1138 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2009738/+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 1404635] Re: rsync: recv_generator: mkdir error with folder ending with space
Interesting! If your recollection is accurate then I unfortunately don't see how rsync could workaround that FAT32 limitation :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1404635 Title: rsync: recv_generator: mkdir error with folder ending with space Status in rsync package in Ubuntu: Fix Released Bug description: Hi, I notice what rsync is not able to copy folder which ending with space : Example which not working : rsync: recv_generator: mkdir "/var/Janji feat. T.R. " failed: Invalid argument (22) *** Skipping any contents from this failed directory *** If I remove space at the end, it works. mkdir can create folder with space at the end. rsync version 3.1.0 protocol version 31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1404635/+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 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors
Jammy's rsync (3.2.7) has --trust-sender that's described as: "trust the remote sender's file list" However that won't be of much help as that's not available in older releases :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009575 Title: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors Status in rsync package in Ubuntu: Confirmed Bug description: Hi Several systems running Ubuntu 20.04 upgraded their rsync package from 3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight. Automated syncs that connect to a 16.04 ESM server are now failing with: receiving file list ... ERROR: rejecting unrequested file-list name: [redacted] rsync error: protocol incompatibility (code 2) at flist.c(916) [Receiver=3.1.3] Reverting to the previous release (3.1.3-8ubuntu0.4) on the client side solves the problem. This has been seen on multiple servers running 20.04 on amd64, I'll update this bug with details if we find it on other series too. The 16.04 ESM server being connected to is using the rsync package version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+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 806880] Re: make_bak_dir mkdir failed: File exists (17)
The rsync versions mentioned in the bug are very old and the distro version they came with, long out of support. As such, I'll mark the issue as incomplete until this can be reproduced/confirmed with a recent/supported version. Thanks! ** Changed in: rsync (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/806880 Title: make_bak_dir mkdir failed: File exists (17) Status in rsync package in Ubuntu: Incomplete Bug description: I have an rsync-based backup routine. Today I had the following error: $ rsync -F -h -av --backup --delete --delete-excluded --force --backup-dir=/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33 --exclude=*.o --exclude=*~ --exclude=#* /media/hp320/Skannat /media/2TBBackup/backup/media/hp320 sending incremental file list Skannat/neg004c/im4114-2.tif.xmp Skannat/neg004c/im4115-2.tif.xmp Skannat/neg004c/im4116-2.tif.xmp Skannat/neg004c/im4123-2.tif.xmp Skannat/neg005c/im4044-2.tif.xmp [...] Skannat/neg023/2003bfl-0169-imh235.tif.xmp rsync: make_bak_dir mkdir "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33" failed: File exists (17) rsync: keep_backup failed: "/media/2TBBackup/backup/media/hp320/Skannat/neg004c/im4114-2.tif.xmp" -> "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp": No such file or directory (2) rsync: stat "/media/2TBBackup/backup/.versions/media/hp320/Skannat#2011-07-07#11:21:33/Skannat/neg004c/im4114-2.tif.xmp" failed: No such file or directory (2) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: rsync 3.0.7-2ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic x86_64 Architecture: amd64 Date: Thu Jul 7 11:26:57 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928.1) SourcePackage: rsync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/806880/+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 1404635] Re: rsync: recv_generator: mkdir error with folder ending with space
I'll mark this old bug as fix released because I can't reproduce it on 20.04 (3.1.3) nor 22.04 (rsync 3.2.7). Here's how I tested it on 20.04: # rsync --version rsync version 3.1.3 protocol version 31 ... # mkdir -p "src/a " dst # rsync -aiv src/ dst/ sending incremental file list .d..t.. ./ cd+ a / sent 73 bytes received 23 bytes 192.00 bytes/sec total size is 0 speedup is 0.00 # ls -l dst/ total 1 drwxr-xr-x 2 root root 2 Mar 8 00:30 'a ' ** Changed in: rsync (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1404635 Title: rsync: recv_generator: mkdir error with folder ending with space Status in rsync package in Ubuntu: Fix Released Bug description: Hi, I notice what rsync is not able to copy folder which ending with space : Example which not working : rsync: recv_generator: mkdir "/var/Janji feat. T.R. " failed: Invalid argument (22) *** Skipping any contents from this failed directory *** If I remove space at the end, it works. mkdir can create folder with space at the end. rsync version 3.1.0 protocol version 31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1404635/+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 2007837] Re: Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix available in 3.2.4
I /think/ there is work being done by security to land a MRE for rsync, you might want to sync with @mdeslaur. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2007837 Title: Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix available in 3.2.4 Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Status in rsync package in Debian: Unknown Bug description: rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling, leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04) to surface [1]. It practically makes using BackupPC 3 impossible with clients using rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04 can't be used to back up machines with 22.04 is rather surprising and has bitten other users [2]. It's unclear whether the bug will be fixed in 18.04's and 20.04's libfile-rsyncp-perl package (for status, see [3]). Because of this, the rsync maintainer has included a patch in 3.2.4 that fixes this regression [4] (even though not strictly an rsync bug). As a result, rsync 3.2.3 is the only affected version, which happens to be the one packaged in 22.04. This report is to request backporting that fix [4] to Ubuntu 22.04, so that things don't silently break in scenarios where the backup server is left at 20.04, and some backup clients happen to upgrade to 22.04. I'm not sure what the criteria for security releases are, but as the issue causes backup denial of service and has easy mitigation, I think it would make sense to put it through the security channel. [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358 [2]: https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html [3]: https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833 [4]: https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
@georgiag, the behaviour changes when you tell tcpdump to do line buffering (`-l`). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in tcpdump package in Ubuntu: Confirmed Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+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 869881] Re: rsyslogd fails to load lmnsd_gtls.so
Yeah, I figured it was likely the outcome when I replied to a bug that was last touched 10 years ago ;) The bug will close itself in ~60 days if nothing happen so I think that's OK. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/869881 Title: rsyslogd fails to load lmnsd_gtls.so Status in rsyslog package in Ubuntu: Incomplete Bug description: rsyslog fails to load tls functionality. Relevant section from rsyslog.conf: (full file is attached, contents of /etc/rsyslog.d is unmodified from package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` does not show any configuration errors. The remote logging section is copy-pasted from a working debian 6 box) REMOTE LOGGING # certificate files $DefaultNetstreamDriverCAFile /root/ssl/ca.pem $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem # set up the action $DefaultNetstreamDriver gtls # use gtls netstream driver $ActionSendStreamDriverMode 1 # require TLS for the connection $ActionSendStreamDriverAuthMode x509/certvalid *.* @@(o)10.181.60.127:10514 # send (all) messages Error written to syslog: Oct 7 09:59:01 alpha rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 Relevant info from running in debug mode (full debug output is attached): 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in nsd_gtls.c:574: Error while reading file. I have also attached strace output from rsyslog. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 Uname: Linux 2.6.35.4-rscloud x86_64 Architecture: amd64 Date: Fri Oct 7 09:38:03 2011 ProcEnviron: SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+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 869881] Re: rsyslogd fails to load lmnsd_gtls.so
I tested a rsyslog client talking to a rsyslog server both using `rsyslog-gnutls 8.2112.0-2ubuntu2.2` on Ubuntu 22.04 and it worked fine. There, there is no error loading "/usr/lib/x86_64-linux- gnu/rsyslog/lmnsd_gtls.so" as long as the `-gnutls` package is installed. I used only a cert (from Let's Encrypt) on the server side but I enabled Apparmor on both sides. I'm not sure if your error could have been due to having enabled the Apparmor profile and using certificate files stored under `/root/ssl` which isn't permitted by the Apparmor profile? Marking as incomplete until you can report on the Apparmor profile situation. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/869881 Title: rsyslogd fails to load lmnsd_gtls.so Status in rsyslog package in Ubuntu: Incomplete Bug description: rsyslog fails to load tls functionality. Relevant section from rsyslog.conf: (full file is attached, contents of /etc/rsyslog.d is unmodified from package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` does not show any configuration errors. The remote logging section is copy-pasted from a working debian 6 box) REMOTE LOGGING # certificate files $DefaultNetstreamDriverCAFile /root/ssl/ca.pem $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem # set up the action $DefaultNetstreamDriver gtls # use gtls netstream driver $ActionSendStreamDriverMode 1 # require TLS for the connection $ActionSendStreamDriverAuthMode x509/certvalid *.* @@(o)10.181.60.127:10514 # send (all) messages Error written to syslog: Oct 7 09:59:01 alpha rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 Relevant info from running in debug mode (full debug output is attached): 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in nsd_gtls.c:574: Error while reading file. I have also attached strace output from rsyslog. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 Uname: Linux 2.6.35.4-rscloud x86_64 Architecture: amd64 Date: Fri Oct 7 09:38:03 2011 ProcEnviron: SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
@paride, I know it's a low priority item but I was wondering what's next to do for the SRU? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
Thanks Paride for the feedback, here's a refreshed debdiff! ** Patch removed: "rsync_3.2.3-8ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff ** Patch added: "rsync_3.2.3-8ubuntu3.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623978/+files/rsync_3.2.3-8ubuntu3.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer" would be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is newer total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 61 bytes received 96 bytes 314.00 bytes/sec total size is 0 speedup is 0.00 ``` If the updated package is installed (from -proposed), "foo is uptodate" should be reported: ``` sending incremental file list delta-transmission disabled for local transfer or --whole-file foo is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 60 bytes received 106 bytes 332.00 bytes/sec total size is 0 speedup is 0.00 ``` [Regression potential] The patch changes the behavior of --update so if something goes wrong, it could break backup/sync jobs. To mitiate that, manual testing of rsync with and without the --update option was done in addition to the quick [Test Plan] outlined above. Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream in September 2021. It also is in Kinetic where no visible regression was observed. [Original description] rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
I packaged the upstream fix (minus the changes to NEWS.md) and created the debdiff attached. ** Description changed: + [Impact] + + This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" + implying they would need to be transfered/sync'ed where in fact they are "uptodate". + + This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed + when in fact, they don't need to be. + + [Test Plan] + + Steps to reproduce: + + 1. Create a local file: + $ touch foo + + 2. Check if rsync would transfer it using the --update option: + $ rsync -avv --update foo . + + + If the regression is present, "foo is newer" would be reported: + + ``` + sending incremental file list + delta-transmission disabled for local transfer or --whole-file + foo is newer + total: matches=0 hash_hits=0 false_alarms=0 data=0 + + sent 61 bytes received 96 bytes 314.00 bytes/sec + total size is 0 speedup is 0.00 + ``` + + If the updated package is installed (from -proposed), "foo is uptodate" + should be reported: + + ``` + sending incremental file list + delta-transmission disabled for local transfer or --whole-file + foo is uptodate + total: matches=0 hash_hits=0 false_alarms=0 data=0 + + sent 60 bytes received 106 bytes 332.00 bytes/sec + total size is 0 speedup is 0.00 + ``` + + [Regression potential] + + The patch changes the behavior of --update so if something goes wrong, it could break backup/sync + jobs. To mitiate that, manual testing of rsync with and without the --update option was done + in addition to the quick [Test Plan] outlined above. + + Please note the patch restores the behavior from before version 3.2.3 and has been integrated by upstream + in September 2021. It also is in Kinetic where no visible regression was observed. + + + [Original description] + rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. The bug was fixed upstream in June 2020: https://github.com/WayneD/rsync/issues/98 $ touch foo $ rsync --update --info=skip foo foo foo is newer<=== THIS IS NOT CORRECT - A file can't be newer than itself. Obviously a file should not be listed as newer than itself. Another way: $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Patch added: "rsync_3.2.3-8ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+attachment/5623548/+files/rsync_3.2.3-8ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Fix Released Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Jammy: Triaged Bug description: [Impact] This bug causes rsync 3.2.3 to wrongly report files with an exact same mtime as being "newer" implying they would need to be transfered/sync'ed where in fact they are "uptodate". This breaks users' scripts depending on "is newer" to signal that files need to be sync'ed when in fact, they don't need to be. [Test Plan] Steps to reproduce: 1. Create a local file: $ touch foo 2. Check if rsync would transfer it using the --update option: $ rsync -avv --update foo . If the regression is present, "foo is newer"
[Touch-packages] [Bug 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
** Also affects: rsync via https://github.com/WayneD/rsync/issues/98 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync: Unknown Status in rsync package in Ubuntu: Confirmed Bug description: rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
If you can fill out the SRU template, that'd be great! I see that you worked with upstream to ID which commit corrected the problem, that will be useful to whoever creates a debdiff! If you need a hand with the debdiff, please let me know and I'll set some time aside. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
@Ian, the back and forth on status was apparently due to a simple mistake on which distro version was affected. The good news is that thanks to comment #7, we now know that Kinetic is fixed which is one of the required step to do a SRU (https://wiki.ubuntu.com/StableReleaseUpdates) to have the fix land in Jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1965076] Re: rsync --update incorrectly reports file "is newer" than itself
I can confirm the problem affects rsync 3.2.3-8ubuntu3 as shipped in 22.04. ** Changed in: rsync (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1965076 Title: rsync --update incorrectly reports file "is newer" than itself Status in rsync package in Ubuntu: Confirmed Bug description: rsync 3.2.3 has a broken "--update" option.See the examples below. The "--update" option incorrectly makes rsync say a file is newer than itself. Remove the "--update" option, and rsync correctly says the file is "uptodate". The right output should of course be "is uptodate" in all cases. This bug also shows up between machines if the source rsync is 3.1.3 and the destination is 3.2.3. The bug does not show up if the source rsync is 3.2.3 and the destination is 3.1.3. $ touch foo $ rsync -avv --update foo . delta-transmission disabled for local transfer or --whole-file foo is newer <=== THIS IS NOT CORRECT - A file can't be newer than itself. total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 38 bytes received 96 bytes 268.00 bytes/sec total size is 0 speedup is 0.00 $ rsync -avv foo . delta-transmission disabled for local transfer or --whole-file foo is uptodate <=== THIS IS CORRECT total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 41 bytes received 106 bytes 294.00 bytes/sec total size is 0 speedup is 0.00 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: rsync 3.2.3-4ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 22:47:44 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1965076/+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 1991975] Re: dev file system is mounted without nosuid
I can confirm the issue on an *old* GCP instance: $ mount | grep devtmp devtmpfs on /dev type devtmpfs (rw,relatime,size=490260k,nr_inodes=122565,mode=755,inode64) $ cat /etc/cloud/build.info build_name: server serial: 20200902 $ uname -a Linux mx1 5.15.0-1018-gcp #24~20.04.1-Ubuntu SMP Mon Sep 12 06:14:01 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 634900] Re: "oom never" makes ssh upstart job fail to start in OpenVZ container
I'll mark the bug as fix released as I think Ubuntu releases no longer suffer from this problem. Also, all Ubuntu releases still receiving normal support have moved away from upstart. ** Changed in: upstart (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/634900 Title: "oom never" makes ssh upstart job fail to start in OpenVZ container Status in upstart package in Ubuntu: Fix Released Bug description: Binary package hint: upstart /etc/init/ssh.conf uses "oom never", which causes the job failing to start in an OpenVZ container. Host: - kernel: 2.6.32-5-openvz-amd64 (Debian testing) Container: openssh-server: 1:5.3p1-3ubuntu4 (Lucid) Upstart: 0.6.5-7 (Lucid) This is a known problem (mentioned on http://ubuntuforums.org/showpost.php?p=9170868=2). What information is required to debug this? Some strace output? WORKAROUND: - comment the "oom never" line POSSIBLE FIXES: 1. Ignore any errors when trying to set "oom never" for the job?! 2. Only apply "oom never" if not in a virtualized context (see comment #2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/634900/+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 1980146] Re: dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
** Summary changed:
- dnsmasq often using 100% of CPU
+ dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1980146
Title:
dnsmasq often using 100% of CPU if the upstream nameserver is
unreachable
Status in dnsmasq package in Ubuntu:
Triaged
Status in dnsmasq source package in Focal:
Triaged
Status in dnsmasq source package in Jammy:
Triaged
Status in dnsmasq source package in Kinetic:
Triaged
Bug description:
Release: 22.04
Codename: jammy
Kernel: Linux 5.15.0-40-generic x86_64
⏵ apt-cache policy dnsmasq
Installed: 2.86-1.1ubuntu0.1
dnsmasq is caught in a loop after every dns request, resulting in 100%
CPU usage for several minutes each time. This leads to a hot and
lethargic computer. During this time thousands of the following
messages (see below) are printed from strace.
The loop tends to obsess on denied connections, but there are so many
I'm not 100% sure.
systemd-resolved is _not_ running, some bugs refer to that.
⏵ head /etc/dnsmasq.d/foo.conf
address=/#/127.0.0.2
port=53
resolv-file=/var/run/NetworkManager/resolv.conf
⏵ sudo strace -p 3519 (dnsmasq)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5,
events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8,
events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14,
events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}])
recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16,
msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify-
client\10ser"..., iov_len=4096}], msg_iovlen=1,
msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO,
cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"),
ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0},
0) = 54
ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0
sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"...,
54, 0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.53")}, 16) = 54
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+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 1983981] [NEW] Wrong package version displayed in action summary if update is available
Public bug reported: If an update for a package is available but not installed, simulating a purge shows the wrong version. On that 20.04 system, an update to libxml2 2.9.10+dfsg-5ubuntu0.20.04.4 was available but only the ".3" one was installed. Simulating a purge gives this bogus output (with `APT::Get::Show-Versions "true"`): $ apt-get autopurge -s libxml2 NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libicu66* (66.1-2ubuntu2.1) libxml2* (2.9.10+dfsg-5ubuntu0.20.04.4) shared-mime-info* (1.15-1) 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. Purg shared-mime-info [1.15-1] Purg libxml2 [2.9.10+dfsg-5ubuntu0.20.04.3] Purg libicu66 [66.1-2ubuntu2.1] In the above, the "REMOVED" section shows the wrong version number but the simulation part is OK. # Additional information Note: libxml2's update was applied before checking the policy. $ apt-cache policy apt libxml2 apt: Installed: 2.0.9 Candidate: 2.0.9 Version table: *** 2.0.9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.2ubuntu0.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages libxml2: Installed: 2.9.10+dfsg-5ubuntu0.20.04.4 Candidate: 2.9.10+dfsg-5ubuntu0.20.04.4 Version table: *** 2.9.10+dfsg-5ubuntu0.20.04.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.10+dfsg-5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ lsb_release -sd Ubuntu 20.04.4 LTS ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1983981 Title: Wrong package version displayed in action summary if update is available Status in apt package in Ubuntu: New Bug description: If an update for a package is available but not installed, simulating a purge shows the wrong version. On that 20.04 system, an update to libxml2 2.9.10+dfsg-5ubuntu0.20.04.4 was available but only the ".3" one was installed. Simulating a purge gives this bogus output (with `APT::Get::Show-Versions "true"`): $ apt-get autopurge -s libxml2 NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libicu66* (66.1-2ubuntu2.1) libxml2* (2.9.10+dfsg-5ubuntu0.20.04.4) shared-mime-info* (1.15-1) 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. Purg shared-mime-info [1.15-1] Purg libxml2 [2.9.10+dfsg-5ubuntu0.20.04.3] Purg libicu66 [66.1-2ubuntu2.1] In the above, the "REMOVED" section shows the wrong version number but the simulation part is OK. # Additional information Note: libxml2's update was applied before checking the policy. $ apt-cache policy apt libxml2 apt: Installed: 2.0.9 Candidate: 2.0.9 Version table: *** 2.0.9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.2ubuntu0.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 2.0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages libxml2: Installed: 2.9.10+dfsg-5ubuntu0.20.04.4 Candidate: 2.9.10+dfsg-5ubuntu0.20.04.4 Version table: *** 2.9.10+dfsg-5ubuntu0.20.04.4 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.10+dfsg-5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ lsb_release -sd Ubuntu 20.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1983981/+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 943819] Re: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/943819 Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in rsyslog package in Ubuntu: Incomplete Bug description: Installation Error. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.2 ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Feb 29 23:16:47 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: Upgraded to natty on 2011-12-13 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/943819/+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 936968] Re: rsyslog-gnutls requires rsyslog=4.2.0-2ubuntu8 which is not latest
The affected Ubuntu release is no longer supported so closing the bug. The problem seemed like a mirror or an apt issue more than a rsyslog one anyway. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/936968 Title: rsyslog-gnutls requires rsyslog=4.2.0-2ubuntu8 which is not latest Status in rsyslog package in Ubuntu: Invalid Bug description: Installing rsyslog-gnutls requires rsyslog which is at 4.2.0-2ubuntu8.1 but rsyslog-gnutls depends on == 4.2.0-2ubuntu8 20/02/12 13:27:13 david@rim-aus-syd-exm-a1 ~: sudo apt-get install rsyslog-gnutls Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: rsyslog-gnutls: Depends: rsyslog (= 4.2.0-2ubuntu8) but 4.2.0-2ubuntu8.1 is to be installed E: Broken packages 20/02/12 13:44:57 david@rim-aus-syd-exm-a1 ~: lsb_release -rd Description: Ubuntu 10.04.4 LTS Release: 10.04 20/02/12 13:44:59 david@rim-aus-syd-exm-a1 ~: apt-cache policy rsyslog-gnutls rsyslog-gnutls: Installed: 4.2.0-2ubuntu8 Candidate: 4.2.0-2ubuntu8 Version table: *** 4.2.0-2ubuntu8 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status 20/02/12 13:45:16 david@rim-aus-syd-exm-a1 ~: apt-cache policy rsyslog rsyslog: Installed: 4.2.0-2ubuntu8 Candidate: 4.2.0-2ubuntu8.1 Version table: 4.2.0-2ubuntu8.1 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages *** 4.2.0-2ubuntu8 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8 Uname: Linux 2.6.34.10-xenU x86_64 Architecture: amd64 Date: Mon Feb 20 13:41:30 2012 ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/936968/+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 1163941] Re: package rsyslog 5.8.6-1ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1163941 Title: package rsyslog 5.8.6-1ubuntu8.1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 10 Status in rsyslog package in Ubuntu: Incomplete Bug description: . ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog 5.8.6-1ubuntu8.1 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic-pae 3.2.37 Uname: Linux 3.2.0-38-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Wed Apr 3 15:55:03 2013 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120426-12:41 MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog 5.8.6-1ubuntu8.1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1163941/+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 1155988] Re: package rsyslog-pgsql 5.8.6-1ubuntu8 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1155988 Title: package rsyslog-pgsql 5.8.6-1ubuntu8 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: I don't know if this is a bug. It may not be. My Xubuntu system popped up a dialog that said it had detected one, so I went ahead and let it submit this report. I had been installing and removing rsyslog, rsyslog-pgsql, postgresql several times, trying to get rsyslog to log messages to the postgresql database. $ lsb_release -rd Description: Ubuntu 12.04.2 LTS Release: 12.04 From "dpkg -l '*syslog*' '*postgres*' ": ii rsyslog 5.8.6-1ubuntu8 reliable system and kernel logging daemon ii rsyslog-pgsql 5.8.6-1ubuntu8 PostgreSQL output plugin for rsyslog ii postgresql 9.1+129ubuntu1 object-relational SQL database (supported version) ii postgresql-9.1 9.1.8-0ubuntu12.04 object-relational SQL database, version 9.1 server ii postgresql-client-9.1 9.1.8-0ubuntu12.04 front-end programs for PostgreSQL 9.1 ii postgresql-client-common129ubuntu1 manager for multiple PostgreSQL client versions ii postgresql-common 129ubuntu1 PostgreSQL database-cluster manager ii postgresql-contrib 9.1+129ubuntu1 additional facilities for PostgreSQL (supported version) ii postgresql-contrib-9.1 9.1.8-0ubuntu12.04 additional facilities for PostgreSQL ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog-pgsql 5.8.6-1ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic-pae 3.2.37 Uname: Linux 3.2.0-38-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Fri Mar 15 20:09:09 2013 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog-pgsql 5.8.6-1ubuntu8 failed to install/upgrade: subprocess installed pre-removal script 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/rsyslog/+bug/1155988/+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 1408748] Re: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1408748 Title: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in rsyslog package in Ubuntu: Incomplete Bug description: Installed with gui updater ProblemType: Package DistroRelease: Ubuntu 14.10 Package: rsyslog 7.4.4-1ubuntu11.1 Uname: Linux 3.16.6-031606-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Thu Jan 8 13:12:56 2015 DuplicateSignature: package:rsyslog:7.4.4-1ubuntu11.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2013-09-18 (476 days ago) InstallationMedia: This SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1408748/+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 1189013] Re: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1189013 Title: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 Status in rsyslog package in Ubuntu: Incomplete Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog 5.8.6-1ubuntu8.4 ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44 Uname: Linux 3.2.0-45-generic i686 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Sat Jun 8 02:35:13 2013 DuplicateSignature: package:rsyslog:5.8.6-1ubuntu8.4:subprocess installed post-installation script returned error exit status 13 ErrorMessage: subprocess installed post-installation script returned error exit status 13 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 13 UpgradeStatus: Upgraded to precise on 2013-06-04 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1189013/+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 1191301] Re: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1191301 Title: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in rsyslog package in Ubuntu: Incomplete Bug description: sudo apt-get upgradeReading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-generic-pae linux-headers-generic-pae linux-image-generic-pae The following packages will be upgraded: cups 1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. Need to get 0 B/1,281 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Y Preconfiguring packages ... (Reading database ... 445284 files and directories currently installed.) Preparing to replace cups 1.5.3-0ubuntu6 (using .../cups_1.5.3-0ubuntu8_i386.deb) ... /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found /etc/init.d/cups: 82: /etc/init.d/cups: stop: not found invoke-rc.d: initscript cups, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg - trying script from the new package instead ... /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found /etc/init.d/cups: 82: /etc/init.d/cups: stop: not found invoke-rc.d: initscript cups, action "stop" failed. dpkg: error processing /var/cache/apt/archives/cups_1.5.3-0ubuntu8_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found Errors were encountered while processing: /var/cache/apt/archives/cups_1.5.3-0ubuntu8_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog 5.8.6-1ubuntu8.4 ProcVersionSignature: Ubuntu 3.2.0-41.66-generic-pae 3.2.42 Uname: Linux 3.2.0-41-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu17.3 AptOrdering: rsyslog: Configure Architecture: i386 Date: Sat Jun 15 19:33:31 2013 DuplicateSignature: package:rsyslog:5.8.6-1ubuntu8.4:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog 5.8.6-1ubuntu8.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1191301/+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 1477584] Re: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1477584 Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: Identified the issue after upgrade to 15.04 from 14.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Thu Jul 23 14:34:45 2015 DuplicateSignature: package:rsyslog:7.4.4-1ubuntu14:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-12 (11 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: rsyslog Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script 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/rsyslog/+bug/1477584/+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 925058] Re: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: le sous-processus dpkg-deb --control a retourné une erreur de sortie d'état 2
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/925058 Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: le sous- processus dpkg-deb --control a retourné une erreur de sortie d'état 2 Status in rsyslog package in Ubuntu: Incomplete Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.2 ProcVersionSignature: Ubuntu 2.6.38-13.54-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Feb 1 06:38:00 2012 ErrorMessage: le sous-processus dpkg-deb --control a retourné une erreur de sortie d'état 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: le sous-processus dpkg-deb --control a retourné une erreur de sortie d'état 2 UpgradeStatus: Upgraded to natty on 2011-09-28 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/925058/+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 1188435] Re: logger --udp does not work (sends AF_UNIX)
Ubuntu 22.04 with rsyslog 8.2112.0 doesn't have this problem so marking
as fixed, thanks!
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1188435
Title:
logger --udp does not work (sends AF_UNIX)
Status in rsyslog package in Ubuntu:
Fix Released
Bug description:
Description: Ubuntu 12.04.2 LTS
Release: 12.04
bsdutils:
Installed: 1:2.20.1-1ubuntu3
Candidate: 1:2.20.1-1ubuntu3
Version table:
*** 1:2.20.1-1ubuntu3 0
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise/main
amd64 Packages
100 /var/lib/dpkg/status
$ logger -n localhost --udp "this is my message"
What I expected to happen: my message would get sent to port 514 UDP.
What happened instead: nothing went to port 514, but it did get
written to /dev/log.
If I run:
$ tcpdump -i lo -s 0 -A port 514
while doing this, I get no output. If I strace the logger process, I
can see it create a UDP socket, connect to the appropriate address and
port, then not send anything on that port. I can also see it send to
/dev/log:
$ strace -e network logger -n localhost --udp "this is my message"
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT
(No such file or directory)
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT
(No such file or directory)
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(514),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 1
connect(1, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
sendto(1, "<13>Jun 7 01:06:49 logger: this"..., 46, MSG_NOSIGNAL, NULL, 0) =
46
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1188435/+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 918965] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/918965 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in rsyslog package in Ubuntu: Incomplete Bug description: This is the third time i have had this problem ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8.1 ProcVersionSignature: Ubuntu 2.6.32-36.79-generic 2.6.32.46+drm33.20 Uname: Linux 2.6.32-36-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Thu Jan 19 17:48:40 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/918965/+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 1204990] Re: rsyslog-relp improperly depends on a specific version of rsyslog no longer in the repo
Ubuntu 18.04 with rsyslog 8.32.0 is not affected by that problem anymore so marking as such. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1204990 Title: rsyslog-relp improperly depends on a specific version of rsyslog no longer in the repo Status in rsyslog package in Ubuntu: Fix Released Bug description: In Ubuntu Precise Pangolin, attempting to install rsyslog-relp results in this: joe@foo:~$ sudo apt-get install rsyslog-relp Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: rsyslog-relp : Depends: rsyslog (= 5.8.6-1ubuntu8) but 5.8.6-1ubuntu8.4 is to be installed E: Unable to correct problems, you have held broken packages. joe@foo:~$ There's really no reason for such a specific version dependency. $ lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 $ apt-cache policy rsyslog rsyslog: Installed: 5.8.6-1ubuntu8.4 Candidate: 5.8.6-1ubuntu8.4 Version table: *** 5.8.6-1ubuntu8.4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ apt-cache policy rsyslog-relp rsyslog-relp: Installed: (none) Candidate: 5.8.6-1ubuntu8 Version table: 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1204990/+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 847665] Re: package rsyslog-mysql 5.8.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/847665 Title: package rsyslog-mysql 5.8.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: application getting crashed ProblemType: Package DistroRelease: Ubuntu 11.10 Package: rsyslog-mysql 5.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 ApportVersion: 1.22.1-0ubuntu2 Architecture: i386 Date: Mon Sep 12 14:53:19 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901) SourcePackage: rsyslog Title: package rsyslog-mysql 5.8.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script 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/rsyslog/+bug/847665/+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 698171] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. action "restart" failed
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/698171 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. action "restart" failed Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog I have very little experience with rsyslog, but it is causing problems on my 64 bit machine as well. It always fails when the update-manager runs. I am using Ubuntu 10.04 LTS both 64 Bit and 32 Bit Versions ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8.1 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 AptOrdering: rsyslog: Configure Architecture: i386 Date: Thu Jan 6 07:59:45 2011 DpkgTerminalLog: Log started: 2011-01-06 07:59:41 Setting up rsyslog (4.2.0-2ubuntu8.1) ... invoke-rc.d: initscript rsyslog, action "restart" failed. dpkg: error processing rsyslog (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/698171/+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 1430457] Re: upgrade from 14.10 to 15.04
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1430457 Title: upgrade from 14.10 to 15.04 Status in rsyslog package in Ubuntu: Incomplete Bug description: After my upgrade with "sudo do-release-upgrade -d" I got some errors about configurations and missing depends I tried a dpkg --configure and got this: sudo dpkg --configure -a avahi-daemon (0.6.31-4ubuntu4) wird eingerichtet ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Job for avahi-daemon.service failed. See "systemctl status avahi-daemon.service" and "journalctl -xe" for details. invoke-rc.d: initscript avahi-daemon, action "start" failed. dpkg: Fehler beim Bearbeiten des Paketes avahi-daemon (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von avahi-utils: avahi-utils hängt ab von avahi-daemon; aber: Paket avahi-daemon ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes avahi-utils (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert rsyslog (7.4.4-1ubuntu14) wird eingerichtet ... Der Benutzer »syslog« ist bereits ein Mitglied der Gruppe »adm«. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Job for rsyslog.service failed. See "systemctl status rsyslog.service" and "journalctl -xe" for details. invoke-rc.d: initscript rsyslog, action "restart" failed. dpkg: Fehler beim Bearbeiten des Paketes rsyslog (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ubuntu-minimal: ubuntu-minimal hängt ab von rsyslog; aber: Paket rsyslog ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ubuntu-minimal (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: avahi-daemon avahi-utils rsyslog ubuntu-minimal ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: rsyslog 7.4.4-1ubuntu14 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 Date: Tue Mar 10 18:29:17 2015 InstallationDate: Installed on 2013-05-31 (648 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: rsyslog UpgradeStatus: Upgraded to vivid on 2015-03-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1430457/+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 498531] Re: package rsyslog 4.2.0-2ubuntu5.1 failed to upgrade: exit status 1. start: Unknown job: rsyslog
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/498531 Title: package rsyslog 4.2.0-2ubuntu5.1 failed to upgrade: exit status 1. start: Unknown job: rsyslog Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog Normal run through update manager resulting in this error ProblemType: Package Architecture: i386 Date: Sat Dec 19 09:25:11 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: rsyslog 4.2.0-2ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/498531/+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 933943] Re: rsyslogd please apply patch for large group handling
Marking as fix released based on versions reported in comment # 10. Ubuntu Trusty ships 7.4.4 so it has the patch. ** Changed in: rsyslog (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/933943 Title: rsyslogd please apply patch for large group handling Status in Rsyslog: Fix Released Status in rsyslog package in Ubuntu: Fix Released Bug description: http://bugzilla.adiscon.com/show_bug.cgi?id=310 rsyslog uses a static 2048 character buffer to perform group lookups. Some of us have large groups and need a larger buffer. This patch repeatedly calls getgrnam_r until it gets a buffer of sufficient size. -A To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/933943/+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 476877] Re: package rsyslog 4.2.0-2ubuntu5.1 failed to upgrade: exit status 1. start: Job is already running: rsyslog
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/476877 Title: package rsyslog 4.2.0-2ubuntu5.1 failed to upgrade: exit status 1. start: Job is already running: rsyslog Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog no further info ProblemType: Package Architecture: i386 Date: Fri Nov 6 21:34:58 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück NonfreeKernelModules: nvidia Package: rsyslog 4.2.0-2ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/476877/+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 588101] Re: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade: Hang after displaying Installing new version of config file /etc/rsyslog.conf
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/588101 Title: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade: Hang after displaying Installing new version of config file /etc/rsyslog.conf Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog During a do-release-upgrade from 9.10 to 10.04 the installatian hangs. It was able to continue after pressing Ctrl+C. I haven't done an apt- get upgrade first, this might be related. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8 ProcVersionSignature: Ubuntu 2.6.31-20.58-generic-pae Uname: Linux 2.6.31-20-generic-pae i686 Architecture: i386 Date: Tue Jun 1 02:33:28 2010 ErrorMessage: ErrorMessage: subprocess installed post-installation script killed by signal (Interrupt) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/588101/+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 506691] Re: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: underprocess installerade post-installation-skript gav felkod 255
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/506691
Title:
package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade:
underprocess installerade post-installation-skript gav felkod 255
Status in rsyslog package in Ubuntu:
Incomplete
Bug description:
Binary package hint: rsyslog
Just ran Computer Cleaning. ("Datorstädare", in swedish).
Well I really don't know what more to say, except good luck :)
... and thanks 4 Ubuntu
ProblemType: Package
Architecture: amd64
Date: Wed Jan 13 00:12:11 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: underprocess installerade post-installation-skript gav felkod
255
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: rsyslog 4.2.0-2ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: rsyslog
Title: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade:
underprocess installerade post-installation-skript gav felkod 255
Uname: Linux 2.6.31-17-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/506691/+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 583936] Re: package rsyslog-mysql 4.2.0-2ubuntu8 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/583936 Title: package rsyslog-mysql 4.2.0-2ubuntu8 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog FAILED TO UNISTALL ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog-mysql 4.2.0-2ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic-pae i686 Architecture: i386 Date: Fri May 21 21:00:21 2010 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: rsyslog Title: package rsyslog-mysql 4.2.0-2ubuntu8 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/583936/+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 873238] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/873238 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in rsyslog package in Ubuntu: Incomplete Bug description: I got this error while I typed the command "sudo apt-get upgrade". I encountered this problem twice. First time, I didn't know what to do. I reinstalled ubuntu. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Thu Oct 13 15:12:16 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 127 SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/873238/+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 498806] Re: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/498806 Title: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: grub Release: 9.10 Upgraded by - apt-get dist-upgrade from 9.04 ProblemType: Package Architecture: i386 Date: Sun Dec 20 21:30:55 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed post-installation script returned error exit status 10 NonfreeKernelModules: nvidia Package: rsyslog 4.2.0-2ubuntu5.1 ProcVersionSignature: Ubuntu 2.6.31-15.50-generic SourcePackage: grub Title: package rsyslog 4.2.0-2ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Uname: Linux 2.6.31-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/498806/+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 670097] Re: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade:
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/670097 Title: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade: Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog 10.04 Lucid Lynx 4.2.0-2ubuntu8 ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Mon Nov 1 18:22:59 2010 ErrorMessage: ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8 failed to install/upgrade: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/670097/+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 701166] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to upgrade: exit status 127. Can not write log, openpty() failed (/dev/pts not mounted?)
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/701166 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to upgrade: exit status 127. Can not write log, openpty() failed (/dev/pts not mounted?) Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog During an update yesterday a failure occured and the system stopped. I tried to start up the system but it failed. I got the mesage: Ubuntu is in safemode: (EE) NVIDIA failed to load ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8.1 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 NonfreeKernelModules: nvidia AptOrdering: rsyslog: Configure Architecture: i386 Date: Mon Jan 10 20:31:54 2011 Df: ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/701166/+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 710045] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 20
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/710045 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 20 Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog Hi there, After many many attempts to upgrade using 'upgrade manager', I still cannot. I've tried several 'solutions' suggested on various websites to no avail. Help! :) --Len ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8.1 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 Architecture: i386 Date: Sat Jan 29 22:30:35 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 20 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/710045/+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 801651] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/801651 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: Update manger opened as usual and I clicked update, things seemed to go fine as usual, but near the end it informed me of this problem. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8.1 ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16 Uname: Linux 2.6.32-32-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 24 14:19:58 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: rsyslog Title: package rsyslog 4.2.0-2ubuntu8.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/801651/+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 801810] Re: package rsyslog (not installed) failed to install/upgrade: ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/801810 Title: package rsyslog (not installed) failed to install/upgrade: ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: I have solved with "sudo apt-get install syslog-ng" ProblemType: Package DistroRelease: Ubuntu 10.04 Package: rsyslog (not installed) ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16 Uname: Linux 2.6.32-32-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sat Jun 25 02:32:21 2011 ErrorMessage: ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 SourcePackage: rsyslog Title: package rsyslog (not installed) failed to install/upgrade: ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/801810/+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 798535] Re: package rsyslog-mysql 4.6.4-2ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/798535 Title: package rsyslog-mysql 4.6.4-2ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog Firestarter log doesn't work. Mysql didn't install for rsyslog. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog-mysql 4.6.4-2ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Thu Jun 16 06:27:45 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: rsyslog Title: package rsyslog-mysql 4.6.4-2ubuntu4 failed to install/upgrade: subprocess installed post-installation script 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/rsyslog/+bug/798535/+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 869500] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: Unterprozess script post-installation installé wurde durch Signal (Processus arrêté) getötet
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/869500 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: Unterprozess script post-installation installé wurde durch Signal (Processus arrêté) getötet Status in rsyslog package in Ubuntu: Incomplete Bug description: mise a jour, update ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Oct 6 22:42:26 2011 ErrorMessage: Unterprozess script post-installation installé wurde durch Signal (Processus arrêté) getötet InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: Unterprozess script post-installation installé wurde durch Signal (Processus arrêté) getötet UpgradeStatus: Upgraded to natty on 2011-05-09 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869500/+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 872258] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/872258 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: - ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 Architecture: amd64 Date: Mon Oct 10 09:27:31 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script 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/rsyslog/+bug/872258/+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 874331] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/874331 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: If I remember correctly, when the "start" command was issued it gave a "process is already running" error. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 AptOrdering: rsyslog: Configure Architecture: i386 Date: Fri Oct 7 17:17:57 2011 DpkgTerminalLog: Setting up rsyslog (4.6.4-2ubuntu4.1) ... start: Job is already running: rsyslog invoke-rc.d: initscript rsyslog, action "restart" failed. dpkg: error processing rsyslog (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to natty on 2011-05-20 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/874331/+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 873609] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/873609 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in rsyslog package in Ubuntu: Incomplete Bug description: And again, same as for cupds install process was not able to stop the service fix: # service rsyslog stop rsyslog stop/waiting # aptitude upgrade ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 9 19:41:46 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to natty on 2011-05-03 (163 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/873609/+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 878337] Re: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/878337 Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in rsyslog package in Ubuntu: Incomplete Bug description: failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 when i tried to install mysql ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed Oct 19 21:50:25 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/878337/+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 967295] Re: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release and report a new bug if appropriate. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/967295 Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in rsyslog package in Ubuntu: Incomplete Bug description: Automated error message popped up on first startup after Ubuntu system upgrade using 'sudo apt-get dist-upgrade'. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: rsyslog 4.6.4-2ubuntu4.2 ProcVersionSignature: Ubuntu 2.6.38-13.57-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 Architecture: i386 Date: Wed Mar 28 17:12:53 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: rsyslog Title: package rsyslog 4.6.4-2ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: Upgraded to natty on 2011-12-29 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/967295/+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 694949] Re: package rsyslog 4.2.0-2ubuntu8.1 failed to upgrade: exit status 127. /etc/init.d/rsyslog: 74: i2c-viapro: not found
This bug was reported against an Ubuntu version that's long been EOL. Please try to reproduce with a supported release. Marked as incomplete until then. Thanks. ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/694949 Title: package rsyslog 4.2.0-2ubuntu8.1 failed to upgrade: exit status 127. /etc/init.d/rsyslog: 74: i2c-viapro: not found Status in rsyslog package in Ubuntu: Incomplete Bug description: Binary package hint: rsyslog guido@guido-desktop:~$ sudo apt-get update && sudo apt-get upgrade[sudo] password for guido: Trovato http://it.archive.ubuntu.com lucid Release.gpg Trovato http://security.ubuntu.com lucid-security Release.gpg Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-it Scaricare:1 http://dl.google.com stable Release.gpg [197B] Trovato http://ppa.launchpad.net lucid Release.gpg Ign http://ppa.launchpad.net/cairo-dock-team/ppa/ubuntu/ lucid/main Translation-it Trovato http://ppa.launchpad.net lucid Release.gpg Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-it Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-it Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-it Scaricare:2 http://archive.canonical.com lucid Release.gpg [198B] Ign http://archive.canonical.com/ubuntu/ lucid/partner Translation-it Trovato http://security.ubuntu.com lucid-security Release Ign http://ppa.launchpad.net/jason-scheunemann/ppa/ubuntu/ lucid/main Translation-it Trovato http://ppa.launchpad.net lucid Release.gpg Ign http://ppa.launchpad.net/mozillateam/firefox-stable/ubuntu/ lucid/main Translation-it Trovato http://ppa.launchpad.net lucid Release.gpg Ign http://ppa.launchpad.net/tualatrix/ppa/ubuntu/ lucid/main Translation-it Trovato http://it.archive.ubuntu.com/ubuntu/ lucid/main Translation-it Scaricare:3 http://archive.canonical.com lucid Release [8215B] Trovato http://ppa.launchpad.net lucid Release Trovato http://security.ubuntu.com lucid-security/main Packages Trovato http://ppa.launchpad.net lucid Release Trovato http://ppa.launchpad.net lucid Release Trovato http://ppa.launchpad.net lucid Release Trovato http://it.archive.ubuntu.com/ubuntu/ lucid/restricted Translation-it Trovato http://security.ubuntu.com lucid-security/restricted Packages Trovato http://security.ubuntu.com lucid-security/main Sources Trovato http://security.ubuntu.com lucid-security/restricted Sources Trovato http://security.ubuntu.com lucid-security/universe Packages Trovato http://security.ubuntu.com lucid-security/universe Sources Trovato http://ppa.launchpad.net lucid/main Packages Scaricare:4 http://archive.canonical.com lucid/partner Packages [11,8kB] Trovato http://security.ubuntu.com lucid-security/multiverse Packages Trovato http://security.ubuntu.com lucid-security/multiverse Sources Trovato http://it.archive.ubuntu.com/ubuntu/ lucid/universe Translation-it Trovato http://ppa.launchpad.net lucid/main Packages Trovato http://ppa.launchpad.net lucid/main Packages Trovato http://ppa.launchpad.net lucid/main Packages Trovato http://it.archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-it Scaricare:5 http://archive.canonical.com lucid/partner Sources [5215B] Trovato http://it.archive.ubuntu.com lucid-updates Release.gpg Ign http://it.archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-it Ign http://it.archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-it Ign http://it.archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-it Ign http://it.archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-it Ign http://dl.google.com/linux/chrome/deb/ stable/main Translation-it Scaricare:6 http://dl.google.com stable Release.gpg [189B] Ign http://dl.google.com/linux/deb/ stable/non-free Translation-it Trovato http://it.archive.ubuntu.com lucid Release Ign http://dl.google.com/linux/deb/ stable/main Translation-it Scaricare:7 http://dl.google.com stable Release [1347B]
[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.
I've proposed the change to Debian: https://salsa.debian.org/sdeziel-
guest/quassel/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1814302
Title:
Quasselcore apparmor profile issue in lxd container.
Status in AppArmor:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in quassel package in Ubuntu:
Confirmed
Status in apparmor source package in Bionic:
Invalid
Status in quassel source package in Bionic:
Fix Released
Status in apparmor source package in Focal:
Invalid
Status in quassel source package in Focal:
Fix Released
Status in apparmor source package in Groovy:
Invalid
Status in quassel source package in Groovy:
Fix Released
Status in apparmor source package in Jammy:
Invalid
Status in quassel source package in Jammy:
Confirmed
Status in apparmor source package in Kinetic:
Invalid
Status in quassel source package in Kinetic:
Confirmed
Bug description:
[impact]
quasselcore cannot start inside lxd container
[test case]
create lxd container, install quassel-core, check quasselcore service:
$ systemctl status quasselcore
● quasselcore.service - distributed IRC client using a central core component
Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor
preset: enabled)
Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
Docs: man:quasselcore(1)
Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR}
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN}
(code=killed, signal=SEGV)
Main PID: 3853 (code=killed, signal=SEGV)
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled
restart job, restart counter is at 7.
Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using
a central core component.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request
repeated too quickly.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with
result 'signal'.
Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC
client using a central core component.
Also, the binary will segfault when run directly due to apparmor denials:
$ /usr/bin/quasselcore
Segmentation fault
[760149.590802] audit: type=1400 audit(1593542073.962:1058):
apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
lp1814302-f_" profile="/usr/bin/quasselcore"
name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100
[regression potential]
this expands the apparmor profile, so any regression would likely
involve problems while starting due to apparmor.
[scope]
this is needed for b/f/g.
this is also needed for e, but that is EOL in weeks and this is not
important enough to bother there.
[original description]
Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
container. Everything up todate via apt.
Install quassel-core. Service will not start.
Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.
I then added "/usr/bin/quasselcore rm," to
"/etc/apparmor.d/usr.bin.quasselcore".
Set "aa-enforce /usr/bin/quasselcore". Restarted main host.
Quasselcore service now starts and I can connect to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1966562] Re: ubuntu-minimal should not depend on isc-dhcp-client
Thanks for the explanation and pointer to the ML thread, makes sense to me now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966562 Title: ubuntu-minimal should not depend on isc-dhcp-client Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-minimal already depends on `init` which depends on `systemd- sysv` which depends on `systemd` which comes with `systemd-networkd` that has a DHCP client in it. Having the isc-dhcp-client package feels redundant. # Additional information $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ apt-cache policy ubuntu-minimal ubuntu-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966562/+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 1222301] Re: rsyncd.conf man page on numeric ids has incorrect instructions about chroot
Looks like this was fixed as it now (rsync 3.2.3-8ubuntu3 from 22.04 dev) says: man rsyncd.conf: > A chroot-enabled module should not have this parameter set to false unless > you're using a "name converter" program or you've taken steps to ensure that > the module has the necessary resources it needs to translate names ... ** Changed in: rsync (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1222301 Title: rsyncd.conf man page on numeric ids has incorrect instructions about chroot Status in rsync package in Ubuntu: Fix Released Bug description: The man page documention (man rsyncd.conf) states: numeric ids Enabling this parameter disables the mapping of users and groups by name for the current daemon module. This prevents the daemon from trying to load any user/group-related files or libraries. This enabling makes the transfer behave as if the client had passed the --numeric-ids command-line option. By default, this parameter is enabled for chroot modules and disabled for non-chroot modules. A chroot-enabled module should not have this parameter enabled unless you’ve taken steps to ensure that the module has the nec‐ essary resources it needs to translate names, and that it is not possible for a user to change those resources. "A chroot-enabled module should not have" should read "A chroot- enabled module should have" (removed the word 'not') as that is the default and expected behavior when chroot is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1222301/+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 530236] Re: rsync options summary is malformed in the online help
`yelp man:rsync` works fine on Ubuntu 20.04 with rsync version 3.1.3-8ubuntu0.3 so marking as fix released, thanks! ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/530236 Title: rsync options summary is malformed in the online help Status in rsync package in Ubuntu: Fix Released Bug description: Binary package hint: yelp When I open "man:rsync" in the online help, in the OPTIONS SUMMARY section, all the options are concatenated on a single line. In the command-line man page, they're printed on separate lines: OPTIONS SUMMARY Here is a short summary of the options available in rsync. Please refer to the detailed description below for a complete description. -v, --verbose increase verbosity -q, --quiet suppress non-error messages --no-motd suppress daemon-mode MOTD (see caveat) ProblemType: Bug Architecture: i386 Date: Mon Mar 1 11:00:41 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/yelp InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: wl Package: yelp 2.28.0-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: yelp Uname: Linux 2.6.31-19-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/530236/+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 1433787] Re: rsync corrupts systematically jpg files when copying from jmtpfs
Hello David, Ubuntu 14.10 was released a long time ago and is long end of life. Are you still able to reproduce the issue on a supported release? I'll mark the bug as Incomplete until you can report back. Thank you! ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1433787 Title: rsync corrupts systematically jpg files when copying from jmtpfs Status in rsync package in Ubuntu: Incomplete Bug description: rsync corrupts systematically jpg files when copying from jmtpfs I am filing the bug with rsync because neither cp nor scp show the problem. They copy the images just fine. Therefore I assume it is not a problem of jmtpfs. When I want to view the jpg files after a copy with rsync I get the following error: "Error interpreting JPEG image file (Application transferred too few scanlines)". Rsync runs through though and does not output any error nor warning. root@kimera:~# lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 root@kimera:~# apt-cache policy rsync rsync: Installed: 3.1.1-2 Candidate: 3.1.1-2 Version table: *** 3.1.1-2 0 500 http://ch.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: rsync 3.1.1-2 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Mar 18 21:47:32 2015 InstallationDate: Installed on 2015-01-14 (63 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1433787/+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 853243] Re: rsync cannot deal with long file names
*** This bug is a duplicate of bug 279557 *** https://bugs.launchpad.net/bugs/279557 This bug was filled a long time ago so it is probably fixed. Also, as Hans noted, this looks like a dup of LP: #279557 so I'll mark it as such. Please re-open if that is still a problem, thanks! ** This bug has been marked a duplicate of bug 279557 rsync does not implement PATH_MAX for large file paths -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/853243 Title: rsync cannot deal with long file names Status in rsync package in Ubuntu: Confirmed Bug description: gpk@nc:~$ rsync -avz --hard-links --delete desk.lan:n/ n/ g...@desk.lan's password: receiving incremental file list ... rsync: mkstemp "/home/gpk/n/.local/share/Trash/files/The Little Orchestra Society, Dino Anagnost, cond. - Peter and the/.The Little Orchestra Society, Dino Anagnost, cond. - Gerald McBoing Boing, Narrated by Carol Channing, Jonathan Haas,percussion soloist.mp3.JN3fVW" failed: File name too long (36) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: rsync 3.0.7-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Sun Sep 18 15:20:43 2011 EcryptfsInUse: Yes InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110426.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/853243/+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 201344] Re: rsync prints out non-informative error messages
The error message is now clearer (IMHO of course): $ rsync rsync://cdimage.ubuntu.com/cdimage/releases/hardy/alpha-6/hardy-desktop-i386.iso rsync: change_dir "/releases/hardy/alpha-6" (in cdimage) failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1677) [Receiver=3.1.3] It now explicitly mentions being unable to change directory to "/releases/hardy/alpha-6" which is a good hint about the problem IMHO. As such, marking as fix released. ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/201344 Title: rsync prints out non-informative error messages Status in rsync package in Ubuntu: Fix Released Bug description: Binary package hint: rsync This is what a user obtains if facing a timeout using rsync: > $ rsync rsync://cdimage.ubuntu.com/cdimage/releases/hardy/alpha-6/hardy-desktop-i386.iso > . > rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(454) [receiver=2.6.9] It should print out a much clear message so the user knows what's going on. ps. saw this on package source. it has the bug mail as: Bugs: mailto:ubuntu-us...@lists.ubuntu.com is this correct? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/201344/+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 286357] Re: rsync crashes: double free or corruption (fasttop)
Ubuntu Natty (11.04) was a long time ago and since it was reported as fixed in that release, it means all still supported releases should be good. ** Changed in: rsync (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/286357 Title: rsync crashes: double free or corruption (fasttop) Status in rsync package in Ubuntu: Fix Released Bug description: Binary package hint: rsync rsync -axAHS --exclude "/home/user/.gvfs" --del --stats / /media/backup-root *** glibc detected *** rsync: double free or corruption (fasttop): 0x0a13f250 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7deba85] /lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb7def4f0] rsync[0x806ec41] rsync[0x8069478] rsync[0x804cc41] rsync[0x804f1e1] rsync[0x8058a75] rsync[0x8059260] rsync[0x805a558] rsync[0x8070a0f] rsync[0x8059d64] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d96450] rsync[0x804ab01] === Memory map: 08048000-0808d000 r-xp 08:01 3290022/usr/bin/rsync 0808d000-0809 rw-p 00044000 08:01 3290022/usr/bin/rsync 0809-0a1a1000 rw-p 0809 00:00 0 [heap] 97f19000-98be2000 rw-p 97f19000 00:00 0 99b0-99b21000 rw-p 99b0 00:00 0 99b21000-99c0 ---p 99b21000 00:00 0 99c1c000-99c23000 r-xp 08:01 2984004 /lib/tls/i686/cmov/libnss_compat-2.7.so 99c23000-99c25000 rw-p 6000 08:01 2984004 /lib/tls/i686/cmov/libnss_compat-2.7.so 99c37000-9b5dc000 rw-p 99c37000 00:00 0 9b5fd000-9b6c rw-p 9b5fd000 00:00 0 9b6e1000-9b7a4000 rw-p 9b6e1000 00:00 0 9b7a4000-9d7a5000 rw-p b7cda000 00:00 0 9d7a5000-9d868000 rw-p 9d7a5000 00:00 0 9d889000-9d94c000 rw-p 9d889000 00:00 0 9d96d000-9da71000 rw-p 9d96d000 00:00 0 9da92000-9db96000 rw-p 9da92000 00:00 0 9dbb7000-9dcbb000 rw-p 9dbb7000 00:00 0 9dcdc000-9de62000 rw-p 9dcdc000 00:00 0 9de83000-9df87000 rw-p 9de83000 00:00 0 9dfa8000-9e0ac000 rw-p 9dfa8000 00:00 0 9e0cd000-9e253000 rw-p 9e0cd000 00:00 0 9e274000-9e337000 rw-p 9e274000 00:00 0 9e358000-9e3da000 rw-p 9e358000 00:00 0 9e3fb000-9e4be000 rw-p 9e3fb000 00:00 0 9e4df000-9e561000 rw-p 9e4df000 00:00 0 9e582000-9e645000 rw-p 9e582000 00:00 0 9e666000-9e729000 rw-p 9e666000 00:00 0 9e74a000-9e7cc000 rw-p 9e74a000 00:00 0 9e7ed000-9e8b rw-p 9e7ed000 00:00 0 9e8d1000-9e994000 rw-p 9e8d1000 00:00 0 9e9b5000-9ea37000 rw-p 9e9b5000 00:00 0 9ea58000-9eb1b000 rw-p 9ea58000 00:00 0 9eb3c000-9ebff000 rw-p 9eb3c000 00:00 0 9ec2-9ece3000 rw-p 9ec2 00:00 0 9ed04000-9edc7000 rw-p 9ed04000 00:00 0 9ede8000-9eeab000 rw-p 9ede8000 00:00 0 9eecc000-9ef4e000 rw-p 9eecc000 00:00 0 9ef6f000-9f032000 rw-p 9ef6f000 00:00 0 9f053000-9f157000 rw-p 9f053000 00:00 0 9f178000-9f23b000 rw-p 9f178000 00:00 0 9f25c000-9f31f000 rw-p 9f25c000 00:00 0 9f34-9f403000 rw-p 9f34 00:00 0 9f424000-9f4e7000 rw-p 9f424000 00:00 0 9f508000-9f5cb000 rw-p 9f508000 00:00 0 9f5ec000-9f6af000 rw-p 9f5ec000 00:00 0 9f6d-9f793000 rw-p 9f6d 00:00 0 9f7b4000-9f877000 rw-p 9f7b4000 00:00 0 9f898000-9f95b000 rw-p 9f898000 00:00 0 9f97c000-9fa8 rw-p 9f97c000 00:00 0 9faa1000-9fba5000 rw-p 9faa1000 00:00 0 9fbc6000-9fcca000 rw-p 9fbc6000 00:00 0 9fceb000-9fdef000 rw-p 9fceb000 00:00 0 9fe1-9ff96000 rw-p 9fe1 00:00 0 9ffb7000-a00bb000 rw-p 9ffb7000 00:00 0 a00dc000-a0262000 rw-p a00dc000 00:00 0 a0283000-a0387000 rw-p a0283000 00:00 0 a03a8000-a042a000 rw-p a03a8000 00:00 0 a044b000-a04cd000 rw-p a044b000 00:00 0 a04ee000-a057 rw-p a04ee000 00:00 0 a0591000-a0613000 rw-p a0591000 00:00 0 a0634000-a06b6000 rw-p a0634000 00:00 0 a06d7000-a0759000 rw-p a06d7000 00:00 0 a077a000-a07fc000 rw-p a077a000 00:00 0 a081d000-a089f000 rw-p a081d000 00:00 0 a08c-a0942000 rw-p a08c 00:00 0 a0963000-a09e5000 rw-p a0963000 00:00 0 a0a06000-a0a88000 rw-p a0a06000 00:00 0 a0aa9000-a0b2b000 rw-p a0aa9000 00:00 0 a0b4c000-a0bce000 rw-p a0b4c000 00:00 0 a0bef000-a0c71000 rw-p a0bef000 00:00 0 a0c92000-a0d14000 rw-p a0c92000 00:00 0 a0d35000-a0db7000 rw-p a0d35000 00:00 0 a0dd8000-a0e5a000 rw-p a0dd8000 00:00 0 a0e7b000-a0f3e000 rw-p a0e7b000 00:00 0 a0f5f000-a0fe1000 rw-p a0f5f000 00:00 0 a1002000-a10c5000 rw-p a1002000 00:00 0 a10e6000-a11a9000 rw-p a10e6000 00:00 0 a11ca000-a128d000 rw-p a11ca000 00:00 0 a12ae000-a133 rw-p a12ae000 00:00 0 a1351000-a1414000 rw-p a1351000 00:00 0 a1435000-a14b7000 rw-p a1435000 00:00 0 a14d8000-a159b000 rw-p a14d8000 00:00 0 a15bc000-rsync: connection unexpectedly closed (2303378 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(454) [sender=2.6.9] lsb_release -rd Description:Ubuntu 8.04.1 Release:
[Touch-packages] [Bug 728227] Re: add --copy-devices option to rsync
Looks like rsync got that option in the end as this is what I get from 18.04's version: # rsync --help | grep copy-devices --copy-devices copy device contents as regular file # dpkg -l| grep rsync ii rsync3.1.2-2.1ubuntu1.4 amd64fast, versatile, remote (and local) file-copying tool ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/728227 Title: add --copy-devices option to rsync Status in rsync package in Ubuntu: Fix Released Status in rsync package in Fedora: Fix Released Bug description: Binary package hint: rsync 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 2) $ apt-cache policy rsync rsync: Installed: 3.0.7-2ubuntu1 Candidate: 3.0.7-2ubuntu1 Version table: *** 3.0.7-2ubuntu1 0 500 http://se.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I want to be able to copy whole device content as part of backing up kvm virtual machines, this can be enabled by adding patches/copy-devices.diff from rsync-patches-3.0.7.tar.gz 4) $ rsync --copy-devices rsync: --copy-devices: unknown option Apparently some one using fedora had the same idea; https://bugzilla.redhat.com/show_bug.cgi?id=494313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/728227/+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 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe
Thanks Jeremy! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe Status in gdm3 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-desktop-minimal is in main but installing it pulls gnome- session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+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 1452115] Re: Python interpreter binary is not compiled as PIE
@alexmurray, totally random observation that is not related to this bug but might save you/others some times. The following 4 steps: # use a LXD VM for testing lxc launch --vm images:ubuntu/jammy sec-jammy-amd64 # stop the VM and disable UEFI secure boot lxc stop sec-jammy-amd64 # ensure secureboot is not used so we can use the msr module later lxc config set set-jammy-amd64 security.secureboot=false lxc start sec-jammy-amd64 Can be reduced to: # use a LXD VM for testing, no secureboot to allow using the msr module later lxc launch --vm images:ubuntu/jammy sec-jammy-amd64 -c security.secureboot=false -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.9 package in Ubuntu: New Status in python3.7 package in Debian: New Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+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 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
When rsyncd cannot find the address it was told to bind to, it exits with rc=10 and systemd doesn't even attempt a restart. To make it restart on such condition, the systemd unit should have `Restart=on-failure` added. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync: Unknown Status in rsync package in Ubuntu: Won't Fix Bug description: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+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 1959047] Re: systemd ignores RootDirectory option in .service units
Bionic verification was successfully done using the steps outlined in the bug description. The important parts are captured here: $ lxc exec lp1959047 -- apt-get install -y lxd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: acl apparmor dns-root-data dnsmasq-base ebtables iptables libip6tc0 libiptc0 liblxc-common liblxc1 liblzo2-2 libnetfilter-conntrack3 libnfnetlink0 libuv1 lxcfs lxd-client rsync squashfs-tools uidmap xdelta3 Suggested packages: apparmor-profiles-extra apparmor-utils criu lxd-tools openssh-server The following NEW packages will be installed: acl apparmor dns-root-data dnsmasq-base ebtables iptables libip6tc0 libiptc0 liblxc-common liblxc1 liblzo2-2 libnetfilter-conntrack3 libnfnetlink0 libuv1 lxcfs lxd lxd-client rsync squashfs-tools uidmap xdelta3 0 upgraded, 21 newly installed, 0 to remove and 9 not upgraded. Need to get 10.9 MB of archives. After this operation, 41.3 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libnfnetlink0 amd64 1.0.1-3 [13.3 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 liblzo2-2 amd64 2.08-1.2 [48.7 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 apparmor amd64 2.12-4ubuntu5.1 [487 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 libip6tc0 amd64 1.6.1-2ubuntu2 [19.9 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 libiptc0 amd64 1.6.1-2ubuntu2 [9308 B] Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 libnetfilter-conntrack3 amd64 1.0.6-2 [37.8 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 iptables amd64 1.6.1-2ubuntu2 [269 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 rsync amd64 3.1.2-2.1ubuntu1.3 [335 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 acl amd64 2.2.52-3build1 [38.5 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 dns-root-data all 2018013001 [5360 B] Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 dnsmasq-base amd64 2.79-1ubuntu0.5 [307 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 ebtables amd64 2.0.10.4-3.5ubuntu2.18.04.3 [79.9 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 liblxc1 amd64 3.0.3-0ubuntu1~18.04.1 [264 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 liblxc-common amd64 3.0.3-0ubuntu1~18.04.1 [438 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 libuv1 amd64 1.18.0-3 [64.4 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 lxcfs amd64 3.0.3-0ubuntu1~18.04.2 [39.0 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 lxd-client amd64 3.0.3-0ubuntu1~18.04.2 [3025 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 squashfs-tools amd64 1:4.3-6ubuntu0.18.04.4 [111 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 uidmap amd64 1:4.5-1ubuntu2.3 [68.0 kB] Get:20 http://archive.ubuntu.com/ubuntu bionic/main amd64 xdelta3 amd64 3.0.11-dfsg-1ubuntu1 [68.9 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 lxd amd64 3.0.3-0ubuntu1~18.04.2 [5199 kB] Fetched 10.9 MB in 4s (2980 kB/s) ... Unpacking xdelta3 (3.0.11-dfsg-1ubuntu1) ... Selecting previously unselected package lxd. Preparing to unpack .../20-lxd_3.0.3-0ubuntu1~18.04.2_amd64.deb ... Adding system user `lxd' (UID 105) ... Adding new user `lxd' (UID 105) with group `nogroup' ... Creating home directory `/var/lib/lxd/' ... Adding group `lxd' (GID 109) ... Done. Unpacking lxd (3.0.3-0ubuntu1~18.04.2) ... ... Setting up liblxc1 (3.0.3-0ubuntu1~18.04.1) ... Setting up liblxc-common (3.0.3-0ubuntu1~18.04.1) ... apparmor.service is not active, cannot reload. invoke-rc.d: initscript apparmor, action "reload" failed. Setting up lxd (3.0.3-0ubuntu1~18.04.2) ... ... $ lxc exec lp1959047 -- lxc exec c1 -- journalctl -b0 --grep 'Failed to set up namespace' -- No entries -- So it worked, thanks! ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in lxd source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Impish: Confirmed Bug description: [Impact] Ubuntu carries a patch on top of systemd [a] to silence namespace set up failures. This is meant as a workaround for a bug in the LXD version shipped in Ubuntu 18.04. Masking namespace set up
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
** Description changed: [Impact] Ubuntu carries a patch on top of systemd [a] to silence namespace set up failures. This is meant as a workaround for a bug in the LXD version shipped in Ubuntu 18.04. Masking namespace set up failures creates a false sense of security for the user/admin. As mentioned in comment #1, systemd upstream explains that silencing this kind of error is dangerous and should be avoided. Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces to work inside containers. This is the goal of this SRU. Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would be possible to drop the Ubuntu-specific patch for systemd [a]. This is however *not an immediate concern for this SRU*. [Test Plan] 1) Create a 18.04 VM: $ lxc launch images:ubuntu/18.04 lp1959047 --vm $ sleep 30 # give it time to boot + + 1.5) Enable bionic-proposed: + $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse" | lxc file push - lp1959047/etc/apt/sources.list.d/proposed.list 2) Install and initialize LXD in it: $ lxc exec lp1959047 -- apt-get update $ lxc exec lp1959047 -- apt-get install -y lxd $ lxc exec lp1959047 -- lxd init --auto 3) Create a Jammy container and enable systemd debugging: $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1 $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init systemd.log_level=debug' $ lxc exec lp1959047 -- lxc start c1 4) Check if namespace set up failures are logged: $ lxc exec lp1959047 -- lxc exec c1 -- journalctl -b0 --grep 'Failed to set up namespace' Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace" messages wouldn't be there. [Where problems could occur] The LXD fix changes the Apparmor profile used for containers. This essentially loosen the mount restrictions applied to containers. Weakening the Apparmor profile could make it easier for a process in the container to do damage that would have otherwise been blocked. On the other hand, this allows making use of namespaces/sandboxing inside the container. Upstream LXD has the fix since 2019 which make it less likely to run into problems with the backport. The backported fix was also tested manually to ensure LXD still behaved normally and that it avoided the namespace set up failures in Jammy containers. [a]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy [b]: https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f [Initial bug description] The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu
[Touch-packages] [Bug 423607] Re: ubuntu-minimal should depends on dhcp3-client | dhcp-client instead of only dhcp3-client
It's been a while that ubuntu-minimal depends on isc-dhcp-client: $ apt-cache show ubuntu-minimal | grep Depends | grep dhcp Depends: adduser, apt, apt-utils, console-setup, debconf, debconf-i18n, e2fsprogs, eject, init, iproute2, iputils-ping, isc-dhcp-client, kbd, kmod, less, locales, lsb-release, mawk, mount, netbase, netcat-openbsd, netplan.io, passwd, procps, python3, sensible-utils, sudo, tzdata, ubuntu-advantage-tools, ubuntu-keyring, udev, vim-tiny, whiptail I checked on Focal with ubuntu-minimal version 1.450.2 but the fix possibly came earlier than that. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/423607 Title: ubuntu-minimal should depends on dhcp3-client | dhcp-client instead of only dhcp3-client Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ubuntu-minimal should depends on dhcp3-client | dhcp-client instead of only dhcp3-client since user can use pump or dhcpcd or udhcpc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/423607/+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 1966562] [NEW] ubuntu-minimal should not depend on isc-dhcp-client
Public bug reported: ubuntu-minimal already depends on `init` which depends on `systemd-sysv` which depends on `systemd` which comes with `systemd-networkd` that has a DHCP client in it. Having the isc-dhcp-client package feels redundant. # Additional information $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 $ apt-cache policy ubuntu-minimal ubuntu-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966562 Title: ubuntu-minimal should not depend on isc-dhcp-client Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-minimal already depends on `init` which depends on `systemd- sysv` which depends on `systemd` which comes with `systemd-networkd` that has a DHCP client in it. Having the isc-dhcp-client package feels redundant. # Additional information $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ apt-cache policy ubuntu-minimal ubuntu-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966562/+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 1959047] Re: systemd ignores RootDirectory option in .service units
@stgraber, I added the SRU template, let me know if something's off. Thanks! ** Description changed: + [Impact] + + Ubuntu carries a patch on top of systemd [a] to silence + namespace set up failures. This is meant as a workaround + for a bug in the LXD version shipped in Ubuntu 18.04. + + Masking namespace set up failures creates a false sense of + security for the user/admin. + + As mentioned in comment #1, systemd upstream explains that silencing + this kind of error is dangerous and should be avoided. + + Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces + to work inside containers. This is the goal of this SRU. + + Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would + be possible to drop the Ubuntu-specific patch for systemd [a]. This + is however *not an immediate concern for this SRU*. + + [Test Plan] + + 1) Create a 18.04 VM: + $ lxc launch images:ubuntu/18.04 lp1959047 --vm + $ sleep 30 # give it time to boot + + 2) Install and initialize LXD in it: + $ lxc exec lp1959047 -- apt-get update + $ lxc exec lp1959047 -- apt-get install -y lxd + $ lxc exec lp1959047 -- lxd init --auto + + 3) Create a Jammy container and enable systemd debugging: + $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1 + $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init systemd.log_level=debug' + $ lxc exec lp1959047 -- lxc start c1 + + 4) Check if namespace set up failures are logged: + $ lxc exec lp1959047 -- lxc exec c1 -- journalctl -b0 --grep 'Failed to set up namespace' + Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied + + If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace" + messages wouldn't be there. + + [Where problems could occur] + + The LXD fix changes the Apparmor profile used for containers. This essentially + loosen the mount restrictions applied to containers. + + Weakening the Apparmor profile could make it easier for a process in the container + to do damage that would have otherwise been blocked. On the other hand, this + allows making use of namespaces/sandboxing inside the container. + + Upstream LXD has the fix since 2019 which make it less likely to run into + problems with the backport. + + The backported fix was also tested manually to ensure LXD still behaved normally + and that it avoided the namespace set up failures in Jammy containers. + + [a]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy + [b]: https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f + + [Initial bug description] + The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: - # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a - - You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. + You should have a chroot environment in the specified RootDirectory, + even though you can still deduce if systemd attempted to chroot or not + from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. - Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25
[Touch-packages] [Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Thanks @stgraber for providing 3.0.3-0ubuntu1~18.04.2~ppa1 (via https://launchpad.net/~stgraber/+archive/experimental). This allowed me to create a Bionic VM in which I created a Jammy container. The Jammy was then configured to have systemd in debug mode: root@bionic-vm:~# lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init systemd.log_level=debug' Then in the container, looking for the "Failed to set up namespace" messaged added by the Ubuntu patch on top of systemd: root@c1:~# journalctl -b0 --grep 'Failed to set up namespace' Mar 24 20:26:32 c1 systemd[100]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[103]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[110]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[113]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:33 c1 systemd[114]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:33 c1 systemd[107]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Now if LXD in the Bionic VM is upgraded from 3.0.3-0ubuntu1~18.04.2 to 3.0.3-0ubuntu1~18.04.2~ppa1: root@bionic-vm:~# apt-get dist-upgrade -y ... The following packages will be upgraded: lxd lxd-client 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 8,335 kB of archives. After this operation, 20.5 kB of additional disk space will be used. Get:1 https://ppa.launchpadcontent.net/stgraber/experimental/ubuntu bionic/main amd64 lxd amd64 3.0.3-0ubuntu1~18.04.2~ppa1 [5,260 kB] Get:2 https://ppa.launchpadcontent.net/stgraber/experimental/ubuntu bionic/main amd64 lxd-client amd64 3.0.3-0ubuntu1~18.04.2~ppa1 [3,075 kB] Fetched 8,335 kB in 4s (1,990 kB/s) ... The namespace setup no longer fails as we see no *new* entries in the journal: root@c1:~# journalctl -b0 --grep 'Failed to set up namespace'containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[100]: systemd-udevd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[103]: systemd-networkd.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[110]: systemd-logind.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:32 c1 systemd[113]: systemd-resolved.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:33 c1 systemd[114]: systemd-hostnamed.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied Mar 24 20:26:33 c1 systemd[107]: e2scrub_reap.service: Failed to set up namespace, assuming containerized execution, ignoring: Permission denied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in lxd source package in Bionic: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Impish: New Bug description: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]:
[Touch-packages] [Bug 1966127] [NEW] ubuntu-desktop-minimal pulls gnome-session which is in universe
Public bug reported: ubuntu-desktop-minimal is in main but installing it pulls gnome-session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-desktop-minimal is in main but installing it pulls gnome- session from universe. Here is how to reproduce it: 1) Create a Jammy VM: $ lxc launch images:ubuntu/jammy jammy-vm --vm 2) Enter the Jammy VM: $ lxc shell jammy-vm 3) Install ubuntu-desktop-minimal root@jammy-vm:~# apt-get update ... root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal ... Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 1:2.0.5-1 [94.7 kB] Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 2:22.1.0-1 [932 kB] Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 42.0-1ubuntu1 [15.2 kB] Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 yaru-theme-gnome-shell all 22.04.2 [66.4 kB] Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 42.0-1ubuntu1 [5,418 B] ... 4) Check the policy of packages: root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session ubuntu-desktop-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Both should be from main. Additional information: root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966127/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory
It works: # witness the original bug while running `sudo -i` in another session: sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam Sep 28 16:56:52 xeon sudo: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Sep 28 16:56:53 xeon sudo: pam_unix(sudo:session): session opened for user root by (uid=0) # install from -proposed: root@xeon:~# apt-get install libpam0g libpam-runtime libpam-modules-bin libpam-modules Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: libpam-doc (1.3.1-5ubuntu4.3) Recommended packages: update-motd (3.6-0ubuntu6.1) The following packages will be upgraded: libpam-modules (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3) libpam-modules-bin (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3) libpam-runtime (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3) libpam0g (1.3.1-5ubuntu4.2 => 1.3.1-5ubuntu4.3) 4 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 394 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam0g amd64 1.3.1-5ubuntu4.3 [55.4 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-modules-bin amd64 1.3.1-5ubuntu4.3 [41.2 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-modules amd64 1.3.1-5ubuntu4.3 [260 kB] Get:4 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-runtime all 1.3.1-5ubuntu4.3 [37.3 kB] Fetched 394 kB in 1s (477 kB/s) Preconfiguring packages ... (Reading database ... 53805 files and directories currently installed.) Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.3_amd64.deb ... Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ... Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ... (Reading database ... 53805 files and directories currently installed.) Preparing to unpack .../libpam-modules-bin_1.3.1-5ubuntu4.3_amd64.deb ... Unpacking libpam-modules-bin (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ... Setting up libpam-modules-bin (1.3.1-5ubuntu4.3) ... (Reading database ... 53805 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.3_amd64.deb ... Unpacking libpam-modules:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ... Setting up libpam-modules:amd64 (1.3.1-5ubuntu4.3) ... (Reading database ... 53805 files and directories currently installed.) Preparing to unpack .../libpam-runtime_1.3.1-5ubuntu4.3_all.deb ... Unpacking libpam-runtime (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ... Setting up libpam-runtime (1.3.1-5ubuntu4.3) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.3) ... ... # confirm the fix by opening another session with `sudo -i`: sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam Sep 28 18:28:51 xeon sudo: pam_unix(sudo:session): session opened for user root by (uid=0) ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1860826 Title: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory Status in pam package in Ubuntu: Fix Released Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Won't Fix Status in pam package in Debian: Fix Released Bug description: [Impact] Removal of the /etc/securetty file from the system results in useless log messages whenever pam_unix is invoked, which for some systems is quite a lot of logging. /etc/securetty is not coming back, and this is not an error. [Test Plan] 1. Run 'sudo -s'. Confirm that 'journalctl | grep sudo.*securetty' returns a line 'sudo[...]: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory'. 2. Install libpam-modules update from -proposed. 3. Confirm that 'grep nullok_secure' /etc/pam.d/common-auth returns no lines. 4. Run 'sudo -k'. 5. Run 'sudo -s' again. 6. Confirm that sudo succeeds and gives you a root shell. 7. Confirm that 'journalctl | grep sudo.*securetty' does not show any new lines. [Where problems could occur] PAM is a sensitive package because it's used in all authentication operations on the system. A bug here could render a user unable to log in to their system. Risks are mitigated by: - including a patch that treats the obsolete 'nullok_secure' as an alias for 'nullok' to ensure any user-edited configurations continue to work rather than throwing errors about unknown options - editing the system-managed /etc/pam.d/common-auth config to use 'nullok' instead of 'nullok_secure' for future compatibility. Because we are editing the system config, this could also cause issues on future upgrades with
[Touch-packages] [Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
> these can be added fairly soon.
> https://gitlab.com/apparmor/apparmor/-/merge_requests/684
>
> though that is just landing it upstream and I am not sure when the
> next ubuntu upload will be
At least on 20.04, the profile comes from the firefox package, not the
apparmor one:
$ dpkg -S /etc/apparmor.d/usr.bin.firefox
firefox: /etc/apparmor.d/usr.bin.firefox
Maybe I'm missing something?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1777070
Title:
firefox plugin libwidevinecdm.so crashes due to apparmor denial
Status in apparmor package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1
Running firefix, then going to netflix.com and attempting to play a
movie. The widevinecdm plugin crashes, the following is found in
syslog:
Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in
libxul.so[7fcdfb77a000+6111000]
Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in
libxul.so[7fe3b34c7000+6111000]
Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in
libxul.so[7fcf307b3000+6111000]
Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328:
[hamster] bad exit code 1
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400
audit(1529046809.263:253): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:29 xplt kernel: [301358.227844] plugin-containe[16188]: segfault
at 0 ip 7fe5667c66af sp 7fffe8cc0da8 error 6 in
libxul.so[7fe564499000+6111000]
Jun 15 19:13:31 xplt kernel: [301360.574177] audit:
[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
Verification for Groovy (246.6-1ubuntu1.5) # Initial repro on groovy: root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf 6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf /etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823 1625844823 0 4096 root@groovy:~# ip link set eth0 down; sleep 1; ip link set eth0 up root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf 6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf /etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844838 1625844837 1625844837 0 4096 # Upgrading to -proposed root@groovy:~# apt update && apt-get dist-upgrade -V Get:1 http://security.ubuntu.com/ubuntu groovy-security InRelease [110 kB] Hit:2 http://archive.ubuntu.com/ubuntu groovy InRelease Get:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease [115 kB] Get:4 http://archive.ubuntu.com/ubuntu groovy-proposed InRelease [269 kB] Get:5 http://archive.ubuntu.com/ubuntu groovy-updates/universe amd64 Packages [450 kB] Get:6 http://archive.ubuntu.com/ubuntu groovy-proposed/restricted amd64 Packages [100 kB] Get:7 http://archive.ubuntu.com/ubuntu groovy-proposed/restricted Translation-en [14.7 kB] Get:8 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages [83.6 kB] Get:9 http://archive.ubuntu.com/ubuntu groovy-proposed/main Translation-en [22.3 kB] Get:10 http://archive.ubuntu.com/ubuntu groovy-proposed/multiverse amd64 Packages [11.6 kB] Get:11 http://archive.ubuntu.com/ubuntu groovy-proposed/multiverse Translation-en [5,932 B] Get:12 http://archive.ubuntu.com/ubuntu groovy-proposed/universe amd64 Packages [24.9 kB] Get:13 http://archive.ubuntu.com/ubuntu groovy-proposed/universe Translation-en [12.8 kB] Fetched 1,220 kB in 1s (840 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 12 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libc-bin (2.32-0ubuntu3 => 2.32-0ubuntu3.2) libc6 (2.32-0ubuntu3 => 2.32-0ubuntu3.2) libgnutls30 (3.6.15-4ubuntu2 => 3.6.15-4ubuntu2.1) libnss-systemd (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) libpam-systemd (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) libsystemd0 (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) libudev1 (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) locales (2.32-0ubuntu3 => 2.32-0ubuntu3.2) systemd (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) systemd-sysv (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) systemd-timesyncd (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) udev (246.6-1ubuntu1.4 => 246.6-1ubuntu1.5) 12 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 14.1 MB of archives. After this operation, 3,072 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libc6 amd64 2.32-0ubuntu3.2 [2,680 kB] Get:2 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libc-bin amd64 2.32-0ubuntu3.2 [628 kB] Get:3 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libnss-systemd amd64 246.6-1ubuntu1.5 [94.6 kB] Get:4 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 udev amd64 246.6-1ubuntu1.5 [1,340 kB] Get:5 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libudev1 amd64 246.6-1ubuntu1.5 [69.2 kB] Get:6 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 systemd-sysv amd64 246.6-1ubuntu1.5 [10.3 kB] Get:7 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 systemd-timesyncd amd64 246.6-1ubuntu1.5 [28.2 kB] Get:8 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libpam-systemd amd64 246.6-1ubuntu1.5 [179 kB] Get:9 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libgnutls30 amd64 3.6.15-4ubuntu2.1 [770 kB] Get:10 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 systemd amd64 246.6-1ubuntu1.5 [4,166 kB] Get:11 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 libsystemd0 amd64 246.6-1ubuntu1.5 [274 kB] Get:12 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 locales all 2.32-0ubuntu3.2 [3,879 kB] Fetched 14.1 MB in 4s (3,313 kB/s) Preconfiguring packages ... (Reading database ... 14742 files and directories currently installed.) Preparing to unpack .../libc6_2.32-0ubuntu3.2_amd64.deb ... Unpacking libc6:amd64 (2.32-0ubuntu3.2) over (2.32-0ubuntu3) ... Setting up libc6:amd64 (2.32-0ubuntu3.2) ... (Reading database ... 14742 files and directories currently installed.) Preparing to unpack .../libc-bin_2.32-0ubuntu3.2_amd64.deb ... Unpacking libc-bin (2.32-0ubuntu3.2) over (2.32-0ubuntu3) ... Setting up libc-bin (2.32-0ubuntu3.2) ... (Reading database ... 14742 files and directories currently installed.) Preparing to unpack .../libnss-systemd_246.6-1ubuntu1.5_amd64.deb ... Unpacking libnss-systemd:amd64
[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
Verification for Focal (245.4-4ubuntu3.8) # Initial repro on focal: root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf /etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273 1625844273 0 4096 root@focal:~# ip link set eth0 down; sleep 1; ip link set eth0 up root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf /etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844310 1625844308 1625844308 0 4096 # Upgrading to -proposed root@focal:~# apt update && apt-get dist-upgrade -V Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-proposed InRelease [267 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,086 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [239 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [840 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/restricted amd64 Packages [191 kB] Get:9 http://archive.ubuntu.com/ubuntu focal-proposed/restricted Translation-en [27.2 kB] Get:10 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages [203 kB] Get:11 http://archive.ubuntu.com/ubuntu focal-proposed/main Translation-en [42.2 kB] Get:12 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse amd64 Packages [18.2 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse Translation-en [6,732 B] Get:14 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages [56.2 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-proposed/universe Translation-en [24.5 kB] Fetched 3,229 kB in 2s (1,428 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 9 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libgnutls30 (3.6.13-2ubuntu1.3 => 3.6.13-2ubuntu1.5) libnss-systemd (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) libpam-systemd (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) libsystemd0 (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) libudev1 (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) systemd (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) systemd-sysv (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) systemd-timesyncd (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) udev (245.4-4ubuntu3.7 => 245.4-4ubuntu3.8) 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 6,672 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.8 [96.1 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.8 [1,365 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.8 [78.4 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.8 [10.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.8 [28.1 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.8 [186 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libgnutls30 amd64 3.6.13-2ubuntu1.5 [828 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.8 [3,810 kB] Get:9 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.8 [271 kB] Fetched 6,672 kB in 3s (2,541 kB/s) (Reading database ... 14718 files and directories currently installed.) Preparing to unpack .../libnss-systemd_245.4-4ubuntu3.8_amd64.deb ... Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.8) over (245.4-4ubuntu3.7) ... Preparing to unpack .../udev_245.4-4ubuntu3.8_amd64.deb ... Unpacking udev (245.4-4ubuntu3.8) over (245.4-4ubuntu3.7) ... Preparing to unpack .../libudev1_245.4-4ubuntu3.8_amd64.deb ... Unpacking libudev1:amd64 (245.4-4ubuntu3.8) over (245.4-4ubuntu3.7) ... Setting up libudev1:amd64 (245.4-4ubuntu3.8) ... (Reading database ... 14718 files and directories currently installed.) Preparing to unpack .../systemd-sysv_245.4-4ubuntu3.8_amd64.deb ... Unpacking systemd-sysv (245.4-4ubuntu3.8) over (245.4-4ubuntu3.7) ... Preparing to unpack .../systemd-timesyncd_245.4-4ubuntu3.8_amd64.deb ... Unpacking systemd-timesyncd (245.4-4ubuntu3.8) over (245.4-4ubuntu3.7) ... Preparing to unpack .../libpam-systemd_245.4-4ubuntu3.8_amd64.deb ...
[Touch-packages] [Bug 1891215] Re: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891215
Title:
systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for
every IPv6 RA received
Status in systemd:
Unknown
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
New
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Committed
Status in systemd source package in Hirsute:
Fix Committed
Bug description:
[impact]
networking changes, like RA events, can cause systemd-resolved to re-
write the resolv.conf file, even if the contents didn't change,
resulting in unnecessary increased amount of inotify events
[test case]
see original description for ipv6ra-related reproducer, or simple
reproducer here:
configure networkd with some config for (e.g.) eth0, but not a config
that would result in /etc/resolv.conf changing when the interface goes
up/down - for example, use static config with no DNS search domains.
Then bring eth0 up/down while observing the md5sum (file content) does
not change but the mtime does change.
root@lp1891215-h:~# ip l set down dev eth0
root@lp1891215-h:~# md5sum /etc/resolv.conf
db23e80078515192c312e5f321ff0340 /etc/resolv.conf
root@lp1891215-h:~# stat -t -L /etc/resolv.conf
/etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238218 1625238216
1625238216 0 4096
root@lp1891215-h:~# ip l set up dev eth0
root@lp1891215-h:~# md5sum /etc/resolv.conf
db23e80078515192c312e5f321ff0340 /etc/resolv.conf
root@lp1891215-h:~# stat -t -L /etc/resolv.conf
/etc/resolv.conf 740 8 81a4 101 103 fc 188 1 0 0 1625238227 1625238226
1625238226 0 4096
[regression potential]
regressions would result in incorrect or missing data in the
resolv.conf file, possibly resulting in dns failures or errors
[scope]
this is needed for h and eralier
this is (potentially) fixed upstream by
f3e1f00d03445911ee73729219cea88c8a70c612 which in first included in
v248, so this is needed in hirsute and earlier
[original description]
# Issue description:
On 2 Linode VMs that are used as lxd hosts, we noticed that
/run/systemd/resolve/*resolv.conf were re-created quite frequently (~
once per second). We noticed because of the log noise from lxd's
dnsmasq instance using inotify to watch the target of /etc/resolv.conf
(which points to the stub-resolv.conf in our case). This was (wrongly)
reported as a lxd bug (https://github.com/lxc/lxd/issues/7765) until
it became apparent it was more likely to be a problem with
systemd(-resolved)?.
The log noise is the observable problem that would be nice to see
addressed:
root@lxd02:~# uptime
17:55:48 up 9:52, 1 user, load average: 0.18, 0.11, 0.05
root@lxd02:~# journalctl -b0 | grep -cF dnsmasq
158609
Upon further investigation, it seems that systemd-resolved re-creates
the resolv.conf and stub-resolv.conf files whenever an IPv6 RA is
received.
1) One can observe that by setting systemd-resolved's service in debug
mode:
$ sudo systemctl edit systemd-resolved
and in the editor that is opened, add and save this content:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
then restart systemd-resolved and watch the logs scroll by with:
$ journalctl -fu systemd-resolved
3) In another terminal, watch the files be recreated with:
watch -d -n 0.1 stat /run/systemd/resolve/stub-resolv.conf
3) In yet another terminal, run a packet capture and watch "ICMP6,
router advertisement" messages come by:
sudo tcpdump -ni eth0 icmp6
You will see that every time a RA packet comes in, resolved's journal
will log this:
Aug 11 17:33:55 lxd02 systemd-resolved[15368]: Sent message
type=signal sender=n/a destination=n/a path=/org/freedesktop/resolve1
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=244 reply_cookie=0 signature=sa{sv}as error-name=n/a error-
message=n/a
And the stat monitoring terminal will blink to highlight the new inode
and timestamps of the freshly replaced stub-resolv.conf file.
# Additional information:
root@lxd02:~# lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
root@lxd02:~# apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.2
Candidate: 245.4-4ubuntu3.2
Version table:
*** 245.4-4ubuntu3.2 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
245.4-4ubuntu3 500
500
