[Touch-packages] [Bug 1710410] [NEW] Must run systemd-resolve --status before DNS resolving is operative

2017-08-12 Thread WoJ
Public bug reported:

Context: fresh install of zesty via

debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
http://fr.archive.ubuntu.com/ubuntu

ran via asystemd-nspawn with a static IP

1. Upon first connexion, a ping fails:

root@zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution

2. The content of /etc/resolv.conf:

root@zesty1:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

3. When running systemd-resolve --status:

root@zesty1:~# systemd-resolve --status
Global
 DNS Servers: 8.8.8.8
  8.8.4.4
  2001:4860:4860::
  2001:4860:4860::8844
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
(...)

4. After running this command the resolution is miraculously restored:

root@zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1710410

Title:
  Must run systemd-resolve --status before DNS resolving is operative

Status in systemd package in Ubuntu:
  New

Bug description:
  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

  root@zesty1:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+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 1636573] Re: xinit flooding syslog

2016-12-02 Thread WoJ
Same here: Ubuntu 16.10, latest kodi

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1636573

Title:
  xinit flooding syslog

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1636573/+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