[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Steve Langasek]

Removing packages from artful:
storage-framework 0.3+17.04.20170320.1-0ubuntu1 in artful
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful amd64
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful arm64
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful armhf
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful i386
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful ppc64el
libstorage-framework-provider-1-5 0.3+17.04.20170320.1-0ubuntu1 
in artful s390x
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful amd64
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful arm64
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful armhf
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful i386
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful ppc64el
libstorage-framework-qt-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful s390x
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful amd64
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful arm64
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful armhf
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful i386
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful ppc64el
libstorage-framework-qt-client-2-0 
0.3+17.04.20170320.1-0ubuntu1 in artful s390x
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful amd64
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful arm64
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful armhf
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful i386
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful ppc64el
libstorage-framework-qt-local-client-1-0 
0.3+17.04.20170320.1-0ubuntu1 in artful s390x
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful amd64
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful arm64
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful armhf
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful i386
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful ppc64el
storage-framework-client-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful s390x
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful amd64
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful arm64
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful armhf
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful i386
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful ppc64el
storage-framework-provider-dev 0.3+17.04.20170320.1-0ubuntu1 in 
artful s390x
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful amd64
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful arm64
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful armhf
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful i386
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful ppc64el
storage-framework-registry 0.3+17.04.20170320.1-0ubuntu1 in 
artful s390x
Comment: Incompatible with Qt5.9 stack; LP: #1695928
1 package successfully removed.


** Changed in: storage-framework (Ubuntu)
   Status: New => Fix Released

** Also affects: online-accounts-api (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Please remove obsolete UOA packages

Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in mcloud package in Ubuntu:
  Fix Released
Status in online-accounts-api package in Ubuntu:
  Fix Released
Status in storage-framework package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Online Accounts is no longer 

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Steve Langasek]

Removing packages from artful:
mcloud 1.0.0+17.10.20170726-0ubuntu1 in artful
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful amd64
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful arm64
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful armhf
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful i386
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful ppc64el
libmcloud-dev 1.0.0+17.10.20170726-0ubuntu1 in artful s390x
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful amd64
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful arm64
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful armhf
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful i386
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful ppc64el
libmcloud-doc 1.0.0+17.10.20170726-0ubuntu1 in artful s390x
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful amd64
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful arm64
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful armhf
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful i386
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful ppc64el
libmcloud1 1.0.0+17.10.20170726-0ubuntu1 in artful s390x
Comment: Incompatible with Qt5.9 stack; LP: #1695928
1 package successfully removed.


** Also affects: mcloud (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mcloud (Ubuntu)
   Status: New => Fix Released

** Also affects: storage-framework (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Please remove obsolete UOA packages

Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in mcloud package in Ubuntu:
  Fix Released
Status in online-accounts-api package in Ubuntu:
  Fix Released
Status in storage-framework package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper #1707801
  mcloud
  (address-book-app removed)
  address-book-service
  (dialer-app removed)
  (messaging-app removed)
  telephony-service bug 1707802
  tone-generator bug 1707802
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  (camera-app removed)
  indicator-transfer
  indicator-transfer-buteo
  libertine
  (ubuntu-experience-tests removed)
  unity-scopes-shell bug 1707797
  (unity8 removed)

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1695928/+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 1695928] Re: Please remove obsolete UOA packages

[Steve Langasek]

Removing packages from artful:
online-accounts-api 0.1+17.04.20161223-0ubuntu1 in artful
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful amd64
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful arm64
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful armhf
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful i386
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful ppc64el
libonline-accounts-daemon-dev 0.1+17.04.20161223-0ubuntu1 in 
artful s390x
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful amd64
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful arm64
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful armhf
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful i386
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful ppc64el
libonline-accounts-daemon1 0.1+17.04.20161223-0ubuntu1 in 
artful s390x
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
amd64
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
arm64
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
armhf
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
i386
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
ppc64el
libonline-accounts-qt-dev 0.1+17.04.20161223-0ubuntu1 in artful 
s390x
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
amd64
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
arm64
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
armhf
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
i386
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
ppc64el
libonline-accounts-qt1 0.1+17.04.20161223-0ubuntu1 in artful 
s390x
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful amd64
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful arm64
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful armhf
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful i386
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful ppc64el
qml-module-ubuntu-onlineaccounts2 0.1+17.04.20161223-0ubuntu1 
in artful s390x
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful amd64
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful arm64
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful armhf
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful i386
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful ppc64el
qml-module-ubuntu-onlineaccounts2-doc 
0.1+17.04.20161223-0ubuntu1 in artful s390x
Comment: Incompatible with Qt5.9 stack; LP: #1695928
1 package successfully removed.


** Changed in: online-accounts-api (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove obsolete UOA packages

Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in mcloud package in Ubuntu:
  Fix Released
Status in online-accounts-api package in Ubuntu:
  Fix Released
Status in storage-framework package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  

[Touch-packages] [Bug 1711204] Re: Remove ubuntu-ui-toolkit from the archive

[Steve Langasek]

Removing packages from artful:
ubuntu-system-settings-online-accounts 0.7+17.04.20170308.2-0ubuntu3 in 
artful
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful amd64
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful arm64
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful armhf
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful i386
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful ppc64el
libonline-accounts-client-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful s390x
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful amd64
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful arm64
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful armhf
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful i386
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful ppc64el
libonline-accounts-client1 0.7+17.04.20170308.2-0ubuntu3 in 
artful s390x
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful amd64
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful arm64
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful armhf
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful i386
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful ppc64el
libonline-accounts-plugin-dev 0.7+17.04.20170308.2-0ubuntu3 in 
artful s390x
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful amd64
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful arm64
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful armhf
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful i386
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful ppc64el
qml-module-ubuntu-onlineaccounts-client 
0.7+17.04.20170308.2-0ubuntu3 in artful s390x
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful amd64
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful arm64
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful armhf
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful i386
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful ppc64el
qml-module-ubuntu-onlineaccounts-client-doc 
0.7+17.04.20170308.2-0ubuntu3 in artful s390x
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful amd64
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful arm64
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful armhf
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful i386
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful ppc64el
qtdeclarative5-online-accounts-client0.1 
0.7+17.04.20170308.2-0ubuntu3 in artful s390x
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful amd64
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful arm64
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful armhf
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful i386
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful ppc64el
ubuntu-system-settings-online-accounts 
0.7+17.04.20170308.2-0ubuntu3 in artful s390x
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful amd64
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful arm64
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful armhf
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful i386
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful ppc64el
ubuntu-system-settings-online-accounts-autopilot 
0.7+17.04.20170308.2-0ubuntu3 in artful s390x
Comment: Incompatible with Qt5.9 stack; LP: 

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Steve Langasek]

Removing packages from artful:
gnome-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in artful
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful amd64
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful arm64
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful armhf
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful i386
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful ppc64el
gir1.2-accountplugin-1.0 0.1.9+16.10.20160825-0ubuntu1 in 
artful s390x
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
amd64
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
arm64
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
armhf
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
i386
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
ppc64el
libaccount-plugin-1.0-0 0.1.9+16.10.20160825-0ubuntu1 in artful 
s390x
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful amd64
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful arm64
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful armhf
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful i386
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful ppc64el
libaccount-plugin-1.0-dev 0.1.9+16.10.20160825-0ubuntu1 in 
artful s390x
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful amd64
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful arm64
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful armhf
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful i386
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful ppc64el
libaccount-plugin-1.0-doc 0.1.9+16.10.20160825-0ubuntu1 in 
artful s390x
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful amd64
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful arm64
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful armhf
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful i386
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful ppc64el
unity-control-center-signon 0.1.9+16.10.20160825-0ubuntu1 in 
artful s390x
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful amd64
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful arm64
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful armhf
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful i386
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful ppc64el
unity-control-center-signon-autopilot 
0.1.9+16.10.20160825-0ubuntu1 in artful s390x
Comment: Obsolete and incompatible with Qt5.9 stack; LP: #1695928
1 package successfully removed.


** Changed in: gnome-control-center-signon (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove obsolete UOA packages

Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Steve Langasek]

Removing packages from artful:
account-plugins 0.13+17.04.20170314-0ubuntu1 in artful
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-facebook 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-flickr 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful amd64
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful arm64
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful armhf
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful i386
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful ppc64el
account-plugin-foursquare 0.13+17.04.20170314-0ubuntu1 in 
artful s390x
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-google 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-identica 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-instagram 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-linkedin 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-mcloud 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
i386
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
ppc64el
account-plugin-microsoft 0.13+17.04.20170314-0ubuntu1 in artful 
s390x
account-plugin-nextcloud 0.13+17.04.20170314-0ubuntu1 in artful 
amd64
account-plugin-nextcloud 0.13+17.04.20170314-0ubuntu1 in artful 
arm64
account-plugin-nextcloud 0.13+17.04.20170314-0ubuntu1 in artful 
armhf
   

[Touch-packages] [Bug 1699664] Re: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Launchpad Bug Tracker]

[Expired for libnl3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: libnl3 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libnl3 package in Ubuntu:
  Expired

Bug description:
  issue in installing packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 22 01:06:06 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package libnl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-08 (74 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1699664/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Eric Carroll]

Uninstalling polychromatic, razer-daemon, and then dbus-user-session
resolved the chrome problem.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

[Eric Carroll]

It turns out the workaround does resolve the long pause, but does not
result in correct operation. Chrome has chrome sync not functioning, and
gnome-encfs mounts fail unless manually mounted using gnome-encfs-
manager

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1712400] Re: [RFE] Show Ubuntu logo on the GDM login screen

[Daniel van Vugt]

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [RFE] Show Ubuntu logo on the GDM login screen

Status in Ubuntu UX:
  New
Status in gdm3 package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Fedora, Debian and many other distributions have their logo displayed
  on the bottom of the GDM screen, Ubuntu has nothing there. I think it
  could be a good idea to show Ubuntu logo or other Ubuntu branding
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1712400/+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 1712356] Re: Update breaks graphical system when X/Wayland is on vt[1-6]

[Daniel van Vugt]

Is this a serious problem? What's not safe?

We used to run Mir servers on arbitrary VTs that already had consoles on
them and never had a problem. You get a GUI while the server is running
and it returns to a tty upon exit.

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

Title:
  Update breaks graphical system when X/Wayland is on vt[1-6]

Status in console-setup package in Ubuntu:
  New

Bug description:
  The update of console-setup in artful-release that just happened
  triggered a bug-

  the postinst calls `setupcon --force' if the foreground console is
  tty1-6. This is not safe any more given that gnome-shell runs on 2.

  We can update this check to ask logind if the foreground console
  corresponds to a tty session, and only do setupcon --force if it does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+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 1709670] Re: logrotate never recovers if the statefile is corrupted

[Launchpad Bug Tracker]

This bug was fixed in the package logrotate - 3.8.7-2ubuntu3.1

---
logrotate (3.8.7-2ubuntu3.1) zesty; urgency=medium

  * logrotate does not ever recover from a corrupted statefile (LP: #1709670)
- d/p/do-not-treat-failure-of-readState-as-fatal.patch
(Backported from commit b9d82003002c98370e4131a7e43c76afcd23306a)

 -- Eric Desrochers   Wed, 09 Aug 2017
11:25:51 -0400

** Changed in: logrotate (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Trusty:
  Fix Released
Status in logrotate source package in Xenial:
  Fix Released
Status in logrotate source package in Zesty:
  Fix Released
Status in logrotate source package in Artful:
  Fix Released
Status in logrotate package in Debian:
  New

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you
  remove it or fix the corruption by hand.

  Impact scenarios :

  - System could eventually run out of disk space on a separate
  partition if mounted in "/var" or specifically "/var/log" or even
  worst if "/var/log" is on the same partition as "/" it could create
  even more damage if by any chance the partition is running out of free
  space.

  - System keep updating the same files over and over, creating large
  size logfiles.

  - ...

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst
  than the actual situation where logrotate simply doesn't recover from
  a corrupt statefile.

   * The current patch does recover (after verification) and has been
  through some upstream CI validation, community feedbacks, et al.

   * Additionally, I will run the /path_to_source/test/test script as a
  dogfooding that does ~72 tests.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1712283] Re: Cannot resolve DNS in artful daily

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: casper (Ubuntu)
   Status: New => Confirmed

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: netcfg (Ubuntu)
   Status: New => Confirmed

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

[Lonnie Lee Best]

I'm just started experiencing this in 16.04 this evening.

** Tags added: xenial

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
  dmi.product.name: MS-7522
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1598300] Re: CUPS web interface stops responding after a while

[Chris Halse Rogers]

Hello dominix, or anyone else affected,

Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cups (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Chris Halse Rogers]

Hello Mark, or anyone else affected,

Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cups (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1642966] Proposed package upload rejected

[Chris Halse Rogers]

An upload of cups to xenial-proposed has been rejected from the upload
queue for the following reason: "Please re-upload including the
changelog from the not-released-from-proposed 2.1.3-4ubuntu0.2 in the
_changes file. This is needed for SRU tracking.".

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1712442] [NEW] Underscore not shown at some DejaVu mono fonts

[Martin Saturka]

Public bug reported:

Ubuntu 16.04.3 LTS, fonts-dejavu 2.35-1,
mono underscore character is shown as space, issue seen:

* first noticed at Tcl/Tk applications, see this
https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73
(14pixel-sized mono font) and this
https://core.tcl.tk/tk/tktview/d4e20ca3dc tickets there;

* then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all
styles, and alike for Bitstream Vera Sans Mono at 14/17 sizes; set
editor fonts (in preferences/interface) to these fonts, underscore
disappears.

Since it is both at a Gtk application (Geany) and Tcl/Tk applications, it 
should be a font issue. It seems that DejaVu Sans Mono have generally issues, 
thus setting some another font as the system default Mono font would be 
reasonable (Liberation Mono seems to work properly).
Notice that mono fonts are commonly used for programming, and underscores are 
common in code, thus it is quite a problem to have spaces instead of 
underscores in system default mono font.

** Affects: fonts-dejavu (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Ubuntu 16.04.3 LTS, fonts-dejavu 2.35-1,
  mono underscore character is shown as space, issue seen:
  
- * first noticed at Tcl/Tk applications, see https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73;>this
 (14pixel-sized mono font) and https://core.tcl.tk/tk/tktview/d4e20ca3dc;>this tickets there;
- * then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all styles, 
and alike for Bitstream Vera Sans Mono at 14/17 sizes; set editor fonts (in 
preferences/interface) to these fonts, underscore disappears.
+ * first noticed at Tcl/Tk applications, see this
+ https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73
+ (14pixel-sized mono font) and this
+ https://core.tcl.tk/tk/tktview/d4e20ca3dc tickets there;
+ 
+ * then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all
+ styles, and alike for Bitstream Vera Sans Mono at 14/17 sizes; set
+ editor fonts (in preferences/interface) to these fonts, underscore
+ disappears.
  
  Since it is both at a Gtk application (Geany) and Tcl/Tk applications, it 
should be a font issue. It seems that DejaVu Sans Mono have generally issues, 
thus setting some another font as the system default Mono font would be 
reasonable (Liberation Mono seems to work properly).
  Notice that mono fonts are commonly used for programming, and underscores are 
common in code, thus it is quite a problem to have spaces instead of 
underscores in system default mono font.

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

Title:
  Underscore not shown at some DejaVu mono fonts

Status in fonts-dejavu package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.3 LTS, fonts-dejavu 2.35-1,
  mono underscore character is shown as space, issue seen:

  * first noticed at Tcl/Tk applications, see this
  https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73
  (14pixel-sized mono font) and this
  https://core.tcl.tk/tk/tktview/d4e20ca3dc tickets there;

  * then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all
  styles, and alike for Bitstream Vera Sans Mono at 14/17 sizes; set
  editor fonts (in preferences/interface) to these fonts, underscore
  disappears.

  Since it is both at a Gtk application (Geany) and Tcl/Tk applications, it 
should be a font issue. It seems that DejaVu Sans Mono have generally issues, 
thus setting some another font as the system default Mono font would be 
reasonable (Liberation Mono seems to work properly).
  Notice that mono fonts are commonly used for programming, and underscores are 
common in code, thus it is quite a problem to have spaces instead of 
underscores in system default mono font.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1712442/+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 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

[Launchpad Bug Tracker]

This bug was fixed in the package zlib - 1:1.2.11.dfsg-0ubuntu2

---
zlib (1:1.2.11.dfsg-0ubuntu2) artful; urgency=medium

  * Add upstream patch to fix deflateParams().
Upstream commit: f9694097dd69354b03cb8af959094c7f260db0a1
LP: #1692870
  * Drop empty patch debian/patches/use-dso

 -- Jean-Louis Dupond   Tue, 23 May 2017 13:32:29
+0200

** Changed in: zlib (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Zesty:
  Confirmed
Status in zlib source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  - Install UniFi controller on Ubuntu 17.04 
(http://dl.ubnt.com/unifi/5.4.16/unifi_sysvinit_all.deb)
  - Go to https://:8443/manage/site/default/settings/guestcontrol
  - Or do: curl - --compress :8880/guest/s/default/

  When compression is enabled, its broken.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1692870/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** Changed in: systemd (Ubuntu Xenial)
   Status: Confirmed => In Progress

-- 
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/1569925

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  In Progress

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

I think you discount a kernel problem too lightly. When CUPS has started a
print job it has to send it to the printer. In my case over the network.
This involves the kernel and or the network driver.

I have just tried the daily build of Ubuntu Gnome - the browser can not
find google and ubuntu Budgie - same problem. The ppd file for the printer
is present in both distributions.

I will re-install Ubuntu tomorrow and try again. 17.04 works perfectly.

On 22 August 2017 at 19:08, Till Kamppeter <1712...@bugs.launchpad.net>
wrote:

> First, the kernel has no influence to printing results. All the printing
> logic is happening in user space.
>
> Please do the following tests and tell in which cases you get useful
> printouts (and if so, also tell whether there are quality differences,
> the PPD files are ones which you had attached in comment #2, file.pdf is
> an arbitrary PDF file):
>
> lpadmin -p oldppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P
> EPSON-WF-3620-Series17-04.ppd
> lpadmin -p newppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P
> EPSON_WF_3620_series17-10.ppd
>
> lp -d oldppd -o cupsPrintQuality=Draft file.pdf
> lp -d oldppd -o cupsPrintQuality=Normal file.pdf
> lp -d oldppd -o cupsPrintQuality=High file.pdf
>
> lp -d newppd -o cupsPrintQuality=Draft file.pdf
> lp -d newppd -o cupsPrintQuality=Normal file.pdf
> lp -d newppd -o cupsPrintQuality=High file.pdf
>
> For these tests please also follow the instructions of the section "CUPS
> error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712019
>
> Title:
>   Driverless printing only prints a blank sheet 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions
>


-- 
Rod Jones

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712433] Re: man page typo

[Denis Molony]

The word 'strogly' should be 'strongly'

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  New

Bug description:
  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
 parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
 wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1712433/+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 1712433] [NEW] man page typo

[Denis Molony]

Public bug reported:

Note  that mount is very strict about non-root users and all paths specified on 
command line are verified before fstab is
   parsed or a helper program is executed. It's strogly recommended to use 
a valid mountpoint to specify filesystem,  other‐
   wise mount may fail. For example it's bad idea to use NFS or CIFS source 
on command line.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: mount 2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Wed Aug 23 07:48:32 2017
InstallationDate: Installed on 2017-03-23 (152 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
SourcePackage: util-linux
UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  New

Bug description:
  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
 parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
 wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1712433/+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 1712400] Re: [RFE] Show Ubuntu logo on the GDM login screen

[Jeremy Bicha]

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: gnome-17.10

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

Title:
  [RFE] Show Ubuntu logo on the GDM login screen

Status in gdm3 package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Fedora, Debian and many other distributions have their logo displayed
  on the bottom of the GDM screen, Ubuntu has nothing there. I think it
  could be a good idea to show Ubuntu logo or other Ubuntu branding
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712400/+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 1712417] Re: New release 3.22.19

[Sebastien Bacher]

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  New release 3.22.19

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Hello,

  
https://git.gnome.org/browse/gtk+/commit/?h=3.22.19=efbf6f183ecd24cddea743a02fe8ce545f1b55f8

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgtk-3-0 3.22.18-1ubuntu1
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug 22 16:45:33 2017
  InstallationDate: Installed on 2017-07-05 (48 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1712417/+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 1712416] [NEW] Inastalé Driver y el no funcionó

[chalosan]

Public bug reported:

Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en ubuntu
17.10

Gracias

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
Date: Tue Aug 22 14:39:30 2017
DistroCodename: artful
DistroVariant: ubuntu
InstallationDate: Installed on 2017-08-22 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful ubuntu

-- 
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/1712416

Title:
  Inastalé Driver y el no funcionó

Status in xorg package in Ubuntu:
  New

Bug description:
  Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en
  ubuntu 17.10

  Gracias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Tue Aug 22 14:39:30 2017
  DistroCodename: artful
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712416/+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 1712417] [NEW] New release 3.22.19

[Cristian Aravena Romero]

Public bug reported:

Hello,

https://git.gnome.org/browse/gtk+/commit/?h=3.22.19=efbf6f183ecd24cddea743a02fe8ce545f1b55f8

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libgtk-3-0 3.22.18-1ubuntu1
Uname: Linux 4.13.0-041300rc6-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug 22 16:45:33 2017
InstallationDate: Installed on 2017-07-05 (48 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gtk+3.0
UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful upgrade-software-version

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

Title:
  New release 3.22.19

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Hello,

  
https://git.gnome.org/browse/gtk+/commit/?h=3.22.19=efbf6f183ecd24cddea743a02fe8ce545f1b55f8

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgtk-3-0 3.22.18-1ubuntu1
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug 22 16:45:33 2017
  InstallationDate: Installed on 2017-07-05 (48 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1712417/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Treviño]

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1704745/+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 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.30.1-0ubuntu3

---
util-linux (2.30.1-0ubuntu3) artful; urgency=medium

  * Cherrypick upstream patches to support getrandom() fallbacks on older
kernels. LP: #1708635

 -- Dimitri John Ledkov   Mon, 14 Aug 2017 11:15:20
+0100

** Changed in: util-linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1708635/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Till Kamppeter]

First, the kernel has no influence to printing results. All the printing
logic is happening in user space.

Please do the following tests and tell in which cases you get useful
printouts (and if so, also tell whether there are quality differences,
the PPD files are ones which you had attached in comment #2, file.pdf is
an arbitrary PDF file):

lpadmin -p oldppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P 
EPSON-WF-3620-Series17-04.ppd
lpadmin -p newppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P 
EPSON_WF_3620_series17-10.ppd

lp -d oldppd -o cupsPrintQuality=Draft file.pdf
lp -d oldppd -o cupsPrintQuality=Normal file.pdf
lp -d oldppd -o cupsPrintQuality=High file.pdf

lp -d newppd -o cupsPrintQuality=Draft file.pdf
lp -d newppd -o cupsPrintQuality=Normal file.pdf
lp -d newppd -o cupsPrintQuality=High file.pdf

For these tests please also follow the instructions of the section "CUPS
error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Bram Biesbrouck]

It seems to be fixed here on KDE neon...

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

There is no dialog to print in draft either in printing from LibreOffice or
from chrome.

If I add another printer and it searches for a driver then draft printing
is on the menu but printing still does not work.

I deleted the PPD files from etc/cups/ppd and  copied the old (17.04) PPD
file into the directory. This does not help.

unfortunately the earliest daily build I have is 14th August when the
problem had already occurred. I can not try an earlier Kernal.

On 22 August 2017 at 17:41, Till Kamppeter <1712...@bugs.launchpad.net>
wrote:

> The problem you see in the PPDs. Resolutions are different.
>
> So can you try to set the Print Quality to Draft to see whether it
> prints?
>
> Another test is creating a new queue with the OLD PPD file. Can you
> print with this queue, Print Quality set to Norml or High?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712019
>
> Title:
>   Driverless printing only prints a blank sheet 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions
>


-- 
Rod Jones

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1586528] Re: Avahi-daemon withdraws address record

[Graham Bosworth]

I am seeing the same problem on a physical host running Linux Mint.  I
too have found that clicking the network icon to toggle it off and back
on can restore connections.  Additionally, I have found that the
connection may be restored without intervention, given sufficient time
(potentially hours).  Sorry that this is a long post - when trying to
add an attachment, the U.R.L. was not found.  I have tried to provide
anything that may be relevant.  The connection was lost at 03:57:51, and
regained at 04:24.

The computers featured are yoyo, 192.168.42.187, 00:25:64:72:72:14, the
Linux Mint computer, and kevin, 192.168.42.129, 00:50:04:23:f7:80, the
D.H.C.P. server and Internet gateway.


[LinuxMint] graham@yoyo $ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Tue Aug 22 17:57:47 ~

[LinuxMint] graham@yoyo $ lspci | grep -i "net"
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast 
Ethernet Controller (rev 13)
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 
01)
Tue Aug 22 17:59:23 ~

The Broadcom wireless adaptor is not active.

[LinuxMint] graham@yoyo $ cat /etc/os-release
NAME="Linux Mint"
VERSION="18 (Sarah)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 18"
VERSION_ID="18"
HOME_URL="http://www.linuxmint.com/;
SUPPORT_URL="http://forums.linuxmint.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/;
UBUNTU_CODENAME=xenial
Tue Aug 22 17:48:57 ~

[LinuxMint] graham@yoyo $ uname -a
Linux yoyo 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
Tue Aug 22 18:04:00 ~


Here is a excerpt from kern.log, showing that the D.H.C.P. lease was not 
renewed and the network connection was lost:-
Aug 21 03:00:30 yoyo NetworkManager[1049]:   [1503280830.6457] dhcp4 
(eth0): state changed bound -> bound
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4009]   address 
192.168.42.187
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4009]   plen 25 
(255.255.255.128)
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   gateway 
192.168.42.129
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   server 
identifier 192.168.42.129
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   lease 
time 1800
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4010]   
nameserver '192.168.42.129'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4011]   
nameserver '192.168.42.248'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.4011]   domain 
name 'example.net'
Aug 21 03:13:25 yoyo NetworkManager[1049]:   [1503281605.5497] dhcp4 (eth0
): state changed bound -> bound
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5210]   address 
192.168.42.187
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   plen 25 
(255.255.255.128)
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   gateway 
192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   server 
identifier 192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   lease 
time 1800
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.129'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.248'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   domain 
name 'example.net'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5213] dhcp4 
(eth0): state changed bound -> bound
Aug 21 04:00:55 yoyo kernel: [2364015.580056] nfs: server gerald not 
responding, timed out
Aug 21 04:03:55 yoyo kernel: [2364195.804051] nfs: server gerald not 
responding, timed out

Here is a (slightly edited) excerpt from the same period in syslog:-
Aug 21 03:27:48 yoyo dhclient[6325]: DHCPREQUEST of 192.168.42.187 on eth0 to 
192.168.42.129 port 67 (xid=0x4ce954e5)
Aug 21 03:27:48 yoyo dhclient[6325]: DHCPACK of 192.168.42.187 from 
192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5210]   address 
192.168.42.187
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   plen 25 
(255.255.255.128)
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   gateway 
192.168.42.129
Aug 21 03:27:49 yoyo dhclient[6325]: bound to 192.168.42.187 -- renewal in 868 
seconds.
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5211]   server 
identifier 192.168.42.129
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   lease 
time 1800
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.129'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   
nameserver '192.168.42.248'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5212]   domain 
name 'example.net'
Aug 21 03:27:49 yoyo NetworkManager[1049]:   [1503282469.5213] dhcp4 
(eth0): state changed bound -> bound
Aug 21 03:27:49 yoyo dbus[999]: [system] 

[Touch-packages] [Bug 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar

[Matthias Klose]

Override component to main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful: universe/misc -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful amd64: 
universe/misc/optional/100% -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful arm64: 
universe/misc/optional/100% -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful armhf: 
universe/misc/optional/100% -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful i386: 
universe/misc/optional/100% -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful ppc64el: 
universe/misc/optional/100% -> main
rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful s390x: 
universe/misc/optional/100% -> main
7 publications overridden.


** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] rhythmbox-plugin-alternative-toolbar

Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  The package is a python plugin and of type arch all, it's building fine in 
artful
  
https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1

  [Rationale]

  The plugin improves the look of rhythmbox and the desktop team
  believes it would be a welcome change to the default experience.

  [Security]

  The plugin only change UI layouts and has no known security report.

  [Quality assurance]

  The package is in sync with Debian and has no open bugs on the Debian
  BTS nor on launchpad. Upstream seems active though activity is rather
  low (but there are no open bugs or request so not a lot is needed)

  [Dependencies]

  The dependency are minimal and already in main

  [Standards compliance]

  The packaging is classic dh and using the current standards.

  [Maintenance]

  The package is well maintained upstream and in Debian, the Ubuntu
  Desktop team is going to keep an eye on it in Ubuntu though (desktop-
  bugs is subscribed)

  [Background information]

  The description summarize what the package is doing "Enhanced play
  controls and interface for Rhythmbox"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Till Kamppeter]

The problem you see in the PPDs. Resolutions are different.

So can you try to set the Print Quality to Draft to see whether it
prints?

Another test is creating a new queue with the OLD PPD file. Can you
print with this queue, Print Quality set to Norml or High?

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712356] Re: Update breaks graphical system when X/Wayland is on vt[1-6]

[Iain Lane]

** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Update breaks graphical system when X/Wayland is on vt[1-6]

Status in console-setup package in Ubuntu:
  New

Bug description:
  The update of console-setup in artful-release that just happened
  triggered a bug-

  the postinst calls `setupcon --force' if the foreground console is
  tty1-6. This is not safe any more given that gnome-shell runs on 2.

  We can update this check to ask logind if the foreground console
  corresponds to a tty session, and only do setupcon --force if it does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+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 1712356] Re: Update breaks graphical system when X/Wayland is on vt[1-6]

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Update breaks graphical system when X/Wayland is on vt[1-6]

Status in console-setup package in Ubuntu:
  New

Bug description:
  The update of console-setup in artful-release that just happened
  triggered a bug-

  the postinst calls `setupcon --force' if the foreground console is
  tty1-6. This is not safe any more given that gnome-shell runs on 2.

  We can update this check to ask logind if the foreground console
  corresponds to a tty session, and only do setupcon --force if it does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[monteleo]

I have the same problem on a fresh installation of kubuntu 17.04,

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Description changed:

  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
  / installed session - running on virtualbox 5.1.26.
  
  However I cannot ping google.com - "Name or service not known"
  
  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.
  
  Happy to provide more details - please can someone guide me producing a
  much better bug-report?
  
  
  
  my zesty VM is working just fine.  As of a week ago, my artful daily was
  working just fine also.
+ 
+ 
+ 
+ 
+ * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?
+ 
+ * Adding a hack, to create /etc/resolv.conf if it does not exist, or is
+ empty. src:systemd
+ 
+ * network-manager does not consider that dns is managed by resolved if
+ .53 is present in /etc/resolv.conf or if it points to stub-resolv.conf.
+ src:network-manager
+ 
+ * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs
+ checking / fixing
+ 
+ * caster has resolvconf integration
+ 
+ * livecd-rootfs has resolvconf integration

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Changed in: network-manager (Ubuntu)
   Importance: Critical => Medium

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712371] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'

[Apport retracing service]

*** This bug is a duplicate of bug 1708947 ***
https://bugs.launchpad.net/bugs/1708947

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1708947, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: gdebi (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1712371/+attachment/4937117/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1712371/+attachment/4937118/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1708947

** Information type changed from Private to Public

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

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  New

Bug description:
  I actually don't know why I have gdebi-kde, since I'm running
  "ordinary" 17.10 (alpha2).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 22 13:05:14 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InstallationDate: Installed on 2017-08-17 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170815)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6 Python 3.6.2
  PythonArgs: ['/usr/bin/gdebi-kde']
  PythonDetails: /usr/bin/python2.7 Python 2.7.13
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1712371/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Also affects: netcfg (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netcfg (Ubuntu)
   Importance: Undecided => Critical

** Also affects: casper (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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Si Dedman]

Also affects Xubuntu 16.06, 16.10 & 17.04. Potentially could/should
change bug name to reflect wider generality of problem.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1712283] Re: Cannot resolve DNS in artful daily

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Confirmed

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1704533] Re: French language locale missing : Gnome-Weather

[Bug Watch Updater]

** Changed in: gnome-weather
   Status: Unknown => Confirmed

** Changed in: gnome-weather
   Importance: Unknown => Medium

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  New
Status in gnome-weather package in Ubuntu:
  In Progress
Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

I have run the ipptool on both 17.04 and 17.10.

running diff produces the following:

rod@rod-desktop ~> diff out4.txt out10.txt
59c59
< printer-up-time (integer) = 146417546
---
> printer-up-time (integer) = 146414147


On 22 August 2017 at 14:38, Roderic Jones  wrote:

> Is this OK?
>
> On 22 August 2017 at 14:16, Till Kamppeter <1712...@bugs.launchpad.net>
> wrote:
>
>> Please run ipptool with the full printer URI, like this:
>>
>> ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer-
>> attributes.test > out.txt
>>
>> Attach the resulting output (here the file out.txt).
>>
>> make sure that attachments get the MIME type text/plain, as then one can
>> easily read them in a web browser.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1712019
>>
>> Title:
>>   Driverless printing only prints a blank sheet 17.10
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/
>> +subscriptions
>>
>
>
>
> --
> Rod Jones
>
>


-- 
Rod Jones

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar

[Mathieu Trudel-Lapierre]

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [MIR] rhythmbox-plugin-alternative-toolbar

Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Committed
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  The package is a python plugin and of type arch all, it's building fine in 
artful
  
https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1

  [Rationale]

  The plugin improves the look of rhythmbox and the desktop team
  believes it would be a welcome change to the default experience.

  [Security]

  The plugin only change UI layouts and has no known security report.

  [Quality assurance]

  The package is in sync with Debian and has no open bugs on the Debian
  BTS nor on launchpad. Upstream seems active though activity is rather
  low (but there are no open bugs or request so not a lot is needed)

  [Dependencies]

  The dependency are minimal and already in main

  [Standards compliance]

  The packaging is classic dh and using the current standards.

  [Maintenance]

  The package is well maintained upstream and in Debian, the Ubuntu
  Desktop team is going to keep an eye on it in Ubuntu though (desktop-
  bugs is subscribed)

  [Background information]

  The description summarize what the package is doing "Enhanced play
  controls and interface for Rhythmbox"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar

[Matthias Klose]

** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu)
   Status: Fix Committed => New

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

Title:
  [MIR] rhythmbox-plugin-alternative-toolbar

Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Committed
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  The package is a python plugin and of type arch all, it's building fine in 
artful
  
https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1

  [Rationale]

  The plugin improves the look of rhythmbox and the desktop team
  believes it would be a welcome change to the default experience.

  [Security]

  The plugin only change UI layouts and has no known security report.

  [Quality assurance]

  The package is in sync with Debian and has no open bugs on the Debian
  BTS nor on launchpad. Upstream seems active though activity is rather
  low (but there are no open bugs or request so not a lot is needed)

  [Dependencies]

  The dependency are minimal and already in main

  [Standards compliance]

  The packaging is classic dh and using the current standards.

  [Maintenance]

  The package is well maintained upstream and in Debian, the Ubuntu
  Desktop team is going to keep an eye on it in Ubuntu though (desktop-
  bugs is subscribed)

  [Background information]

  The description summarize what the package is doing "Enhanced play
  controls and interface for Rhythmbox"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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 1704533] Re: French language locale missing : Gnome-Weather

[Sebastien Bacher]

** Bug watch added: GNOME Bug Tracker #786615
   https://bugzilla.gnome.org/show_bug.cgi?id=786615

** Also affects: gnome-weather via
   https://bugzilla.gnome.org/show_bug.cgi?id=786615
   Importance: Unknown
   Status: Unknown

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  New
Status in gnome-weather package in Ubuntu:
  In Progress
Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1712356] [NEW] Update breaks graphical system when X/Wayland is on vt[1-6]

[Iain Lane]

Public bug reported:

The update of console-setup in artful-release that just happened
triggered a bug-

the postinst calls `setupcon --force' if the foreground console is
tty1-6. This is not safe any more given that gnome-shell runs on 2.

We can update this check to ask logind if the foreground console
corresponds to a tty session, and only do setupcon --force if it does.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Update breaks graphical system when X/Wayland is on vt[1-6]

Status in console-setup package in Ubuntu:
  New

Bug description:
  The update of console-setup in artful-release that just happened
  triggered a bug-

  the postinst calls `setupcon --force' if the foreground console is
  tty1-6. This is not safe any more given that gnome-shell runs on 2.

  We can update this check to ask logind if the foreground console
  corresponds to a tty session, and only do setupcon --force if it does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+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 1712356] Re: Update breaks graphical system when X/Wayland is on vt[1-6]

[Iain Lane]

** Patch added: "console-setup-1.142ubuntu9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+attachment/4937098/+files/console-setup-1.142ubuntu9.debdiff

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

Title:
  Update breaks graphical system when X/Wayland is on vt[1-6]

Status in console-setup package in Ubuntu:
  New

Bug description:
  The update of console-setup in artful-release that just happened
  triggered a bug-

  the postinst calls `setupcon --force' if the foreground console is
  tty1-6. This is not safe any more given that gnome-shell runs on 2.

  We can update this check to ask logind if the foreground console
  corresponds to a tty session, and only do setupcon --force if it does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1712356/+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 1712357] [NEW] xorg

[barkah]

Public bug reported:

keyboard on my laptop cant work properly, sometimes gnomes-screeshot
appears suddenly

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Tue Aug 22 21:53:49 2017
DistUpgraded: 2017-08-15 01:14:37,180 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0724]
InstallationDate: Installed on 2015-12-18 (613 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire V5-471
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=f2ec44d4-d342-4a4c-8707-c1cd535c7931 ro splash quiet plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-08-14 (7 days ago)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V1.16
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V5-471
dmi.board.vendor: Acer
dmi.board.version: V1.16
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.16
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.16:bd09/07/2012:svnAcer:pnAspireV5-471:pvrV1.16:rvnAcer:rnAspireV5-471:rvrV1.16:cvnAcer:ct9:cvrV1.16:
dmi.product.name: Aspire V5-471
dmi.product.version: V1.16
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Aug 22 21:30:48 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty

-- 
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/1712357

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  keyboard on my laptop cant work properly, sometimes gnomes-screeshot
  appears suddenly

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Tue Aug 22 21:53:49 2017
  DistUpgraded: 2017-08-15 01:14:37,180 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0724]
  InstallationDate: Installed on 2015-12-18 (613 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire V5-471
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=f2ec44d4-d342-4a4c-8707-c1cd535c7931 ro splash quiet plymouth:debug
  

[Touch-packages] [Bug 1700100] Re: Dimmed text is very hard to see

[Treviño]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Dimmed text is very hard to see

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  To reproduce:
  1- Install gnome-boxes
  2- Start gnome-boxes
  3- Select New -> Enter URL

  There is a dimmed text, which is very hard to see. It starts with
  'Example:...'.

  I believe all GTK text that is styled as "dim-label" are very hard to
  see. This is also apparent in the warning bars in Firefox.

  Here is the line of code of the referred string in gnome-boxes upstream:
  
https://git.gnome.org/browse/gnome-boxes/tree/data/ui/wizard-source.ui?id=f3f581886ead85d5bfcbc71016f37825ed6ee90c#n291

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: light-themes 14.04+16.04.20161024-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 23 16:47:09 2017
  InstallationDate: Installed on 2017-06-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700100/+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 1700218] Re: Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

[Treviño]

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  As found by
  https://github.com/gtimelog/gtimelog/issues/81#issuecomment-170923964,
  Ambiance theme doesn't respect Gtk3's GtkTextView::monospace. It
  causes issues on some apps. Gitg is affected as well.

  My temporary workaround: https://quan.hoabinh.vn/blog/2017/6/46-fix-
  gitg-doesn-t-use-monospace-font-in-ubuntu

  Please fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1700218/+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 1704745] Re: Ambiance light-themes - LibreOffice has a white square top right

[Treviño]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Ambiance light-themes - LibreOffice has a white square top right

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In LibreOffice, there's a white square that appears in the top right.
  It's a CSS problem. You could check how the guys from Adapta and
  United-Gnome managed to solve it.

  I posted the same issue at the Github of United-Gnome theme :
  https://github.com/godlyranchdressing/United-GNOME/issues/135

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

Is this OK?

On 22 August 2017 at 14:16, Till Kamppeter <1712...@bugs.launchpad.net>
wrote:

> Please run ipptool with the full printer URI, like this:
>
> ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer-
> attributes.test > out.txt
>
> Attach the resulting output (here the file out.txt).
>
> make sure that attachments get the MIME type text/plain, as then one can
> easily read them in a web browser.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712019
>
> Title:
>   Driverless printing only prints a blank sheet 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions
>


-- 
Rod Jones


** Attachment added: "out.txt"
   https://bugs.launchpad.net/bugs/1712019/+attachment/4937062/+files/out.txt

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1010421] Re: Text antialiasing is green.....

[Ralph Corderoy]

It seems odd gimp doesn't override the system and user's configuration
of the rgba attribute to none, e.g. by providing a
/etc/gimp/2.0/fonts.conf, e.g.
https://gist.github.com/csaez/5d8286b134266e51c6cb76fd218d1d5d

If they think that a user might want to produce a PNG with rgba set for
a particular sub-pixel layout then they could have a UI choice on the
text-tool's options, just as they currently have anti-alias to override
the system and user.

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

Title:
  Text antialiasing is green.

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  g.

  So upgraded to Gimp 2.8 and now text antialaising is green.

  Use white text on a black background to check it out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Till Kamppeter]

Please run ipptool with the full printer URI, like this:

ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer-
attributes.test > out.txt

Attach the resulting output (here the file out.txt).

make sure that attachments get the MIME type text/plain, as then one can
easily read them in a web browser.

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted

[Vibhav Chaddha]

Is this issue fixed? And where will I get that fix from?

-- 
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/1118446

Title:
  NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump
  inconsistency detected, interrupted

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I see the following messages in /var/log/syslog:
NetworkManager[14155]:  nl_recvmsgs() error: (-33) Dump inconsistency 
detected, interrupted

  When it goes down, I have to bounce network-manager to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Thu Feb  7 08:59:00 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-01-26 (12 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static 
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.11  metric 9 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca   
802-11-wireless   1360249035   Thu 07 Feb 2013 08:57:15 AM CSTyes   
no /org/freedesktop/NetworkManager/Settings/2
   Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12   
802-11-wireless   1359750784   Fri 01 Feb 2013 02:33:04 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/1
   MIA-WiFi  ea25a58d-9cb8-48a8-843a-2dc3231a1e17   
802-11-wireless   1359754973   Fri 01 Feb 2013 03:42:53 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.7.995  connected   enabled   enabled 
enabledenabled enabled

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

I have reinstalled Ubuntu 17.04 from the daily build available today,
updated it and only installed Fish, Gdebi, Gparted and Synaptic.

The problem persists.

The outputs you requested are attached as a file


On 22 August 2017 at 09:41, Roderic Jones  wrote:

> I think these files are the same. It took me a little while to realise
> that on filename uses hyphens and the other underscores. Otherwise they are
> the same.
>
> On 22 August 2017 at 09:24, Roderic Jones  wrote:
>
>> Here are the two files
>>
>> Good luck
>>
>> On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net>
>> wrote:
>>
>>> Can you please supply the following files:
>>>
>>> PPD file for your printer (in /etc/cups/ppd/) on 17.04.
>>>
>>> PPD file for your printer (in /etc/cups/ppd/) on 17.10.
>>>
>>> Output of the following commands in a terminal window:
>>>
>>> driverless
>>> lpstat -v
>>> ipptool -tv  get-printer-attributes.test
>>>
>>> The  you can find in the output of the "driverless" or "lpstat
>>> -v" commands. It is some expression starting with "ipp://..." or
>>> "ipps://..." (on one of my printers it is
>>> "ipp://HP5CB901E7DDC7.local:631/ipp/print").
>>>
>>> Please attach the files one by one, do not compress them and do not
>>> package them together. Thanks.
>>>
>>> ** Changed in: cups (Ubuntu)
>>>Status: New => Incomplete
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1712019
>>>
>>> Title:
>>>   Driverless printing only prints a blank sheet 17.10
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/
>>> +subscriptions
>>>
>>
>>
>>
>> --
>> Rod Jones
>>
>>
>
>
> --
> Rod Jones
>
>


-- 
Rod Jones


** Attachment added: "printer_diagnostic"
   
https://bugs.launchpad.net/bugs/1712019/+attachment/4937028/+files/printer_diagnostic

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)

[Mitesh Nile]

*** This bug is a duplicate of bug 1654918 ***
https://bugs.launchpad.net/bugs/1654918

I have a similar problem in Ubuntu Server 17.04 and I just can't find a way to 
work out..
I am connecting to a wired internet pppoe connection. It successfully gets 
connected to the internet but I cannot ping outside my network nor can get any 
ping from outside.

-- 
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/1679535

Title:
  ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup  fails)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I think this is a bug in the WIFI-driver or kernel.
  Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server 
to get to the internet.

  I have periodically *serious* problems with WIFI in Ubuntu 17.04.
  The network icon shows "connected" to the router and internet, but browsers 
and other attempts to get data report DNS error / or not connected.

  This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME
  etc.).

  Same laptop with Ubuntu 16.10 works flawlessly.

  The connection works fine after I reboot (power off/on) the router box.
  Then the bug may return (or may not return) after I turn on my laptop next 
time.

  This laptop is Toshiba Stellite P50 C.
  The laptop has Intel Corporation Wireless 3165 (rev 81).

  $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep
  'iwlwifi-7265d'

  0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81)
  Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010]
  Kernel driver in use: iwlwifi
  --
  0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
  Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1179:f840]
  Kernel driver in use: r8169
  Kernel modules: r8169
  4.11.0-041100rc4-generic

  Ref: https://wiki.debian.org/iwlwifi

  Restarting the network.manager does not help.
  $ sudo service network-manager restart
  Network manager connects (and sees) to the router, but cannot access internet.
  -

  Please see also:
  https://ubuntuforums.org/search.php?searchid=14761184
  and
  https://ubuntuforums.org/showthread.php?t=2356828

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.11.0-041100rc4-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  4 08:22:23 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-27 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  IpRoute:
   default via 192.168.1.1 dev wlp13s0 proto static metric 600
   169.254.0.0/16 dev wlp13s0 scope link metric 1000
   192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp13s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-Linux-Network  dda6e4cf-5cd9-4e01-b638-418985262413  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp14s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
------
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1679535/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Sebastien Bacher]

thanks, uploaded to xenial

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1712283] Re: Cannot resolve DNS in artful daily

[Launchpad Bug Tracker]

** Branch linked: lp:~xnox/livecd-rootfs/force-resolved-stub-resolver

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in livecd-rootfs package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in livecd-rootfs package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Also affects: livecd-rootfs (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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in livecd-rootfs package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1712308] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1712308/+attachment/4936983/+files/Stacktrace.txt

-- 
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/1712308

Title:
  systemd-journald crashed with SIGABRT in stpcpy()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 21:30:00 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-08-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
   sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
  UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
  UserGroups: audio pulse pulse-access video
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1712283/+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 1712308] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1712308/+attachment/4936984/+files/StacktraceSource.txt

-- 
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/1712308

Title:
  systemd-journald crashed with SIGABRT in stpcpy()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 21:30:00 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-08-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
   sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
  UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
  UserGroups: audio pulse pulse-access video
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1712308] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1712308/+attachment/4936985/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1712308/+attachment/4936959/+files/CoreDump.gz

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
+ systemd-journald crashed with SIGABRT in stpcpy()

** Tags removed: need-amd64-retrace

-- 
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/1712308

Title:
  systemd-journald crashed with SIGABRT in stpcpy()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 21:30:00 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-08-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
   sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
  UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
  UserGroups: audio pulse pulse-access video
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1712308] systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname()

[Apport retracing service]

StacktraceTop:
 stpcpy () at /usr/include/x86_64-linux-gnu/bits/string3.h:117
 sd_device_new_from_subsystem_sysname (ret=ret@entry=0xb26a042e78, 
subsystem=, subsystem@entry=0x7ffd0ea40060 "pci", 
sysname=0x7ffd0ea40064 ":00:1c.5") at 
../src/libsystemd/sd-device/sd-device.c:319
 sd_device_new_from_device_id (ret=0xb26a042e78, id=) at 
../src/libsystemd/sd-device/sd-device.c:675
 udev_device_new_from_device_id (udev=, id=0xb26a03274f 
"+pci::00:1c.5") at ../src/libudev/libudev-device.c:328
 dev_kmsg_record (l=, p=, s=0x7ffd0ea43b20) at 
../src/journal/journald-kmsg.c:229

-- 
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/1712308

Title:
  systemd-journald crashed with SIGABRT in stpcpy()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 21:30:00 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-08-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
   sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
  UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
  UserGroups: audio pulse pulse-access video
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1712308] [NEW] systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname()

[Ali İhsan ÇAĞLAYAN]

*** This bug is a security vulnerability ***

Public security bug reported:

I don't know this bug

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu6
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
Date: Mon Aug 21 21:30:00 2017
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2017-08-19 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. X555UB
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
 sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
 udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-234.so
Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
UserGroups: audio pulse pulse-access video
dmi.bios.date: 10/18/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555UB.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555UB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555UB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public Security

-- 
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/1712308

Title:
  systemd-journald crashed with SIGABRT in
  sd_device_new_from_subsystem_sysname()

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 21:30:00 2017
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-08-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X555UB
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   sd_device_new_from_subsystem_sysname () from 
/lib/systemd/libsystemd-shared-234.so
   sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in 
sd_device_new_from_subsystem_sysname()
  UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago)
  UserGroups: audio pulse pulse-access video
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1712302] [NEW] package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Matvey Kalistratov]

Public bug reported:

Something wrong

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ssh 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Aug 14 11:26:10 2017
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2017-02-28 (175 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openssh
Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1712302

Title:
  package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in openssh package in Ubuntu:
  New

Bug description:
  Something wrong

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ssh 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 14 11:26:10 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-02-28 (175 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1712302/+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 1712304] Re: avahi-daemon crashed with SIGABRT in avahi_malloc()

[Apport retracing service]

*** This bug is a duplicate of bug 1630037 ***
https://bugs.launchpad.net/bugs/1630037

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1630037, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936930/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936932/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936935/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936936/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936937/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936938/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1712304/+attachment/4936939/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1630037

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  avahi-daemon crashed with SIGABRT in avahi_malloc()

Status in avahi package in Ubuntu:
  New

Bug description:
  avahi-daemon keeps crashing. (Like usual! can we just remove this
  package from the ISO until it's stable?)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: avahi-daemon 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 17 11:02:07 2017
  ExecutablePath: /usr/sbin/avahi-daemon
  InstallationDate: Installed on 2017-07-27 (25 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170727)
  ProcCmdline: avahi-daemon:\ running\ [hostname.local]
  ProcEnviron:
   
  Signal: 6
  SourcePackage: avahi
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_malloc () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_strdup () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_normalize_name_strdup () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_key_new () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7
  Title: avahi-daemon crashed with SIGABRT in avahi_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1712304/+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 1006676] Re: showkey fails with "Couldn't get a file descriptor referring to the console"

[redtux]

Hi there,

I also just had the same problem on an Ubuntu 16.04.3 LTS box (with both
zsh and bash, on tty and on pseudo terminal running X). Is it already
known where this error message comes from, so we could change the string
to something more convenient recommending the user to become root or to
run sudo?

Of course, as explained by ESR it would be nice if it was not even
necessary to run the command as root, but (at least on my system) normal
users have no permission to access the respective file descriptors.

ls -l /dev/console
crw--- 1 root root 5, 1 Aug 22 11:13 /dev/console

ls -l /dev/tty0
crw--w 1 root tty 4, 0 Aug 22 11:13 /dev/tty0

strace tells me that showkey (run as user) does not have enough privileges:
open("/dev/tty0", O_RDWR)   = -1 EACCES (Permission denied)
open("/dev/tty0", O_WRONLY) = -1 EACCES (Permission denied)
open("/dev/tty0", O_RDONLY) = -1 EACCES (Permission denied)
open("/dev/console", O_RDWR)= -1 EACCES (Permission denied)
open("/dev/console", O_WRONLY)  = -1 EACCES (Permission denied)
open("/dev/console", O_RDONLY)  = -1 EACCES (Permission denied)

BTW: I am running the most recent kbd/showkey version that is available
for Xenial. Maybe this bug has already been fixed upstream in version
2.0?

apt-cache policy kbd
kbd:
  Installed: 1.15.5-1ubuntu5
  Candidate: 1.15.5-1ubuntu5
  Version table:
 *** 1.15.5-1ubuntu5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1.15.5-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

Title:
  showkey fails with "Couldn't get a file descriptor referring to the
  console"

Status in kbd package in Ubuntu:
  Invalid

Bug description:
  When invoked in Gnome Terminal 3.0.1 (Ubuntu 11.10), showkey
  uninformatively exits after reporting:

"Couldn't get a file descriptor referring to the console"

  For one who doesn't know what this means (such as myself), showkey is
  thus rendered unusable. The man page has no information about this
  behaviour.

  Installed kbd package: 1.15.2-3ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1006676/+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 1712283] Re: Cannot resolve DNS in artful daily

[Jean-Baptiste Lallement]

manifests diff between 20 and 21. resolvconf is gone from 20170821.

** Patch added: "artful-desktop-amd64.manifest.20-21.diff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283/+attachment/4936908/+files/artful-desktop-amd64.manifest.20-21.diff

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1712283/+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 1712283] Re: Ubuntu Budgie - Cannot resolve DNS in artful daily

[Jean-Baptiste Lallement]

Confirmed with Ubuntu same build number.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- Ubuntu Budgie - Cannot resolve DNS in artful daily
+ Cannot resolve DNS in artful daily

-- 
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/1712283

Title:
  Cannot resolve DNS in artful daily

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

[Zygmunt Krynicki]

** Changed in: snapd
 Assignee: (unassigned) => Michael Vogt (mvo)

-- 
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/1709536

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, 
code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 
'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 
does resolve the problem, confirming that the negative Nice value is the 
problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1709536/+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 1712291] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'

[Apport retracing service]

*** This bug is a duplicate of bug 1708947 ***
https://bugs.launchpad.net/bugs/1708947

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1708947, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: gdebi (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1712291/+attachment/4936859/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1712291/+attachment/4936860/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1708947

** Information type changed from Private to Public

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

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Error appeared on reboot this morning. I had not tried to launch
  gdebi. I'd added the package yesterday.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 15:12:41 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InstallationDate: Installed on 2017-08-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  Python3Details: /usr/bin/python3.6 Python 3.6.2
  PythonArgs: ['/usr/bin/gdebi-kde']
  PythonDetails: /usr/bin/python2.7 Python 2.7.13
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1712291/+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 1712283] Re: Ubuntu Budgie - Cannot resolve DNS in artful daily

[fossfreedom]

** Description changed:

  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
- / installed session.
+ / installed session - running on virtualbox 5.1.26.
  
  However I cannot ping google.com - "Name or service not known"
  
  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.
  
  Happy to provide more details - please can someone guide me producing a
  much better bug-report?
+ 
+ 
+ 
+ my zesty VM is working just fine.  As of a week ago, my artful daily was
+ working just fine also.

-- 
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/1712283

Title:
  Ubuntu Budgie - Cannot resolve DNS in artful daily

Status in systemd package in Ubuntu:
  New

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

I think these files are the same. It took me a little while to realise that
on filename uses hyphens and the other underscores. Otherwise they are the
same.

On 22 August 2017 at 09:24, Roderic Jones  wrote:

> Here are the two files
>
> Good luck
>
> On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net>
> wrote:
>
>> Can you please supply the following files:
>>
>> PPD file for your printer (in /etc/cups/ppd/) on 17.04.
>>
>> PPD file for your printer (in /etc/cups/ppd/) on 17.10.
>>
>> Output of the following commands in a terminal window:
>>
>> driverless
>> lpstat -v
>> ipptool -tv  get-printer-attributes.test
>>
>> The  you can find in the output of the "driverless" or "lpstat
>> -v" commands. It is some expression starting with "ipp://..." or
>> "ipps://..." (on one of my printers it is
>> "ipp://HP5CB901E7DDC7.local:631/ipp/print").
>>
>> Please attach the files one by one, do not compress them and do not
>> package them together. Thanks.
>>
>> ** Changed in: cups (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1712019
>>
>> Title:
>>   Driverless printing only prints a blank sheet 17.10
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/
>> +subscriptions
>>
>
>
>
> --
> Rod Jones
>
>


-- 
Rod Jones

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712039] Re: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache

[ts]

The file itself may be not specific to evince, but the behaviour that evince 
tries to read it (and AppArmor denies that) is specific to the AppArmor profile 
file that gets delivered with evince-common (/etc/apparmor.d/usr.bin.evince).
That is why i think it affects the package evince or evince-common, to be 
precise.

-- 
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/1712039

Title:
  AppArmor profile misses entry for
  /var/lib/snapd/desktop/applications/mimeinfo.cache

Status in apparmor package in Ubuntu:
  New

Bug description:
  The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
  If evince is launched, the following gets logged to syslog:

  kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
  comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  I don't know if this should be allowed or denied. If you could add the
  correct behaviour to the profile, that would be nice; otherwise, every
  time evince is launched, a notification pops up (apparmor-notify
  installed).

  
  (Workaround:

  Add to original profile (/etc/apparmor.d/usr.bin.evince):
#include 

  Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
/var/lib/snapd/desktop/applications/mimeinfo.cache r,
  )

  Release: Ubuntu 16.04.3 LTS
  Package Version: evince-common 3.18.2-1ubuntu4.1

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

Re: [Touch-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

[Roderic Jones]

Here are the two files

Good luck

On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net>
wrote:

> Can you please supply the following files:
>
> PPD file for your printer (in /etc/cups/ppd/) on 17.04.
>
> PPD file for your printer (in /etc/cups/ppd/) on 17.10.
>
> Output of the following commands in a terminal window:
>
> driverless
> lpstat -v
> ipptool -tv  get-printer-attributes.test
>
> The  you can find in the output of the "driverless" or "lpstat
> -v" commands. It is some expression starting with "ipp://..." or
> "ipps://..." (on one of my printers it is
> "ipp://HP5CB901E7DDC7.local:631/ipp/print").
>
> Please attach the files one by one, do not compress them and do not
> package them together. Thanks.
>
> ** Changed in: cups (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712019
>
> Title:
>   Driverless printing only prints a blank sheet 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions
>


-- 
Rod Jones


** Attachment added: "EPSON_WF_3620_series17-10.ppd"
   
https://bugs.launchpad.net/bugs/1712019/+attachment/4936831/+files/EPSON_WF_3620_series17-10.ppd

** Attachment added: "EPSON-WF-3620-Series17-04.ppd"
   
https://bugs.launchpad.net/bugs/1712019/+attachment/4936832/+files/EPSON-WF-3620-Series17-04.ppd

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712283] [NEW] Ubuntu Budgie - Cannot resolve DNS in artful daily

[fossfreedom]

Public bug reported:

in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
/ installed session.

However I cannot ping google.com - "Name or service not known"

Kind of difficult to run ubuntu-bug here without a fully functioning
network.

Happy to provide more details - please can someone guide me producing a
much better bug-report?

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


** Tags: artful

** Tags added: artful

-- 
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/1712283

Title:
  Ubuntu Budgie - Cannot resolve DNS in artful daily

Status in systemd package in Ubuntu:
  New

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283/+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 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error

[pelm]

I see this occasionally, not always, and I'm only using a local user
account.

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

Title:
  /sbin/upstart:indicator-session-unknown-user-error

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed
Status in upstart source package in Wily:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding upstart.  This problem was most recently seen with version
  1.13.2-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1447099/+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 1712268] [NEW] 2 bugs

[Milec Miltec]

Public bug reported:

non

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Aug 22 09:01:50 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2017-08-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Aug 22 07:21:06 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "vboxvideo" (module does not exist, 0)
 Failed to load module "vboxvideo" (module does not exist, 0)
 modeset(0): glamor initialization failed
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
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/1712268

Title:
  2 bugs

Status in xorg package in Ubuntu:
  New

Bug description:
  non

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Aug 22 09:01:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-08-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: