[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

** Description changed:

  [Impact]
  
- hwe-16.04 refresh for 16.04.3
+ *** hwe-16.04 refresh for 16.04.3 ***
  
- Many packages need debhelper10 or would have to revert various packaging
- changes to work with dh9.
+ Revert changes to use debhelper10.
  
- xorg-server 1.19 needs updates
+ xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)
  
- x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
- the unity mouse config doesn't work with -libinput.
+ x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
+ x-x-i-libinput needs newer libinput, which in turn needs libwacom update.
+ 
+ Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.
  
  [Test case]
  
  upgrade from/to stock & old hwe stack, test desktop usage
  
  [Regression potential]
  
  zesty hasn't blown up
  
  [Other information]
  
  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
- 2. libclc
- 3. mesa, xorg-server
+ 2. libclc, xorg-server (build-dep libxfont1-dev)
+ 3. mesa, xorg-server-hwe-16.04
  4. drivers
- 5. xorg
+ 5. xorg-hwe-16.04

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1427807] Re: usermod's man refers to --*-sub-uids but accepts only --*-subuids

[Simon Déziel]

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

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

Title:
  usermod's man refers to --*-sub-uids but accepts only --*-subuids

Status in shadow package in Ubuntu:
  Fix Committed

Bug description:
  The man page refers to sub-uids and sub-gids but those don't take any
  "-" between sub and [ug]ids. The help message conforms to what the
  command accepts though.

  $ man usermod | grep -F -- -sub
 -v, --add-sub-uids FIRST-LAST
 -V, --del-sub-uids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-uids and --add-sub-uids are 
specified remove of all subordinate uid ranges happens before any
 -w, --add-sub-gids FIRST-LAST
 -W, --del-sub-gids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-gids and --add-sub-gids are 
specified remove of all subordinate gid ranges happens before any

  $ usermod --help | grep -F -- -sub
-v, --add-subuids FIRST-LAST  add range of subordinate uids
-V, --del-subuids FIRST-LAST  remvoe range of subordinate uids
-w, --add-subgids FIRST-LAST  add range of subordinate gids
-W, --del-subgids FIRST-LAST  remvoe range of subordinate gids

  
  More info on the environment:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu9
Candidate: 1:4.1.5.1-1ubuntu9
Version table:
   *** 1:4.1.5.1-1ubuntu9 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 13:37:50 2015
  InstallationDate: Installed on 2014-01-26 (400 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1427807/+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 1688433] [NEW] qBittorrent or any qt 5 applications still crashing on ubuntu 16.10

[Alexey Ivanov]

Public bug reported:


https://bugs.launchpad.net/ubuntu/+source/qbittorrent/+bug/1630848

https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

Meanwhile it still not fixed in Ubuntu 16.10 Yakkety. Since 2016-10-21
"patch" was backported from qt 5.8. All Qt5 applications with plugin
architecture creahing on exit.

Like typical strace from qbittorrent:

#0  0x77eba5df in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#1  0x75eda019 in QHashData::free_helper(void (*)(QHashData::Node*)) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x77ecd06f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#3  0x75e77ed3 in QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x76050a2c in QCoreApplicationPrivate::cleanupThreadData() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7639a84b in QGuiApplicationPrivate::~QGuiApplicationPrivate() () 
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x77524869 in QApplicationPrivate::~QApplicationPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x760862c7 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x76052ec6 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x77526331 in QApplication::~QApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  qBittorrent or any qt 5 applications still crashing on ubuntu 16.10

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  
  https://bugs.launchpad.net/ubuntu/+source/qbittorrent/+bug/1630848

  https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

  Meanwhile it still not fixed in Ubuntu 16.10 Yakkety. Since 2016-10-21
  "patch" was backported from qt 5.8. All Qt5 applications with plugin
  architecture creahing on exit.

  Like typical strace from qbittorrent:

  #0  0x77eba5df in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #1  0x75eda019 in QHashData::free_helper(void (*)(QHashData::Node*)) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #2  0x77ecd06f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #3  0x75e77ed3 in QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #4  0x76050a2c in QCoreApplicationPrivate::cleanupThreadData() () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #5  0x7639a84b in QGuiApplicationPrivate::~QGuiApplicationPrivate() 
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #6  0x77524869 in QApplicationPrivate::~QApplicationPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #7  0x760862c7 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #8  0x76052ec6 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #9  0x77526331 in QApplication::~QApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1688433/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Rifester]

Can confirm this on new 17.04 and 17.10 installs.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1669133] Re: Drop unnecessary rename of dlm -> dlm-controld (binary package)

[Launchpad Bug Tracker]

This bug was fixed in the package ocfs2-tools - 1.8.4-4ubuntu1

---
ocfs2-tools (1.8.4-4ubuntu1) artful; urgency=medium

  * Merge with Debian unstable (LP: #1688399). Remaining changes:
- d/t/basic: do not assume local filesystem blocksize will support
  the mkfs.ocfs2 blocksize (e.g., 4k disks will not support a 1k
  blocksize).
  * Drop:
- d/t/control: dlm-controld is renamed to dlm in Ubuntu.
  [ Package has been renamed in Ubuntu to match Debian ]
  + LP: #1669133

 -- Nishanth Aravamudan   Wed, 03 May
2017 17:04:59 -0700

** Changed in: ocfs2-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Drop unnecessary rename of dlm -> dlm-controld (binary package)

Status in dlm package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Triaged
Status in ocfs2-tools package in Ubuntu:
  Fix Released

Bug description:
  dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
- Add transitional dummy binary package to rename back
- Drop delta in lvm2 and ocfs2-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1669133/+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 1427807] Re: usermod's man refers to --*-sub-uids but accepts only --*-subuids

[Gustavo Silva]

This bug has been fixed in commit efbff6a3d9df076da17568c7b5c4787e8fdd3f1c in 
upstream (https://github.com/shadow-maint/shadow).
The corresponding ChangeLog entry was in 2016-12-02 by Serge Hallyn 
.

Updates from upstream will come soon and fix this bug.

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

Title:
  usermod's man refers to --*-sub-uids but accepts only --*-subuids

Status in shadow package in Ubuntu:
  Triaged

Bug description:
  The man page refers to sub-uids and sub-gids but those don't take any
  "-" between sub and [ug]ids. The help message conforms to what the
  command accepts though.

  $ man usermod | grep -F -- -sub
 -v, --add-sub-uids FIRST-LAST
 -V, --del-sub-uids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-uids and --add-sub-uids are 
specified remove of all subordinate uid ranges happens before any
 -w, --add-sub-gids FIRST-LAST
 -W, --del-sub-gids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-gids and --add-sub-gids are 
specified remove of all subordinate gid ranges happens before any

  $ usermod --help | grep -F -- -sub
-v, --add-subuids FIRST-LAST  add range of subordinate uids
-V, --del-subuids FIRST-LAST  remvoe range of subordinate uids
-w, --add-subgids FIRST-LAST  add range of subordinate gids
-W, --del-subgids FIRST-LAST  remvoe range of subordinate gids

  
  More info on the environment:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu9
Candidate: 1:4.1.5.1-1ubuntu9
Version table:
   *** 1:4.1.5.1-1ubuntu9 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 13:37:50 2015
  InstallationDate: Installed on 2014-01-26 (400 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1427807/+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 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Will Cooke]

Oxide can be removed. It's no longer supported.


On Thu, 4 May 2017 at 18:25, Steve Langasek 
wrote:

> I believe I heard this from Will Cooke who is on Cc:, so hopefully he
> can clarify.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1688395
>
> Title:
>   Remove Oxide, webbrowser-app and the Unity webapps
>
> Status in libunity-webapps package in Ubuntu:
>   Incomplete
> Status in oxide-qt package in Ubuntu:
>   Incomplete
> Status in webbrowser-app package in Ubuntu:
>   Incomplete
>
> Bug description:
>   These projects are discontinued, unsupported and should be removed.
>
>   I haven't done any analysis of the deps or rdeps to find out if there
>   is more to cull, or if there is some untangling to do.
>
>   I know of two tasks other than removing packages -
>
>Unity ships an Amazon launcher in its preset favourites which
>   launches a binary from unity-webapps-service. That should be removed.
>
>We need to keep providing the Amazon launcher by default (in GNOME
>   Shell) - it should be reimplemented and added to Shell by default.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+subscriptions
>

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 48734] Re: Home permissions too open

[rifra...@gmail.com]

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

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

Title:
  Home permissions too open

Status in adduser package in Ubuntu:
  Opinion
Status in Ubuntu RTM:
  New

Bug description:
  Binary package hint: debian-installer

  On a fresh dapper install i noticed that the file permissons for the
  home directory for the user created by the installer is set to 755,
  giving read access to everyone on the system.

  Surely this is a bad idea? If your set on the idea can we atleast have
  a option during the boot proccess?

  Also new files that are created via the console ('touch' etc.) are
  done so with '644' permissons, is there anything that can be done
  here? nautlius seems to create files at '600', which is a better
  setting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/48734/+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 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[Bug Watch Updater]

** Changed in: krb5 (Debian)
   Status: Unknown => Fix Released

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688310/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Eric Desrochers]

[Verificaton YAKKETY]

# i386
- Significant performance increase using the yakkety-proposed/i386 package 
inside a 32-bit LXD container build using a Ryzen CPU with Intel SHA Extension 
capability.
- Same performance (as expected) using the yakkety-proposed/i386 package on a 
non SHA Extension Intel CPU (i7-6770HQ) with yakkety-proposed package.

# amd64
- Significant performance increase using the yakkety-proposed/amd64 package on 
Ryzen CPU with Intel SHA Extension capability.
- Same performance (as expected) using the yakkety-proposed/amd64 package on a 
non SHA Extension Intel CPU (i7-6770HQ) with yakkety-proposed package.

Note : I unfortunately don't (nor colleagues) have access to a Intel CPU with 
SHA Extension capability at our disposal. Ideally, if someone has access to one 
to test it would be good. 
Otherwise, I think it is safe to rely on upstream author of the patch who 
confirmed it was working as expected using a Intel CPU with SHA extension 
capability. 

Reference : https://github.com/openssl/openssl/issues/2848
"...Myself I tested on Intel processors, yes, with/without"

==
* Test yakkety-proposed/i386 on a 32-bit LXD container using a non SHA 
Extension Intel CPU (Version before -proposed pkg):
--
ii  libssl1.0.0:i386  1.0.2g-1ubuntu9.1  i386   
  Secure Sockets Layer toolkit - shared libraries
ii  openssl   1.0.2g-1ubuntu9.1  i386   
  Secure Sockets Layer toolkit - cryptographic utility

# openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 12441833 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8997589 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5074636 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 1904828 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 304739 sha1's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -g -O2 
-fdebug-prefix-map=/build/openssl-OIx07U/openssl-1.0.2g=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOUR
CE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall 
-DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
-DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
sha1 66356.44k   191948.57k   433035.61k   650181.29k   832140.63k

# time openssl dgst -sha256 /var/tmp/5Gfile 
SHA256(/var/tmp/5Gfile)= 
7f06c62352aebd8125b2a1841e2b9e1ffcbed602f381c3dcb3200200e383d1d5

real0m15.429s
user0m14.372s
sys 0m1.052s
==
* Test yakkety-proposed/i386 on a 32-bit LXD container using a non SHA 
Extension Intel CPU (With -proposed pkg):
--
ii  libssl1.0.0:i386  1.0.2g-1ubuntu9.2  i386   
  Secure Sockets Layer toolkit - shared libraries
ii  openssl   1.0.2g-1ubuntu9.2  i386   
  Secure Sockets Layer toolkit - cryptographic utility

# openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 12414183 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8947717 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5057099 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 1905356 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 304628 sha1's in 3.00s
OpenSSL 1.0.2g  1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) aes(partial) blowfish(idx) 
compiler: cc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS 
-D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -g -O2 
-fdebug-prefix-map=/build/openssl-h4cyBe/openssl-1.0.2g=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOUR
CE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall 
-DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM 
-DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes   1024 bytes   8192 bytes
sha1 66208.98k   190884.63k   431539.11k   650361.51k   831837.53k

# time openssl dgst -sha256 /var/tmp/5Gfile 
SHA256(/var/tmp/5Gfile)= 
7f06c62352aebd8125b2a1841e2b9e1ffcbed602f381c3dcb3200200e383d1d5

real0m15.047s
user0m14.352s
sys 0m0.692s
==
* Test yakkety-proposed/i386 on a 32-bit LXD container using a Ryzen CPU 
(Version before -proposed pkg):
--
ii  libssl1.0.0:i386   1.0.2g-1ubuntu9.1
 

[Touch-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Steve Langasek]

I believe I heard this from Will Cooke who is on Cc:, so hopefully he
can clarify.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1670959] Re: systemd-resolved using 100% CPU

[Sergio Callegari]

I see it all the time after an upgrade to 17.04. Medium priority seems
an euphemism. This is a true showstopper. It is not just systemd-
resolved taking a whole core. Dnsmasq takes half of another. The cpu
runs hot. In a laptop, batteries drain in a snap.

Has this to do with https://unix.stackexchange.com/questions/304050/how-
to-avoid-conflicts-between-dnsmasq-and-systemd-resolved? Should
DNSStubListener=no be added to /etc/systemd/resolved.conf? Should
dnsmasq not be there?

Note that this bug is now 2 months old, that is over 20% of the expected
life of zesty.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 

[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

Ok, I got a simpler test case for (a) that doesn't involve setting up
FreeIPA, PKINIT or OTP. I'll update the bug description about it
tomorrow and then proceed with the SRU paperwork and actual packages.

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Jamie Strandboge]

Are all of these unsupported? I know that the signage effort was
initially using webapp-container (part of webbrowser-app) with mir. Even
if webbrowser-app were removed, oxide-qt might still be interesting for
signage/etc since it can be used with upstream Qt.

I've not heard an official statement on these as they relate to signage
(et al), so I thought I'd ask.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: Unknown => Confirmed

** Changed in: gnome-online-accounts
   Importance: Unknown => Critical

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1686544] Re: sudo fails to retrieve groups in sudoUser

[quess]

reported here too : https://www.redhat.com/archives/freeipa-
users/2017-May/msg00033.html

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

Title:
  sudo fails to retrieve groups in sudoUser

Status in sudo package in Ubuntu:
  New

Bug description:
  Currently using sudo with sssd 1.13.4 on xenial to manage sudo rules,
  groups are not resolved since last update.

  I troubleshooted :
  - sudo with all@debug
  - sssd with [sudo] debug_level = 9 and [domain/domain.tld] debug_level = 9
  - LDAP requests are correctly sent, and I can obtain correct rules
  - SSSD cache is correctly stored too, I can successfully ldbsearch into!

  I had to downgrade sudo (1.8.16-0ubuntu1.3) xenial to sudo
  (1.8.16-0ubuntu1) xenial, to get my groups working again. I tried sudo
  1.8.19, with no luck.

  
  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: ALL

  Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: #uid

  Broken since 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: %mygroup

  Broken in 1.8.16-0ubuntu1.3:
  sudoCommand: /bin/mount
  sudoHost: ALL
  sudoUser: myuser

  
  Patch sssd-doesnt-handle-netgroups.diff seems to break something...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1686544/+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 1609546] Re: DNS lookup through Netgear DG834G V4 router slow or times out

[Colin Law]

This is particularly annoying when installing Ubuntu, as the system
knows the network is connected, but DNS does not work so it can't
actually do anything useful.

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

Title:
  DNS lookup through Netgear DG834G V4 router slow or times out

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Update:
  On Zesty I am seeing a timeout both with systemd-resolve and dnslookup rather 
than just a slow resolution. The workaround in comment #6 which disables DNSSEC 
still corrects the problem.
  ---

  On up to date Yakkety if I specify my Netgear router as the DNS server (via 
Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I 
run, for example,
  systemd-resolve www.google.com
  or
  wget www.google.com

  I do not see the same delay if I run
  nslookup www.google.com

  A clue may be that in syslog I see
  Aug  3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0+DO) for DNS server 127.0.1.1.
  Aug  3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.1.1.
  Aug  3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set 
(UDP) for DNS server 127.0.1.1.

  I do not see the issue if I specify an external DNS server.
  I do not see the issue on 16.04, nor previous versions, or on other devices 
connected to the network. I have been using this router for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug  3 21:24:07 2016
  InstallationDate: Installed on 2016-08-02 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.47
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068E1220491620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+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 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Bryan Quigley]

(old bug about part of this - https://bugs.launchpad.net/ubuntu/+source
/webapps-applications/+bug/1517509 feel free to mark dup)

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

Initially assigning xnox, but feel free to move that.

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1688395] [NEW] Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

Public bug reported:

These projects are discontinued, unsupported and should be removed.

I haven't done any analysis of the deps or rdeps to find out if there is
more to cull, or if there is some untangling to do.

I know of two tasks other than removing packages -

 Unity ships an Amazon launcher in its preset favourites which launches
a binary from unity-webapps-service. That should be removed.

 We need to keep providing the Amazon launcher by default (in GNOME
Shell) - it should be reimplemented and added to Shell by default.

** Affects: libunity-webapps (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: oxide-qt (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: Incomplete

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Iain Lane]

Moving from bug #1649310

On Thu, May 04, 2017 at 08:02:57PM -, Steve Langasek wrote:
> On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> > Notable things not listed:
> >  * oxide/webbrowser app, still in use for amazon "app"
>·
> What pulls in the amazon app?  I have heard that oxide is definitively not
> on the supported list for 17.10+.

It's /usr/share/applications/ubuntu-amazon-default.desktop, so...

  application://ubuntu-amazon-default.desktop is in Unity's favourites 
  by default

and the chain is

 unity-webapps-service -> webapp-container -> webbrowser-app

I heard that we need to keep this, so if it is confirmed that Oxide, the
web browser and the Unity webapps are to be removed, then we will need
to provide this in another way. The desktop team will do that. (An
initial implementation might just be opening a new tab in Firefox.)

** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libunity-webapps (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

** Changed in: libunity-webapps (Ubuntu)
   Status: New => Incomplete

** Changed in: oxide-qt (Ubuntu)
   Status: New => Incomplete

** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1688395

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Incomplete
Status in oxide-qt package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1688395/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Iain Lane]

On Thu, May 04, 2017 at 08:02:57PM -, Steve Langasek wrote:
> On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> > Notable things not listed:
> >  * oxide/webbrowser app, still in use for amazon "app"
> 
> What pulls in the amazon app?  I have heard that oxide is definitively not
> on the supported list for 17.10+.

Opened bug #1688395 to discuss this stack.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

[John Johansen]

So the first kernel tried may have had the flock mediation patch. It was in
  4.4.0-67.88

Reverted in
  4.4.0-70.91

which would help explain the switch in denial from
  file_mmap   rm

to
  file_mprotect r

I am unsure why the request for mprotect is showing up. At this point we
need to start stracing the application

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  New

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cups-browsed" pid=17681 comm="apparmor_parser"
  [95224.610016] audit: type=1400 audit(1484230178.466:1012): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610029] audit: type=1400 audit(1484230178.466:1013): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610046] audit: type=1400 audit(1484230178.466:1014): apparmor="DENIED" 
operation="file_mmap" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=17765 
comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=10 
ouid=10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1655982/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

[Brian Murray]

Hello Eric, or anyone else affected,

Accepted openssl into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu9.2 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: openssl (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  In Progress
Status in openssl source package in Yakkety:
  Fix Committed
Status in openssl source package in Zesty:
  In Progress
Status in openssl source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 

[Touch-packages] [Bug 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

[John Johansen]

Okay, this kernel does NOT contain the caching fix. So it is not the
cause of the issue.

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  New

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cups-browsed" pid=17681 comm="apparmor_parser"
  [95224.610016] audit: type=1400 audit(1484230178.466:1012): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610029] audit: type=1400 audit(1484230178.466:1013): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610046] audit: type=1400 audit(1484230178.466:1014): apparmor="DENIED" 
operation="file_mmap" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=17765 
comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=10 
ouid=10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1655982/+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 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

[Jamie Strandboge]

Host:
$ uname -a
Linux sec-xenial-amd64 4.4.0-77-generic #98-Ubuntu SMP Wed Apr 26 08:34:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

$ apparmor_parser -V
AppArmor parser version 2.10.95
Copyright (C) 1999-2008 Novell Inc.
Copyright 2009-2012 Canonical Ltd.


Container:
root@xen:~# uname -a
Linux xen 4.4.0-77-generic #98-Ubuntu SMP Wed Apr 26 08:34:02 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

root@xen:~# apparmor_parser -V
AppArmor parser version 2.10.95
Copyright (C) 1999-2008 Novell Inc.
Copyright 2009-2012 Canonical Ltd.

Note, the reproducer is:

1. apt-get install lxd
2. sg lxd
3. lxc launch ubuntu:16.04 xen
4. lxc exec xen -- apt update
5. lxc exec xen -- apt dist-upgrade -y
6. lxc exec xen -- /bin/bash and edit /etc/apparmor.d/abstractions/base to have:
 /run/systemd/journal/stdout rw,
7. lxc exec xen -- apt install cups -y

and get the denial. If add to /etc/apparmor.d/usr.sbin.cups-browsed in
the container:

  /usr/sbin/cups-browsed r,

then I can (after reloading the profile):

$ lxc exec xen -- /bin/bash
root@xen:~# service cups-browsed stop
root@xen:~# service cups-browsed start
root@xen:~# systemctl status cups-browsed
● cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: 
   Active: active (running) since Thu 2017-05-04 20:06:50 UTC; 10s ago
 Main PID: 11697 (cups-browsed)
Tasks: 3
   Memory: 2.5M
  CPU: 17ms
   CGroup: /system.slice/cups-browsed.service
   └─11697 /usr/sbin/cups-browsed

May 04 20:06:50 xen systemd[1]: Started Make remote CUPS printers
available locally.

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  New

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 

Re: [Touch-packages] [Bug 1688367] [NEW] Split More Widely Used Plugins in a Separate Package

[Iain Lane]

On Thu, May 04, 2017 at 06:50:29PM -, Vasco Alves wrote:
> Public bug reported:
> 
> I think it would be really useful if the more useful plugins from the
> "bad" set could be split into a separate package, on which the full set
> could depend. By more useful, I mean the ones required to play popular
> video and audio formats. I'm being deliberately vague because there's no
> point in being specific if there is no openness to the idea, but if
> there is I'm more than willing to work on a list.
> 
> It just annoys me that I have to install things I never use, which are
> fairly large, like all the opencv libraries, to be able to watch certain
> popular media formats as well, and it seems like this is easily fixable.

Please raise this request on the Debian bugtracker, with the maintainers
there. It isn't something that we would want to be different from Debian
on, but if they agree to such a split then we would go along with it.

  https://www.debian.org/Bugs/Reporting

Except from Ubuntu, you need to do

  $ reportbug -B debian

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  Split More Widely Used Plugins in a Separate Package

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  I think it would be really useful if the more useful plugins from the
  "bad" set could be split into a separate package, on which the full
  set could depend. By more useful, I mean the ones required to play
  popular video and audio formats. I'm being deliberately vague because
  there's no point in being specific if there is no openness to the
  idea, but if there is I'm more than willing to work on a list.

  It just annoys me that I have to install things I never use, which are
  fairly large, like all the opencv libraries, to be able to watch
  certain popular media formats as well, and it seems like this is
  easily fixable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1688367/+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 1669133] Re: Drop unnecessary rename of dlm -> dlm-controld (binary package)

[Launchpad Bug Tracker]

This bug was fixed in the package dlm - 4.0.7-1ubuntu2

---
dlm (4.0.7-1ubuntu2) artful; urgency=medium

  * Rename dlm -> dlm-controld (LP: #1669133).
- The dlm transitional package will need to be kept until 18.04
  releases.
  * Drop:
- d/control,dlm.install, rules: Rename dlm-controld -> dlm inline
  with packaging history in Ubuntu

 -- Nishanth Aravamudan   Wed, 03 May
2017 16:48:18 -0700

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

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

Title:
  Drop unnecessary rename of dlm -> dlm-controld (binary package)

Status in dlm package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Triaged
Status in ocfs2-tools package in Ubuntu:
  Triaged

Bug description:
  dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
- Add transitional dummy binary package to rename back
- Drop delta in lvm2 and ocfs2-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1669133/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Jeremy Bicha]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => High

** Package changed: gnome-online-accounts (Arch Linux) => gnome-online-
accounts

** Changed in: gnome-online-accounts
   Importance: Undecided => Unknown

** Changed in: gnome-online-accounts
   Status: New => Unknown

** Changed in: gnome-online-accounts
 Remote watch: None => GNOME Bug Tracker #781990

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

** Changed in: ubuntu-gnome
   Importance: Undecided => High

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
Milestone: None => artful

** Tags added: gnome-1710

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+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 1470663] Re: Owncloud is not present in the list of available services

[Jeremy Bicha]

Owncloud only works if you are using gnome-control-center not unity-
control-center.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
  Owncloud is not present in the list of available services

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Hi, according to gnome changelog, there should be support for owncloud
  starting from version 3.8, but owncloud doesn't appear in the list of
  available services.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-lowlatency 3.19.8-ckt1
  Uname: Linux 3.19.0-22-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME-Notion:Unity
  Date: Thu Jul  2 00:48:09 2015
  InstallationDate: Installed on 2012-04-26 (1161 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to vivid on 2015-05-30 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1470663/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Steve Langasek]

On Thu, May 04, 2017 at 01:31:44PM -, Jamie Strandboge wrote:
> Can you add click-apparmor and apparmor-easyprof-ubuntu to your list if
> they aren't there already?

If you know of specific packages that you are the maintainer/upstream for
and should be removed, could you please just file bugs directly on these and
subscribe ubuntu-archive?

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1674529] Re: Credentials expired on all accounts.

[Jeremy Bicha]

Please try turning your computer off then try again.

If that fixes your issues, this is a duplicate of
https://launchpad.net/bugs/1610944

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
   Credentials expired on all accounts.

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Hello!
  I can not synchronize any account, I already tried eliminating each one, 
removed the key from the "Passwords" app, restarting and nothing.
  Any solution?
  Pd: Some have two-step verification enabled, some do not.
  GNOME Shell 3.20.4
  Ubuntu GNOME 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 20 22:10:02 2017
  InstallationDate: Installed on 2017-03-18 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1674529/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Steve Langasek]

On Thu, May 04, 2017 at 03:20:01PM -, Dimitri John Ledkov wrote:
> Notable things not listed:
>  * oxide/webbrowser app, still in use for amazon "app"

What pulls in the amazon app?  I have heard that oxide is definitively not
on the supported list for 17.10+.

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Brian Murray]

Hello Frank, or anyone else affected,

Accepted openssh into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:7.4p1-10ubuntu0.1 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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: openssh (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Fix Committed
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT 

[Touch-packages] [Bug 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

[John Johansen]

@Jamie may be right in his guesses but there is not enough information
here to be sure. The stacking work exists in the Xenial, Yakkety, and
Zesty kernels. But the patch Jamie is referring to only exists in the
Zesty kernel (it did exist in Xenial and Yakkety until reverted).

Please attach the output of
 uname -a

and
 apparmor_parser -V

for both the host system and the container

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  New

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cups-browsed" pid=17681 comm="apparmor_parser"
  [95224.610016] audit: type=1400 audit(1484230178.466:1012): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610029] audit: type=1400 audit(1484230178.466:1013): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610046] audit: type=1400 audit(1484230178.466:1014): apparmor="DENIED" 
operation="file_mmap" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed" pid=17765 
comm="cups-browsed" requested_mask="rm" denied_mask="rm" fsuid=10 
ouid=10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1655982/+subscriptions

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

[Touch-packages] [Bug 1688381] Re: package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  my system got hanged every time

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: mount 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-103.150-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-103-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu May  4 21:50:54 2017
  DpkgTerminalLog:
   dpkg: error processing package mount (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: package:mount:2.20.1-5.1ubuntu20.9:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-07-22 (651 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: util-linux
  Title: package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to trusty on 2015-08-16 (627 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1688381/+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 1688381] [NEW] package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Prashant vardhan singh]

Public bug reported:

my system got hanged every time

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mount 2.20.1-5.1ubuntu20.9
ProcVersionSignature: Ubuntu 3.13.0-103.150-generic 3.13.11-ckt39
Uname: Linux 3.13.0-103-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Thu May  4 21:50:54 2017
DpkgTerminalLog:
 dpkg: error processing package mount (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature: package:mount:2.20.1-5.1ubuntu20.9:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-07-22 (651 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: util-linux
Title: package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to trusty on 2015-08-16 (627 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  my system got hanged every time

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: mount 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-103.150-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-103-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Thu May  4 21:50:54 2017
  DpkgTerminalLog:
   dpkg: error processing package mount (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: package:mount:2.20.1-5.1ubuntu20.9:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-07-22 (651 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: util-linux
  Title: package mount 2.20.1-5.1ubuntu20.9 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to trusty on 2015-08-16 (627 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1688381/+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 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Konrad Zapałowicz]

I'm afraid that this is how the bluetoothctl is designed. This tool is a
command-line interface to the bluetoothd and requires it up and running.
It will not quit however when it is not running for a situations where
the daemon might come back online.

Ubuntu does not do anything special here, the bluetoothctl tool is
packaged as is from the upstream.

For Ubuntu this normally should not be a problem because a user is
expected to use {unity,gnome}-system-settings anyway to interact with BT
subsystem. Is there a particular use-case that is failing on this
behavior?

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+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 1678187] Re: dpkg fails to remove a linux-image-extra package, if /boot is about full

[Jarno Suni]

** Description changed:

  "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space in
  /boot temporarily. But there is no space left, if /boot is full.
  
- The fix could be to create the new initrg.img file in different
- partition before replacing the old one by it in update-initramfs. So the
- update-initramfs script should be fixed. But there may not be such a
- partition..
+ The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
+ Anyway the likely case when space runs out is when there is a separate /boot 
partition.
  
  Alternatively the init script should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  
  Related question: http://askubuntu.com/q/898499/21005
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dpkg fails to remove a linux-image-extra package, if /boot is about
  full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init script should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 

  Related question: http://askubuntu.com/q/898499/21005

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+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 1687501] Re: Wifi can't connect on Ubuntu Gnome live usb 17.04

[Phillip Susi]

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

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

Title:
  Wifi can't connect on Ubuntu Gnome live usb 17.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  When using Ubuntu Gnome 17.04 live usb my wifi network shows as
  available, but when I enter the password it can't connect. I attempted
  several times and ensured the password was correct.

  Tried using Ubuntu Gnome 16.04 live usb as a comparison and it
  connects without issue.

  I know my wifi adapter is supported by linux. I have Xubuntu 16.04
  installed on my hard drive and have never had an issue with wifi
  connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1687501/+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 1687501] [NEW] Wifi can't connect on Ubuntu Gnome live usb 17.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When using Ubuntu Gnome 17.04 live usb my wifi network shows as
available, but when I enter the password it can't connect. I attempted
several times and ensured the password was correct.

Tried using Ubuntu Gnome 16.04 live usb as a comparison and it connects
without issue.

I know my wifi adapter is supported by linux. I have Xubuntu 16.04
installed on my hard drive and have never had an issue with wifi
connection.

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

-- 
Wifi can't connect on Ubuntu Gnome live usb 17.04
https://bugs.launchpad.net/bugs/1687501
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

-- 
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 1688367] [NEW] Split More Widely Used Plugins in a Separate Package

[Vasco Alves]

Public bug reported:

I think it would be really useful if the more useful plugins from the
"bad" set could be split into a separate package, on which the full set
could depend. By more useful, I mean the ones required to play popular
video and audio formats. I'm being deliberately vague because there's no
point in being specific if there is no openness to the idea, but if
there is I'm more than willing to work on a list.

It just annoys me that I have to install things I never use, which are
fairly large, like all the opencv libraries, to be able to watch certain
popular media formats as well, and it seems like this is easily fixable.

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Split More Widely Used Plugins in a Separate Package

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  I think it would be really useful if the more useful plugins from the
  "bad" set could be split into a separate package, on which the full
  set could depend. By more useful, I mean the ones required to play
  popular video and audio formats. I'm being deliberately vague because
  there's no point in being specific if there is no openness to the
  idea, but if there is I'm more than willing to work on a list.

  It just annoys me that I have to install things I never use, which are
  fairly large, like all the opencv libraries, to be able to watch
  certain popular media formats as well, and it seems like this is
  easily fixable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1688367/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

affects 17.04 - worked fine on 16.10 and 16.04

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+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 1688364] [NEW] Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[Fodder]

Public bug reported:

May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1
May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 
127.0.0.1

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

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Tim Shannon]

Yeah, setting the nameserver in /etc/resolve.conf doesn't seem to work
for me either.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

** Description changed:

  [Impact]
  
  hwe-16.04 refresh for 16.04.3
  
  Many packages need debhelper10 or would have to revert various packaging
  changes to work with dh9.
  
  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)
  
  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.
  
  [Test case]
  
  upgrade from/to stock & old hwe stack, test desktop usage
  
  [Regression potential]
  
  zesty hasn't blown up
+ 
+ [Other information]
+ 
+ build order:
+ 1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
+ 2. libclc
+ 3. mesa, xorg-server
+ 4. drivers
+ 5. xorg

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libinput, libxfont, libxfont1, libwacom, 
llvm-toolchain-4.0, wayland
  2. libclc
  3. mesa, xorg-server
  4. drivers
  5. xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

** Also affects: llvm-toolchain-4.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: llvm-toolchain-4.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

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

** Changed in: libclc (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Vincent Gerris]

You can still add the vpn nameserver to /etc/resolv.conf . Epic blunder by
both systemd-resolv maintainer and Ubuntu packagers for stacking a broken
configuration together for at the 3rd release. Does anyone know how to
escalate this?

On May 4, 2017 19:04, "Winckler"  wrote:

> It's a really ugly workaround, but I'm using iptables to block
> connections to my ISP's DNS. I manually create and remove iptables rules
> using a script but at least this allows me to work remotely. I hope this
> get fix soon.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1624317
>
> Title:
>   systemd-resolved breaks VPN with split-horizon DNS
>
> Status in systemd:
>   New
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I use a VPN configured with network-manager-openconnect-gnome in which
>   a split-horizon DNS setup assigns different addresses to some names
>   inside the remote network than the addresses seen for those names from
>   outside the remote network.  However, systemd-resolved often decides
>   to ignore the VPN’s DNS servers and use the local network’s DNS
>   servers to resolve names (whether in the remote domain or not),
>   breaking the split-horizon DNS.
>
>   This related bug, reported by Lennart Poettering himself, was closed
> with the current Fedora release at the time reaching EOL:
>   https://bugzilla.redhat.com/show_bug.cgi?id=1151544
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions
>

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[Andreas Hasenack]

** Bug watch added: Debian Bug tracker #860767
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767

** Also affects: krb5 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
   Importance: Unknown
   Status: Unknown

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688310/+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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Tags added: zesty

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+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 1686344] Re: Mesa 17.0.x stable release

[Timo Aaltonen]

** No longer affects: libdrm (Ubuntu)

** No longer affects: libdrm (Ubuntu Xenial)

** No longer affects: libdrm (Ubuntu Zesty)

** No longer affects: mesa (Ubuntu Xenial)

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Zesty:
  New

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Winckler]

It's a really ugly workaround, but I'm using iptables to block
connections to my ISP's DNS. I manually create and remove iptables rules
using a script but at least this allows me to work remotely. I hope this
get fix soon.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1679784] Update Released

[Brian Murray]

The verification of the Stable Release Update for software-properties
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Confirmed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  software-properties does not display debconf prompts. while most debconf 
prompts have default answers and this is fine, for installing dkms modules on a 
SecureBoot-capable system we specifically have a critical debconf prompt with 
no possible default answer that users need to step through in order for their 
dkms modules to be usable.

  [Test case]
  1. sudo apt-add-repository ppa:vorlon/debconf-tests
  2. sudo apt update
  3. Launch Settings -> Software & Updates -> Additional Drivers
  4. Confirm that you are offered the option of using the 'noisy-fake-driver' 
package.
  5. Select this driver and apply changes.
  6. Confirm that no debconf prompt is shown, and the driver package fails to 
install ('dpkg -l noisy-fake-driver' shows 'iF').
  7. Reset the package state by removing the driver again.
  8. Enable -proposed.
  9. Run update-manager and verify that the new software-properties package is 
successfully installed from -proposed, pulling in libgtk2-perl in the process.
  10. Close Software & Updates and re-launch it.
  11. Select the 'noisy-fake-driver' package again.
  12. Confirm that you are shown a debconf prompt, and the driver package 
installs successfully.

  [Regression potential]
  The actual code change is small and self-contained, but the fix also requires 
pulling in new package dependencies which will also need to be promoted from 
universe to main in the process.  We need to take extra care to ensure the 
upgrade path is correct.  This SRU should also be done serially one release at 
a time to gather feedback at each stage.

  [Original bug description]
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1679784/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.96.24.7.2

---
software-properties (0.96.24.7.2) yakkety-security; urgency=medium

  * software-properties-gtk:
- fix the backend code to set the gnome debconf frontend, without which
  libgtk2-perl goes unused.
- depend on libgtk2-perl to ensure it's available, since it was not seeded
  on the desktop at release time.  This is only a Recommends: in zesty,
  but we need to ensure this isn't ignored on upgrade.
LP: #1679784.

 -- Steve Langasek   Fri, 14 Apr 2017
16:01:47 -0700

** Changed in: software-properties (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  Confirmed
Status in software-properties source package in Xenial:
  Confirmed
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  software-properties does not display debconf prompts. while most debconf 
prompts have default answers and this is fine, for installing dkms modules on a 
SecureBoot-capable system we specifically have a critical debconf prompt with 
no possible default answer that users need to step through in order for their 
dkms modules to be usable.

  [Test case]
  1. sudo apt-add-repository ppa:vorlon/debconf-tests
  2. sudo apt update
  3. Launch Settings -> Software & Updates -> Additional Drivers
  4. Confirm that you are offered the option of using the 'noisy-fake-driver' 
package.
  5. Select this driver and apply changes.
  6. Confirm that no debconf prompt is shown, and the driver package fails to 
install ('dpkg -l noisy-fake-driver' shows 'iF').
  7. Reset the package state by removing the driver again.
  8. Enable -proposed.
  9. Run update-manager and verify that the new software-properties package is 
successfully installed from -proposed, pulling in libgtk2-perl in the process.
  10. Close Software & Updates and re-launch it.
  11. Select the 'noisy-fake-driver' package again.
  12. Confirm that you are shown a debconf prompt, and the driver package 
installs successfully.

  [Regression potential]
  The actual code change is small and self-contained, but the fix also requires 
pulling in new package dependencies which will also need to be promoted from 
universe to main in the process.  We need to take extra care to ensure the 
upgrade path is correct.  This SRU should also be done serially one release at 
a time to gather feedback at each stage.

  [Original bug description]
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
    subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1679784/+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 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172

[Brian Murray]

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

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Tags added: rls-aa-incoming

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

Title:
  /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-
  repository@168:add_source_from_shortcut:/usr/bin/add-apt-
  repository@172

Status in software-properties package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.13, the problem page at 
https://errors.ubuntu.com/problem/01a945aed47dfff0cdfea51c5923f51cadeafb00 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1687122/+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 1688344] [NEW] package systemd 229-4ubuntu17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

[luis]

Public bug reported:

/bin/sh: 1: /usr/sbin/dpkg-preconfigure: Too many levels of symbolic links
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../dpkg_1.18.4ubuntu1.2_amd64.deb ...
Desempaquetando dpkg (1.18.4ubuntu1.2) sobre (1.18.4ubuntu1.1) ...
Configurando dpkg (1.18.4ubuntu1.2) ...
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../libudev1_229-4ubuntu17_amd64.deb ...
Desempaquetando libudev1:amd64 (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
Configurando libudev1:amd64 (229-4ubuntu17) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../udev_229-4ubuntu17_amd64.deb ...
Desempaquetando udev (229-4ubuntu17) sobre (229-4ubuntu16) ...
Preparando para desempaquetar .../libsystemd0_229-4ubuntu17_amd64.deb ...
Desempaquetando libsystemd0:amd64 (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
Configurando libsystemd0:amd64 (229-4ubuntu17) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../systemd_229-4ubuntu17_amd64.deb ...
Desempaquetando systemd (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para ureadahead (0.100.0-19) ...
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
Configurando systemd (229-4ubuntu17) ...
/var/lib/dpkg/info/systemd.postinst: 100: /var/lib/dpkg/info/systemd.postinst: 
addgroup: Too many levels of symbolic links
dpkg: error al procesar el paquete systemd (--configure):
 el subproceso instalado el script post-installation devolvió el código de 
salida de error 2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu May  4 11:24:58 2017
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2016-05-19 (349 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Dell Inc. Latitude E6430
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=03e348db-efce-4dc1-bf5d-6be046201d31 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.18
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu17 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Magnus Hoff]

FWIW, I did not experience this as fixed in 16.10, but now that I have
updated to 17.04 it works well :)

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable "connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

[Brian Murray]

The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Needs to allow updates from the ESM archive

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Precise:
  Fix Released

Bug description:
  [SRU Justification]
  When the dust has settled on the ESM archive Release file format[1], 
unattended-upgrades needs to be tweaked to match.

  [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43

  Since the ESM archive contains packages updated by the Ubuntu Security
  team, we should ensure the behavior of unattended-upgrades applies the
  same default policy to both.

  [Test case]
  1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
  2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to 
enable the ESM archive
  3. run 'sudo apt-get update'
  4. create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no 
unattended-upgrades package is installed.
  6. install unattended-upgrades from -proposed.
  7. again create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers 
to install a new unattended-upgrades package.

  [Regression potential]
  Worst-case scenario is a bug that prevents future security updates from being 
applied correctly.  This is not a concern for precise because there will be no 
further security updates /except/ those enabled by this SRU, but this SRU 
should also be included in all later stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1687129] Re: Needs to allow updates from the ESM archive

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.76ubuntu1.3

---
unattended-upgrades (0.76ubuntu1.3) precise; urgency=medium

  * Add UbuntuESM to the list of sources automatically upgraded from by
default.  LP: #1687129.

 -- Steve Langasek   Tue, 02 May 2017
15:45:12 -0400

** Changed in: unattended-upgrades (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

Title:
  Needs to allow updates from the ESM archive

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Precise:
  Fix Released

Bug description:
  [SRU Justification]
  When the dust has settled on the ESM archive Release file format[1], 
unattended-upgrades needs to be tweaked to match.

  [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43

  Since the ESM archive contains packages updated by the Ubuntu Security
  team, we should ensure the behavior of unattended-upgrades applies the
  same default policy to both.

  [Test case]
  1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades'
  2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to 
enable the ESM archive
  3. run 'sudo apt-get update'
  4. create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  5. run 'sudo unattended-upgrades --debug --dry-run' and verify that no 
unattended-upgrades package is installed.
  6. install unattended-upgrades from -proposed.
  7. again create a faked-up entry in 
/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages
 for the unattended-upgrades package with a higher version number
  8. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers 
to install a new unattended-upgrades package.

  [Regression potential]
  Worst-case scenario is a bug that prevents future security updates from being 
applied correctly.  This is not a concern for precise because there will be no 
further security updates /except/ those enabled by this SRU, but this SRU 
should also be included in all later stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Tim Shannon]

Yeah currently none of the workaround mentioned in the previous comments
seem to work at all for me on 17.04.

Not sure what to do at this point.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Dimitri John Ledkov]

First take at removals for unity8 stack are here:
https://code.launchpad.net/~xnox/ubuntu-seeds/unity8-removals/+merge/323615

This is incomplete, but I hope it does not have false removals listed.

Notable things not listed:
 * unity7 stack as we are still using that in artful
 * click - as it is seeded into multiple flavors

W.r.t. click, once the store goes offline, we will no longer support
clicks? or e.g. click is not going to be supported in artful?

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Dimitri John Ledkov]

Notable things not listed:
 * oxide/webbrowser app, still in use for amazon "app"

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Bug Watch Updater]

** Changed in: krb5 (Debian)
   Status: Unknown => Fix Released

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  $ sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1422795] Update Released

[Brian Murray]

The verification of the Stable Release Update for bash has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  bash crashes often if inputrc contains revert-all-at-newline

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Trusty:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
  The Debian bug includes complete reproduction case. Basically:
  with .inputrc containing
  set revert-all-at-newline On

  Go back in the commandline history, edit a command, then submit a different 
command (may be empty)
  Such as:
  $ ls something
  $ 

  Attached diff is confirmed to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop]
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Feb 17 15:49:30 2015
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.bash.bashrc: [modified]
  mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405

  
  [Test Case]

  Adapted from the Debian bug report:

  1. echo "set revert-all-at-newline on" > bug.inputrc
  2. INPUTRC=bug.inputrc bash
  3. echo hello
  4. ^P^U^N^M  [Hold down control and type "punm".]

  Bash should die immediately with SIGABRT.

  
  [Regression Potential]

  Relatively low.

  The change has no effect at all unless _rl_revert_all_lines() is called,
  which only happens if revert-all-at-newline is set, and then only when a
  newline is typed.  So, the potential for regression is essentially zero for
  non-interactive shells and for anyone not using revert-all-at-newline (which
  is not the default).

  Further, this change appeared upstream and in both Debian and Ubuntu over
  a year ago, so it's had plenty of public testing.

  lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates
  over history entries, reverting changes to each history entry.  This patch
  causes entry->data, which points to the per-entry undo list, to be cleared
  before reverting edits rather than after.  At first glance, this shouldn't
  make any difference.  However, it prevents rl_do_undo() from replacing the
  history entry with one reflecting the change.  Otherwise, the entry gets
  freed, leaving _rl_revert_all_lines() with an invalid pointer.

  _Not_ having an invalid pointer and double-free certainly can't be worse
  than the current situation.  Since we're avoiding is making the pointer
  invalid rather than not doing the free, the chance of a new leak is pretty
  much nonexistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+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 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline

[Launchpad Bug Tracker]

This bug was fixed in the package bash - 4.3-7ubuntu1.6

---
bash (4.3-7ubuntu1.6) trusty-proposed; urgency=medium

  * When the readline `revert-all-at-newline' option is set, pressing newline
when the current line is one retrieved from history results in a double
free and a segmentation fault. LP: #1422795.

 -- Jeffrey Hutzelman   Fri, 16 Oct 2015
17:21:23 -0400

** Changed in: bash (Ubuntu Trusty)
   Status: In Progress => Fix Released

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

Title:
  bash crashes often if inputrc contains revert-all-at-newline

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Trusty:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
  The Debian bug includes complete reproduction case. Basically:
  with .inputrc containing
  set revert-all-at-newline On

  Go back in the commandline history, edit a command, then submit a different 
command (may be empty)
  Such as:
  $ ls something
  $ 

  Attached diff is confirmed to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop]
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Feb 17 15:49:30 2015
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.bash.bashrc: [modified]
  mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405

  
  [Test Case]

  Adapted from the Debian bug report:

  1. echo "set revert-all-at-newline on" > bug.inputrc
  2. INPUTRC=bug.inputrc bash
  3. echo hello
  4. ^P^U^N^M  [Hold down control and type "punm".]

  Bash should die immediately with SIGABRT.

  
  [Regression Potential]

  Relatively low.

  The change has no effect at all unless _rl_revert_all_lines() is called,
  which only happens if revert-all-at-newline is set, and then only when a
  newline is typed.  So, the potential for regression is essentially zero for
  non-interactive shells and for anyone not using revert-all-at-newline (which
  is not the default).

  Further, this change appeared upstream and in both Debian and Ubuntu over
  a year ago, so it's had plenty of public testing.

  lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates
  over history entries, reverting changes to each history entry.  This patch
  causes entry->data, which points to the per-entry undo list, to be cleared
  before reverting edits rather than after.  At first glance, this shouldn't
  make any difference.  However, it prevents rl_do_undo() from replacing the
  history entry with one reflecting the change.  Otherwise, the entry gets
  freed, leaving _rl_revert_all_lines() with an invalid pointer.

  _Not_ having an invalid pointer and double-free certainly can't be worse
  than the current situation.  Since we're avoiding is making the pointer
  invalid rather than not doing the free, the chance of a new leak is pretty
  much nonexistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+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 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[Andreas Hasenack]

** Changed in: krb5 (Ubuntu)
 Assignee: Andreas Hasenack (ahasenack) => (unassigned)

** Changed in: krb5 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: krb5 (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: krb5 (Ubuntu Zesty)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688310/+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 1688317] [NEW] PCI/internal sound card not detected

[K Y]

Public bug reported:

No sound card detected at all, no sound for laptop/bluetooth headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Thu May  4 10:41:20 2017
InstallationDate: Installed on 2017-01-25 (98 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages 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/1688317

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound card detected at all, no sound for laptop/bluetooth
  headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu May  4 10:41:20 2017
  InstallationDate: Installed on 2017-01-25 (98 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1688317/+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 1655982] Re: cups-browsed fails to start in containers after apparmor stacking backport to xenial

[Jamie Strandboge]

FYI, http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3658 fixes the /run/systemd/journal/stdout
denials. It seems like the real cause of this bug is this denial:

[95224.610046] audit: type=1400 audit(1484230178.466:1014):
apparmor="DENIED" operation="file_mmap" namespace="root//lxd-xen_" profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-browsed"
pid=17765 comm="cups-browsed" requested_mask="rm" denied_mask="rm"
fsuid=10 ouid=10

Suspecting this had something to do with the flock and mmap mediation
fixes, I tried the reproducer with an updated 16.04 kernel
(4.4.0-77.98-generic). This fixes the file_mmap denial, but we still
have a file_mprotect 'r' denial:

[  825.339262] audit: type=1400 audit(1493908654.440:86):
apparmor="DENIED" operation="file_mprotect" namespace="root//lxd-xen_
" profile="/usr/sbin/cups-browsed" name="/usr/sbin/cups-
browsed" pid=14249 comm="cups-browsed" requested_mask="r"
denied_mask="r" fsuid=165536 ouid=165536

I'm not sure if this indicates a bug in the apparmor policy or apparmor
itself. If the policy, adjusting /etc/apparmor.d/usr.sbin.cups-browsed
to have:

  /usr/sbin/cups-browsed r,

resolves the issue.

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

Title:
  cups-browsed fails to start in containers after apparmor stacking
  backport to xenial

Status in apparmor package in Ubuntu:
  New

Bug description:
  The SRU of apparmor stacking for the Ubuntu 16.04 LTS kernel causes a
  regression in cups-browsed (shipped by cups) which now fails to start
  and gets respawned in a loop by systemd until it completely gives up.

  To reproduce:
   - lxc launch ubuntu:16.04 xen
   - lxc exec xen -- apt update
   - lxc exec xen -- apt dist-upgrade -y
   - lxc exec xen -- apt install cups -y

  You'll get:

  root@xen:~# systemctl status cups-browsed
  ● cups-browsed.service - Make remote CUPS printers available locally
 Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Thu 2017-01-12 14:09:38 UTC; 8min ago
   Main PID: 7725 (code=killed, signal=SEGV)

  Jan 12 14:09:38 xen systemd[1]: Started Make remote CUPS printers available 
locally.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Main process exited, 
code=killed, status=11/SEGV
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Unit entered failed 
state.
  Jan 12 14:09:38 xen systemd[1]: cups-browsed.service: Failed with result 
'signal'.


  And in dmesg (in a loop):
  [95217.312576] audit: type=1400 audit(1484230171.171:1004): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=16941 comm="apparmor_parser"
  [95217.313011] audit: type=1400 audit(1484230171.171:1005): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd" pid=16941 comm="apparmor_parser"
  [95217.313202] audit: type=1400 audit(1484230171.171:1006): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cupsd//third_party" pid=16941 comm="apparmor_parser"
  [95218.126005] audit: type=1400 audit(1484230171.983:1007): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95218.126018] audit: type=1400 audit(1484230171.983:1008): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17074 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686493] audit: type=1400 audit(1484230176.542:1009): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95222.686624] audit: type=1400 audit(1484230176.542:1010): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cupsd" name="/run/systemd/journal/stdout" pid=17553 
comm="cupsd" requested_mask="w" denied_mask="w" fsuid=10 ouid=10
  [95224.324494] audit: type=1400 audit(1484230178.182:1011): apparmor="STATUS" 
operation="profile_load" 
label="lxd-xen_//&:lxd-xen_://unconfined" 
name="/usr/sbin/cups-browsed" pid=17681 comm="apparmor_parser"
  [95224.610016] audit: type=1400 audit(1484230178.466:1012): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-xen_" 
profile="/usr/sbin/cups-browsed" name="/run/systemd/journal/stdout" pid=17765 
comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=10 
ouid=10
  [95224.610029] audit: type=1400 audit(1484230178.466:1013): 

[Touch-packages] [Bug 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems

[LocutusOfBorg]

** Also affects: krb5 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  In Progress
Status in krb5 source package in Zesty:
  New

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

  e) Confirm the kerberos services are bound to IPv6 local sockets:
  $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
  tcp6   0  0 :::88   :::*LISTEN
  1078/krb5kdc
  tcp6   0  0 :::749  :::*LISTEN
  1065/kadmind
  tcp6   0  0 :::464  :::*LISTEN
  1065/kadmind
  udp6   0  0 :::88   :::*  
  1078/krb5kdc
  udp6   0  0 :::464  :::*  
  1065/kadmind
  udp6   0  0 :::750  :::*  
  1078/krb5kdc

  f) configure the system to not support IPv6. There are probably many ways to 
do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
  e.1) edit /etc/default/grub
  e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
  e.3) run sudo update-grub
  e.4) reboot

  f) Confirm the kdc and admin services are NOT running:
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
  $

  g) /var/log/auth.log will contain the reason:
  $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
  May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for 
::.750)
  May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for 
::.464)
  May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for 
::.750)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688310/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

[Andreas Hasenack]

https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688310 filed for
(c)

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Fix Released

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1688310] [NEW] KDC/kadmind may fail to start on IPv4-only systems

[Andreas Hasenack]

Public bug reported:

This is fixed in artful in krb5 1.15-2

- upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
- debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
- debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

getaddrinfo() called on a wildcard address might return the IPv6 "::1"
address. On machines without IPv6 support, binding to it will likely
fail and the kdc/kadmin services won't start.

Steps to reproduce the problem on zesty:

a) install krb5-kdc krb5-admin-server
$ sudo apt install krb5-kdc krb5-admin-server
when prompted, use EXAMPLE.ORG (all caps) as the default realm
when prompted, use the IP of this machine for the KDC and the Admin servers

b) configure a new realm called EXAMPLE.ORG
$ sudo krb5_newrealm
use any password of your liking when prompted

c) confirm the kdc and admin services are running.
$ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
 4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
 4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
$ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
$ kinit
Password for ubu...@example.org: 
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: ubu...@example.org

Valid starting   Expires  Service principal
05/04/2017 14:20:17  05/05/2017 00:20:17  krbtgt/example@example.org
renew until 05/05/2017 14:20:13

e) Confirm the kerberos services are bound to IPv6 local sockets:
$ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)"
tcp6   0  0 :::88   :::*LISTEN  
1078/krb5kdc
tcp6   0  0 :::749  :::*LISTEN  
1065/kadmind
tcp6   0  0 :::464  :::*LISTEN  
1065/kadmind
udp6   0  0 :::88   :::*
1078/krb5kdc
udp6   0  0 :::464  :::*
1065/kadmind
udp6   0  0 :::750  :::*
1078/krb5kdc

f) configure the system to not support IPv6. There are probably many ways to do 
this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel 
command line:
e.1) edit /etc/default/grub
e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save
e.3) run sudo update-grub
e.4) reboot

f) Confirm the kdc and admin services are NOT running:
$ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
$

g) /var/log/auth.log will contain the reason:
$ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log 
May  4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for ::.750)
May  4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464)
May  4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for ::.750)
May  4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for ::.750)
May  4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464)
May  4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for ::.750)

** Affects: krb5 (Ubuntu)
 Importance: Undecided
 Assignee: Andreas Hasenack (ahasenack)
 Status: In Progress

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

Title:
  KDC/kadmind may fail to start on IPv4-only systems

Status in krb5 package in Ubuntu:
  In Progress

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch

  getaddrinfo() called on a wildcard address might return the IPv6 "::1"
  address. On machines without IPv6 support, binding to it will likely
  fail and the kdc/kadmin services won't start.

  Steps to reproduce the problem on zesty:

  a) install krb5-kdc krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, use the IP of this machine for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) confirm the kdc and admin services are running.
  $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep
   4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid
   4306 ?Ss 0:00 /usr/sbin/kadmind -nofork

  d) create a principal and obtain a ticket to confirm kerberos is working 
properly:
  $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  $ kinit
  Password for ubu...@example.org: 
  $ 

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

I'll modify the hwe-pkg scripts so that packages will still use
debhelper9, so dropping the requirement of backporting dh-
autoreconf/debhelper.

** Changed in: debhelper (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: dh-autoreconf (Ubuntu)
   Status: New => Invalid

** Changed in: dh-autoreconf (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  Won't Fix
Status in dh-autoreconf source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

** Description changed:

  This is fixed in artful in krb5 1.15-2
  
  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
  
  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP
  
  On zesty:
  a) install krb5-kdc and krb5-admin-server
- sudo apt install krb5-kdc krb5-admin-server
+ $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers
  
  b) configure a new realm called EXAMPLE.ORG
- sudo krb5_newrealm
+ $ sudo krb5_newrealm
  use any password of your liking when prompted
  
  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
- sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
+ $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
  
  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org
  
  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08
  
  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
- sudo ip addr add 10.0.5.155/24 dev ens3
+ $ sudo ip addr add 10.0.5.155/24 dev ens3
  
  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155
  
  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s
  
  Step (g) shows the bug.
  
  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!
  
  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  $ sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  $ sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to 

[Touch-packages] [Bug 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

** Changed in: krb5 (Ubuntu Zesty)
   Status: New => In Progress

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[LocutusOfBorg]

** Bug watch added: Debian Bug tracker #860767
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767

** Changed in: krb5 (Debian)
 Remote watch: krbdev.mit.edu/rt/ #8530 => Debian Bug tracker #860767

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[LocutusOfBorg]

** Changed in: krb5 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

** Changed in: krb5 (Ubuntu Zesty)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: krb5 (Ubuntu)
 Assignee: Andreas Hasenack (ahasenack) => (unassigned)

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[LocutusOfBorg]

** Also affects: krb5 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Zesty:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688265] [NEW] Wifi disconnects when screen is locked

[Mark Haase]

Public bug reported:

Ubuntu: 17.04
Wifi Chipset: Intel 7260 rev bb
Driver: iwlwifi 4.10.0-19-generic

If I lock my screen overnight, the following morning my Wifi will be
disconnected and is slow to reconnect and often requires multiple
connection attempts. Locking my screen for a short period of time
(minutes or hours) doesn't trigger the behavior.

Dmesg:


```
[1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256404.230281] wlp5s0: authenticated
[1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256413.048999] wlp5s0: authenticated
[1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256422.365122] wlp5s0: authenticated
[1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
[1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
[1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
[1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
[1256426.582424] wlp5s0: authenticated
[1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
[1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
[1256426.584763] wlp5s0: associated
[1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
[1256426.630815] bridge-wlp5s0: device is wireless, enabling SMAC
[1256426.630817] bridge-wlp5s0: up
[1256426.630823] bridge-wlp5s0: attached
```

There are hundreds of lines like this. It looks like it gets into a loop
where it disconnects every 5 seconds. Once I log in and reconnect using
the applet in the menu bar, the connection is pretty reliable for hours
-- I generally work a full day without wifi dropping.

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

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

Title:
  Wifi disconnects when screen is locked

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu: 17.04
  Wifi Chipset: Intel 7260 rev bb
  Driver: iwlwifi 4.10.0-19-generic

  If I lock my screen overnight, the following morning my Wifi will be
  disconnected and is slow to reconnect and often requires multiple
  connection attempts. Locking my screen for a short period of time
  (minutes or hours) doesn't trigger the behavior.

  Dmesg:

  
  ```
  [1256404.227085] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256404.229298] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256404.230281] wlp5s0: authenticated
  [1256404.843347] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256409.234035] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256413.045691] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256413.047962] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256413.048999] wlp5s0: authenticated
  [1256413.661996] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256418.051499] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256422.361848] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256422.364062] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256422.365122] wlp5s0: authenticated
  [1256422.978086] wlp5s0: Connection to AP 00:25:9c:xx:xx:xx lost
  [1256426.516541] wlp5s0: aborting authentication with 00:25:9c:xx:xx:xx by 
local choice (Reason: 3=DEAUTH_LEAVING)
  [1256426.518958] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.524074] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.544019] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
  [1256426.578930] wlp5s0: authenticate with 00:25:9c:xx:xx:xx
  [1256426.581309] wlp5s0: send auth to 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.582424] wlp5s0: authenticated
  [1256426.582716] wlp5s0: associate with 00:25:9c:xx:xx:xx (try 1/3)
  [1256426.583584] wlp5s0: RX AssocResp from 00:25:9c:xx:xx:xx (capab=0x11 
status=0 aid=1)
  [1256426.584763] wlp5s0: associated
  [1256426.584867] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
  [1256426.630815] bridge-wlp5s0: 

[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[UBUNTU user]

confirm issue on UBUNTU 16.04 with pulseaudio 8.0
Vahid Mardani's script is a valid temporary workaround by running it every time 
the bug appear

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

With the fix applied, we get this:

$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real0m0.023s


And the traffic happens all in UDP, since kinit got the "PREAUTH required" 
response (because now it came from the correct source IP) and just issued the 
updated request right away:
1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
2 0.002060386   10.0.5.155 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
3 0.00541204610.0.5.55 → 10.0.5.155   KRB5 311 AS-REQ
4 0.012516720   10.0.5.155 → 10.0.5.55KRB5 793 AS-REP

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  In Progress
Status in krb5 source package in Zesty:
  New
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Jamie Strandboge]

"Once I have a list of things, I was planning to file individual bugs
with a tag repeal-act-2019 (or similar)"

Can you add click-apparmor and apparmor-easyprof-ubuntu to your list if
they aren't there already?

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

Another interesting finding with grep'ing around in /var/log for VGA-1:

root@vega:/var/log# grep VGA-1 syslog
May  4 14:27:10 vega unity-settings-[1644]: unable to get EDID for 
xrandr-VGA-1: unable to get EDID for output

And maybe the even more interesing part in /var/log/gpu-manager.log

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.10.0-21-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.10.0-21-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 8086:152
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-VGA-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Nothing to do
No change - nothing to do

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I've never had a problem like this before. Now, after upgraded to
  Ubuntu 17.04 it was already strange to see the boot logo in a kind of
  low and fuzzy resolution. And it remained for the LightDM login
  screen, also for the desktop after logged on. System setting ->
  Display reports "Unknown Display". System settings -> Software &
  updates  -> Additional drivers shows title "Unknown: Unknown" though
  after that "Using Processor microcode firmware for Intel CPUs from
  intel-microcode" is active. I could "work the problem around" (see the
  end of this writing) but it's really ugly that I need to run a script
  every time, when it always worked well on the same machine before this
  Ubuntu release.

  According to xrandr:

  lgb@vega:~$ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  

  My GPU:
  lgb@vega:~$ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

  Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
  (this monitor hasn't got any other connector like HDMI or DVI).

  My workaround was to create this script and run:

  DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
  xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 
1120 -hsync +vsync
  xrandr --addmode $DEV 1920x1080
  xrandr --output $DEV --mode 1920x1080

  After this, the resolution is fine, but still everything reports
  "Unknown display" and such. The output of xrandr after running my
  script (I played with adding some modes, that is the _60.00 stuff):

  root@vega:~# xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00  
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
 1920x1080 59.96* 
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
  h: width  1920 start 2048 end 2248 total 2576 skew0 clock  
67.16KHz
  v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 

[Touch-packages] [Bug 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo

[Andreas Hasenack]

** Bug watch added: krbdev.mit.edu/rt/ #8530
   http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530

** Also affects: krb5 (Debian) via
   http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
   Importance: Unknown
   Status: Unknown

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

Title:
  KDC/kadmind explicit wildcard listener addresses do not use pktinfo

Status in krb5 package in Ubuntu:
  In Progress
Status in krb5 package in Debian:
  Unknown

Bug description:
  This is fixed in artful in krb5 1.15-2

  - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
  - debian: conflated into 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
  - debian patch in artful's krb5: 
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch

  TL;DR when kinit uses udp on an aliased interface address, server
  responds with the wrong source IP

  On zesty:
  a) install krb5-kdc and krb5-admin-server
  sudo apt install krb5-kdc krb5-admin-server
  when prompted, use EXAMPLE.ORG (all caps) as the default realm
  when prompted, select your own IP for the KDC and the Admin servers

  b) configure a new realm called EXAMPLE.ORG
  sudo krb5_newrealm
  use any password of your liking when prompted

  c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and 
with mandatory PREAUTH:
  sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu

  d) extract the ubuntu principal keytab and time how long it takes to obtain a 
ticket:
  $ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
  $ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m0.022s
  $ klist
  Ticket cache: FILE:/tmp/krb5cc_1000
  Default principal: ubu...@example.org

  Valid starting   Expires  Service principal
  05/03/2017 21:22:08  05/04/2017 07:22:08  krbtgt/example@example.org
   renew until 05/04/2017 21:22:08

  e) add another IP to your network interface. For example, this adds 
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
  sudo ip addr add 10.0.5.155/24 dev ens3

  f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc 
and admin server's IP to this new IP you just added in step (e):
  [realms]
  EXAMPLE.ORG = {
  kdc = 10.0.5.155
  admin_server = 10.0.5.155

  g) Time again how long it takes to obtain a ticket:
  $ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
  real  0m2.017s

  Step (g) shows the bug.

  On a more technical level, we can see that the server responds to kinit's UDP 
request using an incorrect source IP, therefore kinit never "sees" it. It 
quickly times out and switches to TCP, where the server responds using the 
correct source IP:
  1 0.010.0.5.55 → 10.0.5.155   KRB5 216 AS-REQ
  2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (2) has the incorrect source ip!

  After roughly 1s, kinit switches to tcp and tries again:
  3 1.00323150710.0.5.55 → 10.0.5.155   TCP 76 55588 → 88 [SYN] Seq=0 
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
  4 1.003269692   10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK] 
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273 
TSecr=3523453804 WS=128
  5 1.00330261410.0.5.55 → 10.0.5.155   TCP 68 55588 → 88 [ACK] Seq=1 
Ack=1 Win=43776 Len=0 TSval=3523453804 TSecr=2572724273
  6 1.00354520410.0.5.55 → 10.0.5.155   KRB5 244 AS-REQ
  7 1.003567693   10.0.5.155 → 10.0.5.55TCP 68 88 → 55588 [ACK] Seq=1 
Ack=177 Win=44800 Len=0 TSval=2572724273 TSecr=3523453804
  8 1.003799664   10.0.5.155 → 10.0.5.55KRB5 326 KRB Error: 
KRB5KDC_ERR_PREAUTH_REQUIRED
  (continues)
  (8) and the whole tcp handshake happens with the correct IP addresses and the 
exchange happens and we get the ticket, but not before kinit repeats the 
request with PREAUTH and UDP again. That's why it takes 2 seconds in the end :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1688121/+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 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

I'm really not an xrandr / etc wizard, but what looks strange for me,
that it seems something reports "VGA-1" when all the examples on the Net
(and in xrandr man page) mentions "VGA". Even in Xorg.log:

root@vega:~# fgrep VGA /var/log/Xorg.0.log
[25.034] (II) modeset(0): Output VGA-1 has no monitor section
[25.037] (II) modeset(0): EDID for output VGA-1
[25.037] (II) modeset(0): Printing probed modes for output VGA-1
[25.037] (II) modeset(0): Output VGA-1 connected
[25.037] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0

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

Title:
  Wrong resolution, and "unknown monitor" since upgraded to 17.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I've never had a problem like this before. Now, after upgraded to
  Ubuntu 17.04 it was already strange to see the boot logo in a kind of
  low and fuzzy resolution. And it remained for the LightDM login
  screen, also for the desktop after logged on. System setting ->
  Display reports "Unknown Display". System settings -> Software &
  updates  -> Additional drivers shows title "Unknown: Unknown" though
  after that "Using Processor microcode firmware for Intel CPUs from
  intel-microcode" is active. I could "work the problem around" (see the
  end of this writing) but it's really ugly that I need to run a script
  every time, when it always worked well on the same machine before this
  Ubuntu release.

  According to xrandr:

  lgb@vega:~$ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
  VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  

  My GPU:
  lgb@vega:~$ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

  Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
  (this monitor hasn't got any other connector like HDMI or DVI).

  My workaround was to create this script and run:

  DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
  xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 
1120 -hsync +vsync
  xrandr --addmode $DEV 1920x1080
  xrandr --output $DEV --mode 1920x1080

  After this, the resolution is fine, but still everything reports
  "Unknown display" and such. The output of xrandr after running my
  script (I played with adding some modes, that is the _60.00 stuff):

  root@vega:~# xrandr
  Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
  VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
 1024x768  60.00  
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
 1920x1080 59.96* 
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
  h: width  1920 start 2048 end 2248 total 2576 skew0 clock  
67.16KHz
  v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  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: Thu May  4 15:03:53 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-06-10 (328 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology 

[Touch-packages] [Bug 1688253] [NEW] Wrong resolution, and "unknown monitor" since upgraded to 17.04

[LGB [Gábor Lénárt]]

Public bug reported:

I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display reports "Unknown
Display". System settings -> Software & updates  -> Additional drivers
shows title "Unknown: Unknown" though after that "Using Processor
microcode firmware for Intel CPUs from intel-microcode" is active. I
could "work the problem around" (see the end of this writing) but it's
really ugly that I need to run a script every time, when it always
worked well on the same machine before this Ubuntu release.

According to xrandr:

lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 
0mm x 0mm
   1024x768  60.00* 
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  

My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)

Monitor is Samsung SyncMaster E2220, standard VGA-cable connection (this
monitor hasn't got any other connector like HDMI or DVI).

My workaround was to create this script and run:

DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 
-hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080

After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my script
(I played with adding some modes, that is the _60.00 stuff):

root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 0mm x 0mm
   1024x768  60.00  
   800x600   60.3256.25  
   848x480   60.00  
   640x480   59.94  
   1920x1080 59.96* 
  1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width  1920 start 2048 end 2248 total 2576 skew0 clock  67.16KHz
v: height 1080 start 1083 end 1088 total 1120   clock  59.96Hz

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
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: Thu May  4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Touch-packages] [Bug 1382071] Re: List of access points is empty after turning flightmode on and back off

[Duan Jiawei]

Still exist in Ubuntu 16.04.2 after I have the Hotspot off and on. 
The indicator does not show anything but I can still connect to the last wifi.

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

Title:
  List of access points is empty after turning flightmode on and back
  off

Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  14.09-proposed #109

  Test Case
  1. Open the network indicator
-> Verify that the list of access point is not empty
  2. Turn flight mode on and wait a little bit
-> Verify that cellular and wifi are disabled
  3. Turn flight mode off and wait a little bit
-> Verify that cellular and wifi are enabled
-> Verify that the list of AP is not empty

  Actual result
  The list of AP is empty after turning flightmode back on.

  "nmcli dev wifi list" shows the right list of access points

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+14.10.20141015-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct 16 16:05:38 2014
  InstallationDate: Installed on 2014-10-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141016-010328)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382071/+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 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[bugproxy]

** Tags added: architecture-s39064 bugnameltc-153940 severity-high
targetmilestone-inin1704

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  In Progress
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  In Progress
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password
  debug1: 

[Touch-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

[Stefan]

On my Lenovo B590, I was watching an mp4 movie using VLC and the computer 
became completely unresponsive, even the command line would not log me in.
Mint 17.03 (Ubuntu 14.04)
ALSA 1.0.25+dfsg-0ubuntu4
VLC Plugin Pulse 2.1.6-0ubuntu14.04.2
Pulse Audio: 1:4.0-0ubuntu11.1

My relevant syslog is attached.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+attachment/4871889/+files/pulseaudio_syslog

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Duan Jiawei]

I have encountered the same issue, I'm sure there is nothing related to the 
network-manager. This package is working properly and I can connect to any wifi 
as I with. 
However i thing it's related with the wifi indicator:)
Generally this issue recovers after I relaunch the Xorg.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware

[Etienne URBAH]

With bluez version 5.43-0ubuntu1 from Ubuntu 17.04 (Zesty), the issue is
still there :

The command 'bluetoothctl' displays 'Waiting to connect to
bluetoothd...', then hangs.


** Tags added: zesty

** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

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

Title:
  bluetoothctl systematically hangs when there is no bluetooth hardware

Status in bluez package in Ubuntu:
  New

Bug description:
  On a machine WITH bluetooth hardware, the 'bluetoothctl' command works 
correctly.
  For example, the command 'bluetoothctl < /dev/null' terminates correctly.

  On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command 
systematically hangs.
  Even the command 'bluetoothctl < /dev/null' systematically hangs.

  $ bluetoothctl &
  [1] 6208

  $ ps -l $!
  F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTYTIME CMD
  0 T  1001  6208  2525  0  80   0 -  9578 signal pts/1  0:00 bluetoothctl

  [1]+  Stopped bluetoothctl

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr  4 20:09:39 2016
  InstallationDate: Installed on 2015-07-20 (259 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterestingModules: bluetooth
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed 
root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago)
  dmi.bios.date: 06/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  hciconfig:
   
  rfkill:
   
  syslog:
   avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)...
   avril 03 15:10:45 urbah-sirius NetworkManager[986]:   Loaded device 
plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

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

** Changed in: libwacom (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

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

** Changed in: libdrm (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1687981/+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 1510570] Re: Bluetooth LE pairing fail

[Robie Basak]

Adding a task for Xenial as requested on IRC. But note that I haven't
looked into the details of the proposed fix - in particular checking for
and understanding any proposed change in behaviour for Xenial users. So
please don't take this as a +1 from ~ubuntu-sru. Before accepting this
SRU, please consider whether the proposed fix is appropriate from
scratch.

** Also affects: bluez (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Bluetooth LE pairing fail

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  New

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1649310] Re: RM Upstart, obsolete, superseded by systemd / Products discontinued

[Iain Lane]

On Thu, May 04, 2017 at 10:50:21AM -, Dimitri John Ledkov wrote:
> On 4 May 2017 at 11:32, Will Cooke <1649...@bugs.launchpad.net> wrote:
> > Can/Should we deal with the U8 apps which are unsupported in this bug as
> > well?
> >
> 
> The list for those might be a bit too large to load and manipulate
> statuses effectively.
> I am preparing a great repeal list of u8 things. Because it includes
> android-touch, gles, and platform apis as well as the top-level apps.
> Once I have a list of things, I was planning to file individual bugs
> with a tag repeal-act-2019 (or similar), as we should be removing
> things in the right order to avoid proposed-migration seeing
> uninstallable things.

It would be a good idea to share this list before starting to act on it.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  RM Upstart, obsolete, superseded by systemd / Products discontinued

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart-watchdog package in Ubuntu:
  Fix Released

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+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 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

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

** Changed in: libinput (Ubuntu)
   Status: New => Invalid

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in debhelper package in Ubuntu:
  Invalid
Status in dh-autoreconf package in Ubuntu:
  New
Status in libinput package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in debhelper source package in Xenial:
  New
Status in dh-autoreconf source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  hwe-16.04 refresh for 16.04.3

  Many packages need debhelper10 or would have to revert various
  packaging changes to work with dh9.

  xorg-server 1.19 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because
  the unity mouse config doesn't work with -libinput.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

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