[Touch-packages] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Note that same udevd rule exists as far back as 16.04 LTS:
ubuntu@xenial-test:~$ md5sum /lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4 /lib/udev/rules.d/40-vm-hotadd.rules
ubuntu@focal-test:~$ md5sum /usr/lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4 /usr/lib/udev/rules.d/40-vm-hotadd.rules
There is a previous bug,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457 which
addressed a different symptom but may be related.
--
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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
New
Bug description:
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1829968] Re: motd [on at least some instances] does not auto-update daily
I think this is related to https://github.com/systemd/systemd/issues/6680, specifically this comment: "hmm, so OnUnitActiveSec= operates relative to a unit becoming active, but Type=oneshot service units actually never become active, unless you combine them with RemainAfterExit=, hence the confusion... Type=oneshot units after all do stuff during their start-up and when that's complete they go down again, they never stay up continiously... Hence, combining Type=oneshot with OnUnitActiveSec= can't really work... This is a big underdocumented though" Which seems relevant, since: $ cat /lib/systemd/system/motd-news.service [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force -- 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/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: New Bug description: I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1829968] [NEW] motd [on at least some instances] does not auto-update daily
Public bug reported: I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #6680 https://github.com/systemd/systemd/issues/6680 -- 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/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: New Bug description: I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+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 1799702] [NEW] rsyslog fails to bind to tcp socket on restart
Public bug reported: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. ** Affects: rsyslog (Ubuntu) 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/1799702 Title: rsyslog fails to bind to tcp socket on restart Status in rsyslog package in Ubuntu: New Bug description: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1799702/+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 1799702] Re: rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart
I discussed with slangasek, who said: - The workaround is to either to configure systemd to restart rsyslog when the socket is available, or to have openvpn restart rsyslog when the VPN comes up. - The definitive fix would require rsyslogd to grow netlink support (or be managed by something else that does). For now, I'm working around this by using openvpn config. ** Summary changed: - rsyslog fails to bind to tcp socket on restart + rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart -- 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/1799702 Title: rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart Status in rsyslog package in Ubuntu: New Bug description: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1799702/+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 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified
This should be fixed as of Zesty based on the changelog in the Debian bug report, but remains an issue on Xenial. -- 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/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: New Status in rsync package in Debian: Unknown Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+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 1707136] [NEW] ryncd does not start when RSYNC_ENABLE is specified
Public bug reported: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Affects: rsync (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #764616 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764616 ** Also affects: rsync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764616 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/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: New Status in rsync package in Debian: Unknown Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+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 1576341] Re: systemd in degraded state on startup in LXD containers
And added a snapd task based on Nish's last comment. -- 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/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in nfs-utils package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: systemd in degraded state on startup in LXD containers
I've also noticed that nfs-common triggers a failure: root@sendmail:~# systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● run-rpc_pipefs.mount loaded failed failed RPC Pipe File System ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems ● lvm2-lvmetad.socketloaded failed failed LVM2 metadata daemon socket So I've added a task for nfs-common. The remaining failures I believe have been handled by this bug and are just unfixed in Xenial (and will likely remain unfixed right?) ** Also affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (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/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in nfs-utils package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1575779] Re: hostnamectl fails under lxd unpriv container
I also see this trigger with juju-deployed jenkins and jenkins-slave services against the lxd provider: apparmor="DENIED" operation="file_lock" profile="lxd-juju- 449b90-9_" pid=18662 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none -- 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/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Triaged Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:
ii dnsmasq-base2.75-1ubuntu0.16.04.1
amd64Small caching DNS proxy and DHCP/TFTP server
ii network-manager 1.2.6-0ubuntu0.16.04.1
amd64network management framework (daemon and
userspace tools)
And I am still seeing the same behaviour.
--
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/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
suspend/resume reconnects the interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Invalid
Status in dnsmasq source package in Xenial:
Fix Released
Status in network-manager source package in Xenial:
Invalid
Status in dnsmasq source package in Yakkety:
Fix Released
Status in network-manager source package in Yakkety:
Invalid
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
Hmm, just noticed this is likely the same patch merged here -- well, I'm
running the latest Xenial packages:
ii dnsmasq-base2.75-1ubuntu0.16.04.1
amd64Small caching DNS proxy and DHCP/TFTP server
ii network-manager 1.2.6-0ubuntu0.16.04.1
amd64network management framework (daemon and
userspace tools)
And I am still seeing the same behaviour.
--
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/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
suspend/resume reconnects the interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Invalid
Status in dnsmasq source package in Xenial:
Fix Released
Status in network-manager source package in Xenial:
Invalid
Status in dnsmasq source package in Yakkety:
Fix Released
Status in network-manager source package in Yakkety:
Invalid
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
FWIW I continue to face this issue specifically when suspending while
using the mobile broadband connection(predictable interface name
wwp0s29u1u4i6) on my x220. I noticed this thread:
https://mail.gnome.org/archives/networkmanager-
list/2016-September/msg0.html
Which notes this command is a workaround:
busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager
Reload "u" 4
and a link to an upstream bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1367772 -- I do wonder
whether the fix we've adopted has diverged from what's recommended
there, since it's reported to fix the OP's issue.
** Bug watch added: Red Hat Bugzilla #1367772
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
--
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/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
suspend/resume reconnects the interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Invalid
Status in dnsmasq source package in Xenial:
Fix Released
Status in network-manager source package in Xenial:
Invalid
Status in dnsmasq source package in Yakkety:
Fix Released
Status in network-manager source package in Yakkety:
Invalid
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Thanks, understood. Now is this is a fresh install or an upgrade, eproust? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1186662] Re: isc-dhcp-server fails to renew lease file
I don't think this bug still happens with 16.04 LTS. Can anyone who is seeing it reproduce from a from-scratch install? There could be an issue with upgrades, if people are actually still seeing this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1351814] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
This bug is quite annoying as it means that the modem-manager GUI will not run unless you do something like: mv ~/.local/share/modem-manager-gui ~/.local/share/modem-manager- gui.old The upstream bug is here: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?0.item.3.32.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351814 Title: manager crash: GLib-GObject-CRITICAL (ubutu 13) Status in Modem Manager Gui: Incomplete Status in modem-manager-gui package in Ubuntu: Expired Status in modemmanager package in Ubuntu: Invalid Bug description: When I insert my modem (huawei e153u) the aplication is closed: The error on console: Module applicable: Modem Manager <= 0.6.0/Wader (modmm_mm06.so) Module applicable: pppd >= 2.4.5 (modcm_pppd245.so) Connection manager: pppd >= 2.4.5 Modem manager: Modem Manager <= 0.6.0/Wader Device: huawei, E153, 11.609.18.00.279 [3] [44af59d16429bca0c4a77be00627e2d3] (modem-manager-gui:8350): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Device successfully opened Segmentation fault at address: 0x8 Stack trace: 1. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 2. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 3. /lib/x86_64-linux-gnu/libc.so.6(strftime_l+0x16) [0x7f597f77f9a6] 4. modem-manager-gui() [0x41b9e7] 5. modem-manager-gui() [0x41f372] 6. modem-manager-gui() [0x41f4f3] 7. modem-manager-gui() [0x423abd] 8. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x138) [0x7f59803c5188] 9. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21b1d) [0x7f59803d6b1d] I use ubuntu 13.10 thanks and sorry for my english. PD: the first time it works fine, but I restart the computer and not work more :/. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-02 (427 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True Package: modem-manager-gui 0.0.16-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Tags: saucy Uname: Linux 3.11.0-26-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-02 (434 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: modem-manager-gui 0.0.16-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-08-07 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-02 (434 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: modem-manager-gui 0.0.16-4~ppa1~ubuntu14.04.1~ppa1 [origin: LP-PPA-ginggs-testing] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: third-party-packages trusty Uname: Linux 3.13.0-32-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: Upgraded to trusty on 2014-08-07 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-06-02 (434 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: modem-manager-gui 0.0.16-4~ppa1~ubuntu14.04.1~ppa1 [origin: LP-PPA-ginggs-testing] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: third-party-packages trusty Uname: Linux 3.13.0-32-generic x86_64 UnreportableReason: Este no es un paquete oficial de Ubuntu. Desinstale cualquier paquete de terceros e inténtelo de nuevo. UpgradeStatus: Upgraded to trusty on 2014-08-07 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+bug/1351814/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
** Tags added: cdo-qa-blocker -- 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/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in systemd package in Ubuntu: Confirmed Bug description: I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411/+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 1589317] [NEW] Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy
Public bug reported: During an upgrade from a Trusty system to Xenial, I ended up with the following problem: Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ... depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic WARNING: missing /lib/modules/3.13.0-85-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cryptsetup: WARNING: failed to detect canonical device of /dev/nfs cryptsetup: WARNING: could not determine root device from /etc/fstab cp: cannot stat '/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-3.13.0-85-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Turns out this was directly caused by simplistic checking in the plymouth initramfs-tools hook: # wheezy if ls /usr/lib/x86_64-linux-gnu/pango/1* > /dev/null 2>&1 I want back and checked a backup of my original Trusty filesystem, and it indeed has an empty hierarchy here: kiko@gasolinux:/usr/lib/x86_64-linux-gnu/pango$ ls -lR .: total 4 drwxr-xr-x 3 root root 4096 Feb 26 2014 1.6.0/ ./1.6.0: total 4 drwxr-xr-x 2 root root 4096 Feb 27 2014 modules/ ./1.6.0/modules: total 0 This may be better handled by smarter code in the plymouth hook, or if the empty directory may have further consequences, by making the pango upgrade really clean up that directory. I solved the problem by removing the hierarchy and re-running apt-get -f install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpango1.0-0 1.36.3-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39 Uname: Linux 3.13.0-87-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 5 20:45:27 2016 SourcePackage: pango1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu-une -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1589317 Title: Upgrading to Xenial leaves empty /usr/lib/x86_64-linux-gnu/pango/ hierarchy Status in pango1.0 package in Ubuntu: New Bug description: During an upgrade from a Trusty system to Xenial, I ended up with the following problem: Removing linux-image-extra-3.13.0-85-generic (3.13.0-85.129) ... depmod: FATAL: could not load /boot/System.map-3.13.0-85-generic: No such file or directory run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-85-generic /boot/vmlinuz-3.13.0-85-generic update-initramfs: Generating /boot/initrd.img-3.13.0-85-generic WARNING: missing /lib/modules/3.13.0-85-generic Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/3.13.0-85-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory cryptsetup: WARNING: failed to detect canonical device of /dev/nfs cryptsetup: WARNING: could not determine root device from /etc/fstab cp: cannot stat '/usr/lib/x86_64-linux-gnu/pango/1.6.0/module-files.d/libpango1.0-0.modules': No such file or directory E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1. update-initramfs: failed for /boot/initrd.img-3.13.0-85-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-3.13.0-85-generic (--remove): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-extra-3.13.0-85-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Turns out this was directly caused by simplistic checking in the plymouth initramfs-tools hook: # wheezy if ls /u
[Touch-packages] [Bug 1556357] Re: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume?
I've run into this with my x220 which was recently upgraded to Xenial as well. It is not consistent; it happens at maybe 1 out of 3 suspend/resume cycles. Removing and reinserting the iwldvm module also fixes the issue, but kudos to Haw for noting that it doesn't seem to be a lower-level bug but rather in NM itself; as he suggests, a `sudo wpa_cli resume` triggers a reconnection. Toggling the kill switch does not cause a reconnection to happen, nor does disabling and reenabling wifi. The UI symptom is that the list of available networks in the dropdown does not update; either a single item or no item is displayed, and no reconnection happens (regardless of whether or not the item displayed is one which you have associated with before). -- 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/1556357 Title: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume? Status in network-manager package in Ubuntu: Confirmed Status in wpasupplicant package in Ubuntu: Confirmed Bug description: Hi, I'm constantly having issues where my WiFi connection doesn't re- establish after resuming from suspend. I think it may be a race where the interface isn't ready yet and systemd-sleep calls /lib/systemd /system-sleep/wpasupplicant (which is a wrapper to wpa_cli). I normally restart NetworkManager but then found that calling 'wpa_cli resume' works also. Here's the logs: | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked min/max coordinates: x [1024..5112], y [2024..4832] | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 562.709 msecs | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup. | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done. | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed. | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend. | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed anymore. Stopping. | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep. | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend. | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too. | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: wake requested (sleeping: yes enabled: yes) | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend. | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: waking up... | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' finished. | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: NetworkManager state is now DISCONNECTED | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to construct signal | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read interface p2p-dev-wlp3s0 flags: No such device | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: (wlp3s0): supplicant interface state: starting -> ready | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: Device 'wlp3s0' has no connection; scheduling activate_check in 0 seconds. | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Thanks, Haw --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo if
[Touch-packages] [Bug 1556357] Re: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume?
** Tags added: regression-release -- 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/1556357 Title: WiFi fails to resume after suspend; Race with wpasupplicant / wpa_cli resume? Status in network-manager package in Ubuntu: Confirmed Status in wpasupplicant package in Ubuntu: Confirmed Bug description: Hi, I'm constantly having issues where my WiFi connection doesn't re- establish after resuming from suspend. I think it may be a race where the interface isn't ready yet and systemd-sleep calls /lib/systemd /system-sleep/wpasupplicant (which is a wrapper to wpa_cli). I normally restart NetworkManager but then found that calling 'wpa_cli resume' works also. Here's the logs: | Mar 12 13:53:06 ragnar.local kernel: psmouse serio1: synaptics: quirked min/max coordinates: x [1024..5112], y [2024..4832] | Mar 12 13:53:06 ragnar.local kernel: PM: resume of devices complete after 562.709 msecs | Mar 12 13:53:06 ragnar.local kernel: PM: Finishing wakeup. | Mar 12 13:53:06 ragnar.local systemd[1]: Time has been changed | Mar 12 13:53:06 ragnar.local systemd[1066]: Time has been changed | Mar 12 13:53:06 ragnar.local kernel: Restarting tasks ... done. | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: System resumed. | Mar 12 13:53:06 ragnar.local systemd-sleep[29174]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory | Mar 12 13:53:06 ragnar.local systemd-sleep[29227]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. | Mar 12 13:53:06 ragnar.local systemd[1]: Started Suspend. | Mar 12 13:53:06 ragnar.local systemd[1]: sleep.target: Unit not needed anymore. Stopping. | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Sleep. | Mar 12 13:53:06 ragnar.local systemd[1]: Reached target Suspend. | Mar 12 13:53:06 ragnar.local systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too. | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: wake requested (sleeping: yes enabled: yes) | Mar 12 13:53:06 ragnar.local systemd[1]: Stopped target Suspend. | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: waking up... | Mar 12 13:53:06 ragnar.local systemd-logind[662]: Operation 'sleep' finished. | Mar 12 13:53:06 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:06 ragnar.local NetworkManager[23292]: (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] | Mar 12 13:53:06 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local kernel: iwlwifi :03:00.0: L1 Enabled - LTR Enabled | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: NetworkManager state is now DISCONNECTED | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: dbus: Failed to construct signal | Mar 12 13:53:07 ragnar.local wpa_supplicant[23157]: Could not read interface p2p-dev-wlp3s0 flags: No such device | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: (wlp3s0): supplicant interface state: starting -> ready | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] | Mar 12 13:53:07 ragnar.local NetworkManager[23292]: Device 'wlp3s0' has no connection; scheduling activate_check in 0 seconds. | Mar 12 13:53:07 ragnar.local kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready Thanks, Haw --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-24 (687 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: wpasupplicant PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sudo users _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] modified.conffile..etc.dnsmasq.d.network.manager: [modified] mtime.conffile..etc.NetworkManager.NetworkManager
[Touch-packages] [Bug 1548421] Re: python stacktrace during 'apport-bug'
Same here; upgraded today from Trusty to Xenial and crashed reporting
bug 1570966.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1548421
Title:
python stacktrace during 'apport-bug'
Status in apport package in Ubuntu:
Confirmed
Bug description:
smoser@milhouse:~/src/maas-images/trunk$ sudo apport-bug
/var/crash/libtesseract4.0.crash
[sudo] password for smoser:
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use
gi.require_version('Wnck', '3.0') before import to ensure that the right
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first.
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right
version gets loaded.
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 170, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 468, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.encode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 468, in
report['DpkgTerminalLog'] = '\n'.join([str(line.encode('utf-8')) for line
in lines])
AttributeError: 'bytes' object has no attribute 'encode'
seems like a python2 to python3 conversion bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportLog:
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashReports:
640:0:116:846362:2016-02-22 12:27:09.709648847 -0500:2016-02-22
12:27:10.709648847 -0500:/var/crash/libtesseract4.0.crash
644:0:116:0:2016-02-22 12:27:11.629635693 -0500:2016-02-22
12:27:11.629635693 -0500:/var/crash/libtesseract4.0.upload
CurrentDesktop: Unity
Date: Mon Feb 22 12:35:39 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (214 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1548421/+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 1570966] [NEW] package libglib2.0-0:amd64 2.48.0-1ubuntu4 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Triggered during upgrade from Trusty to Xenial. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.0-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 15 10:41:37 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-01-23 (813 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.0-1ubuntu4 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-15 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1570966 Title: package libglib2.0-0:amd64 2.48.0-1ubuntu4 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Triggered during upgrade from Trusty to Xenial. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.0-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 15 10:41:37 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-01-23 (813 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.0-1ubuntu4 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1570966/+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 1569099] [NEW] package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Public bug reported: This was easily fixed via an apt-get -f install, and there was no mention of libgcrypt20, so I don' t think it' s a dupe of but 1560797. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 11 11:20:26 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2012-01-26 (1537 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-11 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1569099 Title: package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: New Bug description: This was easily fixed via an apt-get -f install, and there was no mention of libgcrypt20, so I don' t think it' s a dupe of but 1560797. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 11 11:20:26 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2012-01-26 (1537 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569099/+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 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be
** Changed in: openssl (Ubuntu)
Status: Incomplete => In Progress
--
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/1552939
Title:
arm64 build doesn't use asm and is 4x-16x slower than it could be
Status in OpenSSL:
New
Status in openssl package in Ubuntu:
In Progress
Status in openssl package in Debian:
New
Bug description:
The openssl build for arm64 doesn't compile in the assembly that is
present in openssl as of version 1.0.2 for aarch64 because the debian-
targets.patch that is applied specifies a target that doesn't have
assembly. The line at issue is debian-arm64 target which needs
${no_asm} changed to ${aarch64_asm}:linux64. Running openssl speed
-evp aes-128-gcm shows a 4x-16x improvement in performance with this
change made and the package rebuilt. Other aes and sha variants show
similar performance gains by enabling asm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1552939/+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 972077] Re: apt repository disk format has race conditions
We had a report of a MAAS user yesterday with this issue affecting some of his deployments. He was not behind a proxy. He retried the deployment and it worked, but we'd like to avoid sporadic failures as much as possible so this would be nice to see addressed. ** Also affects: maas 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/972077 Title: apt repository disk format has race conditions Status in MAAS: New Status in apt package in Ubuntu: Confirmed Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (e.g. Releases-2), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * Releases-2, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/972077/+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 1403516] Re: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS)
Hmm, I wonder if putting this in a tmpfs might work around this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1403516 Title: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS) Status in eglibc package in Ubuntu: New Bug description: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+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 1403516] [NEW] nscd crashes upon sudo when hosts caching is enabled (NIS, NFS)
Public bug reported: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627:GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627:GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627:GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627:GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu-une -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1403516 Title: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS) Status in eglibc package in Ubuntu: New Bug description: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+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 1403516] Re: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS)
I've also noticed that with hosts cache enabled that lookups for the same name seem to always be reported as missing; here's the output of subsequent "ping gasolinux" commands: Wed 17 Dec 2014 11:42:02 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3642 Wed 17 Dec 2014 11:42:02 AM BRST - 3627:GETFDHST Wed 17 Dec 2014 11:42:02 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:02 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3642 Wed 17 Dec 2014 11:42:02 AM BRST - 3627:GETHOSTBYNAME (gasolinux) Wed 17 Dec 2014 11:42:02 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! Wed 17 Dec 2014 11:42:02 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3642 Wed 17 Dec 2014 11:42:02 AM BRST - 3627:GETHOSTBYADDR (192.168.99.14) Wed 17 Dec 2014 11:42:02 AM BRST - 3627: Haven't found "192.168.99.14" in hosts cache! Wed 17 Dec 2014 11:42:09 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3643 Wed 17 Dec 2014 11:42:09 AM BRST - 3627:GETFDHST Wed 17 Dec 2014 11:42:09 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:09 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3643 Wed 17 Dec 2014 11:42:09 AM BRST - 3627:GETHOSTBYNAME (gasolinux) Wed 17 Dec 2014 11:42:09 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! Wed 17 Dec 2014 11:42:09 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3643 Wed 17 Dec 2014 11:42:09 AM BRST - 3627:GETHOSTBYADDR (192.168.99.14) Wed 17 Dec 2014 11:42:09 AM BRST - 3627: Haven't found "192.168.99.14" in hosts cache! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1403516 Title: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS) Status in eglibc package in Ubuntu: New Bug description: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+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 1403516] Re: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS)
To workaround, I'm just disabling hosts caching in /etc/nscd.conf: - enable-cachehosts yes + enable-cachehosts no FWIW the /var/cache/nscd directory is on NFS, but disabling persistent doesn't change the crash. ** Attachment added: "nsswitch.conf" https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+attachment/4282871/+files/nsswitch.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1403516 Title: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS) Status in eglibc package in Ubuntu: New Bug description: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+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 1403516] Re: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS)
(Ignore the medibuntu hook error, which seems unrelated and caused by bad python in apport-hooks-medibuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1403516 Title: nscd crashes upon sudo when hosts caching is enabled (NIS, NFS) Status in eglibc package in Ubuntu: New Bug description: We use nscd in our diskless clients, but we've found regular evidence of crashes in our dmesg output, and I've been able to easily reproduce it by running sudo ls while hosts caching is enabled. The debug output when running nscd -d is as follows: Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDPW Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 5, for passwd Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDGR Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 7, for group Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETFDHST Wed 17 Dec 2014 11:42:48 AM BRST - 3627: provide access to FD 9, for hosts Wed 17 Dec 2014 11:42:48 AM BRST - 3627: handle_request: request received (Version = 2) from PID 3649 Wed 17 Dec 2014 11:42:48 AM BRST - 3627: GETAI (gasolinux) Wed 17 Dec 2014 11:42:48 AM BRST - 3627: Haven't found "gasolinux" in hosts cache! and then it dies. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nscd 2.19-0ubuntu6.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 17 11:45:11 2014 SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.nscd.conf: [modified] mtime.conffile..etc.nscd.conf: 2014-12-17T11:43:58.035583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1403516/+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 1397435] Re: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization
I should have noted I have 2FA in place. The page it's posting to and getting a 403 is https://launchpad.net /+authorize-token The actual error page reads: No REFERER Header Launchpad requires a REFERER header to perform this action. There is no REFERER header present. This can be caused by configuring your browser to block REFERER headers. Unblock REFERER headers for launchpad.net and try again, or see the FAQ Why does Launchpad require a REFERER header? for more information. You can also join the #launchpad IRC support channel on chat.freenode.net for further assistance. Launchpad • Take the tour • Read the guide Search Launchpad © 2004-2014 Canonical Ltd. • Terms of use • Contact Launchpad Support • Blog • Careers • System status • r17267 (Get the code!) IFRAME: javascript:void(0); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1397435 Title: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization Status in apport package in Ubuntu: New Bug description: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1397435/+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 1397435] [NEW] Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization
Public bug reported: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1397435 Title: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization Status in apport package in Ubuntu: New Bug description: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1397435/+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
