[Touch-packages] [Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Stéphane Graber]

I fixed this in upstream LXC yesterday, will upload SRUs today.

** Changed in: lxc (Ubuntu)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

** Changed in: lxc (Ubuntu)
   Importance: Undecided => High

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  In Progress

Bug description:
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

[Gennadii Kurabko]

I've enabled extended and debug logging (-E -d) in file:
/lib/systemd/system/bluetooth.service

was: ExecStart=/usr/lib/bluetooth/bluetoothd
now: ExecStart=/usr/lib/bluetooth/bluetoothd -E -d

Please find logs below, in attachments. Hope it will help to pin down
the problem.

$ uname -a
Linux xxx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC 2016 i686 
i686 i686 GNU/Linux

BlueZ version 5.37

$ journalctl --unit=bluetooth


** Attachment added: "bluetoothd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+attachment/4764895/+files/bluetoothd.txt

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Martin Pitt]

Hello Curtis, or anyone else affected,

Accepted lxc into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/2.0.5-0ubuntu1.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 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: lxc (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions

-- 

[Touch-packages] [Bug 1635639] Please test proposed package

[Martin Pitt]

Hello Curtis, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.5-0ubuntu1~ubuntu16.04.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 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!

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+subscriptions

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

[Touch-packages] [Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Curtis Hovey]

Current and new lxd containers are still broken. We see errors like this

lxc start xenial-manual-a xenial-manual-b xenial-manual-c
error: Error calling 'lxd forkstart xenial-manual-a /var/lib/lxd/containers 
/var/log/lxd/xenial-manual-a/lxc.conf': err='exit status 1'
  lxc 20161021035819.243 ERROR lxc_seccomp - seccomp.c:get_new_ctx:224 - 
Seccomp error -17 (File exists) adding arch: 15
  lxc 20161021035819.243 ERROR lxc_start - start.c:lxc_init:430 - failed 
loading seccomp policy
  lxc 20161021035819.243 ERROR lxc_start - start.c:__lxc_start:1313 - failed to 
initialize the container

** Description changed:

  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.
  
  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x
  
  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.
  
- $ cat lxc.log 
-   lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
-   lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
-   lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
-   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
-   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
-   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.
- 
+ $ cat lxc.log
+   lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
+   lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
+   lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
+   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
+   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
+   lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.
  
  #  sinzui: checking when s390x seccomp support was added to the
- # kernel, to see if it's just a missing config in our kernel that'd fix that 
- # cleanly or if we'd need it backported to 4.4 which would be a bit more 
+ # kernel, to see if it's just a missing config in our kernel that'd fix that
+ # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again
  
- WORK AROUND
+ WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  Fix Committed
Status in lxc package in Ubuntu:
  New

Bug description:
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 

[Touch-packages] [Bug 1635654] [NEW] Machine fails to stop, or start interfaces. hangs in systemd waiting for completion

[LaMont Jones]

Public bug reported:

The attached /etc/network/interfaces file is fatal to
/lib/systemd/system/networking.service, resulting in a loop that never
finishes.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ifupdown 0.8.13ubuntu4
ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 21 09:14:33 2016
InstallationDate: Installed on 2014-09-22 (759 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: ifupdown
UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Machine fails to stop, or start interfaces.  hangs in systemd waiting
  for completion

Status in ifupdown package in Ubuntu:
  New

Bug description:
  The attached /etc/network/interfaces file is fatal to
  /lib/systemd/system/networking.service, resulting in a loop that never
  finishes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ifupdown 0.8.13ubuntu4
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 09:14:33 2016
  InstallationDate: Installed on 2014-09-22 (759 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Curtis Hovey]

** Changed in: juju-ci-tools
   Status: Fix Committed => In Progress

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  New

Bug description:
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion

[LaMont Jones]

** Attachment added: "/e/n/i that results in a loop"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+attachment/4764881/+files/interfaces

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

Title:
  Machine fails to stop, or start interfaces.  hangs in systemd waiting
  for completion

Status in ifupdown package in Ubuntu:
  New

Bug description:
  The attached /etc/network/interfaces file is fatal to
  /lib/systemd/system/networking.service, resulting in a loop that never
  finishes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ifupdown 0.8.13ubuntu4
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 09:14:33 2016
  InstallationDate: Installed on 2014-09-22 (759 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+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 1635668] [NEW] [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted

[Jim Tarvid]

Public bug reported:

This defect is not apparent on two other Ubuntu 16.04 machines. The
upgrade to 16.10 did not change the symptoms.

lsb_release -rd
Description:Ubuntu 16.10
Release:16.10

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 21 11:53:54 2016
InstallationDate: Installed on 2016-09-22 (29 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA 
ATI HDMI
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0773VG
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This defect is not apparent on two other Ubuntu 16.04 machines. The
  upgrade to 16.10 did not change the symptoms.

  lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 11:53:54 2016
  InstallationDate: Installed on 2016-09-22 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - 
HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0773VG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+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 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion

[LaMont Jones]

After you change your /e/n/i to that, and reproduce the issue,
break=init, and then mount -oremount,rw /root; chroot /root; vi
/etc/network/interfaces and comment out everything from "auto br1" to
end of file, exit; mount -oremount,ro /root; exit

and you're back to a bootable system...  Which is why the apport files
are pretty much useless on this report.

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

Title:
  Machine fails to stop, or start interfaces.  hangs in systemd waiting
  for completion

Status in ifupdown package in Ubuntu:
  New

Bug description:
  The attached /etc/network/interfaces file is fatal to
  /lib/systemd/system/networking.service, resulting in a loop that never
  finishes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ifupdown 0.8.13ubuntu4
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 09:14:33 2016
  InstallationDate: Installed on 2014-09-22 (759 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+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 1635654] Re: Machine fails to stop, or start interfaces. hangs in systemd waiting for completion

[LaMont Jones]

The reboot of the system prior to this morning was after a dist-upgrade
on "2016-10-14 08:30:10" according to  /var/log/apt/history.log -- the
upgrade to zesty occurred on 2016-10-18, and the reboot was after a
fresh dist-upgrade this morning, on zesty.

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

Title:
  Machine fails to stop, or start interfaces.  hangs in systemd waiting
  for completion

Status in ifupdown package in Ubuntu:
  New

Bug description:
  The attached /etc/network/interfaces file is fatal to
  /lib/systemd/system/networking.service, resulting in a loop that never
  finishes.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ifupdown 0.8.13ubuntu4
  ProcVersionSignature: Ubuntu 
4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 09:14:33 2016
  InstallationDate: Installed on 2014-09-22 (759 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to zesty on 2014-11-14 (706 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1635654/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

[Alessio Tona]

I applied both solution of #5 and #45. After running the python script
my headset started working correctly. I don't know if it is solution of
#45 or the combination of #5 and #45, but it works now. Thanks!

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Stéphane Graber]

** Changed in: lxc (Ubuntu)
   Status: In Progress => Triaged

** Also affects: lxc (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: lxc (Ubuntu Zesty)
   Importance: High
 Assignee: Stéphane Graber (stgraber)
   Status: Triaged

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: lxc (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: lxc (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: lxc (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: lxc (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: lxc (Ubuntu Yakkety)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxc (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Description changed:

+ ## SRU paperwork
+ ### Rationale
+ LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.
+ 
+ This effectively means that LXC 2.0.5 fails out of the box on s390x.
+ 
+ ### Test case
+ With LXC:
+  - lxc-start -n some-container -F
+ 
+ With LXD:
+  - lxc start some-container
+ 
+ ### Regression potential
+ Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.
+ 
+ The worst that can happen should this fix be wrong is either status quo
+ (container won't start) or having the container start without seccomp
+ support (status quo when compared to 2.0.4).
+ 
+ 
+ ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.
  
  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x
  
  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.
  
  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.
  
  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again
  
  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed
Status in lxc source package in Yakkety:
  Fix Committed
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - 

[Touch-packages] [Bug 1471123] Re: suddenly tabulator-key stops working normally

[Aapo Rantalainen]

After fresh install on Ubuntu 16.04 I found this will break tab key instantly:
xmodmap -e 'clear Mod4'


My goal was to remap Super_L to be additional Alt_L (and not affect tab key at 
all):

This works for me on Ubuntu 16.04 (with xfce):
xmodmap -e 'remove mod4 = Super_L'
xmodmap -e 'remove mod4 = Hyper_L'
xmodmap -e 'keycode 133 = Alt_L'
xmodmap -e 'add mod4 = Super_L Hyper_L'

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

Title:
  suddenly tabulator-key stops working normally

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04
  xserver-xorg: 1:7.7+1ubuntu8.1

  I don't know how to trigger this bug, but I have seen it now more than
  ten times.

  "Suddenly" = I can't figure pattern how this triggers. Sometimes it
  happens when computer just idles

  'stops working normally' = tab-key alone doesn't do anything.

  --
  When tab-key is working normally, xev reports:

  KeyPress event, serial 37, synthetic NO, window 0x241,
  root 0x290, subw 0x0, time 2088488, (164,-6), root:(1515,797),
  state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XmbLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x241,
  root 0x290, subw 0x0, time 2088509, (164,-6), root:(1515,797),
  state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  --
  When this bug triggers, xev reports (when tab-key pressed and released):

  FocusOut event, serial 37, synthetic NO, window 0x561,
  mode NotifyGrab, detail NotifyAncestor

  FocusIn event, serial 37, synthetic NO, window 0x561,
  mode NotifyUngrab, detail NotifyAncestor

  KeymapNotify event, serial 37, synthetic NO, window 0x0,
  keys: 4294967184 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

  --
  When this bug triggers, xev reports (when holding CTRL and tab-key pressed 
and released):

  KeyPress event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350060, (172,-19), root:(1523,784),
  state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350228, (172,-19), root:(1523,784),
  state 0x4, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XmbLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350276, (172,-19), root:(1523,784),
  state 0x4, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350572, (172,-19), root:(1523,784),
  state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
  ---
  And behaviour is like xev reports: tab pressed alone doesn't do anything, but 
with any modifier it works as expected:
  alt+tab = change window
  shift+tab = previous element (e.g. fields in browser)
  ctrl+tab = change tab (e.g. in firefox)

  -
  I have ~/.Xmodmap and it contains line:
  keycode 23 = Tab ISO_Left_Tab Tab ISO_Left_Tab Tab ISO_Left_Tab

  Running xmodmap ~/.Xmodmap will not fix.

  ---
  Attaching new usb-keyboard doesn't help.
  ---
  Reboot helps.
  Restarting xorg helps.
  ---
  Changing to virtual terminal -> tab is working. But after returning to xorg, 
tab is still broken.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-15 (740 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags: trusty third-party-packages
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-13 (561 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1471123/+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 1611821] Re: Dell XPS One 27: Headphone jack and speakers mutuated after upgrade to 16.04

[Rubeosis]

As a workarount use hda-jack-retask

http://askubuntu.com/questions/832248/sound-is-not-working-in-dell-xps-
all-in-one-2710-running-ubuntu-16-04

"Praise of God i could solving the problem by installing "hda-jack-
retask" - open the terminal and post: [ sudo apt-get install alsa-tools-
gui ] - then post: [ hdajackretask ] in the gui of "jack retasking" i
found "green Headphone" set as "headphone" i checked "override" and
choose "internal speaker" then i pressed the button "apply now" then
"install boot override" then reboot finally, the problem solved ... I'm
happy now ... thanks for every one tried to help me ... thank you very
much"

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

Title:
  Dell XPS One 27: Headphone jack and speakers mutuated after upgrade to
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Dell XPS One 27: Sound working correctly in 14.04. After complete
  reinstall of 16.04 headphone jack and speakers are mutuated. Manual
  correction of output level (headphones) with alsamixer leads to a
  correct sound output.

  
  Same problem here: 
http://askubuntu.com/questions/810053/speaker-and-headphone-ports-are-switched

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   fabian 3570 F...m pulseaudio
   /dev/snd/controlC0:  fabian 3570 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 10 17:21:18 2016
  InstallationDate: Installed on 2016-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02XMCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/03/2012:svnDellInc.:pnXPSOne2710:pvr00:rvnDellInc.:rn02XMCT:rvrA01:cvnDellInc.:ct13:cvr00:
  dmi.product.name: XPS One 2710
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1611821/+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 1635707] [NEW] package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

[Jeraimee]

Public bug reported:

Description:Ubuntu 16.10
Release:16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: openssh-server 1:7.3p1-1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 ncurses-term:amd64: Install
 openssh-sftp-server:amd64: Install
 openssh-server:amd64: Install
 ssh-import-id:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Oct 18 10:39:14 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
InstallationDate: Installed on 2016-10-14 (7 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: openssh
Title: package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 255
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages yakkety

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

Title:
  package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 255

Status in openssh package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: openssh-server 1:7.3p1-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ncurses-term:amd64: Install
   openssh-sftp-server:amd64: Install
   openssh-server:amd64: Install
   ssh-import-id:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Oct 18 10:39:14 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2016-10-14 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: openssh
  Title: package openssh-server 1:7.3p1-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 255
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1635707/+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 1635683] [NEW] lxc bridged interface with multiple bridges sometimes assign the interface to wrong bridge

[Yinon]

Public bug reported:

I am launching a massive setup of 220 containers over 11 bare metal servers.
I set this in the profile for all containers:
lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip

stack@c6-bl-13:~$ lxc profile show devstack-profile
name: devstack-profile
config:
  linux.kernel_modules: br_netfilter
description: ""
devices:
  eth0:
nictype: bridged
parent: br-lxd-mgmt
type: nic
  eth1:
nictype: bridged
parent: br-lxd-fip
type: nic

But I found that for some containers, the conf file was not created accordingly:
stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br-lxd-fip
lxc.network.hwaddr = 00:16:3e:f5:bf:60
lxc.network.name = eth0
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br-lxd-mgmt
lxc.network.hwaddr = 00:16:3e:cb:8e:17
lxc.network.name = eth1

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

** Description changed:

  I am launching a massive setup of 220 containers over 11 bare metal servers.
  I set this in the profile for all containers:
  lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
  lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip
  
- But I found that the conf file was not created accordingly:
+ stack@c6-bl-13:~$ lxc profile show devstack-profile
+ name: devstack-profile
+ config:
+   linux.kernel_modules: br_netfilter
+ description: ""
+ devices:
+   eth0:
+ nictype: bridged
+ parent: br-lxd-mgmt
+ type: nic
+   eth1:
+ nictype: bridged
+ parent: br-lxd-fip
+ type: nic
  
+ But I found that for some containers, the conf file was not created 
accordingly:
+ stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-fip
  lxc.network.hwaddr = 00:16:3e:f5:bf:60
  lxc.network.name = eth0
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-mgmt
  lxc.network.hwaddr = 00:16:3e:cb:8e:17
  lxc.network.name = eth1

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

Title:
  lxc bridged interface with multiple bridges sometimes assign the
  interface to wrong bridge

Status in lxc package in Ubuntu:
  New

Bug description:
  I am launching a massive setup of 220 containers over 11 bare metal servers.
  I set this in the profile for all containers:
  lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
  lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip

  stack@c6-bl-13:~$ lxc profile show devstack-profile
  name: devstack-profile
  config:
linux.kernel_modules: br_netfilter
  description: ""
  devices:
eth0:
  nictype: bridged
  parent: br-lxd-mgmt
  type: nic
eth1:
  nictype: bridged
  parent: br-lxd-fip
  type: nic

  But I found that for some containers, the conf file was not created 
accordingly:
  stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-fip
  lxc.network.hwaddr = 00:16:3e:f5:bf:60
  lxc.network.name = eth0
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-mgmt
  lxc.network.hwaddr = 00:16:3e:cb:8e:17
  lxc.network.name = eth1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1635683/+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 1635683] Re: lxc bridged interface with multiple bridges sometimes assign the interface to wrong bridge

[Yinon]

OK, Thanks. Closed as invalid.

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

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

Title:
  lxc bridged interface with multiple bridges sometimes assign the
  interface to wrong bridge

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  I am launching a massive setup of 220 containers over 11 bare metal servers.
  I set this in the profile for all containers:
  lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
  lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip

  stack@c6-bl-13:~$ lxc profile show devstack-profile
  name: devstack-profile
  config:
linux.kernel_modules: br_netfilter
  description: ""
  devices:
eth0:
  nictype: bridged
  parent: br-lxd-mgmt
  type: nic
eth1:
  nictype: bridged
  parent: br-lxd-fip
  type: nic

  But I found that for some containers, the conf file was not created 
accordingly:
  stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-fip
  lxc.network.hwaddr = 00:16:3e:f5:bf:60
  lxc.network.name = eth0
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-mgmt
  lxc.network.hwaddr = 00:16:3e:cb:8e:17
  lxc.network.name = eth1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1635683/+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 1629552] Re: files with the same name installed in / and /usr

[Martin Pitt]

** Changed in: json-c (Ubuntu)
   Status: New => In Progress

** Changed in: json-c (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: json-c (Ubuntu)
Milestone: None => ubuntu-16.11

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

Title:
  files with the same name installed in / and /usr

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in genwqe package in Ubuntu:
  Invalid
Status in grub package in Ubuntu:
  New
Status in json-c package in Ubuntu:
  In Progress

Bug description:
  A few remaining packages in Ubuntu are incompatible with a merged /usr
  because they ship the same file in /bin and /usr/bin; it looks like
  Debian will soon default to that, and we surely want to follow suit.

  The duplicate file/symlink needs to be removed, or created in
  postinst.

https://bugs.debian.org/cgi-
  bin/pkgreport.cgi?tag=usrmerge;users=m...@linux.it

  cgroup-lite:

  lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-umount -> 
/bin/cgroups-umount
  lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-mount -> 
/bin/cgroups-mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1629552/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

[Jorge Niedbalski]

** Changed in: libnl3 (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: libnl3 (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  In Progress

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635681] [NEW] font related bug

[imran]

Public bug reported:

i upgrade 16.04 to 16.10 after upgrading it occurs fonts related
bugs.please fix it.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
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
Date: Fri Oct 21 22:54:23 2016
DistUpgraded: 2016-10-21 19:00:00,788 DEBUG running apport_crash()
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
InstallationDate: Installed on 2016-10-16 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 003: ID 17ef:4810 Lenovo Integrated Webcam [R5U877]
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 0585DG2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=16572a56-8faa-4a65-ab95-b5efced0cc37 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
dmi.bios.date: 01/11/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET49WW (1.25 )
dmi.board.name: 0585DG2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr81ET49WW(1.25):bd01/11/2011:svnLENOVO:pn0585DG2:pvrThinkPadL412:rvnLENOVO:rn0585DG2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 0585DG2
dmi.product.version: ThinkPad L412
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Oct 21 22:17:26 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 fonts ubuntu yakkety

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

Title:
  font related bug

Status in xorg package in Ubuntu:
  New

Bug description:
  i upgrade 16.04 to 16.10 after upgrading it occurs fonts related
  bugs.please fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  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
  Date: Fri Oct 21 22:54:23 2016
  DistUpgraded: 2016-10-21 19:00:00,788 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-10-16 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 003: 

[Touch-packages] [Bug 1446448] Re: ssh-agent terminates

[Andrej Ricnik]

Thanks Seth, I doubt that keychain is (even in part) responsible for
this behaviour; I'll try to confirm Tuesday - after the long weekend -
when I'm back at work.

Thanks for responding Robie.

I apologise - was on a rampage because the other bug that I'm sitting on
(not as the original reporter, but as an impatient watcher) has been
open since 2012 ... and it bites many people, anyone who has a)
resonably frequent changes to network interfaces and b) runs an iSCSI
connected SAN.

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

Title:
  ssh-agent terminates

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I have set-up password less ssh connectivity for my workstation.  ssh-
  agent gets started via keychain when fluxbox boots.

  When I use ssh to connect to a server, and then use scp to shuffle a
  file from that server to my workstation the ssh-agent on my
  workstation dies after the file was transferred.

  This has started happening after the upgrade  from 12.04 to 14.04.

  I have wrapped strace into the fluxbox startup to keep an eye on ssh-
  agent (I initially didn't see a pattern to the sudden death), here's
  an example of the breakdown post transfer.

  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21130, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "\0\0\0\1\v", 1024) = 5
  select(5, [3 4], [4], NULL, NULL)   = 1 (out [4])
  write(4, "\0\0\1<\f\0\0\0\1\0\0\1\27\0\0\0\7ssh-rsa\0\0\0\3\1\0\1\0"..., 320) 
= 320
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21284, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = ? ERESTARTNOHAND (To be restarted 
if no handler)
  --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=21284, si_uid=0} ---
  unlink("/tmp/ssh-DEwJJTGLUETC/agent.19556") = 0
  rmdir("/tmp/ssh-DEwJJTGLUETC")  = 0
  close(-1)   = -1 EBADF (Bad file descriptor)
  exit_group(2)   = ?
  +++ exited with 2 +++


  1) lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  
  2) apt-cache policy openssh-client
  openssh-client:
Installed: 1:6.6p1-2ubuntu2
Candidate: 1:6.6p1-2ubuntu2
Version table:
   *** 1:6.6p1-2ubuntu2 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.6p1-2ubuntu1 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) I expect ssh-agent to carry on running as it did in previous
  releases.

  4) It dies when connecting back from a machine I ssh into to my
  workstation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Tue Apr 21 15:28:02 2015
  InstallationDate: Installed on 2015-02-03 (77 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-ssh2.0-1
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ssh-agent.log: ssh-agent stop/pre-start, process 1973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1446448/+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 1577460] Re: mkinitramfs --help > Core dumped

[Anders Kaseorg]

Upstream applied an equivalent patch:
http://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/?id=e1164591f7927402af8d73d340e75dbfeb06a288

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

Title:
  mkinitramfs --help > Core dumped

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in glibc package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in glibc source package in Xenial:
  Fix Committed
Status in util-linux source package in Xenial:
  New

Bug description:
  Problem Description
  ==
  root@zlin060:~# mkinitramfs --help
  Segmentation fault (core dumped)
  W: non-GNU getopt
  root@zlin060:~#

  == Comment: #9 - Heinz-Werner Seeck  - 
2016-05-02 10:09:34 ==
  With Ubuntu 14.40 login via ssh:

  Following cmd :
  'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help'

  Following call-stack occured (creates coredump):

  #0  __strncmp_c (s1=0x2e6575634a500a6d , 
  s1@entry=0x2e6575634a500a6a , 
  s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at 
../string/strncmp.c:44
  #1  0x03ff7e9d4252 in _getopt_internal_r (argc=, 
argv=0x40, 
  optstring=0x20030 , longopts=, 
  longind=, long_only=0, d=0x3ff7ea8c330 , 
posixly_correct=0) at getopt.c:546
  #2  0x03ff7e9d51f2 in _getopt_internal (argc=, 
argv=, 
  optstring=, longopts=, 
longind=0x3fff7ffe674, long_only=0, posixly_correct=0)
  at getopt.c:1175
  #3  0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, 
  long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65
  #4  0x02aa236821d8 in ?? ()
  #5  0x02aa23681c22 in main ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+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 1635683] Re: lxc bridged interface with multiple bridges sometimes assign the interface to wrong bridge

[Yinon]

** Tags added: lxc lxd

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

Title:
  lxc bridged interface with multiple bridges sometimes assign the
  interface to wrong bridge

Status in lxc package in Ubuntu:
  New

Bug description:
  I am launching a massive setup of 220 containers over 11 bare metal servers.
  I set this in the profile for all containers:
  lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
  lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip

  stack@c6-bl-13:~$ lxc profile show devstack-profile
  name: devstack-profile
  config:
linux.kernel_modules: br_netfilter
  description: ""
  devices:
eth0:
  nictype: bridged
  parent: br-lxd-mgmt
  type: nic
eth1:
  nictype: bridged
  parent: br-lxd-fip
  type: nic

  But I found that for some containers, the conf file was not created 
accordingly:
  stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-fip
  lxc.network.hwaddr = 00:16:3e:f5:bf:60
  lxc.network.name = eth0
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-mgmt
  lxc.network.hwaddr = 00:16:3e:cb:8e:17
  lxc.network.name = eth1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1635683/+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 1635683] Re: lxc bridged interface with multiple bridges sometimes assign the interface to wrong bridge

[Stéphane Graber]

That's actually completely expected since you didn't set the "name"
property on that network device.

"eth0" above refers to the LXD device entry name which has nothing to do
with the device name in the container.

So you need to do:
lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt name=eth0
lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip name=eth1

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

Title:
  lxc bridged interface with multiple bridges sometimes assign the
  interface to wrong bridge

Status in lxc package in Ubuntu:
  New

Bug description:
  I am launching a massive setup of 220 containers over 11 bare metal servers.
  I set this in the profile for all containers:
  lxc profile device add devstack-profile eth0 nic nictype=bridged 
parent=br-lxd-mgmt
  lxc profile device add devstack-profile eth1 nic nictype=bridged 
parent=br-lxd-fip

  stack@c6-bl-13:~$ lxc profile show devstack-profile
  name: devstack-profile
  config:
linux.kernel_modules: br_netfilter
  description: ""
  devices:
eth0:
  nictype: bridged
  parent: br-lxd-mgmt
  type: nic
eth1:
  nictype: bridged
  parent: br-lxd-fip
  type: nic

  But I found that for some containers, the conf file was not created 
accordingly:
  stack@c6-bl-13:~$ grep network 
/var/log/lxd/nvp-scale-1-c6-bl-13-compute-2/lxc.conf
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-fip
  lxc.network.hwaddr = 00:16:3e:f5:bf:60
  lxc.network.name = eth0
  lxc.network.type = veth
  lxc.network.flags = up
  lxc.network.link = br-lxd-mgmt
  lxc.network.hwaddr = 00:16:3e:cb:8e:17
  lxc.network.name = eth1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1635683/+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 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[Matt Raines]

I see this immediately after upgrading from 16.04 to 16.10. It's also
the case with the result area in gnome-calculator. A screenshot is
attached.

** Attachment added: "Screenshot from 2016-10-21 18-55-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1620806/+attachment/4764943/+files/Screenshot%20from%202016-10-21%2018-55-22.png

** Information type changed from Public to Public Security

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+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 1635690] [NEW] package udev 229-4ubuntu10 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Salvador Villalgordo]

Public bug reported:

informar del problema

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 98_smfpautoconf_samsung.rules
Date: Tue Oct 18 15:48:54 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2016-09-03 (47 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=e0cbe8e9-b9c4-4526-9b51-94dec439f0db ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: systemd
Title: package udev 229-4ubuntu10 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: G31M-GS.
dmi.board.vendor: ASRock
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.:bvrP1.60:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS.:rvr: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.

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


** Tags: apport-package i386 xenial

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

Title:
  package udev 229-4ubuntu10 failed to install/upgrade: el subproceso
  instalado el script post-installation devolvió el código de salida de
  error 1

Status in systemd package in Ubuntu:
  New

Bug description:
  informar del problema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 
98_smfpautoconf_samsung.rules
  Date: Tue Oct 18 15:48:54 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-09-03 (47 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=e0cbe8e9-b9c4-4526-9b51-94dec439f0db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu10 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: G31M-GS.
  dmi.board.vendor: ASRock
  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.:bvrP1.60:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS.:rvr: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635690/+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 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop

[Launchpad Bug Tracker]

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

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

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

Title:
  brightness not changing from either  u-s-s or hardkey on
  unity8-desktop

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in repowerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Running unity8-desktop session on my macbookpro which has a hard display 
brightness key, currently it makes no effect. Also, opened 
ubuntu-sytstem-settings and changing the brightness slider also makes no effect.
  sorry for spamming projects, not sure which to log against.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+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 1635639] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1635639

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.5-0ubuntu1~ubuntu16.04.2

---
lxc (2.0.5-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium

  * Cherry-pick bugfix from upstream:
- s390x: Fix seccomp handling of personalities (LP: #1635639)

 -- Stéphane Graber   Fri, 21 Oct 2016 12:39:18
-0400

** Changed in: lxc (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1635753] [NEW] After Installing Ubuntu

[Joshua Arnejo]

Public bug reported:

My further request for any crashing applications and errors, please that
I promise when I use this Operating System after I installed types of
applications.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
BootLog: /dev/sda5: clean, 312852/12214272 files, 4583018/48827904 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Oct 22 07:21:26 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-10-12 (9 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=e31e261f-58b4-4524-974a-ad1958cf37e5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H55M-LE
dmi.board.vendor: ASRock
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.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr: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.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Oct 22 06:00:57 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSIGMACHIP Usb Mouse  MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.1
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 possible-manual-nvidia-install ubuntu xenial

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

Title:
  After Installing Ubuntu

Status in xorg package in Ubuntu:
  New

Bug description:
  My further request for any crashing applications and errors, please
  that I promise when I use this Operating System after I installed
  types of applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog: /dev/sda5: clean, 312852/12214272 files, 4583018/48827904 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 22 07:21:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-10-12 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   

[Touch-packages] [Bug 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.5-0ubuntu1.1

---
lxc (2.0.5-0ubuntu1.1) yakkety; urgency=medium

  * Cherry-pick bugfix from upstream:
- s390x: Fix seccomp handling of personalities (LP: #1635639)

 -- Stéphane Graber   Fri, 21 Oct 2016 12:40:08
-0400

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Stéphane Graber]

Confirmed on both xenial and yakkety.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Triaged
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Triaged

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1633219] Re: Upgrade to yakkety fails due to non-us locale

[VPablo]

Please, correct this bug. With Spanish format it hangs as described but
changing the numbers, date and so on to English (EEUU) it works perfect.

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

Title:
  Upgrade to yakkety fails due to non-us locale

Status in python-apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to yakkety failed during updates installation. The do-release-
  upgrade window froze and there was a stacktrace in the terminal:

  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in 
add_to_existing
  self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
  block = f.read(1048576)
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: 
invalid start byte

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-tqyb12c_/yakkety", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeMain.py", line 
242, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1880, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1845, in fullUpgrade
  if not self.doDistUpgrade():
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeController.py", 
line 1183, in doDistUpgrade
  res = self.cache.commit(fprogress,iprogress)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeCache.py", line 
267, in commit
  apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
  res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in 
install_archives
  res = install_progress.run(pm)
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeView.py", line 
234, in run
  res = os.WEXITSTATUS(self.wait_child())
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 339, in wait_child
  self.update_interface()
File 
"/tmp/ubuntu-release-upgrader-tqyb12c_/DistUpgrade/DistUpgradeViewGtk3.py", 
line 346, in update_interface
  InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in 
update_interface
  if float(percent) != self.percent or status_str != self.status:
  ValueError: could not convert string to float: '0,'

  
  It seems, that it's because release-upgrader incorrectly works with locale: 
Russian locale uses "," as a floating point separator, rather than ".", so it 
generates the "0," somewhere and cannot parse it 

[Touch-packages] [Bug 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

[Joshua Powers]

** Changed in: ubuntu-release-notes
   Status: New => Incomplete

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

Title:
  Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

Status in Release Notes for Ubuntu:
  Incomplete
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  With lxc installed, the 15.04 -> 15.10 upgrade fails. The upgrade
  completes if LXC is removed and then reinstalled later. Here is me
  using apt to try and make it work (gives same errors as upgrade-
  manager did):

  
  Setting up lxc (1.1.4-0ubuntu1) ...
  Job for lxc-net.service failed because the control process exited with error 
code. See "systemctl status lxc-net.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lxc-net, action "start" failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of lxc-templates:
   lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however:
Package lxc is not configured yet.

  dpkg: error processing package lxc-templates (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   lxc
   lxc-templates
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ╭─michael@michael-desktop-ubuntu  ~ ‹› 
  ╰─$ systemctl status lxc-net.service  

   100 ↵
  ● lxc-net.service - LXC network bridge setup
 Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2015-10-22 12:50:07 AEDT; 27s 
ago
Process: 22655 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start 
(code=exited, status=1/FAILURE)
   Main PID: 22655 (code=exited, status=1/FAILURE)

  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Starting LXC network 
bridge setup...
  Oct 22 12:50:07 michael-desktop-ubuntu lxc-net[22655]: lxc-net is already 
running
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Main 
process exited, code=exited, status=1/FAILURE
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Failed to start LXC 
network bridge setup.
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Unit 
entered failed state.
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+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 1360342] Re: Add Multi-arch support in libxi-dev

[Bug Watch Updater]

** Changed in: libxi (Debian)
   Status: Unknown => New

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

Title:
  Add Multi-arch support in libxi-dev

Status in libxi package in Ubuntu:
  Confirmed
Status in libxi package in Debian:
  New

Bug description:
  Please add Multi-arch support in libxi-dev. Would really help in
  crosscompiling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1360342/+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 1635774] [NEW] package libflite1 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x8

[Thomas Beltran]

Public bug reported:

This happened while installing updates

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libflite1 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
Uname: Linux 3.13.0-100-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Oct 21 19:50:59 2016
DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
InstallationDate: Installed on 2016-10-22 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: flite
Title: package libflite1 (not installed) failed to install/upgrade: cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package libflite1 (not installed) failed to install/upgrade: cannot
  copy extracted data for './usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end of file or
  stream

Status in flite package in Ubuntu:
  New

Bug description:
  This happened while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libflite1 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 21 19:50:59 2016
  DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: flite
  Title: package libflite1 (not installed) failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' 
to '/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1635774/+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 1635639] Re: Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Stéphane Graber]

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

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  In Progress
Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Xenial:
  Fix Released
Status in lxc source package in Yakkety:
  Fix Released
Status in lxc source package in Zesty:
  Fix Committed

Bug description:
  ## SRU paperwork
  ### Rationale
  LXC 2.0.5 added support for Seccomp on the s390x architecture for those 
kernels that support it. Unfortunately the personality handling for s390x is 
wrong and results in the profile being setup twice, causing a failure to start 
the container.

  This effectively means that LXC 2.0.5 fails out of the box on s390x.

  ### Test case
  With LXC:
   - lxc-start -n some-container -F

  With LXD:
   - lxc start some-container

  ### Regression potential
  Our own testing shows that the fix works perfectly fine. The code change 
itself only affects s390x (under ifdef) so can't possibly affect the other 
architectures.

  The worst that can happen should this fix be wrong is either status
  quo (container won't start) or having the container start without
  seccomp support (status quo when compared to 2.0.4).


  ## Original bug report
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log
    lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
    lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
    lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
    lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that
  # cleanly or if we'd need it backported to 4.4 which would be a bit more
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you can workaround it by putting a file
  # with lxc.seccomp=
  # in /usr/share/lxc/config/common.conf.d/, that should get you going again

  WORK AROUND for LXC 1
  # on the s390x-slave
  sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  $ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
  # Advised to stgraber to add this file after seeing lxc-start fail with
  # lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
  lxc.seccomp=

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-ci-tools/+bug/1635639/+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 1373070] Re: full fix for disconnected path (paths)

[Launchpad Bug Tracker]

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

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

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

Title:
  full fix for disconnected path (paths)

Status in cups package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  With the apparmor 3 RC1 upload, there is an incomplete bug fix for
  disconnected paths. This bug is to track that work.

  This denial may be related:
  Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 
audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed 
name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" 
name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  This is related to bug 1375410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1579580] Re: ureadahead reports relative path errors in journalctl output

[Rich McAllister]

/sbin/ureadahead is writing out warnings every time it gets a relative
path from debugfs.  This seems excessively wordy, but putting a -q on
the ExecStart in ureadahead.service would shut it up.

I did a systemd drop-in as a workaround by creating
/etc/systemd/system/ureadahead.service.d/quiet.conf containing

[Service]
ExecStart=
ExecStart=/sbin/ureadahead -q

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1379427] Re: /etc/network/if-up.d/upstart emits static-network-up too early

[Jared Fernandez]

** Summary changed:

- /etc/network/if-up.d/upstart emits static-network-up to early
+ /etc/network/if-up.d/upstart emits static-network-up too early

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

Title:
  /etc/network/if-up.d/upstart emits static-network-up too early

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  I came across this when debugging bug 1352255.
  as implemented right now (trusty and utopic) the 'static-network-up' event is 
emitted when each 'auto' interface has had *an* address configured, as opposed 
to *all* addresses configured.

  Heres why:
   ifupdown calls runparts on /etc/network/if-up.d/ after each stanza for a 
network inteface, rather than once after *all* stanzas are executed.

  The result is that things that were waiting on 'static-network-up',
  expecting that would provide them with expected networking are not
  actually guaranteed anything other than the first stanza for each
  interface.

  (note also that this happens to cause strange behavior in bug
  1352255).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ifupdown 0.7.47.2ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Oct  9 12:37:10 2014
  InstallationDate: Installed on 2011-12-06 (1037 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ifupdown
  UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1379427/+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 1633046] Re: Pressing play/pause hotkey hangs U8 session

[Ben]

Tested on Thinkpad X220T, using play/pause hotkey hangs session.
However, brightness up/down hotkeys do nothing at all, if that's
important.

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

Title:
  Pressing play/pause hotkey hangs U8 session

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Log in to a U8 session in 16.10.
  Press the play/pause hotkey.
  Note that the session is now hung.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1633046/+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 1635775] [NEW] No sound unity8 apps 16.10

[Ben]

Public bug reported:

Testing on a Lenovo Thinkpad X220T running fresh install of Ubuntu
16.10. Running Checkbox passes the sound tests (as audio is played), but
when using unity8 apps no sound comes out. However, sound does come out
from Libertine containerized apps.

For example, I can be running the default Browser app playing a video,
and no sound will come out. However, when playing the same video under
Firefox or playing music in Pithos in a Libertine container, sound works
fine.

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

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

Title:
  No sound unity8 apps 16.10

Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing on a Lenovo Thinkpad X220T running fresh install of Ubuntu
  16.10. Running Checkbox passes the sound tests (as audio is played),
  but when using unity8 apps no sound comes out. However, sound does
  come out from Libertine containerized apps.

  For example, I can be running the default Browser app playing a video,
  and no sound will come out. However, when playing the same video under
  Firefox or playing music in Pithos in a Libertine container, sound
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1635775/+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 1392317] Re: Incorrect order of messages with RepeatedMsgReduction on

[Trent Lloyd]

** Tags added: sts

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

Title:
  Incorrect order of messages with RepeatedMsgReduction on

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  In rsyslog Version 7.4.4-1ubuntu2.3 there is a bug which mixes up the order 
of some messages when $RepeatedMsgReduction is enabled.
  This can sometimes result in a message missing in the current syslog and 
being printed even days later.
  Using Ubuntu 14.04.1 LTS.
  […]
  Nov 12 16:32:01 ws-api3 CRON[5572]: pam_unix(cron:session): session closed 
for user www-data
  Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session opened 
for user www-data by (uid=0)
  Nov 10 11:56:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I>> $CL/import.log 2>> 
$PL/api_cli_er
  rlog)
  Nov 12 16:33:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php 
/var/www/api/scripts/import/php/import.php all^I>> $CL/dev_import.log 2>> 
$PL/dev_ap
  i_cli_errlog)
  Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session closed 
for user www-data
  […]

  
  To reproduce this error, turn on $RepeatedMsgReduction in the rsyslog.conf 
and generate a whole bunch of syslog message, e.g. with the following php 
script:
   $k'");
   }
  }

  Result will be (after a short while):
  Nov 12 11:17:08 syslogTest vm[21410]: log > 0
  Nov 12 11:18:05 syslogTest vm[21410]: log > 1
  Nov 12 11:17:08 syslogTest vm[21412]: log > 0
  Nov 12 11:18:05 syslogTest vm[21412]: log > 1
  Nov 12 11:17:08 syslogTest vm[21414]: log > 0
  Nov 12 11:18:05 syslogTest vm[21414]: log > 1

  What's pretty suspicious is that after the pool of process IDs is exhausted 
and resettet, old messages are from the same process ID but from the previous 
iteration.
  Is RepeatedMsgReduction somehow grouping by process ID? In the first example 
is a cron process using the same process ID like one before, therefore printing 
the old message from Nov, 10. The old message was not at the position inside 
the syslog where it should have been.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1392317/+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 1635774] Re: package libflite1 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x86_

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

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

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

Title:
  package libflite1 (not installed) failed to install/upgrade: cannot
  copy extracted data for './usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end of file or
  stream

Status in flite package in Ubuntu:
  Invalid

Bug description:
  This happened while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libflite1 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 21 19:50:59 2016
  DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: flite
  Title: package libflite1 (not installed) failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' 
to '/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1635774/+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 1615401] Re: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  Expired

Bug description:
  error indicated that the system would be in an unstable state

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 08:37:35 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-30 (722 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1615401/+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 1615423] Re: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone

[Launchpad Bug Tracker]

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

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

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

Title:
  it was working fine from original install, one day it just stopped!
  sounds like a cocked up update by someone

Status in cups package in Ubuntu:
  Expired

Bug description:
  from install it was fine, but all of a sudden it lost all printers and
  will not add any

  16.04.1
  chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 21 19:16:31 2016
  InstallationDate: Installed on 2016-05-08 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire ES1-531
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-531
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire ES1-531
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1615423/+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 1584367] Re: Samsung printer automatically disabled; cannot print

[Launchpad Bug Tracker]

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

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

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

Title:
  Samsung printer automatically disabled; cannot print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Samsung ML-1660 laser printer is found and installed, but cannot print
  as it is automatically disabled. CUPS error log is filled with the
  following:

  E [21/May/2016:10:55:13 -0600] [cups-deviced] PID 26623
  (gutenprint52+usb) stopped with status 1!

  This behaviour is new in Xenial, it worked fine in Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1584367/+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 1615395] Re: Ubuntu 16.04 no sound devices showing

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 16.04 no sound devices showing

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I recently upgraded my laptop from Ubuntu 15.04 to 16.04. After that
  no sound is working, there is no sound devices listed in sound
  settings. Please help to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Aug 21 20:52:55 2016
  InstallationDate: Installed on 2015-05-28 (451 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1615395/+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 1609919] Re: Need "pivot_root" and "change_profile" exceptions for the unconfined template

[Launchpad Bug Tracker]

[Expired for apparmor-easyprof-ubuntu (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Need "pivot_root" and "change_profile" exceptions for the unconfined
  template

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Expired

Bug description:
  Per discussion on IRC, in order to support the Libertine Manager UI
  click package, we would need the "pivot_root" and "change_profile"
  exceptions added to the unconfined template in order for it to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609919/+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 1603406] Re: /etc/init.d/networking restart

[Jared Fernandez]

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

** This bug has been marked a duplicate of bug 1301015
   Networking does not restart

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

Title:
  /etc/init.d/networking restart

Status in ifupdown package in Ubuntu:
  New

Bug description:
  stop: Job failed while stopping
  start: Job is already running: networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1603406/+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 1635783] [NEW] Regression with suspend 229-4ubuntu4/10 on 32bits old thinkpad t40

[mike]

Public bug reported:

(I"m actually on linux mint)

In the live USB and default install, suspend worked correctly
(hibernation didn't). At some point, it stopped working (and hibernation
started working), it just get blocked on a black screen, the laptop is
totally blocked, i have to press the power button.

sudo pm-suspend still works correctly.
systemctl suspend gives the above behavior.

I"m actually on linux mint 18 MATE 32bits, everything upgraded and with 
original kernel.
I think it stopped working after the systemd update, still with original 
kernel. I tried installing other kernels from the official repos and from 
kernel.ubuntu.com, but nothing changed (4.4.1 and 4.8).

I think a regression hapened in systemd somewhere between 229-4ubuntu4(xenial) 
and 229-4ubuntu10(xenial)
I couldn't test between 4 and 10.

I can send you logs, if you tell me exactly how and what.

---
linux mint 18 32bit
thinkpad t40 (2003)
ATI Mobility Radeon 7500

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

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

Title:
  Regression with suspend 229-4ubuntu4/10 on 32bits old thinkpad t40

Status in systemd package in Ubuntu:
  New

Bug description:
  (I"m actually on linux mint)

  In the live USB and default install, suspend worked correctly
  (hibernation didn't). At some point, it stopped working (and
  hibernation started working), it just get blocked on a black screen,
  the laptop is totally blocked, i have to press the power button.

  sudo pm-suspend still works correctly.
  systemctl suspend gives the above behavior.

  I"m actually on linux mint 18 MATE 32bits, everything upgraded and with 
original kernel.
  I think it stopped working after the systemd update, still with original 
kernel. I tried installing other kernels from the official repos and from 
kernel.ubuntu.com, but nothing changed (4.4.1 and 4.8).

  I think a regression hapened in systemd somewhere between 
229-4ubuntu4(xenial) and 229-4ubuntu10(xenial)
  I couldn't test between 4 and 10.

  I can send you logs, if you tell me exactly how and what.

  ---
  linux mint 18 32bit
  thinkpad t40 (2003)
  ATI Mobility Radeon 7500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635783/+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 1635423] Re: Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. in the syslog

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Status: New => Triaged

** Changed in: ubuntu-z-systems
   Importance: Undecided => Low

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

Title:
  Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for
  path "/var/log", ignoring.  in the syslog

Status in Ubuntu on IBM z Systems:
  Triaged
Status in rsyslog package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Summary
  ===
  zEC12 System LPAR
  Linux r35lp50 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:12:40 UTC 2016 
s390x s390x s390x GNU/Linux

  
  Details
  ===
  Every 24h systemd-tmpfiles is logging a message similar to this:
  Oct 18 15:18:41 sysname systemd-tmpfiles[34404]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

  We have seen varying times on different Ubuntu system instances.

  
  Additional information
  ===
  Pasting the contents of the '/usr/lib/tmpfiles.d/var.conf' file below:

  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.

  # See tmpfiles.d(5) for details

  q /var 0755 - - -

  L /var/run - - - - ../run

  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  d /var/cache 0755 - - -

  d /var/lib 0755 - - -

  d /var/spool 0755 - - -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1635423/+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 1634869] Re: telepathy-ofono test failures on armhf, arm64 and s390x

[Łukasz Zemczak]

The package now builds correctly as it required some re-tries until the
flaky test succeeded. I filled in a separate bug for the test issue
itself: https://bugs.launchpad.net/ubuntu/+source/telepathy-
ofono/+bug/1635542

** Changed in: telepathy-ofono (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  telepathy-ofono test failures on armhf, arm64 and s390x

Status in telepathy-ofono package in Ubuntu:
  Fix Released

Bug description:
  see https://launchpad.net/ubuntu/+source/telepathy-
  ofono/0.2+16.10.20160909-0ubuntu2

  failing tests on armhf, arm64, ppc64el and s390x.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1634869/+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 1635573] [NEW] package zlib1g-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/x86_64-linux-gnu/zconf.h', which is also in package lib64z1-dev:i38

[Tushar Anand]

Public bug reported:

error occurred with installing apt packages.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zlib1g-dev (not installed)
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Oct 21 15:00:35 2016
DuplicateSignature:
 package:zlib1g-dev:(not installed)
 Unpacking libc6-dev-amd64:i386 (2.23-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-amd64_2.23-0ubuntu3_i386.deb (--unpack):
  trying to overwrite '/usr/include/bits', which is also in package 
libc6-dev-i386 2.23-0ubuntu3
ErrorMessage: trying to overwrite '/usr/include/x86_64-linux-gnu/zconf.h', 
which is also in package lib64z1-dev:i386 1:1.2.8.dfsg-2ubuntu4
InstallationDate: Installed on 2016-10-20 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: zlib
Title: package zlib1g-dev (not installed) failed to install/upgrade: trying to 
overwrite '/usr/include/x86_64-linux-gnu/zconf.h', which is also in package 
lib64z1-dev:i386 1:1.2.8.dfsg-2ubuntu4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package zlib1g-dev (not installed) failed to install/upgrade: trying
  to overwrite '/usr/include/x86_64-linux-gnu/zconf.h', which is also in
  package lib64z1-dev:i386 1:1.2.8.dfsg-2ubuntu4

Status in zlib package in Ubuntu:
  New

Bug description:
  error occurred with installing apt packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zlib1g-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 21 15:00:35 2016
  DuplicateSignature:
   package:zlib1g-dev:(not installed)
   Unpacking libc6-dev-amd64:i386 (2.23-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-amd64_2.23-0ubuntu3_i386.deb (--unpack):
trying to overwrite '/usr/include/bits', which is also in package 
libc6-dev-i386 2.23-0ubuntu3
  ErrorMessage: trying to overwrite '/usr/include/x86_64-linux-gnu/zconf.h', 
which is also in package lib64z1-dev:i386 1:1.2.8.dfsg-2ubuntu4
  InstallationDate: Installed on 2016-10-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zlib
  Title: package zlib1g-dev (not installed) failed to install/upgrade: trying 
to overwrite '/usr/include/x86_64-linux-gnu/zconf.h', which is also in package 
lib64z1-dev:i386 1:1.2.8.dfsg-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1635573/+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 1446448] Re: ssh-agent terminates

[Robie Basak]

Let's set Importance to Low to make it clear that this won't be worked
on any time soon. Sorry Andrej - with only one person marked as affected
we can't prioritise this.

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

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

Title:
  ssh-agent terminates

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I have set-up password less ssh connectivity for my workstation.  ssh-
  agent gets started via keychain when fluxbox boots.

  When I use ssh to connect to a server, and then use scp to shuffle a
  file from that server to my workstation the ssh-agent on my
  workstation dies after the file was transferred.

  This has started happening after the upgrade  from 12.04 to 14.04.

  I have wrapped strace into the fluxbox startup to keep an eye on ssh-
  agent (I initially didn't see a pattern to the sudden death), here's
  an example of the breakdown post transfer.

  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21130, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "\0\0\0\1\v", 1024) = 5
  select(5, [3 4], [4], NULL, NULL)   = 1 (out [4])
  write(4, "\0\0\1<\f\0\0\0\1\0\0\1\27\0\0\0\7ssh-rsa\0\0\0\3\1\0\1\0"..., 320) 
= 320
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21284, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = ? ERESTARTNOHAND (To be restarted 
if no handler)
  --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=21284, si_uid=0} ---
  unlink("/tmp/ssh-DEwJJTGLUETC/agent.19556") = 0
  rmdir("/tmp/ssh-DEwJJTGLUETC")  = 0
  close(-1)   = -1 EBADF (Bad file descriptor)
  exit_group(2)   = ?
  +++ exited with 2 +++


  1) lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  
  2) apt-cache policy openssh-client
  openssh-client:
Installed: 1:6.6p1-2ubuntu2
Candidate: 1:6.6p1-2ubuntu2
Version table:
   *** 1:6.6p1-2ubuntu2 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.6p1-2ubuntu1 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) I expect ssh-agent to carry on running as it did in previous
  releases.

  4) It dies when connecting back from a machine I ssh into to my
  workstation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Tue Apr 21 15:28:02 2015
  InstallationDate: Installed on 2015-02-03 (77 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-ssh2.0-1
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ssh-agent.log: ssh-agent stop/pre-start, process 1973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1446448/+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 1632620] Re: No audio from webbrowser-app in 16.10

[Launchpad Bug Tracker]

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

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

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

Title:
  No audio from webbrowser-app in 16.10

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress
Status in apparmor-easyprof-ubuntu source package in Yakkety:
  Confirmed
Status in webbrowser-app source package in Yakkety:
  Confirmed

Bug description:
  [Test case]
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube.
  Play a video.
  Notice there is no sound. Nor does the browser show in the sound menu/panel.

  TLDR: this is an apparmor confinement issue: on yakkety pulse audio
  needs write access to /{run,dev}/shm/pulse-shm*, which is being denied
  by the audio and microphone policy groups. The fix consists in
  punching an additional hole in the generated apparmor profile for
  webbrowser-app.

  [Regression potential]
  Low. As the fix consists in weakening the apparmor profile for 
webbrowser-app, the only concerns should be security-related. The change was 
ack’d by Jamie Strandboge (see comment #11 in this bug report).
  It is not anticipated that this change would make the browser’s functionality 
regress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1632620] Re: No audio from webbrowser-app in 16.10

[Launchpad Bug Tracker]

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

** Changed in: apparmor-easyprof-ubuntu (Ubuntu Yakkety)
   Status: New => Confirmed

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

Title:
  No audio from webbrowser-app in 16.10

Status in Oxide:
  Invalid
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress
Status in apparmor-easyprof-ubuntu source package in Yakkety:
  Confirmed
Status in webbrowser-app source package in Yakkety:
  Confirmed

Bug description:
  [Test case]
  Load the browser on 16.10 in either a U8 or U7 session.
  Browse to YouTube.
  Play a video.
  Notice there is no sound. Nor does the browser show in the sound menu/panel.

  TLDR: this is an apparmor confinement issue: on yakkety pulse audio
  needs write access to /{run,dev}/shm/pulse-shm*, which is being denied
  by the audio and microphone policy groups. The fix consists in
  punching an additional hole in the generated apparmor profile for
  webbrowser-app.

  [Regression potential]
  Low. As the fix consists in weakening the apparmor profile for 
webbrowser-app, the only concerns should be security-related. The change was 
ack’d by Jamie Strandboge (see comment #11 in this bug report).
  It is not anticipated that this change would make the browser’s functionality 
regress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1632620/+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 1632361] Re: unattended-update installArchives

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  unattended-update installArchives

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-98-generic 
/boot/vmlinuz-3.13.0-98-generic
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-3.13.0-98-generic
  Found initrd image: /boot/initrd.img-3.13.0-98-generic
  Found linux image: /boot/vmlinuz-3.13.0-85-generic
  Found initrd image: /boot/initrd.img-3.13.0-85-generic
  Found linux image: /boot/vmlinuz-3.13.0-83-generic
  Found initrd image: /boot/initrd.img-3.13.0-83-generic
  done
  Setting up mysql-client-core-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-client-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-server-core-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  Setting up mysql-server-5.5 (5.5.52-0ubuntu0.14.04.1) ...
  start: Job failed to start
  invoke-rc.d: initscript mysql, action "start" failed.
  dpkg: error processing package mysql-server-5.5 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of mysql-server:
   mysql-server depends on mysql-server-5.5; however:
Package mysql-server-5.5 is not configured yet.

  dpkg: error processing package mysql-server (--configure):
   dependency problems - leaving unconfigured
  Setting up php5-common (5.5.9+dfsg-1ubuntu4.20) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  php5_invoke pdo: already enabled for apache2 SAPI
  php5_invoke pdo: already enabled for cli SAPI
  php5_invoke opcache: already enabled for apache2 SAPI
  php5_invoke opcache: already enabled for cli SAPI
  Setting up php5-mysql (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke mysql: already enabled for apache2 SAPI
  php5_invoke mysql: already enabled for cli SAPI
  php5_invoke mysqli: already enabled for apache2 SAPI
  php5_invoke mysqli: already enabled for cli SAPI
  php5_invoke pdo_mysql: already enabled for apache2 SAPI
  php5_invoke pdo_mysql: already enabled for cli SAPI
  Setting up php5-cli (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke opcache: already enabled for cli SAPI
  php5_invoke apcu: already enabled for cli SAPI
  php5_invoke json: already enabled for cli SAPI
  php5_invoke pdo_mysql: already enabled for cli SAPI
  php5_invoke pdo: already enabled for cli SAPI
  php5_invoke mysqli: already enabled for cli SAPI
  php5_invoke mysql: already enabled for cli SAPI
  php5_invoke gd: already enabled for cli SAPI
  php5_invoke mcrypt: already enabled for cli SAPI
  php5_invoke curl: already enabled for cli SAPI
  php5_invoke readline: already enabled for cli SAPI
  Setting up php5-readline (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke readline: already enabled for apache2 SAPI
  php5_invoke readline: already enabled for cli SAPI
  Setting up apache2-bin (2.4.7-1ubuntu4.13) ...
  Setting up apache2-data (2.4.7-1ubuntu4.13) ...
  Setting up apache2 (2.4.7-1ubuntu4.13) ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_prefork.load ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_worker.load ...
  Installing new version of config file 
/etc/apache2/mods-available/mpm_event.load ...
   * Restarting web server apache2
 ...done.
  Setting up apache2-mpm-prefork (2.4.7-1ubuntu4.13) ...
  Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke opcache: already enabled for apache2 SAPI
  php5_invoke apcu: already enabled for apache2 SAPI
  php5_invoke json: already enabled for apache2 SAPI
  php5_invoke pdo_mysql: already enabled for apache2 SAPI
  php5_invoke pdo: already enabled for apache2 SAPI
  php5_invoke mysqli: already enabled for apache2 SAPI
  php5_invoke mysql: already enabled for apache2 SAPI
  php5_invoke gd: already enabled for apache2 SAPI
  php5_invoke mcrypt: already enabled for apache2 SAPI
  php5_invoke curl: already enabled for apache2 SAPI
  php5_invoke readline: already enabled for apache2 SAPI
  apache2_invoke php5: already enabled
   * Restarting web server apache2
 ...done.
  Setting up php5-gd (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke gd: already enabled for apache2 SAPI
  php5_invoke gd: already enabled for cli SAPI
  Setting up php5-curl (5.5.9+dfsg-1ubuntu4.20) ...
  php5_invoke curl: already enabled for apache2 SAPI
  php5_invoke curl: already enabled for cli SAPI
  Setting up apt-utils (1.0.1ubuntu2.13) ...
  Setting up apt-transport-https (1.0.1ubuntu2.13) ...
  Setting up libisc95 (1:9.9.5.dfsg-3ubuntu0.9) ...
  Setting up libdns100 (1:9.9.5.dfsg-3ubuntu0.9) 

[Touch-packages] [Bug 1635624] [NEW] package account-plugin-owncloud (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui a

[p1pon]

Public bug reported:

package account-plugin-owncloud (not installed) failed to
install/upgrade: tentative de remplacement de «
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi
au paquet owncloud-client:amd64 2.2.4-1.1

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: account-plugin-owncloud (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 account-plugin-owncloud:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 21 14:42:59 2016
ErrorMessage: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
InstallationDate: Installed on 2016-10-20 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: account-plugins
Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient
  aussi au paquet owncloud-client:amd64 2.2.4-1.1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient
  aussi au paquet owncloud-client:amd64 2.2.4-1.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-owncloud (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   account-plugin-owncloud:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 21 14:42:59 2016
  ErrorMessage: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
  InstallationDate: Installed on 2016-10-20 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1635624/+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 1584685] Re: Xenial fails to install with Preseed d-i apt-setup/local0/repository set

[catsem]

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xenial fails to install with Preseed d-i apt-setup/local0/repository
  set

Status in debian-installer:
  New
Status in One Hundred Papercuts:
  Triaged
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Triaged

Bug description:
  Preseed install of Ubuntu Xenial fails with d-i apt-
  setup/localX/repository option set. The problem is that debian
  installer does not concat the last string in sources.list correctly.
  The prefix "deb" is missing. So apt fails to update and the installer
  cannot continue because there are no valid package sources.

To manage notifications about this bug go to:
https://bugs.launchpad.net/debian-installer/+bug/1584685/+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 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key

[catsem]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

** Changed in: debian-installer (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xenial preseed fails to load key for 3rd party repo with apt-
  setup/local0/key

Status in apt-setup package in Ubuntu:
  Confirmed
Status in base-installer package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  I have an automated preseed installation that uses these lines to add
  custom repos during the installation:

  d-i apt-setup/local0/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local0/comment string JTS local repository
  d-i apt-setup/local0/source boolean false
  d-i apt-setup/local0/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local1/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local1/comment string Google Chrome Browser
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string 
http://dl.google.com/linux/linux_signing_key.pub

  
(seehttps://github.com/jschule/ubuntu/blob/d46f1cef49ed71dc4bfe317119cccd3f39097ef4/preseed/jts.txt
  for complete preseed file that causes the problem).

  In xenial the installation fails because the GPG key for the local0
  repo is not loaded into the system so that it can be used (see
  screenshot). Strangely, "chroot /target apt-key list" shows the key
  9E62229E to be installed.

  Just to be sure that there is no problem with my repo and key I
  started the Xenial live CD and installed my repo there manually. All
  works well. IMHO this shows that the problem is clearly related to the
  automated installation with preseed.

  Maybe this is related to #1512347, that was the only thing I could
  find on Launchpad that is in the same area.

  If you want to reproduce this then you can checkout the scripts from
  https://github.com/jschule/ubuntu/tree/gh-pages/qemu and run "./run.sh
  xenial" to start my installation.

  I found a very ugly workaround by changing the apt-setup lines to
  this:

  d-i apt-setup/local0/repository string deb 
http://archive.canonical.com/ubuntu trusty partner
  d-i apt-setup/local0/source boolean false

  d-i apt-setup/local1/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local1/comment string JTS local repository
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local2/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local2/comment string Google Chrome Browser
  d-i apt-setup/local2/source boolean false
  d-i apt-setup/local2/key string 
http://dl.google.com/linux/linux_signing_key.pub

  I suppose that the workaround works because now the local0 repo is one
  where the signing key is already part of Ubuntu. I just hope that
  there is no package in the trusty partner repo that is not also in the
  xenial partner repo.

  For me it is very important that you fix this bug before 16.04 is
  released so that I can continue to use Ubuntu with an automated setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+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 1553147] Re: xenial preseed cannot set keyboard layout

[catsem]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: debian-installer (Ubuntu)

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

Title:
  xenial preseed cannot set keyboard layout

Status in console-setup package in Ubuntu:
  Fix Released

Bug description:
  Using network booted preseed with the following lines to configure
  keyboard layout:

  d-i console-setup/ask_detect false
  d-i keyboard-configuration/layoutcode string de
  d-i keyboard-configuration/layout select German
  d-i keyboard-configuration/modelcode string pc105

  System comes up with US keyboard only (see screenshot).

  Content of /etc/default/keyboard:
  XKBMODEL="pc105"
  XKBLAYOUT=""
  XKBVARIANT=""
  XKBOPTIONS=""
  BACKSPACE="guess"

  Content of /etc/default/console-setup:
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  CODESET="guess"
  FONTFACE="Fixed"
  FONTSIZE="8x16"
  VIDEOMODE=

  The same preseed file works on wily and successfully configures a
  German keyboard layout.

  The full preseed file can be found at
  https://github.com/jschule/ubuntu/blob/gh-pages/preseed/jts.txt

  Please advice how to set German keyboard layout with preseed
  installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1553147/+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 1634263] Re: Touchpad movement doesn't work after suspend

[svenmeier]

After switching back into Gnome session touchpad movement works again.
Thus I suspect this to be a Gnome problem.

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

Title:
  Touchpad movement doesn't work after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Once or twice a week *after* resume from suspend I can no longer use
  the touchpad to movethe mouse pointer, mouse clicks are registered
  though.

  Reloading module psmouse works as a workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:52:05 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  MachineType: LENOVO 20344
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN31WW(V1.17)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+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 1634263] Re: Touchpad movement doesn't work after suspend

[svenmeier]

It seems all events are still correctly recognized by xorg.

** Summary changed:

- Touchpad movements doesn't work after suspend
+ Touchpad movement doesn't work after suspend

** Attachment added: "evtest output after touchpad went unresponsive"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+attachment/4764856/+files/evtest.log

** Changed in: xorg (Ubuntu)
   Status: Incomplete => New

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

Title:
  Touchpad movement doesn't work after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Once or twice a week *after* resume from suspend I can no longer use
  the touchpad to movethe mouse pointer, mouse clicks are registered
  though.

  Reloading module psmouse works as a workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:52:05 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  MachineType: LENOVO 20344
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN31WW(V1.17)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+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 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

[Treviño]

I've the impression this is due to nautilus not being properly resized
when display size changes (in a VM) or a new one is added...

nautilus -q

and starting the filemanager again should fix this.

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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
  Date: Fri Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Ugnius]

Also having the issue on a fresh 16.04.1. init-headphone 0.11 gets EBUSY
on the first write to SMBus (modified to print out errno, diff below).
Used to work on 15.04-15.10 on the same laptop.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial


$ sudo init-headphone-errno
INFO:root:Version: 0.11
INFO:root:Trying to add module to the kernel: i2c_dev
INFO:root:Trying to add module to the kernel: i2c_i801
DEBUG:root:Available i2c busses: ['i915 gmbus ssc', 'i915 gmbus vga', 'i915 
gmbus panel', 'i915 gmbus dpc', 'i915 gmbus dpb', 'i915 gmbus dpd', 'DPDDC-A', 
'SMBus I801 adapter at f040']
DEBUG:root:Supported i2c bus names: ['SMBus I801 adapter']
DEBUG:root:Selected i2c bus: SMBus I801 adapter at f040
INFO:SMBus:Opening I2C bus: /dev/i2c-7
INFO:SMBus:Setting I2C slave address: 115
INFO:SMBus:Writing byte data on I2C bus: (device_cmd: 0xa, value: 0x41)
ERROR:SMBus:Can't transfer data on I2C bus [EBUSY]
INFO:SMBus:Closing I2C bus
ERROR:root:Operation failed
DEBUG:root:Exception occurred:
Traceback (most recent call last):
  File "/usr/sbin/init-headphone-errno", line 329, in 
main()
  File "/usr/sbin/init-headphone-errno", line 315, in main
init()
  File "/usr/sbin/init-headphone-errno", line 247, in init
set_effect(DEFAULT_EFFECT)
  File "/usr/sbin/init-headphone-errno", line 263, in set_effect
DATA_ENABLE_OUTPUT)
  File "/usr/sbin/init-headphone-errno", line 241, in write_data_to_device
write_prolog(i2c_bus)
  File "/usr/sbin/init-headphone-errno", line 232, in write_prolog
i2c_bus.write_byte_data(0x0a, 0x41)
  File "/usr/sbin/init-headphone-errno", line 149, in write_byte_data
self.__access(I2C_SMBUS_WRITE, device_cmd, I2C_SMBUS_BYTE_DATA, data)
  File "/usr/sbin/init-headphone-errno", line 141, in __access
raise RuntimeError("Can't transfer data on I2C bus [{}]".format(e))
RuntimeError: Can't transfer data on I2C bus [EBUSY]


$ sudo i2cdetect 7
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-7.
I will probe address range 0x03-0x77.
Continue? [Y/n] 
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --


$ diff -u /usr/sbin/init-headphone /usr/sbin/init-headphone-errno 
--- /usr/sbin/init-headphone2016-05-08 10:27:04.0 +0300
+++ /usr/sbin/init-headphone-errno  2016-10-21 16:58:45.292881695 +0300
@@ -82,6 +82,12 @@
 ("size", ctypes.c_uint),
 ("data", ctypes.POINTER(i2c_smbus_data))]
 
+_errno = ctypes.cdll.LoadLibrary("libc.so.6").__errno_location
+_errno.restype = ctypes.POINTER(ctypes.c_int)
+
+def get_errno():
+import errno
+return errno.errorcode[_errno()[0]]
 
 class SMBus(object):
 def __init__(self, path):
@@ -129,9 +135,10 @@
 args.size = size
 args.data = ctypes.pointer(data)
 err = self.__libc.ioctl(self.__fd, I2C_SMBUS, ctypes.byref(args))
+e = get_errno()
 if err != 0:
-self.__logger.error("Can't transfer data on I2C bus")
-raise RuntimeError("Can't transfer data on I2C bus")
+self.__logger.error("Can't transfer data on I2C bus 
[{}]".format(e))
+raise RuntimeError("Can't transfer data on I2C bus [{}]".format(e))
 
 def write_byte_data(self, device_cmd, value):
 self.__logger.info("Writing byte data on I2C bus: "

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through 

[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

[RAMupgrade]

Thanks for the info. Much appreciated!

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

[Louis Bouchard]

** Also affects: libnl3 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: libnl3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  New

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

[Jorge Niedbalski]

** Changed in: libnl3 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: libnl3 (Ubuntu)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: libnl3 (Ubuntu Trusty)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: libnl3 (Ubuntu Precise)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  New

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635639] [NEW] Seccomp error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

[Curtis Hovey]

Public bug reported:

The s390x host used to Juju testing spontaneously broke today.
The disk filled up, we restarted so that we could remove unused
kernels. We discovered that lxc1 cannot create containers any more.

$ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

$ sudo lxc-start -o lxc.log -n curtis
lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
lxc-start: tools/lxc_start.c: main: 346 To get more details, run the container 
in foreground mode.
lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained 
by setting the --logfile and --logpriority options.

$ cat lxc.log 
  lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
  lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 - 
failed loading seccomp policy
  lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
  lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
  lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
  lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.


#  sinzui: checking when s390x seccomp support was added to the
# kernel, to see if it's just a missing config in our kernel that'd fix that 
# cleanly or if we'd need it backported to 4.4 which would be a bit more 
# annoying
#  sinzui: config-4.4.0-45-generic is what you're running right?
#  stgraber uname-a says 4.4.0-45-generic
# stgraber> sinzui: you can workaround it by putting a file
# with lxc.seccomp=
# in /usr/share/lxc/config/common.conf.d/, that should get you going again

WORK AROUND
# on the s390x-slave
sudo vim /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
$ cat /usr/share/lxc/config/common.conf.d/10-secomp-hack.conf
# Advised to stgraber to add this file after seeing lxc-start fail with
# lxc-start 20161020121833.069 ERRORlxc_seccomp - seccomp.
lxc.seccomp=

** Affects: juju-ci-tools
 Importance: Critical
 Assignee: Curtis Hovey (sinzui)
 Status: Fix Committed

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


** Tags: jujuqa lxd regression s390x

** Also affects: lxc
   Importance: Undecided
   Status: New

** Project changed: lxc => juju-ci-tools

** Changed in: juju-ci-tools
   Status: New => Fix Committed

** Changed in: juju-ci-tools
   Importance: Undecided => Critical

** Changed in: juju-ci-tools
 Assignee: (unassigned) => Curtis Hovey (sinzui)

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

Title:
  Seccomp  error with 2.0.5-0ubuntu1~ubuntu16.04.1 on s390x

Status in juju-ci-tools:
  Fix Committed
Status in lxc package in Ubuntu:
  New

Bug description:
  The s390x host used to Juju testing spontaneously broke today.
  The disk filled up, we restarted so that we could remove unused
  kernels. We discovered that lxc1 cannot create containers any more.

  $ sudo lxc-create -t ubuntu-cloud -n curtis -- -r xenial -a s390x

  $ sudo lxc-start -o lxc.log -n curtis
  lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
  lxc-start: tools/lxc_start.c: main: 346 To get more details, run the 
container in foreground mode.
  lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
obtained by setting the --logfile and --logpriority options.

  $ cat lxc.log 
lxc-start 20161020121833.069 ERRORlxc_seccomp - 
seccomp.c:get_new_ctx:224 - Seccomp error -17 (File exists) adding arch: 15
lxc-start 20161020121833.069 ERRORlxc_start - start.c:lxc_init:430 
- failed loading seccomp policy
lxc-start 20161020121833.069 ERRORlxc_start - 
start.c:__lxc_start:1313 - failed to initialize the container
lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:344 - The container failed to start.
lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:346 - To get more details, run the container in 
foreground mode.
lxc-start 20161020121838.075 ERRORlxc_start_ui - 
tools/lxc_start.c:main:348 - Additional information can be obtained by setting 
the --logfile and --logpriority options.

  
  #  sinzui: checking when s390x seccomp support was added to the
  # kernel, to see if it's just a missing config in our kernel that'd fix that 
  # cleanly or if we'd need it backported to 4.4 which would be a bit more 
  # annoying
  #  sinzui: config-4.4.0-45-generic is what you're running right?
  #  stgraber uname-a says 4.4.0-45-generic
  # stgraber> sinzui: you 

[Touch-packages] [Bug 1446448] Re: ssh-agent terminates

[Seth Arnold]

Sorry Andrej; you may be the only one experiencing this issue, and it
sounds extremely frustrating. But I don't know what to suggest next to
debug why it's happening.

About all I can suggest is that I gave up on the keychain script myself
~five years ago, but I can't recall why. You may reconsider if it's
helpful or not in your environment.

Thanks

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

Title:
  ssh-agent terminates

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  I have set-up password less ssh connectivity for my workstation.  ssh-
  agent gets started via keychain when fluxbox boots.

  When I use ssh to connect to a server, and then use scp to shuffle a
  file from that server to my workstation the ssh-agent on my
  workstation dies after the file was transferred.

  This has started happening after the upgrade  from 12.04 to 14.04.

  I have wrapped strace into the fluxbox startup to keep an eye on ssh-
  agent (I initially didn't see a pattern to the sudden death), here's
  an example of the breakdown post transfer.

  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21130, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "\0\0\0\1\v", 1024) = 5
  select(5, [3 4], [4], NULL, NULL)   = 1 (out [4])
  write(4, "\0\0\1<\f\0\0\0\1\0\0\1\27\0\0\0\7ssh-rsa\0\0\0\3\1\0\1\0"..., 320) 
= 320
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = 1 (in [3])
  accept(3, {sa_family=AF_LOCAL, NULL}, [2]) = 4
  getsockopt(4, SOL_SOCKET, SO_PEERCRED, {pid=21284, uid=1000, gid=1000}, [12]) 
= 0
  getuid()= 1000
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
  select(5, [3 4], [], NULL, NULL)= 1 (in [4])
  read(4, "", 1024)   = 0
  close(4)= 0
  select(4, [3], [], NULL, NULL)  = ? ERESTARTNOHAND (To be restarted 
if no handler)
  --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=21284, si_uid=0} ---
  unlink("/tmp/ssh-DEwJJTGLUETC/agent.19556") = 0
  rmdir("/tmp/ssh-DEwJJTGLUETC")  = 0
  close(-1)   = -1 EBADF (Bad file descriptor)
  exit_group(2)   = ?
  +++ exited with 2 +++


  1) lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  
  2) apt-cache policy openssh-client
  openssh-client:
Installed: 1:6.6p1-2ubuntu2
Candidate: 1:6.6p1-2ubuntu2
Version table:
   *** 1:6.6p1-2ubuntu2 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.6p1-2ubuntu1 0
  500 http://nz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) I expect ssh-agent to carry on running as it did in previous
  releases.

  4) It dies when connecting back from a machine I ssh into to my
  workstation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Tue Apr 21 15:28:02 2015
  InstallationDate: Installed on 2015-02-03 (77 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-ssh2.0-1
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ssh-agent.log: ssh-agent stop/pre-start, process 1973

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1446448/+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 1611078] Re: Support snaps inside of lxd containers

[dt9394]

NVM, I will download and compile the kernel and test it this week. Let
see how it go.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1589005] Re: After update DNS work unstable

[Tamas Papp]

I still have this problem with network-manager 1.2.4-0ubuntu1.

sudo service network-manager restart

provides a temporary workaround.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589005/+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 1630765] Re: webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration()

[Timo Jyrinki]

Sorry, I missed the reference for the bug report but the fix now landed
in zesty and xenial-overlay.

https://lists.ubuntu.com/archives/zesty-changes/2016-October/50.html

Version 5.6.1+dfsg-3ubuntu7~2:

  * debian/patches/Stop-unloading-plugins-in-QPluginLoader-and-QFactory.patch:
- Backport from Qt 5.8.

It seems upstream will introduce the same change, possibly as opt-in in
5.6.3 and the default in 5.6.4 as per most recent discussions:
http://lists.qt-
project.org/pipermail/development/2016-October/027519.html

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  webbrowser-app crashed with SIGSEGV in
  QNetworkConfiguration::~QNetworkConfiguration()

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I changed the session to unity 7 and I guess the browser didn't
  stopped.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Wed Oct  5 22:00:38 2016
  ExecutablePath: /usr/bin/webbrowser-app
  ExecutableTimestamp: 1475051112
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  ProcCmdline: webbrowser-app
  ProcCwd: /home/jbenitez
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=es_ES
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd1d609a5df <_ZN21QNetworkConfigurationD2Ev+63>:
mov0x8(%rax),%rax
   PC (0x7fd1d609a5df) ok
   source "0x8(%rax)" (0x7fd15ef5b7d8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QNetworkConfiguration::~QNetworkConfiguration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QHashData::free_helper(void (*)(QHashData::Node*)) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplicationPrivate::cleanupThreadData() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: webbrowser-app crashed with SIGSEGV in 
QNetworkConfiguration::~QNetworkConfiguration()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1630765/+subscriptions

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Łukasz Zemczak]

I think I will just go forward and start preparing the release of dbus
with this fix in zesty and then backporting it to yakkety and xenial.
Upstream didn't seem to officially review the fix or provide any
feedback on our test results, but the fix is enough high-priority to
consider including it anyway. I will of course get someone to review all
this, but I suppose we'll be pushing upstream about it separately.

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Confirmed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions

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

[Touch-packages] [Bug 1589005] Re: After update DNS work unstable

[Aron Xu]

Can't reproduce with current version, is it still affecting you?

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589005/+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 1635456] Re: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking station] No sound at all

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking
  station] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  nao funciona caixas som usei alsamixer, usei pulseaudio, etc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-73.81~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-73-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 20 21:40:40 2016
  InstallationDate: Installed on 2016-09-14 (35 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Áudio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front, Docking station
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking 
station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P17G
  dmi.board.vendor: PCCHIPS
  dmi.board.version: ECS
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PCCHIPS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd02/13/2008:svnPCCHIPS:pnP17G:pvr1.0:rvnPCCHIPS:rnP17G:rvrECS:cvnPCCHIPS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: P17G
  dmi.product.version: 1.0
  dmi.sys.vendor: PCCHIPS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635456/+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 1635456] Re: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking station] No sound at all

[Seth Arnold]

This computer may have hardware problems; please install the mcelog
package and see what the /var/log/mcelog file reports:


[ 1800.75] mce: [Hardware Error]: Machine check events logged
[ 1840.847894] CPU0: Core temperature/speed normal
[ 1950.41] mce: [Hardware Error]: Machine check events logged
[ 2140.844426] CPU0: Core temperature/speed normal
[ 2175.62] mce: [Hardware Error]: Machine check events logged

Thanks

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

Title:
  [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking
  station] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  nao funciona caixas som usei alsamixer, usei pulseaudio, etc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-73.81~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-73-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 20 21:40:40 2016
  InstallationDate: Installed on 2016-09-14 (35 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Áudio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front, Docking station
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking 
station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P17G
  dmi.board.vendor: PCCHIPS
  dmi.board.version: ECS
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PCCHIPS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd02/13/2008:svnPCCHIPS:pnP17G:pvr1.0:rvnPCCHIPS:rnP17G:rvrECS:cvnPCCHIPS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: P17G
  dmi.product.version: 1.0
  dmi.sys.vendor: PCCHIPS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635456/+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 1635542] [NEW] The CallTest unit test is flaky and frequenly fails with a timeout

[Łukasz Zemczak]

Public bug reported:

Example failure output (for s390x, but happened also for armhf and
arm64):

https://launchpadlibrarian.net/290188283/buildlog_ubuntu-zesty-s390x
.telepathy-ofono_0.2+16.10.20160909-0ubuntu2_BUILDING.txt.gz

Start 5: CallTest
5/5 Test #5: CallTest .***Timeout  30.01 sec

The CallTest seems to be very flaky, frequently failing. After several
retries it passes normally.

** Affects: telepathy-ofono
 Importance: Medium
 Status: New

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: telepathy-ofono (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The CallTest unit test is flaky and frequenly fails with a timeout

Status in telepathy-ofono:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  Example failure output (for s390x, but happened also for armhf and
  arm64):

  https://launchpadlibrarian.net/290188283/buildlog_ubuntu-zesty-s390x
  .telepathy-ofono_0.2+16.10.20160909-0ubuntu2_BUILDING.txt.gz

  Start 5: CallTest
  5/5 Test #5: CallTest .***Timeout  30.01 sec

  The CallTest seems to be very flaky, frequently failing. After several
  retries it passes normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-ofono/+bug/1635542/+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 1626605] Re: xorg error when waking up after suspend in YY

[Launchpad Bug Tracker]

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

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

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

Title:
  xorg error when waking up after suspend in YY

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Enviroment: latest image of yy

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD

  Steps to reproduce:

  1º Boot or reboot your laptop
  2º Once you're in log in screen go to indicator-session and suspend it
  3º Once suspended, wake it up be pressing power button for example

  Current result: My mouse can move but clicking is not working on
  anything, then black screen and window error saying "The system is
  running on low graphics mode", finally it lets me choose how to start
  session again. Pics 1 and 2 attached

  Expected result: Laptop should wake up and let the user enter his
  session with out any issue.

  Add info: please find attached xorg logs, crash file saved in
  /sys/class/drm/card0/error and here is the dmesg output (line 938)
  https://pastebin.canonical.com/166279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626605/+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 1635558] [NEW] When wifi disconnect, unity8 shouldn't reconnect to 3G automatically

[Emanuele Sorce]

Public bug reported:

I'm on bq aquaris E5, and for me this automatic function isn't good
because I'll pay for that. However seem an intresting function. Why
don't put a switch in the settings?

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

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

Title:
  When wifi disconnect, unity8 shouldn't reconnect to 3G automatically

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm on bq aquaris E5, and for me this automatic function isn't good
  because I'll pay for that. However seem an intresting function. Why
  don't put a switch in the settings?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1635558/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[AW]

Unfortunately I have to confirm, that I no longer have the hardware to
test it on.

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  618.059121]  [] 
do_vfs_ioctl+0x29f/0x490
  Aug 23 15:09:46 

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Łukasz Zemczak]

** Also affects: dbus (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Confirmed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions

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

[Touch-packages] [Bug 1633845] Re: network-manager does not connect to wifi

[Launchpad Bug Tracker]

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

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

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

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1633845] Re: network-manager does not connect to wifi

[Quentin]

Same issue on ubuntu-gnome 16.10 after resuming from sleep.

Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01)
Hardware: Dell XPS 9550

It is required to restart the network manager.

There was the same issue in Ubuntu 16.04 6/7 months ago and it was fixed
in an update.

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

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1611078] Re: Support snaps inside of lxd containers

[dt9394]

The fix only for Yakkety? I still have the same error on Xenial with
proposed enabled.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1630399] Re: [Phone] Please enable opus audio codec support in qtmultimedia

[Timo Jyrinki]

Sorry Devid for the wait, we are definitely very happy to land these
fixes! We need to just decide who/when will land it.

So action items, since I'm away at least next week:
1. Jin will check with Lukasz (sil2100) on whether he could help getting a silo 
to land the fixes to vivid OTA. The patches from Devid should be pretty much 
fine as is.
2. Someone please re-check if this is already fixed in xenial-overlay and zesty 
or not. This week I heard it would be fixed in the very latest packages, but 
need to confirm.

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

Title:
  [Phone] Please enable opus audio codec support in qtmultimedia

Status in Canonical System Image:
  New
Status in gst-plugins-bad0.10 package in Ubuntu:
  In Progress
Status in qtmultimedia-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Hi, as described in QTBUG-50567 [1], qtmultimedia doesn't support opus
  audio codec so for example we cannot record Telegram voice messages (
  bug #1460464 and bug #1375179 ).

  I patched qtmultimedia adding the support for audio/x-opus codec
  through opusdec encoder in qtmultimedia, then I found qtmultimedia
  5.4.1 (shipped with Ubuntu Phone vivid) is built against gstreamer0.10
  and, as gstreamer0.10-plugins-bad packages is not installed by
  default, opusdec encoder is not available.

  I'm working on this bug, I created it to track the progress, in order
  to add opus support I have to:

  1 - create a new gstreamer0.10-opus package containing only the
  opusdec plugin: I don't know whether I have to create a new source
  package containing opusdec sources or only a new .deb package
  (generated from gst-plugins-bad0.10 sources). I'm working on the
  latter as gst-plugins-bad0.10 package requires work in any ways.

  2 - properly patch qtmultimedia source, I'm attaching a 
working-but-needs-cleanup patch. I think some opus declarations in the attached 
patch can be avoided, but I haven't had time to work on it so I'm attaching the 
patch I tested (requires gstreamer0.10-plugins-bad).
  I don't know if qtmultimedia xenial/yakkety versions requires the patch too, 
I haven't checked them yet.

  [1] https://bugreports.qt.io/browse/QTBUG-50567

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630399/+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 1591510] Re: lxc-copy: unrecognized option '--backingstorage'

[Po-Hsu Lin]

This looks like a typo in lxc_copy.c

static const struct option my_longopts[] = {
{ "newname", required_argument, 0, 'N'},
{ "newpath", required_argument, 0, 'p'},
{ "rename", no_argument, 0, 'R'},
{ "snapshot", no_argument, 0, 's'},
{ "foreground", no_argument, 0, 'F'},
{ "daemon", no_argument, 0, 'd'},
{ "ephemeral", no_argument, 0, 'e'},
{ "mount", required_argument, 0, 'm'},
{ "backingstore", required_argument, 0, 'B'},

Should be "backingstorage" here. Which can be verified with
--backingstore=dir

** Changed in: lxc (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

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

Title:
  lxc-copy: unrecognized option '--backingstorage'

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  lxc:
    Installed: 2.0.1-0ubuntu1~16.04.1
  linux-image-virtual:
    Installed: 4.4.0.24.25

  Man ref:
  http://manpages.ubuntu.com/manpages/xenial/man1/lxc-copy.1.html

  Problem:
  The man package references '-B' and '--backingstorage' as aliases of one 
another, but when the following command is executed:

  lxc-copy --name=cache --newname container1 --backingstorage=dir
  # as a test I also tried
  lxc-copy --name=cache --newname container1 --backingstorage dir

  The result is:
  lxc-copy: unrecognized option '--backingstorage'

  Expected result:
  '--backingstorage' and '-B' should be aliases and both execute correctly

  Existing workaround:
  #Use '-B' instead.
  lxc-copy --name=cache --newname container1 -B dir

  Steps to recreate:
  apt-get update && apt-get install -y lxc
  lxc-create --name=cache --template=download -- --dist ubuntu --release trusty 
--arch amd64
  lxc-copy --name=cache --newname container1 --backingstorage=dir

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1591510/+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 1592040] Re: Can't update repos due to signing problems

[Christian Doczkal]

** Description changed:

  I can't update the repos through 'sudo apt-get update' due to these
  errors:
  
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial InRelease: Errore 
sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates InRelease' 
is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-backports InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-security InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-security 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  
- 
- The /etc/apt/sources.list contains only the official Ubuntu repo since it's 
untouched from a clean 16.04 install.
+ The /etc/apt/sources.list contains only the official Ubuntu repo since
+ it's untouched from a clean 16.04 install.

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

Title:
  Can't update repos due to signing problems

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I can't update the repos through 'sudo apt-get update' due to these
  errors:

  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial InRelease: Errore 
sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates InRelease' 
is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-backports InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-security InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-security 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  The /etc/apt/sources.list contains only the official Ubuntu repo since
  it's untouched from a clean 16.04 install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1592040/+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 1634199] Re: In 16.10, LXD won't work with enforced dsnmasq profile

[Christian Boltz]

Patch commited to bzr trunk r3574. AppArmor 2.11 will include it.

** Changed in: apparmor
   Status: New => Fix Committed

** Changed in: apparmor
Milestone: None => 2.11

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

Title:
  In 16.10, LXD won't work with enforced dsnmasq profile

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  New

Bug description:
  After upgrading to 16.0, LXD networking stopped working due to
  enforced dnsmasq profile.

  audit: type=1400 audit(1476709813.572:4291): apparmor="DENIED"
  operation="truncate" profile="/usr/sbin/dnsmasq"
  name="/var/lib/lxd/networks/lxdbr0/dnsmasq.leases" pid=13540
  comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1634199/+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 1592040] Re: Can't update repos due to signing problems

[Christian Doczkal]

I added the Ubuntu package signing keys to my personal key chain.
Afterwards I can verify the the signatures on the lists downloaded by
'apt-get update', e.g.

$ LANG=C gpg --verify 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_Release 
gpg: Signature made Fri Oct 21 09:32:24 2016 CEST using DSA key ID 437D05B5
gpg: Good signature from "Ubuntu Archive Automatic Signing Key 
"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
gpg: Signature made Fri Oct 21 09:32:24 2016 CEST using RSA key ID C0B21F32
gpg: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32

So the error message of apt:

W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates
InRelease' is not signed.

appears to be wrong. The problem appears to be that apt is unable to
recognize/check the perfectly good signature on the downloaded files. Is
there any way to debug the signature verification process?

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

Title:
  Can't update repos due to signing problems

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I can't update the repos through 'sudo apt-get update' due to these
  errors:

  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial InRelease: Errore 
sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-updates InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates InRelease' 
is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-backports InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-backports 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: Errore GPG: http://archive.ubuntu.com/ubuntu xenial-security InRelease: 
Errore sconosciuto durante l'esecuzione di apt-key
  W: The repository 'http://archive.ubuntu.com/ubuntu xenial-security 
InRelease' is not signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  The /etc/apt/sources.list contains only the official Ubuntu repo since
  it's untouched from a clean 16.04 install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1592040/+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 1434986] Re: Not working network connection after boot

[Ilya Bizyaev]

Seems to affect me on Ubuntu 16.04. Also I don't think that's a GNOME
problem as I use KDE.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1434986] Re: Not working network connection after boot

[Ilya Bizyaev]

Oh, sorry for a typo! That's Ubuntu 16.10!

** Tags added: yakkety

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1628552] Re: on startup gateway & dns- options in /etc/network/interfaces are not always set

[Thomas Hood]

** Changed in: resolvconf (Ubuntu)
   Status: New => Incomplete

** Changed in: ifupdown (Ubuntu)
   Status: New => Incomplete

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

Title:
  on startup gateway & dns- options in /etc/network/interfaces are not
  always set

Status in ifupdown package in Ubuntu:
  Incomplete
Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  recently i have upgraded 4 VM-based systems to 16.04.1 LTS (Xenial
  Xerus). on startup, settings within /etc/network/interfaces do not
  appear to be taking effect reliably. specifically, the gateway and
  dns- settings have been problematic for me. on subsequent restarts,
  all or some of the settings take effect other times the gateway is set
  and the dns- options are not set. very problematic when the default
  gateway is not added to the routing table.

  the dns- settings were a bit easier to illustrate the issue. i added a
  comment to /etc/resolvconf/resolv.conf.d/base (# base) &
  etc/resolvconf/resolv.conf.d/tail (# tail).

  $ cat /etc/resolvconf/resolv.conf.d/*
  # base
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # tail

  on startup on 1 of the systems showed this:
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # tail

  you can see the "# base" comment wasn't added.
  let me know if i can add anymore details or if this should be posted 
somewhere else.

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1.1
Candidate: 0.8.10ubuntu1.1
Version table:
   *** 0.8.10ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.8.10ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  $ apt-cache policy resolvconf
  resolvconf:
Installed: 1.78ubuntu2
Candidate: 1.78ubuntu2
Version table:
   *** 1.78ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

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