[Desktop-packages] [Bug 1636573] Re: xinit flooding syslog

[Dean Robinson]

** Changed in: pyopenssl (Ubuntu Yakkety)
   Status: Triaged => Fix Released

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

Title:
  xinit flooding syslog

Status in pyOpenSSL:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in pyopenssl source package in Yakkety:
  Fix Released
Status in xorg source package in Yakkety:
  Invalid

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/pyopenssl/+bug/1636573/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked "Connect Automatically"

[Dean Robinson]

** Package changed: network-manager (Ubuntu) => network-manager-openvpn
(Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/280571

Title:
  NetworkManager does not auto-connect to VPNs marked "Connect
  Automatically"

Status in NetworkManager:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  VPN connections marked "Connect Automatically" are not activated when
  a wired or wireless network becomes available.

  Fixed upstream in commit:

  commit ece5e209cdc409a21e249dacbdbc953a1db4c6b7
  Author: Jiří Klimeš 
  Date:   Tue Aug 21 17:49:41 2012 +0200

  core: VPN autoconnect feature (bgo #560471) (rh #483120)

  We go through the SECONDARIES state where we check if there are some
  secondary
  (VPN or other) UUIDs that are to be activated before progressing to
  ACTIVATED.
  In case of an error with a secondary UUID or its activation, the base
  connection
  can't activate successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp