[Touch-packages] [Bug 1860500] [NEW] consider disabling apt-secure's Label check in Ubuntu
Public bug reported: As of 1.5 (per apt-secure(8)) apt checks and warns if a repository's Label value changes. This probably makes sense for Debian, where folks may be tracking stable instead of buster, and will want to be warned when stable starts pointing somewhere else. However, Ubuntu doesn't have such repository aliases and, furthermore, for PPAs, the Label value is populated from the "display name" of the PPA. This means that a PPA owner, fixing what they may assume is a simple typo, will require their users to take action before they receive further updates from the PPA, which is less than ideal. Please consider disabling this check by default in Ubuntu, if only for PPAs. ** 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/1860500 Title: consider disabling apt-secure's Label check in Ubuntu Status in apt package in Ubuntu: New Bug description: As of 1.5 (per apt-secure(8)) apt checks and warns if a repository's Label value changes. This probably makes sense for Debian, where folks may be tracking stable instead of buster, and will want to be warned when stable starts pointing somewhere else. However, Ubuntu doesn't have such repository aliases and, furthermore, for PPAs, the Label value is populated from the "display name" of the PPA. This means that a PPA owner, fixing what they may assume is a simple typo, will require their users to take action before they receive further updates from the PPA, which is less than ideal. Please consider disabling this check by default in Ubuntu, if only for PPAs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1860500/+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 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: In Progress Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+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 1802804] [NEW] crash due to assertion failure on busy VM host
Public bug reported: Version: 1:4.2.8p4+dfsg-3ubuntu5.9 We've observed the following crash on an Ubuntu 16.04 s390x nova-compute host, apparently related to the VMs network interfaces coming and going: Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8 [fe80::2c99:58ff:fefa:b081%616530]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542171 qvb8dd4fc29-b8 [fe80::b809:4ff:fefc:1b17%616531]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542172 tap3ca379f2-d1 [fe80::fc16:3eff:fe6e:5ef7%616532]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542173 tap8dd4fc29-b8 [fe80::fc16:3eff:fedf:c527%616533]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542174 qvo92509b39-cf [fe80::a489:5ff:fe82:d27%616535]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542175 qvb92509b39-cf [fe80::d8b1:d4ff:fe48:a44d%616536]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Deleting interface #542166 tap3ca379f2-d1, fe80::fc16:3eff:fe6e:5ef7%616526#123, interface stats: received=0, sent=0, dropped=0, active_time=57 secs Nov 11 01:40:34 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver Nov 11 01:40:37 s0lp3 ntpd[2426]: bind(122) AF_INET6 fe80::fc16:3eff:fea1:a01c%616537#123 flags 0x11 failed: Cannot assign requested address Nov 11 01:40:37 s0lp3 ntpd[2426]: unable to create socket on tap92509b39-cf (542176) for fe80::fc16:3eff:fea1:a01c%616537#123 Nov 11 01:40:37 s0lp3 ntpd[2426]: failed to init interface for address fe80::fc16:3eff:fea1:a01c%616537 Nov 11 01:40:39 s0lp3 ntpd[2426]: Listen normally on 542177 tap92509b39-cf [fe80::fc16:3eff:fea1:a01c%616537]:123 Nov 11 01:40:39 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver Nov 11 01:40:52 s0lp3 ntpd[2426]: Deleting interface #542172 tap3ca379f2-d1, fe80::fc16:3eff:fe6e:5ef7%616532#123, interface stats: received=0, sent=0, dropped=0, active_time=18 secs Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542163 qvo3ca379f2-d1, fe80::14ad:deff:fe5b:4165%616523#123, interface stats: received=0, sent=0, dropped=0, active_time=81 secs Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542164 qvb3ca379f2-d1, fe80::7cf6:4dff:fe23:b119%616524#123, interface stats: received=0, sent=0, dropped=0, active_time=81 secs Nov 11 01:41:05 s0lp3 ntpd[2426]: ./../lib/isc/unix/ifiter_getifaddrs.c:163: INSIST(ifa->ifa_name != ((void *)0)) failed Nov 11 01:41:05 s0lp3 ntpd[2426]: exiting (due to assertion failure) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1802804 Title: crash due to assertion failure on busy VM host Status in ntp package in Ubuntu: New Bug description: Version: 1:4.2.8p4+dfsg-3ubuntu5.9 We've observed the following crash on an Ubuntu 16.04 s390x nova- compute host, apparently related to the VMs network interfaces coming and going: Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8 [fe80::2c99:58ff:fefa:b081%616530]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542171 qvb8dd4fc29-b8 [fe80::b809:4ff:fefc:1b17%616531]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542172 tap3ca379f2-d1 [fe80::fc16:3eff:fe6e:5ef7%616532]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542173 tap8dd4fc29-b8 [fe80::fc16:3eff:fedf:c527%616533]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542174 qvo92509b39-cf [fe80::a489:5ff:fe82:d27%616535]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542175 qvb92509b39-cf [fe80::d8b1:d4ff:fe48:a44d%616536]:123 Nov 11 01:40:34 s0lp3 ntpd[2426]: Deleting interface #542166 tap3ca379f2-d1, fe80::fc16:3eff:fe6e:5ef7%616526#123, interface stats: received=0, sent=0, dropped=0, active_time=57 secs Nov 11 01:40:34 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver Nov 11 01:40:37 s0lp3 ntpd[2426]: bind(122) AF_INET6 fe80::fc16:3eff:fea1:a01c%616537#123 flags 0x11 failed: Cannot assign requested address Nov 11 01:40:37 s0lp3 ntpd[2426]: unable to create socket on tap92509b39-cf (542176) for fe80::fc16:3eff:fea1:a01c%616537#123 Nov 11 01:40:37 s0lp3 ntpd[2426]: failed to init interface for address fe80::fc16:3eff:fea1:a01c%616537 Nov 11 01:40:39 s0lp3 ntpd[2426]: Listen normally on 542177 tap92509b39-cf [fe80::fc16:3eff:fea1:a01c%616537]:123 Nov 11 01:40:39 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver Nov 11 01:40:52 s0lp3 ntpd[2426]: Deleting interface #542172 tap3ca379f2-d1, fe80::fc16:3eff:fe6e:5ef7%616532#123, interface stats: received=0, sent=0, dropped=0, active_time=18 secs Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542163 qvo3ca379f2-d1, fe80::14ad:deff:fe5b:4165%616523#123, interface stats: received=0, sent=0, dropped=0, active_time=81 secs Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542
[Touch-packages] [Bug 1772222] [NEW] dangling symlink in /etc/rsyslog.d breaks rsyslogd
Public bug reported: Since upgrading from artful to bionic, I noticed that /var/log/kern.log, etc., were not being updated on my machine. In comparing to another machine running a fresh install of bionic, I discovered that this seems to be the culprit: [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf lrwxrwxrwx 1 root root 45 Jun 14 2017 /etc/rsyslog.d/99-conjure-up.conf -> /usr/share/conjure-up/conjure-up-rsyslog.conf [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such file or directory [agnew(etc)] _ Before deletion: [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. [agnew(etc)] _ After deletion: [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf [agnew(etc)] sudo service rsyslog restart [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. rsyslogd 30686 syslog8w REG 253,122782 15213384 /var/log/syslog rsyslogd 30686 syslog9w REG 253,1 2065 15219687 /var/log/auth.log [agnew(etc)] _ It didn't occur to me to check the service status until writing this bug report, but in fact it does report the problem on startup: May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file /etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file or directory '/etc/rsyslog.d/99-conjure May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active actions configured. Inputs will run, but no output whatsoever is created. [v8.32.0 try http://www.rsyslog.com However, it's unlikely this warning will be discovered until it's too late, if ever -- consider a remote syslogging setup on a machine that has since been decommissioned or reinstalled -- and so it would probably better for rsyslogd to cope with dangling symlinks. Indeed, given the age of the symlink, this is a regression from artful or earlier. ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Affects: rsyslog (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu Bionic) Importance: Undecided Status: New -- 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/177 Title: dangling symlink in /etc/rsyslog.d breaks rsyslogd Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Bionic: New Bug description: Since upgrading from artful to bionic, I noticed that /var/log/kern.log, etc., were not being updated on my machine. In comparing to another machine running a fresh install of bionic, I discovered that this seems to be the culprit: [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf lrwxrwxrwx 1 root root 45 Jun 14 2017 /etc/rsyslog.d/99-conjure-up.conf -> /usr/share/conjure-up/conjure-up-rsyslog.conf [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such file or directory [agnew(etc)] _ Before deletion: [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. [agnew(etc)] _ After deletion: [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf [agnew(etc)] sudo service rsyslog restart [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. rsyslogd 30686 syslog8w REG 253,122782 15213384 /var/log/syslog rsyslogd 30686 syslog9w REG 253,1 2065 15219687 /var/log/auth.log [agnew(etc)] _ It didn't occur to me to check the service status until writing this bug report, but in fact it does report the problem on startup: May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file /etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file or directory '/etc/rsyslog.d/99-conjure May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active actions configured. Inputs will run, but no output whatsoever is created. [v8.32.0 try http://www.rsyslog.com However, it's unlikely this warning will be discovered until it's too late, if ever -- consider a remote syslogging setup on a machine that has since been decommissioned or reinstalled -- and so it would probably better for rsyslogd to cope with dangling symlinks. Indeed, given the age of the symlink, this is a regression f
[Touch-packages] [Bug 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04
Also no longer able to reproduce when installing systemd from tvoss's PPA on a fresh VM (ubuntu-trusty-daily-amd64-server-20170131-disk1.img). -- 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/1660573 Title: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04 Status in snapd: Invalid Status in systemd package in Ubuntu: Invalid Status in systemd source package in Trusty: Triaged Bug description: I've installed snapd on an up-to-date Ubuntu 14.04 server system running LTS enablement kernel. After toying with snapd and some simple snaps I logged out (so far everything was OK). I returned to the console after a while (I'm not sure if I logged out but I suspect I had to) and I saw the login prompt. After entering my username a line was printed "System is booting up" and I was kicked back ot the login prompt (It never asked for my password). After rebooting the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+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 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04
I forgot to mention that pam_nologin prints "System is booting up." and fails non-root logins when /var/run/nologin exists, which is why that is relevant. :) -- 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/1660573 Title: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I've installed snapd on an up-to-date Ubuntu 14.04 server system running LTS enablement kernel. After toying with snapd and some simple snaps I logged out (so far everything was OK). I returned to the console after a while (I'm not sure if I logged out but I suspect I had to) and I saw the login prompt. After entering my username a line was printed "System is booting up" and I was kicked back ot the login prompt (It never asked for my password). After rebooting the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+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 1660573] Re: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04
With a freshly-booted up to date trusty VM (ubuntu-trusty-daily- amd64-server-20170130-disk1.img, then dist-upgraded for libssl1.0.0 openssl), simply installing systemd seems to be sufficient to cause the file to exist. ubuntu@pjdc-test:~$ ls -l /var/run/nologin ls: cannot access /var/run/nologin: No such file or directory ubuntu@pjdc-test:~$ sudo apt-get install systemd sudo: unable to resolve host pjdc-test Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd-journal0 Suggested packages: systemd-ui The following NEW packages will be installed: libsystemd-journal0 systemd 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,476 kB of archives. After this operation, 9,229 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main libsystemd-journal0 amd64 204-5ubuntu20.22 [51.0 kB] Get:2 http://prodstack-zone-2.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/main systemd amd64 204-5ubuntu20.22 [1,425 kB] Fetched 1,476 kB in 0s (17.6 MB/s) Selecting previously unselected package libsystemd-journal0:amd64. (Reading database ... 51302 files and directories currently installed.) Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.22_amd64.deb ... Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.22) ... Selecting previously unselected package systemd. Preparing to unpack .../systemd_204-5ubuntu20.22_amd64.deb ... Unpacking systemd (204-5ubuntu20.22) ... Processing triggers for ureadahead (0.100.0-16) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Setting up libsystemd-journal0:amd64 (204-5ubuntu20.22) ... Setting up systemd (204-5ubuntu20.22) ... Initializing machine ID from D-Bus machine ID. systemd start/running, process 3110 Processing triggers for libc-bin (2.19-0ubuntu6.9) ... Processing triggers for ureadahead (0.100.0-16) ... ubuntu@pjdc-test:~$ ls -l /var/run/nologin -rw-r--r-- 1 root root 21 Feb 1 01:31 /var/run/nologin ubuntu@pjdc-test:~$ -- 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/1660573 Title: "system is booting up" while trying to log in after installing snapd on ubuntu 14.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I've installed snapd on an up-to-date Ubuntu 14.04 server system running LTS enablement kernel. After toying with snapd and some simple snaps I logged out (so far everything was OK). I returned to the console after a while (I'm not sure if I logged out but I suspect I had to) and I saw the login prompt. After entering my username a line was printed "System is booting up" and I was kicked back ot the login prompt (It never asked for my password). After rebooting the problem went away. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1660573/+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
