[Touch-packages] [Bug 1610241] Re: Failed upgrade from 14.04 to 16.04 : package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit

2016-09-13 Thread abner
** Changed in: hundredpapercuts
 Assignee: (unassigned) => abner (a75)

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => abner (a75)

** Changed in: update-manager (Ubuntu)
 Assignee: (unassigned) => abner (a75)

** Changed in: virtuoso-opensource (Ubuntu)
 Assignee: (unassigned) => abner (a75)

** Changed in: virtuoso-opensource (Ubuntu)
   Status: Triaged => In Progress

** Changed in: update-manager (Ubuntu)
   Status: Triaged => In Progress

** Changed in: hundredpapercuts
   Status: Triaged => Confirmed

** Changed in: sysvinit (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: virtuoso-opensource (Ubuntu)
   Status: In Progress => Confirmed

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

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

Status in One Hundred Papercuts:
  Confirmed
Status in sysvinit package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  In Progress
Status in virtuoso-opensource package in Ubuntu:
  Confirmed

Bug description:
  This happened on an computer that was installed many years ago, and upgraded 
on each LTS version.
  When upgrading from 14.04 to 16.04.1, it started telling me that something 
wrong happened with sysv-rc, then that there were some "initscripts dependency 
problems" making it "leaving unconfigured".
  Then many packages were reported as incorrectly setup : procps, udev, 
initramfs, keyboard-configuration, console-setup, plymouth, cups, upower, 
gnome-session, gnome-shell, udisk, gvfs, software-center, mountall, upstart, 
etc.

  After reading the log files, I found out that this was caused by insserv, 
reporting "insserv rejected the script header", coming from package 
virtuoso-nepomuk having an incorrect header in /etc/init.d : "missing end of 
LSB comment", "missing LSB tags and overrides".
  This package http://packages.ubuntu.com/precise/database/virtuoso-nepomuk was 
existing on 12.04, but was removed afterwards.
  The latest version 6.1.4+dfsg1-0ubuntu1 indeed contains an incorrect header 
in /etc/init.d/virtuoso-nepomuk.

  I managed to solve the issue by adding the "END INIT INFO" in this
  file, like below :

  #! /bin/sh
  #
  # virtuoso  OpenLink Virtuoso Open-Source Edition
  #
  #   Written by OpenLink Virtuoso Maintainer
  #   
  #
  # Version:  @(#)virtuoso  6.1.4  25-Mar-2011
vos.ad...@openlinksw.com
  #

  ### BEGIN INIT INFO
  # Provides: virtuoso
  # Required-Start:   $syslog
  # Required-Stop:$syslog
  # Default-Start:2 3 4 5
  # Default-Stop: 0 1 6
  # Short-Description:Start Virtuoso database server on startup
  # Description:  Start and stop the primary instance of Virtuoso 
running
  #   in /var/lib/virtuoso/db/. The first time this runs, it loads the
  #   Conductor administrative package.
  ### END INIT INFO

  Then a "sudo apt-get upgrade" allowed me to finish the installation
  successfully.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Aug  5 11:21:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2010-05-22 (2267 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  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-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1610241/+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 1576692] Re: fully support package installation in systemd

2016-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package init-system-helpers - 1.44

---
init-system-helpers (1.44) unstable; urgency=medium

  * invoke-rc.d, service: Check for multi-user.target instead of 
graphical.target.
There is a curious bug which sometimes causes "systemctl is-active
default.target" to say inactive until "show" or "status" gets called on
the unit. This needs to be investigated.  Until then, check for
multi-user.target which by and large does the same job, but seems to work
reliably.

 -- Martin Pitt   Mon, 12 Sep 2016 22:52:23
+0200

** Changed in: init-system-helpers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  fully support package installation in systemd

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in init-system-helpers source package in Xenial:
  In Progress

Bug description:
  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]

  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.

  We'd like to have a way to fully support this in cloud-init.

  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out

  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02

  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure.
  Errors in it will break installation/upgrades of packages or
  /etc/network/if-up.d/ hooks and the like. This changes the condition
  when systemd units get started without their dependencies, and the
  condition gets weakened. This means that behaviour in a booted system
  is unchanged, but during boot this could change the behaviour of if-
  up.d/ hooks (although they have never been defined well during boot
  anyway). However, I tested this change extensively in cloud images and
  desktop installations (particularly I recreated
  https://bugs.debian.org/777113 and confirmed that this approach also
  fixes it) and could not find any regression.

  TEST CASE (for both packages):
  Run
 lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1

  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.

  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:

 lxc launch ubuntu-daily:x xprep
 lxc exec xprep bash
 # enable -proposed and dist-upgrade, then poweroff
 lxc publish xprep x-proposed

  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:

lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1

  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.

  Also test interactively installing a package that ships a service,
  like "apache2", and verify that it starts properly after installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+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 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel

2016-09-13 Thread Daniel van Vugt
Two years later... Upstream has now offered some thoughts. Although I
don't think this bug is around any more(?)

https://bugs.freedesktop.org/show_bug.cgi?id=86366

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

Title:
  Double-buffered compositing performance is sometimes very poor (30
  FPS) on intel

Status in Mesa:
  Confirmed
Status in Mir:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Double-buffered compositing performance is sometimes artificially poor
  on some intel systems. When this happens the frame rate seen is halved
  - about 30 FPS. However at the same time, Mir is observed to use very
  little render time and both the CPU and GPU are still mostly idle.
  It's just the Intel DRM logic sometimes takes two frames (~32ms) to
  complete a single page flip.

  Two known workarounds avoid the issue:
(a) Add glFinish() into the mesa DisplayBuffer code; or
(b) env INTEL_DEBUG=sync for the Mir server binary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1377872/+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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-13 Thread Daniel van Vugt
Maybe... Mesa only just started to care about mixing and matching GL
with GLES in invalid ways. I know we have done it in the past and
possibly still do. Maybe today is the day Mesa finally started checking
the validity of our GL calls...?

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1622893] [NEW] NetworkManager takes very log to start, or times out

2016-09-13 Thread Martin Pitt
Public bug reported:

Since a few days ago, NetworkManager.service takes awfully long to
start, or even times out on failure and then gets restarted. This
happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
due to the NM timeout.

In the journal there is no actual logging from /usr/sbin/NetworkManager
yet, just the start timeout.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.2-0ubuntu8
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: i3
Date: Tue Sep 13 10:05:05 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 
 source-directory interfaces.d
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile,ofono
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  NetworkManager takes very log to start, or times out

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622893/+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 1503551] Re: Java segfaulted in i965 driver - lots of deleted mmapped files

2016-09-13 Thread Timo Aaltonen
please try on yakkety

** Package changed: xorg (Ubuntu) => mesa (Ubuntu)

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

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

Title:
  Java segfaulted in i965 driver - lots of deleted mmapped files

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Java encountered a segfault in the i965 driver while running
  Minecraft. A perusal of the dump report suggests that the issue is not
  due to Minecraft but due to heavy use of the graphics exacerbating a
  memory mapping leak in the driver - it seems that the mappings for
  /dev/drm/card0 and /dri objects are not properly freed.

  Note that I was running Optifine with Multi-Core loading, which causes
  multi-threaded use of the graphics driver.

  Important parts of the hs_err file are pasted below. However, I cut
  out a *lot* of the /drm mm object and /dev/dri/card0 mappings. There's
  a more than a hundred pages at 30 lines a page.

  ---

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7f180efcc4e3, pid=31233, tid=139740657592064
  #
  # JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
  # Java VM: OpenJDK 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea 2.5.6
  # Distribution: Ubuntu 15.04, package 7u79-2.5.6-0ubuntu1.15.04.1
  # Problematic frame:
  # C  [i965_dri.so+0x1914e3]
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
  #
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  Stack: [0x7f17e831a000,0x7f17e841b000],  sp=0x7f17e84197e0,  free 
space=1021k
  Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
code)
  C  [i965_dri.so+0x1914e3]

  Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
  J 1853  org.lwjgl.opengl.GL11.nglDrawArrays(IIIJ)V (0 bytes) @ 
0x7f18614fc92a [0x7f18614fc8e0+0x4a]
  J 2863 C2 net.minecraft.client.renderer.Tessellator.func_78381_a()I (346 
bytes) @ 0x7f186177e020 [0x7f186177d7e0+0x840]
  J 5013 C2 
WorldRendererThreaded.postRenderBlocksThreaded(ILnet/minecraft/entity/EntityLivingBase;)V
 (114 bytes) @ 0x7f1861ced92c [0x7f1861ced8c0+0x6c]
  J 2709 C2 WorldRendererThreaded.updateRenderer(LIWrUpdateListener;)V (823 
bytes) @ 0x7f18617a3504 [0x7f18617a2b20+0x9e4]
  J 4593% C2 WrUpdateThread.run()V (140 bytes) @ 0x7f1861abb340 
[0x7f1861abb020+0x320]
  v  ~StubRoutines::call_stub

  Dynamic libraries:
  0040-00401000 r-xp  fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  0060-00601000 r--p  fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  00601000-00602000 rw-p 1000 fc:00 13763814   
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
  0066f000-0069 rw-p  00:00 0  
[heap]
  b5a0-bda0 rw-p  00:00 0
  bda0-c000 rw-p  00:00 0
  c000-eaa8 rw-p  00:00 0
  eaa8-1 rw-p  00:00 0
  7f1743442000-7f174344a000 rw-s  00:05 3198953/drm 
mm object (deleted)
  7f174344a000-7f1743452000 rw-s  00:05 3198952/drm 
mm object (deleted)
  7f1743452000-7f174345a000 rw-s  00:05 3198951/drm 
mm object (deleted)
  7f174345a000-7f1743462000 rw-s  00:05 3198950/drm 
mm object (deleted)
  7f1743462000-7f174346a000 rw-s 142cc8000 00:06 11074 
/dev/dri/card0
  7f174346a000-7f1743472000 rw-s  00:05 3198949/drm 
mm object (deleted)
  7f1743472000-7f174347a000 rw-s 142cc 00:06 11074 
/dev/dri/card0
  7f174347a000-7f1743482000 rw-s  00:05 3198948/drm 
mm object (deleted)
  7f1743482000-7f174348a000 rw-s 142cb8000 00:06 11074 
/dev/dri/card0
  7f174348a000-7f1743492000 rw-s 142cb 00:06 11074 
/dev/dri/card0

   snip 

  7f1745c72000-7f1745c7a000 rw-s 14168 00:06 11074 
/dev/dri/card0
  7f1745c7a000-7f1745c82000 rw-s 141678000 00:06 11074 
/dev/dri/card0
  7f1745c82000-7f1745c8a000 rw-s 14167 00:06 11074 
/dev/dri/card0
  7f1745c8a000-7f1745c92000 rw-s 141668000 00:06 11074 
/dev/dri/card0
  7f1745c92000-7f1745c9a000 rw-s  00:05 3200480/drm 
mm object (deleted)
  7f1745c9a000-7f1745ca2000 rw-s 14166 00:06 11074 
/dev/dri/card0
  7f1745c

[Touch-packages] [Bug 1622897] [NEW] Can't create LXC container

2016-09-13 Thread Dmitry Gribenchuk
Public bug reported:

Hi everyone! I'm start to use LXC version 1.1.5 on Debian Jessie.
Sometimes when I create a container I recieve an error:

lxc-create -n test -t vps --bdev=lvm --lvname=test --vgname=vg
--fstype=xfs --fssize=8G -- --release=jessie --clean

File descriptor 3 (/var/lib/lxc/test/partial) leaked on lvcreate invocation. 
Parent PID 1089: lxc-create
  Logical volume "test" created
lxc-create: bdev/lxclvm.c: lvm_create: 411 Error creating filesystem type xfs 
on /dev/vg/test
lxc-create: lxccontainer.c: do_bdev_create: 1035 Failed to create backing store 
type lvm
lxc-create: lxccontainer.c: do_lxcapi_create: 1511 Error creating backing store 
type lvm for test
lxc-create: tools/lxc_create.c: main: 318 Error creating container test 

Recently I'm upgrade LXC to 2.0.4, but the error remains.

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

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

Title:
  Can't create LXC container

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi everyone! I'm start to use LXC version 1.1.5 on Debian Jessie.
  Sometimes when I create a container I recieve an error:

  lxc-create -n test -t vps --bdev=lvm --lvname=test --vgname=vg
  --fstype=xfs --fssize=8G -- --release=jessie --clean

  File descriptor 3 (/var/lib/lxc/test/partial) leaked on lvcreate invocation. 
Parent PID 1089: lxc-create
Logical volume "test" created
  lxc-create: bdev/lxclvm.c: lvm_create: 411 Error creating filesystem type xfs 
on /dev/vg/test
  lxc-create: lxccontainer.c: do_bdev_create: 1035 Failed to create backing 
store type lvm
  lxc-create: lxccontainer.c: do_lxcapi_create: 1511 Error creating backing 
store type lvm for test
  lxc-create: tools/lxc_create.c: main: 318 Error creating container test 

  Recently I'm upgrade LXC to 2.0.4, but the error remains.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1622897/+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 1622893] Re: NetworkManager takes very log to start, or times out

2016-09-13 Thread Martin Pitt
Same often happens on shutdown.

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

Title:
  NetworkManager takes very log to start, or times out

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622893/+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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-13 Thread Sebastien Bacher
** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Volume notification keeps popping up constantly(the notifyosd bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1622709] Re: wrong app name "docker"

2016-09-13 Thread Sebastien Bacher
** Package changed: apt (Ubuntu) => command-not-found (Ubuntu)

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

Title:
  wrong app name "docker"

Status in command-not-found package in Ubuntu:
  New

Bug description:
  This is a minor name bug. If I want to start the command "docker" in
  bash and docker.io is not installed, It recommends to  install docker:
  "sudo apt-get install docker" - This is not the right package name.
  The docker command is associated with the "docker.io" package. So It
  has to recommend "sudo apt-get install docker.io".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.14
  ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-76-generic x86_64
  NonfreeKernelModules: openafs nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 12 20:22:18 2016
  InstallationDate: Installed on 2016-01-21 (235 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1622709/+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 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2016-09-13 Thread Martin
Same here

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in cups package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  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:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1571531/+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 1615716] Re: VPN profile grayed out

2016-09-13 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

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

Title:
  VPN profile grayed out

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.04 to 16.04, the VPN profile which was
  used daily is now grayed out on boot. See attached screenshot.

  After restarting the network-manager service, the profile is then
  active and can be selected and connects without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Aug 22 12:02:05 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-03-23 (883 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   10.0.2.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.2.1 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.108  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (11 days ago)
  modified.conffile..etc.dnsmasq.d.network-manager: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-08-07T19:56:59.679956
  mtime.conffile..etc.dnsmasq.d.network-manager: 2014-06-30T11:51:24.816947
  nmcli-nm:
   RUNNING  VERSION  STATE   STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connecting  starting  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1615716/+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 1619285] Re: cc_growpart fails on yakkety

2016-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.28.2-1ubuntu1

---
util-linux (2.28.2-1ubuntu1) yakkety; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
- Regularly trim SSDs automatically (core-1311-ssd-trimming):
  + Add debian/fstrim-all.cron: Call fstrim --all. Installed as
/etc/cron.weekly/fstrim.
- Drop debian/hwclock.rules and hwclock.default, recent kernels sync the
  RTC automatically.
- Add sulogin-fallback-static-sh.patch: Add support for /bin/static-sh as
  fallback if the regular shell fails to execute. Patch ported from
  sysvinit. (see LP #505887)
- Add sulogin-lockedpwd.patch: Make sure file systems can be fixed on
  machines with locked root accounts (as Ubuntu does by default). Don't
  require --force for sulogin.
- Drop debian/util-linux.preinst: Unconditionally deleting files
  is wrong, and dpkg will overwrite symlinks with real files anyway.
- Drop the Breaks: cloud-utils, Ubuntu has a different cloud-utils
  packaging and this does not affect Ubuntu > 16.04 any more.
- Add debian/util-linux.maintscript to clean upstart jobs on upgrade. This
  needs to be kept until after 18.04 LTS.
  * The new upstream version reverts the sfdisk exit code change from 2.28.1.
(LP: #1619285)

util-linux (2.28.2-1) unstable; urgency=medium

  * debian/gbp.conf: set upstream-vcs-tag for import-orig
  * New upstream release.
- among other things includes fixes for HPPA testsuite failures
  (Closes: #827225)
  * Drop d/p/tests-Fix-fdisk-id-and-fdisk-mbr-nondos-mode-on-Sparc.patch
- now include in upstream release.

 -- Martin Pitt   Mon, 12 Sep 2016 23:22:44
+0200

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

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

Title:
  cc_growpart fails on yakkety

Status in cloud-utils:
  Fix Committed
Status in cloud-utils package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  cc_growpart fails on ppc64el, with the following messages :

  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command 
['growpart', '--dry-run', '/dev/vda', '1'] with allowed return codes [0] 
(shell=False, capture=True)
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Running command 
['growpart', '/dev/vda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[WARNING]: Failed: growpart 
/dev/vda 1
  Sep  1 12:06:58 ubuntu [CLOUDINIT] util.py[DEBUG]: Failed: growpart /dev/vda 
1#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 109, in 
resize#012util.subp(["growpart", diskdev, partnum])#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['growpart', '/dev/vda', '1']#012Exit code: 
2#012Reason: -#012Stdout: 'FAILED: failed to resize\n'#012Stderr: "attempt to 
resize /dev/vda failed. sfdisk output below:\n| GPT PMBR size mismatch (4612095 
!= 41943039) will be corrected by w(rite).\n| Backup files:\n| PMBR 
(offset 0, size   512): 
/tmp/growpart.wr7bvu/orig.save-vda-0x.bak\n|   GPT Header (offset   
512, size   512): /tmp/growpart.wr7bvu/orig.save-vda-0x0200.bak\n|  GPT 
Entries (offset  1024, size 16384): 
/tmp/growpart.wr7bvu/orig.save-vda-0x0400.bak
 \n| \n| Disk /dev/vda: 20 GiB, 21474836480 bytes, 41943040 sectors\n| Units: 
sectors of 1 * 512 = 512 bytes\n| Sector size (logical/physical): 512 bytes / 
512 bytes\n| I/O size (minimum/optimal): 512 bytes / 512 bytes\n| Disklabel 
type: gpt\n| Disk identifier: 5AF0CCE2-DDF5-4419-B991-213EE1F1B873\n| \n| Old 
situation:\n| \n| Device Start End Sectors  Size Type\n| /dev/vda1  
18432 4612062 4593631  2.2G Linux filesystem\n| /dev/vda2   2048   18431   
163848M PowerPC PReP boot\n| \n| Partition table entries are not in disk 
order.\n| \n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> 
Script header accepted.\n| >>> Script header accepted.\n| >>> Script header 
accepted.\n| >>> Created a new GPT disklabel (GUID: 
5AF0CCE2-DDF5-4419-B991-213EE1F1B873).\n| Created a new partition 1 of type 
'Linux filesystem' and of size 20 GiB.\n| /dev/vda2: Created a new partition 2 
of type 'PowerPC PReP boot' and of size 8 MiB.\n| /dev/vda3: \n| New 
situation:\n| \n| Device
  Start  End  Sectors Size Type\n| /dev/vda1  18432 41943006 41924575  20G 
Linux filesystem\n| /dev/vda2   20481843116384   8M PowerPC PReP 
boot\n| \n| Partition table entries are not in disk order.\n| \n| The partition 
table has been altered.\n| Calling ioctl() to re-read partition table.

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2016-09-13 Thread Martin
It happened after I installed ESET Node32.

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in cups package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  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:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1571531/+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 1622707] Re: CUPS Web UI stops responding after a while

2016-09-13 Thread Iiro Laiho
** Changed in: cups (Ubuntu)
   Status: New => Invalid

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  Invalid

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1622707/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch

2016-09-13 Thread Petras
how this can stll have the incomplete status? the gps is broken, it does not 
work on bq m10. the test_gps in /usr/bin results in segfaults. this is key 
feature of mobile (together with sensorsors) to do the cool stuff (not cool is 
like reading mail, tweeting, facebook, and other stuff calculating 1+1, at the 
moment ubuntu touch is capable only that), else I dont see what I need for the 
mobile linux.
I see gps outputs the nmea output. why not use the gpsd as middle layer. it 
also would make possible to use bluetooth gps more advanced/precise receivers.

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in Canonical System Image:
  Incomplete
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms & Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442105/+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 1186662] Re: isc-dhcp-server fails to renew lease file

2016-09-13 Thread Emmanuel Proust
Double checked with several devices connected with static leases.

Nothing else than the following content in my dhcpd.leases file...

cat /var/lib/dhcp/dhcpd.leases

gives :

# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.3.3

server-duid "\000\001\000\001\037@\213\210\000PV\213\320+";

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Triaged

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-13 Thread Ihar Hrachyshka
I added Ubuntu dnsmasq package to affected projects to raise visibility
around missing dependency for OpenStack Neutron in Xenial dnsmasq
package.

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

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  In Progress
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+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 1622969] [NEW] History view is slow to load with a large amount of records

2016-09-13 Thread Andrew Hayzen
Public bug reported:

What happened:
The history view takes many seconds (between 8-9 seconds on mako) to load when 
it has a large number of records (I currently have 4640 records).

What I expected to happen:
For the view to load in a reasonable amount of time, by either only showing 
recent entries or trimming the db. Other browsers only show the history for 
today/yesterday in the initial view and then have buttons to show older history.

Note: that when testing multiple windows, if one window is looking at
the history view and the other navigates to page it blocks the UI for a
few seconds as the history view is being updated.

$ apt-cache policy webbrowser-app
webbrowser-app:
  Installed: 0.23+15.04.20160912-0ubuntu1
  Candidate: 0.23+15.04.20160912-0ubuntu1
  Version table:
 *** 0.23+15.04.20160912-0ubuntu1 0
   1003 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
100 /var/lib/dpkg/status
 0.23+15.04.20160825-0ubuntu1 0
   1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
 0.23+15.04.20150416-0ubuntu1 0
500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

$ system-image-cli -i
current build number: 398
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-09-12 15:18:40
version version: 398
version ubuntu: 20160910
version device: 20160401.1
version custom: 20160904-9-vivid

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  What happened:
- The history view takes many seconds to load when it has a large number of 
records (I currently have 4640 records). 
+ The history view takes many seconds (between 8-9 seconds on mako) to load 
when it has a large number of records (I currently have 4640 records).
  
  What I expected to happen:
  For the view to load in a reasonable amount of time, by either only showing 
recent entries or trimming the db. Other browsers only show the history for 
today/yesterday in the initial view and then have buttons to show older history.
  
- 
- Note: that when testing multiple windows, if one window is looking at the 
history view and the other navigates to page it blocks the UI for a few seconds 
as the history view is being updated.
- 
+ Note: that when testing multiple windows, if one window is looking at
+ the history view and the other navigates to page it blocks the UI for a
+ few seconds as the history view is being updated.
  
  $ apt-cache policy webbrowser-app
  webbrowser-app:
-   Installed: 0.23+15.04.20160912-0ubuntu1
-   Candidate: 0.23+15.04.20160912-0ubuntu1
-   Version table:
-  *** 0.23+15.04.20160912-0ubuntu1 0
-1003 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
- 100 /var/lib/dpkg/status
-  0.23+15.04.20160825-0ubuntu1 0
-1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
-  0.23+15.04.20150416-0ubuntu1 0
- 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages
+   Installed: 0.23+15.04.20160912-0ubuntu1
+   Candidate: 0.23+15.04.20160912-0ubuntu1
+   Version table:
+  *** 0.23+15.04.20160912-0ubuntu1 0
+    1003 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
+ 100 /var/lib/dpkg/status
+  0.23+15.04.20160825-0ubuntu1 0
+    1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
+  0.23+15.04.20150416-0ubuntu1 0
+ 500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages
  
  $ system-image-cli -i
  current build number: 398
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-09-12 15:18:40
  version version: 398
  version ubuntu: 20160910
  version device: 20160401.1
  version custom: 20160904-9-vivid

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

Title:
  History view is slow to load with a large amount of records

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  What happened:
  The history view takes many seconds (between 8-9 seconds on mako) to load 
when it has a large number of records (I currently have 4640 records).

  What I expected to happen:
  For the view to load in a reasonable amount of time, by either only showing 
recent entries or trimming the db. Other browsers only show the history for 
today/yesterday in the initial view and then have buttons to show older history.

  Note: that when testing multiple windows, if one window is looking at
  the history view and the other navigates to page it blocks the UI for
  a few seconds as the history view is being updated.

  $ apt-cache policy webbrowser-app
  webbrow

[Touch-packages] [Bug 1613670] Re: Webview turns white after clicking on it

2016-09-13 Thread Timo Jyrinki
** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => High

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

Title:
  Webview turns white after clicking on it

Status in oxide-qt package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  This happens on yakkety with unity7 (xcb).

  1) Go to System Settings -> Online Accounts
  2) Choose "Add account"
  3) Choose Google, Facebook, Evernote or any web-base providers
  4) Wait for the page to load
  5) Click anywhere on the page (even clicking on a scrollbar triggers this 
behaviour)

  After step 5, the webview will turn white, and apparently stop responding.
  When running signon-ui with logging enabled, one can see several warnings 
coming from Oxide:

  http://paste.ubuntu.com/23061298/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1613670/+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 1613670] Re: Webview turns white after clicking on it

2016-09-13 Thread Alberto Mardegan
It turns out we've been extremely lucky, in that the commit which fixes
(or hides?) this bug landed in Qt 5.6 just yesterday:

  https://codereview.qt-project.org/#/c/153945/

I've tried building Qt with and without that commit, and indeed it makes
a difference.

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

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

Title:
  Webview turns white after clicking on it

Status in oxide-qt package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  This happens on yakkety with unity7 (xcb).

  1) Go to System Settings -> Online Accounts
  2) Choose "Add account"
  3) Choose Google, Facebook, Evernote or any web-base providers
  4) Wait for the page to load
  5) Click anywhere on the page (even clicking on a scrollbar triggers this 
behaviour)

  After step 5, the webview will turn white, and apparently stop responding.
  When running signon-ui with logging enabled, one can see several warnings 
coming from Oxide:

  http://paste.ubuntu.com/23061298/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1613670/+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 1622969] Re: History view is slow to load with a large amount of records

2016-09-13 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  History view is slow to load with a large amount of records

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  The history view takes many seconds (between 8-9 seconds on mako) to load 
when it has a large number of records (I currently have 4640 records).

  What I expected to happen:
  For the view to load in a reasonable amount of time, by either only showing 
recent entries or trimming the db. Other browsers only show the history for 
today/yesterday in the initial view and then have buttons to show older history.

  Note: that when testing multiple windows, if one window is looking at
  the history view and the other navigates to page it blocks the UI for
  a few seconds as the history view is being updated.

  $ apt-cache policy webbrowser-app
  webbrowser-app:
    Installed: 0.23+15.04.20160912-0ubuntu1
    Candidate: 0.23+15.04.20160912-0ubuntu1
    Version table:
   *** 0.23+15.04.20160912-0ubuntu1 0
     1003 http://ppa.launchpad.net/ci-train-ppa-service/landing-084/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   0.23+15.04.20160825-0ubuntu1 0
     1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
   0.23+15.04.20150416-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

  $ system-image-cli -i
  current build number: 398
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-09-12 15:18:40
  version version: 398
  version ubuntu: 20160910
  version device: 20160401.1
  version custom: 20160904-9-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1622969/+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 1398193] Re: The bluetooth headset can not control the media playback

2016-09-13 Thread fabrice
it would be great if this bug was treated

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

Title:
  The bluetooth headset can not control the media playback

Status in Canonical System Image:
  Triaged
Status in bluez package in Ubuntu:
  Triaged
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+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 1622990] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

2016-09-13 Thread Capt. Heinz Reich jr.
Public bug reported:

problems installing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Sep 13 13:12:52 2016
ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 
1 zurück
InstallationDate: Installed on 2016-09-05 (7 days ago)
InstallationMedia: budgie-remix 16.04 - Release i386
Lpstat: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'lpstat'
MachineType: Acer Aspire One 522
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=b36d4d96-29a4-4715-95c5-b8f02899fc00 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=b36d4d96-29a4-4715-95c5-b8f02899fc00 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE10-BZ
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.modalias: 
dmi:bvnAcer:bvrV1.12:bd06/08/2011:svnAcer:pnAspireOne522:pvrV1.12:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12:
dmi.product.name: Aspire One 522
dmi.product.version: V1.12
dmi.sys.vendor: Acer

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess
  installiertes pre-removal-Skript gab den Fehlerwert 1 zurück

Status in cups package in Ubuntu:
  New

Bug description:
  problems installing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Sep 13 13:12:52 2016
  ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2016-09-05 (7 days ago)
  InstallationMedia: budgie-remix 16.04 - Release i386
  Lpstat: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'lpstat'
  MachineType: Acer Aspire One 522
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=b36d4d96-29a4-4715-95c5-b8f02899fc00 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=b36d4d96-29a4-4715-95c5-b8f02899fc00 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: Unterprozess 
installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.modalias: 
dmi:bvnAcer:bvrV1.12:bd06/08/2011:svnAcer:pnAspireOne522:pvrV1.12:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.12:
  dmi.product.name: Aspire One 522
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1622990/+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 1622987] [NEW] Auto-completion seems broken with umount command

2016-09-13 Thread Nairwolf
Public bug reported:

I'm using Xubuntu with the devel version. I've seen this bug with Ubuntu
also, in the daily version.

The auto-completion of the command 'umount' seems broken.

I have an usb key called "Xubuntu 16.10 amd64". I verify that with the
command lsblk.

Then, I type 'umount /media' then I press 'tab' to have the
autocompletion. With 16.04, the autocompletion completes correctly with
backslash : "/media/nairwolf/\ Xubuntu\ amd64"

But, now, with Yakkety, the autocompletion stops before the first space.

There is a screenshot to explain what I have :
https://i.imgur.com/UOyUEyn.png

Don't forget that I'm typing only "umount /media", and then, I press tab
to have the autocompletion. And this picture is the result of the auto-
completion.

I'm unable to reproduce that with other basic command like "ls", "cd" or
"rm". That means if I'm typing "ls /media", then "TAB" it will be
completed correctly.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: util-linux 2.28.1-1ubuntu1
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: XFCE
Date: Tue Sep 13 13:07:22 2016
InstallationDate: Installed on 2016-08-18 (25 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "screenshot"
   https://bugs.launchpad.net/bugs/1622987/+attachment/4739955/+files/url.png

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

Title:
  Auto-completion seems broken with umount command

Status in util-linux package in Ubuntu:
  New

Bug description:
  I'm using Xubuntu with the devel version. I've seen this bug with
  Ubuntu also, in the daily version.

  The auto-completion of the command 'umount' seems broken.

  I have an usb key called "Xubuntu 16.10 amd64". I verify that with the
  command lsblk.

  Then, I type 'umount /media' then I press 'tab' to have the
  autocompletion. With 16.04, the autocompletion completes correctly
  with backslash : "/media/nairwolf/\ Xubuntu\ amd64"

  But, now, with Yakkety, the autocompletion stops before the first
  space.

  There is a screenshot to explain what I have :
  https://i.imgur.com/UOyUEyn.png

  Don't forget that I'm typing only "umount /media", and then, I press
  tab to have the autocompletion. And this picture is the result of the
  auto-completion.

  I'm unable to reproduce that with other basic command like "ls", "cd"
  or "rm". That means if I'm typing "ls /media", then "TAB" it will be
  completed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: util-linux 2.28.1-1ubuntu1
  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: XFCE
  Date: Tue Sep 13 13:07:22 2016
  InstallationDate: Installed on 2016-08-18 (25 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1622987/+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 1224007] Re: mtu not always set properly on bond/vlan interface

2016-09-13 Thread Robie Basak
Subscribing ~ubuntu-sponsors

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

Title:
  mtu not always set properly on bond/vlan interface

Status in ifupdown package in Ubuntu:
  Confirmed
Status in vlan package in Ubuntu:
  New
Status in ifupdown package in Debian:
  New

Bug description:
  * Description

  When configuring a network with bonding+vlan and setting the MTU,
  occasionally the MTU doesn't get set properly on the vlan interface.

  In addition if one checks /var/log/upstart/networking.log whenever there is a 
failure the following message is printed:
  SIOCSIFMTU: Numerical result out of range

  I've tested the latest ifupdown package (0.7.44) and the problem still exists.
  Multi/single CPU settings both exhibit the issue.

  * Versions
  This affects latest ifupdown and ubuntu p/q/r/s.

  * Test Case

  # Create a p/q/r/s server vm with two network interfaces
  # This is reproducible on real hardware as well

  # Install the following
  sudo apt-get install vlan ifenslave-2.6 bridge-utils
  sudo modprobe bonding 8021q

  # Edit the interfaces file
  /etc/networking/interfaces:

  auto bond0
  iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
bond-lacp-rate 1
bond-slaves eth0 eth1
post-up ifconfig bond0 mtu 9000

  auto eth0
  iface eth0 inet manual
bond-master bond0
post-up ifconfig eth0 mtu 9000

  auto eth1
  iface eth1 inet manual
bond-master bond0
post-up ifconfig eth1 mtu 9000

  auto bond0.123
  iface bond0.123 inet static
address 192.168.122.68
netmask 255.255.255.0
gateway 192.168.122.1
post-up ifconfig bond0.123 mtu 9000

  # edit rc.local (or another startup script) so we reboot until we hit the 
error
  /etc/rc.local:

  DEVS="eth0 eth1 bond0 bond0.123"
  for d in $DEVS; do
  mtu=$(cat /sys/class/net/$d/mtu)
  if [ $mtu != 9000 ]; then
  echo "FAIL"
  exit 1
  fi
  done

  reboot
  exit 0

  # Now reboot the machine, within 10m or so you should be at the login prompt
  # if you ifconfig | grep MTU you will see some of our interfaces did not get 
  # the MTU properly set and the test failed.
  # Essentially we want to ensure that all MTU's (except lo) were set to 9000

  * Workaround

  Change the bond0.123 post-up command to:
post-up sleep 2 && ifconfig bond0.123 mtu 9000

  Now when rebooting the interfaces will all be brought up with the
  proper MTU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007/+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 1508905] Re: Graphics disorder, a large "claw" ('>') appearing

2016-09-13 Thread Ivo Xavier
Good morning everybody,

Today this claw/arrow appeared again. There isn't a way to reproduce it
exactly the same way everytime, but the behavior is almost the same, at
least with me. Scrooling up and down, enable and disable "show results
from (...)" click on cards, get back, scooling up and down, enable and
disable "show results from (...)" , doing this consistently and the
claw/arrow appears. Today Scope is the only one affected by this, I've
tried to do the same on NearBy Scope, but nothing happens.

The upcoming refresh of scopes also suffers from this bug?

** Attachment added: "screenshot2"
   
https://bugs.launchpad.net/today-scope/+bug/1508905/+attachment/4739983/+files/Sem%20t%C3%ADtulo.png

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

Title:
  Graphics disorder, a large "claw" ('>') appearing

Status in Today Scope:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Currently I have this bug. It was already present in the OTA-6.
  Usually a reboot fix the problem, but after a while it come back
  again.

  It only appears ate the bottom of the scope! If I swipe back to the
  top the "claw" fade out.

  I've attached a screenshot.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1508905/+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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-13 Thread Gerry Boland
Note it is only Unity8 which is mixing GL and GLES calls, clients are
not doing that. Qt clients are only doing GL calls on desktop.

Nothing obvious comes to mind here.

It may be Qt's EGL configuration code is failing - code that QtUbuntu is
using. Another consumer of that same code is the EGL backend for the XCB
QPA plugin - the non-default - as usually the GLX backend is used.

Could someone with a problematic system log into Unity7, and for a simple qml 
file, run:
QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml
and see does it fail?

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1622447] Re: libnss3-1d: dependcies update

2016-09-13 Thread Kai Kasurinen
** Changed in: ecryptfs-utils (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  libnss3-1d: dependcies update

Status in ecryptfs-utils package in Ubuntu:
  Fix Released
Status in nss package in Ubuntu:
  Invalid
Status in ecryptfs-utils package in Debian:
  Fix Released

Bug description:
  in Yakkety Yak one dependency(or more precisely dependency definition)
  of the package libnss3-1d is outdated

  it has 'Depends: libnss3 (= 2:3.25-1ubuntu1)' but it should has
  'Depends: libnss3 >= 2:3.25-1ubuntu1)' or something like
  that(otherwise libnss3-1d can't install when libnss3 !=
  2:3.25-1ubuntu1)...

  $ lsb_release -rd
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1622447/+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 1622707] Re: CUPS Web UI stops responding after a while

2016-09-13 Thread Till Kamppeter
*** This bug is a duplicate of bug 1598300 ***
https://bugs.launchpad.net/bugs/1598300

** This bug has been marked a duplicate of bug 1598300
   cups hang after a while

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

Title:
  CUPS Web UI stops responding after a while

Status in cups package in Ubuntu:
  Invalid

Bug description:
  CUPS Web administration UI available at localhost:631 stops responding
  after a while. Initially it works fine, but after it has been running
  for a moment it just shows the "Connection refused" message of the
  browser. The printing system keeps running otherwise. This is a clean
  install of Ubuntu. I have installed Seafile from PPA but I don't think
  it has anything to do with this.

  I am unable to find anything relevant from journalctl nor CUPS logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Mon Sep 12 21:10:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6320
  Papersize: a4
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=0b75be02-897e-4a0b-9ff6-441512bb7493 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 05VMY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn05VMY6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1622707/+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 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

2016-09-13 Thread Martin Pitt
strace shows what happens:

14:04:49.135589 getrandom(0x7ffdc3857ecf, 1, GRND_NONBLOCK) = -1 EAGAIN 
(Resource temporarily unavailable)
14:04:49.135620 getrusage(0x1 /* RUSAGE_??? */, {ru_utime={0, 0}, ru_stime={0, 
8000}, ru_maxrss=8344, ru_ixrss=0, ru_idrss=0, ru_isrss=0, ru_minflt=509, 
ru_majflt=17, ru_nswap=0, ru_inblock=4048, ru_oublock=0, ru_msgsnd=0, 
ru_msgrcv=0, ru_nsignals=0, ru_nvcsw=969, ru_nivcsw=20}) = 0
14:04:49.135640 
getrandom("\20@\251\341k\216T!\215\230\23\5\236\r\v~\253\360\321d\370_\263\227\364\376\20;}\314\271\217",
 32, 0) = 32
14:05:16.540470 
getrandom("FQ\212\356\17\17\17\323\316\230\7\275X1\3557\226\373U4F\\ 
sHOz\3\244$\226\270", 32, 0) = 32
14:05:16.540565 getrandom("+\262\232k\304\234\375R", 8, 0) = 8

So it's blocking on the getrandom() call. dmesg shows that the RNG pool
only gets initialized 30 seconds into the boot.

This happens even before NM gets to write its first "NetworkManager ..
is starting" log message.

** Summary changed:

- NetworkManager takes very log to start, or times out
+ NetworkManager takes very log to start, or times out, blocked on RNG

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

Title:
  NetworkManager takes very log to start, or times out, blocked on RNG

Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622893/+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 1622893] Re: NetworkManager takes very log to start, or times out, blocked on RNG

2016-09-13 Thread Martin Pitt
Downgrading libgnutls30 from 3.5.3 (current yakkety) to the previous
upstream version 3.5.2
(https://launchpad.net/ubuntu/+source/gnutls28/3.5.2-2ubuntu4/) fixes
this. So apparently libgnutls now does a blocking getrandom() on
startup, which is rather unfriendly as you cannot use the library during
early boot any more.

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

** Changed in: gnutls28 (Ubuntu)
   Status: New => Triaged

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

Title:
  NetworkManager takes very log to start, or times out, blocked on RNG

Status in gnutls28 package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  Since a few days ago, NetworkManager.service takes awfully long to
  start, or even times out on failure and then gets restarted. This
  happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
  systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
  due to the NM timeout.

  In the journal there is no actual logging from
  /usr/sbin/NetworkManager yet, just the start timeout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  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: i3
  Date: Tue Sep 13 10:05:05 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   source-directory interfaces.d
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1622893/+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 1622987] Re: Auto-completion seems broken with umount command

2016-09-13 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1622987

** Tags added: iso-testing

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

Title:
  Auto-completion seems broken with umount command

Status in util-linux package in Ubuntu:
  New

Bug description:
  I'm using Xubuntu with the devel version. I've seen this bug with
  Ubuntu also, in the daily version.

  The auto-completion of the command 'umount' seems broken.

  I have an usb key called "Xubuntu 16.10 amd64". I verify that with the
  command lsblk.

  Then, I type 'umount /media' then I press 'tab' to have the
  autocompletion. With 16.04, the autocompletion completes correctly
  with backslash : "/media/nairwolf/\ Xubuntu\ amd64"

  But, now, with Yakkety, the autocompletion stops before the first
  space.

  There is a screenshot to explain what I have :
  https://i.imgur.com/UOyUEyn.png

  Don't forget that I'm typing only "umount /media", and then, I press
  tab to have the autocompletion. And this picture is the result of the
  auto-completion.

  I'm unable to reproduce that with other basic command like "ls", "cd"
  or "rm". That means if I'm typing "ls /media", then "TAB" it will be
  completed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: util-linux 2.28.1-1ubuntu1
  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: XFCE
  Date: Tue Sep 13 13:07:22 2016
  InstallationDate: Installed on 2016-08-18 (25 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1622987/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2016-09-13 Thread Vahid Mardani
After two years of changing profile, disconnectiong, reconnecting and
setting a2dp profile, for my headset manually about 6-7 times per day, i
decided to throw the pain out for ever, anyway.

You are welcome, Jônata Tyska Carvalho.

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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


Re: [Touch-packages] [Bug 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-13 Thread Daniel d'Andrada
On 13/09/2016 08:49, Gerry Boland wrote:
> Could someone with a problematic system log into Unity7, and for a simple qml 
> file, run:
> QT_XCB_GL_INTEGRATION=xcb_egl qmlscene ~/test.qml
> and see does it fail?

It works fine.

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1623036] [NEW] Sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main)

2016-09-13 Thread Sam Hartman
Public bug reported:

Please sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Merge from Debian unstable.  Remaining changes:
- Fix uninitialized variable warning on ppc64el.

A revised version of this patch has been committed and included in the Debian 
release.
In addition, the Debian version includes a critical fix for KDCs running on 
32-bit systems.


Changelog entries since current yakkety version 1.14.3+dfsg-1ubuntu1:

krb5 (1.14.3+dfsg-2) UNRELEASED; urgency=medium

  * Fix gcc -O3, thanks Ben Kaduk/Steve Langasek, Closes: #833798
  * Fix kdb5_util create on 32-bit platforms, thanks Greg Hudson, Closes:
#834035

 -- Sam Hartman   Mon, 05 Sep 2016 21:03:14 -0400

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

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

Title:
  Sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main)

Status in krb5 package in Ubuntu:
  New

Bug description:
  Please sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge from Debian unstable.  Remaining changes:
  - Fix uninitialized variable warning on ppc64el.

  A revised version of this patch has been committed and included in the Debian 
release.
  In addition, the Debian version includes a critical fix for KDCs running on 
32-bit systems.

  
  Changelog entries since current yakkety version 1.14.3+dfsg-1ubuntu1:

  krb5 (1.14.3+dfsg-2) UNRELEASED; urgency=medium

* Fix gcc -O3, thanks Ben Kaduk/Steve Langasek, Closes: #833798
* Fix kdb5_util create on 32-bit platforms, thanks Greg Hudson, Closes:
  #834035

   -- Sam Hartman   Mon, 05 Sep 2016 21:03:14 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1623036/+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 1623046] [NEW] text doesn't fit the button field in low battery notification(spanish)

2016-09-13 Thread Victor gonzalez
Public bug reported:

Enviroment:

current build number: 187
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-09-13 10:09:37
version version: 187
version ubuntu: 20160913
version device: 20160809.0
version custom: 20160831--42-26-vivid

Preconditions:  > 15% battery life

Steps to reproduce:

1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)

Current result: Left button of low battery notification is bigger than
button field

Expected result: Text should be inside the button field

Add info: not sure if it happens also in krillin as mine is fully
charged right now

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot20160913_151918295.png"
   
https://bugs.launchpad.net/bugs/1623046/+attachment/4740091/+files/screenshot20160913_151918295.png

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

Title:
  text doesn't fit the button field in low battery notification(spanish)

Status in indicator-power package in Ubuntu:
  New

Bug description:
  Enviroment:

  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions:  > 15% battery life

  Steps to reproduce:

  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)

  Current result: Left button of low battery notification is bigger than
  button field

  Expected result: Text should be inside the button field

  Add info: not sure if it happens also in krillin as mine is fully
  charged right now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1623046/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-13 Thread Eric Desrochers
** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu)
   Status: New => In Progress

** Tags added: sts

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1532358] Re: flaky autopkgtests cause migration issues

2016-09-13 Thread Marcus Tomlinson
** Branch linked: lp:~marcustomlinson/unity-scopes-shell/relax-harness-
timeouts

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

Title:
  flaky autopkgtests cause migration issues

Status in Canonical System Image:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  A few times recently when unity8 got into xenial-proposed for
  migration, unity-scope-click's autopkgtest failed on the first run,
  having passed on the next:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz

  This delays migration until someone notices the failure and asks for a
  re-run, which usually passes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan  9 00:29:21 2016
  SourcePackage: unity-scope-click
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch

2016-09-13 Thread Thomas Voß
/usr/bin/test_gps is known to segfault and we should totally remove it.

For "Why not gpsd?": It does not support assisted GPS in the way we need
it, nor does it provide any sort of fusioning of network- and satellite-
based positioning ootb. More to this, the NMEA that is reported back
here does not report a position either, all the respective entries are
marked invalid.

Let's focus on the issue at hand.

The bug is marked as incomplete as:

(1.) we fail to reproduce it reliably
(2.) spot something meaningful in the logs that tells us what is going wrong

With that, it would be very helpful if you could provide us with the
information described in the forensics doc:
https://wiki.ubuntu.com/Process/Merges/TestPlan/location-
service#Forensics

If you are fine with switching your image to rw, the output of:

  > sudo apt install ubuntu-location-service-examples
  > sudo GLOG_v=1000 GLOG_logtostderr=1 
/usr/lib/*/ubuntu-location-service/examples/client --bus system

would be very helpful.

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in Canonical System Image:
  Incomplete
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms & Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442105/+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 1532358] Re: flaky autopkgtests cause migration issues

2016-09-13 Thread Rodney Dawes
** Changed in: unity-scope-click (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: unity-scopes-shell (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  flaky autopkgtests cause migration issues

Status in Canonical System Image:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  A few times recently when unity8 got into xenial-proposed for
  migration, unity-scope-click's autopkgtest failed on the first run,
  having passed on the next:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz

  This delays migration until someone notices the failure and asks for a
  re-run, which usually passes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan  9 00:29:21 2016
  SourcePackage: unity-scope-click
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+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 1532358] Re: flaky autopkgtests cause migration issues

2016-09-13 Thread Launchpad Bug Tracker
** Branch linked: lp:~dobey/unity-scope-click/update-harness-tests

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

Title:
  flaky autopkgtests cause migration issues

Status in Canonical System Image:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  A few times recently when unity8 got into xenial-proposed for
  migration, unity-scope-click's autopkgtest failed on the first run,
  having passed on the next:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz

  This delays migration until someone notices the failure and asks for a
  re-run, which usually passes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan  9 00:29:21 2016
  SourcePackage: unity-scope-click
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+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 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2016-09-13 Thread Till Kamppeter
OdyX, Jamie, Marc, should we simply allow cupsd accessing
/etc/ld.so.preload? Or are there any security reasons against it? If
there are reasons against it, how can we silence these messages?

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in cups package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  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:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1571531/+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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-13 Thread Timo Aaltonen
Probably caused by

commit de695014eb6c819b050a4f7f2f952c4466047292
Author: Nicolas Boichat 
Date:   Fri Jul 15 16:24:20 2016 +0800

egl/dri2: dri2_make_current: Set EGL error if bindContext fails

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1620934] Re: Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")

2016-09-13 Thread Timo Aaltonen
Without this, if a configuration is, say, available only on GLES2/3, but
not on GLES1, and is rejected by the dri module's bindContext call,
eglMakeCurrent fails with error "EGL_SUCCESS".

In this patch, we set error to EGL_BAD_MATCH, which is what CTS/dEQP
dEQP-EGL.functional.surfaceless_context expect.

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

Title:
  Qt/QML apps don't render any more (logs say "QEGLPlatformContext:
  eglMakeCurrent failed: 3001")

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  nothing works, all apps, dash are just black windows - Ubuntu 16.10 +
  proposed (x86, and using Nvidia 8600GT with nouveau drivers)

  
  and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 
3001"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1602737] Comment bridged from LTC Bugzilla

2016-09-13 Thread bugproxy
--- Comment From barbara.mun...@de.ibm.com 2016-09-13 10:13 EDT---
Updated to kernel 4.7.0-040700-generic. With the appropriate entry in 
/etc/udev/rules.d/70-persistent-net.rules, the PCI device shows uip renamed.

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: /lib/udev/rules.d/60-gnupg.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
  Reading rules file: /lib/udev/rules.d/6

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-09-13 Thread bpowell
Log file attached.


** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+attachment/4740094/+files/pulseverbose.log

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

Title:
  Volume notification keeps popping up constantly(the notifyosd bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Ken VanDine
** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1623073] [NEW] source package build is failing

2016-09-13 Thread Max
Public bug reported:

Trying to build the source package using sbuild is failing with the
following error.

dh_clean
 debian/rules build
gtkdocize --docdir libkmod/docs
autoreconf --force --install --symlink
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: linking file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: linking file 'm4/libtool.m4'
libtoolize: linking file 'm4/ltoptions.m4'
libtoolize: linking file 'm4/ltsugar.m4'
libtoolize: linking file 'm4/ltversion.m4'
libtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:13: installing 'build-aux/compile'
configure.ac:19: installing 'build-aux/config.guess'
configure.ac:19: installing 'build-aux/config.sub'
configure.ac:17: installing 'build-aux/install-sh'
configure.ac:17: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
Makefile.am:207: installing 'build-aux/py-compile'
parallel-tests: installing 'build-aux/test-driver'
libkmod/docs/gtk-doc.make:33: error: EXTRA_DIST must be set with '=' before 
using '+='
libkmod/docs/Makefile.am:29:   'libkmod/docs/gtk-doc.make' included from here
autoreconf: automake failed with exit status: 1
debian/rules:60: recipe for target 'configure' failed
make: *** [configure] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

** Attachment added: "buildlog"
   https://bugs.launchpad.net/bugs/1623073/+attachment/4740110/+files/buildlog

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

Title:
  source package build is failing

Status in kmod package in Ubuntu:
  New

Bug description:
  Trying to build the source package using sbuild is failing with the
  following error.

  dh_clean
   debian/rules build
  gtkdocize --docdir libkmod/docs
  autoreconf --force --install --symlink
  libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
  libtoolize: linking file 'build-aux/ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: linking file 'm4/libtool.m4'
  libtoolize: linking file 'm4/ltoptions.m4'
  libtoolize: linking file 'm4/ltsugar.m4'
  libtoolize: linking file 'm4/ltversion.m4'
  libtoolize: linking file 'm4/lt~obsolete.m4'
  configure.ac:13: installing 'build-aux/compile'
  configure.ac:19: installing 'build-aux/config.guess'
  configure.ac:19: installing 'build-aux/config.sub'
  configure.ac:17: installing 'build-aux/install-sh'
  configure.ac:17: installing 'build-aux/missing'
  Makefile.am: installing 'build-aux/depcomp'
  Makefile.am:207: installing 'build-aux/py-compile'
  parallel-tests: installing 'build-aux/test-driver'
  libkmod/docs/gtk-doc.make:33: error: EXTRA_DIST must be set with '=' before 
using '+='
  libkmod/docs/Makefile.am:29:   'libkmod/docs/gtk-doc.make' included from here
  autoreconf: automake failed with exit status: 1
  debian/rules:60: recipe for target 'configure' failed
  make: *** [configure] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1623073/+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 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Martin Pitt
2784  readlinkat(AT_FDCWD, "/sys/devices/virtual/net", 0x40136358, 99) = -1 
EINVAL (Invalid argument)
# plus a few more readlinkat()'s failing the same way
2784  writev(2, [{"enp1s0: Could not set route: Inv"..., 45}, {"\n", 1}], 2) = 
46

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file

2016-09-13 Thread ChristianEhrhardt
Quickly clarified - that was running on Xenial + kernel mainline ppa.

That means it is nothing in e.g. udev in userspace.

Barbara will try to test 4.5, 4.6 quickly as well.
Only if also 4.5 mainline is good too she will test 4.4 from mainline as well 
(to check if a diff to the xenial 4.4 is causing the issue).

Then I expect it is up to recreating and bisecting on our side?

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Re

[Touch-packages] [Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Martin Pitt
Just to collect all the info, can you please re-run with

  sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

I assume this is a missing kernel feature (systemd only officially
supports kernels ≤ 2 years old), so we'd need some fallback. Can you
please step through with gdb and figure out which call fails in
particular? I don't immediately see where this comes from --
readlinkat() is only called in some wrapper functions in src/basic/fs-
util.c and copy_tree_at, neither of which are being called by networkd.
So I sugguest to build a debug version with CFLAGS="-g -O0" (from
upstream or the Debian package) and gdb through networkd.

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Simon Fels
Output of

  sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

ubuntu@nirvana:~$   sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd
sudo: unable to resolve host nirvana: Connection refused
Failed to connect to bus, trying again in 5s: No such file or directory
timestamp of '/etc/systemd/network' changed
p2p0: Flags change: +MULTICAST +BROADCAST
p2p0: Link 7 added
p2p0: udev initialized link
p2p0: Saved original MTU: 1500
sit0: MAC address not found for new device, continuing without
sit0: Flags change: +NOARP
sit0: Link 6 added
sit0: udev initialized link
sit0: Saved original MTU: 1480
wlan0: Flags change: +MULTICAST +BROADCAST
wlan0: Link 5 added
wlan0: udev initialized link
wlan0: Saved original MTU: 1500
enx00606e43a573: Flags change: +MULTICAST +BROADCAST
enx00606e43a573: Link 4 added
enx00606e43a573: udev initialized link
enx00606e43a573: Saved original MTU: 1500
enp1s0: Flags change: +MULTICAST +BROADCAST
enp1s0: Link 3 added
enp1s0: udev initialized link
enp1s0: Saved original MTU: 1500
dummy0: Flags change: +BROADCAST +NOARP
dummy0: Link 2 added
dummy0: udev initialized link
dummy0: Saved original MTU: 1500
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 16436
lo: Adding address: ::1/128 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
Enumeration completed
p2p0: Link state is up-to-date
p2p0: Unmanaged
sit0: Link state is up-to-date
sit0: Unmanaged
wlan0: Link state is up-to-date
wlan0: Unmanaged
enx00606e43a573: Link state is up-to-date
enx00606e43a573: Unmanaged
enp1s0: Link state is up-to-date
enp1s0: found matching network '/etc/systemd/network/enp1s0.network'
enp1s0: Bringing link up
enp1s0: Setting addresses
dummy0: Link state is up-to-date
dummy0: Unmanaged
lo: Link state is up-to-date
lo: Unmanaged
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Updating address: 192.168.178.30/24 (valid forever)
enp1s0: Addresses set
enp1s0: Setting routes
enp1s0: Could not set route: Invalid argument
enp1s0: Routes set

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1623085] [NEW] source package build is failing

2016-09-13 Thread Max
Public bug reported:

Trying to build the source package using sbuild is failing with the
following error.

+--+
| Install mountall build dependencies (apt-based resolver) |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-mountall-dummy : Depends: plymouth-dev (>= 0.8.5.1) but 
it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed

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

** Attachment added: "buildlog"
   https://bugs.launchpad.net/bugs/1623085/+attachment/4740114/+files/buildlog

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

Title:
  source package build is failing

Status in mountall package in Ubuntu:
  New

Bug description:
  Trying to build the source package using sbuild is failing with the
  following error.

  
+--+
  | Install mountall build dependencies (apt-based resolver)
 |
  
+--+

  Installing build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   sbuild-build-depends-mountall-dummy : Depends: plymouth-dev (>= 0.8.5.1) but 
it is not installable
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
  Package installation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1623085/+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 1622897] Re: Can't create LXC container

2016-09-13 Thread Stéphane Graber
Since you're using LXC on Debian and not on Ubuntu, can you file a bug
at https://github.com/lxc/lxc instead?

** 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/1622897

Title:
  Can't create LXC container

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Hi everyone! I'm start to use LXC version 1.1.5 on Debian Jessie.
  Sometimes when I create a container I recieve an error:

  lxc-create -n test -t vps --bdev=lvm --lvname=test --vgname=vg
  --fstype=xfs --fssize=8G -- --release=jessie --clean

  File descriptor 3 (/var/lib/lxc/test/partial) leaked on lvcreate invocation. 
Parent PID 1089: lxc-create
Logical volume "test" created
  lxc-create: bdev/lxclvm.c: lvm_create: 411 Error creating filesystem type xfs 
on /dev/vg/test
  lxc-create: lxccontainer.c: do_bdev_create: 1035 Failed to create backing 
store type lvm
  lxc-create: lxccontainer.c: do_lxcapi_create: 1511 Error creating backing 
store type lvm for test
  lxc-create: tools/lxc_create.c: main: 318 Error creating container test 

  Recently I'm upgrade LXC to 2.0.4, but the error remains.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1622897/+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 1623068] [NEW] Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Simon Fels
Public bug reported:

Knowing that a 3.4 based kernel is unsupported we have to get it working
for a specific customer.

Systemd itself boots up nicely already but networkd fails to configure a
network device with the following configuration file in
/etc/systemd/network

$ cat /etc/systemd/network/enp1s0.network 
[Match]
Name=enp1s0

[Network]
DNS=8.8.8.8
Address=192.168.178.30
Gateway=192.168.178.1

This gives the following error messages

$ sudo /lib/systemd/systemd-networkd
Enumeration completed
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Could not set route: Invalid argument

ifupdown or NetworkManager is reliable able to get the same interface up
and configured.

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

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Simon Fels
** Attachment added: "systemd-networkd-on-3.4.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+attachment/4740099/+files/systemd-networkd-on-3.4.log

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel

2016-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Networkd fails to configure a ethernet network device on a 3.4 kernel

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Knowing that a 3.4 based kernel is unsupported we have to get it
  working for a specific customer.

  Systemd itself boots up nicely already but networkd fails to configure
  a network device with the following configuration file in
  /etc/systemd/network

  $ cat /etc/systemd/network/enp1s0.network 
  [Match]
  Name=enp1s0

  [Network]
  DNS=8.8.8.8
  Address=192.168.178.30
  Gateway=192.168.178.1

  This gives the following error messages

  $ sudo /lib/systemd/systemd-networkd
  Enumeration completed
  enp1s0: Could not bring up interface: Invalid argument
  enp1s0: Could not set route: Invalid argument

  ifupdown or NetworkManager is reliable able to get the same interface
  up and configured.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Andreas Pokorny
** Bug watch added: GNOME Bug Tracker #768138
   https://bugzilla.gnome.org/show_bug.cgi?id=768138

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=768138
   Importance: Unknown
   Status: Unknown

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1614045] Re: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton

2016-09-13 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/triggerComboButtonCorrectly

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

Title:
  tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The cases for ComboButton in tst_focus.13.qml listed in
  test_trigger_via_keyboard_data use "button" as the item, which means
  they're not actually testing a ComboButton. Also the comboButton has
  no override mechanism in the test so it wouldn't be testable as-is.
  This needs to be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+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 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility

2016-09-13 Thread Simon Déziel
Xenial debdiff with the proper version number, thanks stgraber.

** Patch removed: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4736972/+files/lp1531622-xenial.debdiff

** Patch added: "lp1531622-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+attachment/4740141/+files/lp1531622-xenial.debdiff

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

    $KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

   Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]

  Error  is described as "legacy parameter no longer permitted".

  This legacy parameter causes config syntax checks (rsyslogd -N1) to
  fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1531622/+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 1623046] Re: text doesn't fit the button field in low battery notification(spanish)

2016-09-13 Thread Matthew Paul Thomas
** Package changed: indicator-power (Ubuntu) => ubuntu-ui-toolkit
(Ubuntu)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

** Description changed:

  Enviroment:
  
  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid
  
  Preconditions:  > 15% battery life
  
  Steps to reproduce:
  
  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)
  
  Current result: Left button of low battery notification is bigger than
  button field
  
  Expected result: Text should be inside the button field
  
  Add info: not sure if it happens also in krillin as mine is fully
  charged right now
+ 
+ <http://goo.gl/pNkFp1> (Canonical-only link): “In the unlikely event
+ that a button’s label is too long for its maximum possible width, it
+ should be ellipsized in the middle, and a warning should be logged for
+ the developer’s attention.”

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

Title:
  text doesn't fit the button field in low battery notification(spanish)

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  Enviroment:

  current build number: 187
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-09-13 10:09:37
  version version: 187
  version ubuntu: 20160913
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  Preconditions:  > 15% battery life

  Steps to reproduce:

  1º When battery < 15% you can trigger low battery notification by plug/unplug 
charger
  2º When in Spanish language, check the left button doesn't fit the 
screen(battery settings)

  Current result: Left button of low battery notification is bigger than
  button field

  Expected result: Text should be inside the button field

  Add info: not sure if it happens also in krillin as mine is fully
  charged right now

  <http://goo.gl/pNkFp1> (Canonical-only link): “In the unlikely event
  that a button’s label is too long for its maximum possible width, it
  should be ellipsized in the middle, and a warning should be logged for
  the developer’s attention.”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1623046/+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 1580981] Re: PKGCONFIG not working in SDK

2016-09-13 Thread Benjamin Zeller
** Changed in: ubuntu-sdk-ide
   Status: New => 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/1580981

Title:
  PKGCONFIG not working in SDK

Status in Client Developer Experience:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Ubuntu SDK IDE:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  having this in a qmake .pro file:

  CONFIG += link_pkgconfig
  PKGCONFIG += url-dispatcher-1 qmenumodel

  works fine for native building, but fails for crossbuilding for armhf.

  https://codereview.qt-project.org/#/c/143276/2//ALL,unified

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1580981/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Fix Released

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1614045] Re: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton

2016-09-13 Thread Christian Dywan
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

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

Title:
  tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The cases for ComboButton in tst_focus.13.qml listed in
  test_trigger_via_keyboard_data use "button" as the item, which means
  they're not actually testing a ComboButton. Also the comboButton has
  no override mechanism in the test so it wouldn't be testable as-is.
  This needs to be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+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 1620991] Re: Anchoring warnings in Buttons page in UITK Gallery

2016-09-13 Thread Christian Dywan
=== modified file 'src/imports/Components/1.3/ComboButton.qml'
--- src/imports/Components/1.3/ComboButton.qml  2016-09-13 15:01:14 +
+++ src/imports/Components/1.3/ComboButton.qml  2016-09-13 15:57:46 +
@@ -395,6 +395,7 @@
 }
 }
 Scrollbar {
+parent: comboHolder.parent
 flickableItem: comboHolder
 }

This appears to work. However no test seems to catch this problem - we
need to find a way to test that this is actually fixed.

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

Title:
  Anchoring warnings in Buttons page in UITK Gallery

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-ui-toolkit/staging, r2090

  1) Build uitk
  2) run gallery with ./gallery.sh
  3) Open Buttons page

  Expected outcome: 
  no warnings

  Actual outcome:
  A few "QML Scrollbar: Cannot anchor to an item that isn't a parent or 
sibling."

  Explanation:
  That happens because Scrollbar anchors to the flickable item, but the 
ComboButton code has a hack that changes the parent of the Flickable to 
actually be Flickable's child. As a consequence  Flickable is not a sibling of 
the scrollbar anymore, thus producing the anchor-related warning.

  See http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
  toolkit/staging/annotate/2090/src/Ubuntu/Components/1.3/ComboButton.qml#L354

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1620991/+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 1616448] Re: [MIR] qtsensors-opensource-src

2016-09-13 Thread Sebastien Bacher
the source was in main until 15.10 so just need to be repromoted

** Changed in: qtsensors-opensource-src (Ubuntu)
   Importance: Undecided => Low

** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  [MIR] qtsensors-opensource-src

Status in qtsensors-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Availability: In universe, builds for all archs.

  Rationale: A goal for Ubuntu 16.10 is to have unity8 installed by
  default as an optional session. qtsensors is part of the stack that is
  needed for this goal. Qtsensors was already in main earlier when
  qtwebkit was, bug #1192567.

  Security: No known security history. No daemons or services.

  Quality assurance: No bugs open in Debian. A bug about certain tests
  failing on builders is in Ubuntu (those tests only work in local
  installations and are disabled with a patch). The latest upstream
  stable LTS version is part of yakkety and upcoming Debian release. For
  yakkety, we will not upgrade to Qt 5.7 but stay with the 5.6 LTS.

  Dependencies: All binary dependencies are in main.

  Standard compliance: Packaging seems compliant with 1 lintian warning.

  Maintenance: Qt Company maintains qtsensors as an official module in
  Qt. Qt 5.6 will be supported for bug and security fixes for three
  years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsensors-opensource-src/+bug/1616448/+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 1588524] Re: FIPS_mode_set reports incorrect error message

2016-09-13 Thread Joy Latten
I tested this on 1.0.2g-1ubuntu4.3 using the openssl_fips_test.c that
was attached. And all worked as expected and I received the expected
error message. Thus verifying this issue has been resolved in 1.0.2g-
1ubuntu4.3,

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

Title:
  FIPS_mode_set reports incorrect error message

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Hi! Some integration tests we run attempt to enable FIPS mode in
  OpenSSL, and assert that either our software continues to work, or
  that the error message emitted by OpenSSL is related to missing the
  FIPS module.

  On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
  140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

  On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
  FIPS_mode_set fails, but does not produce an error message.

  I have attached a C file which, when executed on both these platforms,
  will demonstrate this behavior.

  I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
  It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
  +@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
  + fips_selftest_fail = 0;
  + ret = 1;
  +  end:
  ++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
  + fips_clear_owning_thread();
  + fips_w_unlock();
  + return ret;

  This appears to be clearing the error messages we're asserting on
  before returning from FIPS_module_mode_set.

  For reference, here is our ticket where we are tracking this issue:
  https://jira.mongodb.org/browse/SERVER-24350

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1588524/+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 1367551] Re: [MIR] capnproto

2016-09-13 Thread Sebastien Bacher
** Changed in: capnproto (Ubuntu)
   Status: Incomplete => New

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

Title:
  [MIR] capnproto

Status in capnproto package in Ubuntu:
  New

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1367551/+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 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2016-09-13 Thread Jamie Strandboge
/etc/ld.so.preload should be a site-specific file (ie, it shouldn't come
from Ubuntu). I wouldn't want to break people by adding an explicit
deny, but I'd prefer users encountering this to update their
/etc/apparmor.d/local/usr.sbin.cupsd file to have:

/etc/ld.so.preload r,

Or if people just want to silence it and not allow it:

deny /etc/ld.so.preload r,

Then run: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd
(note, that the file to apparmor_parser is not the one that was modified)

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in cups package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  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:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

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

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

[Touch-packages] [Bug 1612270] Re: [MIR] qdjango

2016-09-13 Thread Sebastien Bacher
should it be assigned to security team then?

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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

  [Standards compliance]
   * This package uses qmake and does not require translations.

  [Maintenance]
   * This package is maintained by Jeremy Laine, upstream in Debian and 
actively in use on the phone images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qdjango/+bug/1612270/+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 1594748] Re: CRYPTO_set_mem_functions() is broken

2016-09-13 Thread Joy Latten
I tested version 1.0.2g-1ubuntu4.3 with the death.c program from the
upstream openssl bug ticket 4559 and confirmed this problem is now
resolved.

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

Title:
  CRYPTO_set_mem_functions() is broken

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
   *** 1.0.2g-1ubuntu4.1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization already calls CRYPTO_malloc() and disables it:

  #0  CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c 
"fips_drbg_lib.c",
  line=line@entry=106) at mem.c:329
  #1  0x770596df in FIPS_drbg_new (type=type@entry=0, 
flags=flags@entry=0)
  at fips_drbg_lib.c:106
  #2  0x7705aeb9 in FIPS_drbg_health_check (
  dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
  #3  0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960 
,
  type=, flags=) at fips_drbg_lib.c:94
  #4  0x76fe38f3 in RAND_init_fips () at rand_lib.c:287
  #5  0x76f26f7a in OPENSSL_init_library () at o_init.c:119
  #6  0x77de74ea in call_init (l=, argc=argc@entry=1,
  argv=argv@entry=0x7fffe5e8, env=env@entry=0x7fffe5f8) at 
dl-init.c:72
  #7  0x77de75fb in call_init (env=0x7fffe5f8, argv=0x7fffe5e8, 
argc=1,
  l=) at dl-init.c:30
  #8  _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffe5e8,
  env=0x7fffe5f8) at dl-init.c:120

  This doesn't happen in upstream OpenSSL or in Debian's OpenSSL.
  Looking at the patches, this is caused by FIPS_drbg_init() in
  openssl-1.0.2g-fips.patch:

  +if (!(dctx->xflags & DRBG_FLAG_TEST)) {
  +if (!FIPS_drbg_health_check(dctx)) {
  +FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE);
  +return 0;
  +}
  +}

  I don't want any FIPS mode enabled though, so does it really even need
  to call RAND_init_fips() then?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1594748/+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 1617335] Re: notifications not making their way to unity8 from libertine

2016-09-13 Thread Christopher Townsend
After further investigation, notifications to make it from apps in a
Libertine container to U8.  The problematic case is using notify-send
from within the container.

The way NotificationServer tries to figure out if notify-send is being
used is not compatible with using it in a container.  NotificationServer
uses a function called isCmdLine() which checks if a pid's path is the
notify-send path, but this does not work in an LXC due to namespacing.
It would probably be better to check if the notifications app_name is
"notify-send" instead.

I will probably open a new bug against unity-notifications to see about
changing the behavior for isCmdLine().  In the meantime, I'm closing
this bug Invalid.

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

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

** Changed in: canonical-devices-system-image
   Status: New => Invalid

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

Title:
  notifications not making their way to unity8 from libertine

Status in Canonical System Image:
  Invalid
Status in libertine package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Not completely sure where this bug lies.
  This was an area of "this should just work" in theory.
  We did perform some investigation using notification but it's not clear if 
the msg is somehow getting lost on in dbus or if unity8 is somehow 
rejecting/ignoring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617335/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-13 Thread Scott Garman
Just to chime in as well, I've been using the PA packages that Joakim
rebuilt without that patch set, and as an end-user it's totally resolved
this bug on my laptop and desktop. If we can't move forward with The
Right Way (TM) to fix this, perhaps someone could create a PPA with
these packages in the meantime?

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1614210] Re: Remove incomplete fips in openssl in xenial.

2016-09-13 Thread Marc Deslauriers
** 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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1614210

Title:
  Remove incomplete fips in openssl in xenial.

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed
Status in openssl source package in Yakkety:
  Fix Released

Bug description:
  Package: openssl-1.0.2g-1ubuntu4.1
  Distro: xenial

  The openssl contains incomplete fips patches. In light that the fips
  is incomplete and will not be completed in the main archive and they
  are impacting customers, they should be withdrawn. See lp bugs
  1593953, 1591797, 1594748, 1588524, 1613658. Removal of these fips
  patches will remove these fips-related issues.

  [Test case]
  1. Problem in 1594748
  Note: this problem was reported in upstream openssl and testcase posted there 
also.
  https://rt.openssl.org/Ticket/Display.html?id=4559

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization within fips code already calls CRYPTO_malloc() and
  disables it.

  This testcase should cause openssl to abort, but instead it returns a
  context.

  #include 
  #include 
  #include 
  void * my_alloc(size_t n) { abort(); }
  void my_free(void *p) { abort(); }
  void * my_realloc(void *p, size_t n) { abort(); }
  int main(int argc, const char **argv)
  {
    const SSL_METHOD *method;
    SSL_CTX *ctx;
    CRYPTO_set_mem_functions(my_alloc, my_realloc, my_free);
    SSL_library_init();
    method = SSLv23_client_method();
    ctx = SSL_CTX_new(method);
    printf("Got ctx %p\n", ctx);
    return 0;
  }

  2. Problem in 1593953
  EC key generation allows user to generate keys using EC curves that the EC 
sign and verify
  do not support when OPENSSL_FIPS is defined.
  Testcase taken from lp #1593953

  openssl ecparam -genkey -name Oakley-EC2N-4

  will fail when OPENSSL_FIPS is defined since it causes a fips key-pair 
consistency check to be done.
  Otherwise, without OPENSSL_FIPS defined, the check is not done.

  3. Problem reported in 1588524
  Error code being skipped...

  Testcase taken from lp #1588524

  #include 
  #include 

  int main() {
  int rc;
  unsigned long fips_err;
  SSL_library_init();
  SSL_load_error_strings();
  ERR_load_crypto_strings();
  OpenSSL_add_all_algorithms();
  rc = FIPS_mode_set(1);
  fips_err = ERR_peek_last_error();

  // FIPS_mode_set will return 0 on failure, which is expected if
  // the FIPS module is not compiled. In this case, we should then
  // be able to get the error code
  // CRYPTO_R_FIPS_MODE_NOT_SUPPORTED (0xf06d065)
  // https://wiki.openssl.org/index.php/FIPS_mode_set%28%29
  printf("%d %lu\n", rc, fips_err);
  ERR_print_errors_fp(stdout);

  ERR_free_strings();
  return 0;
  }

  Should report an error message.

  [ Regression potential ]
  Removing the fips patches should decrease regression potential of openssl in 
the main archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1614210/+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 1588524] Re: FIPS_mode_set reports incorrect error message

2016-09-13 Thread Marc Deslauriers
** 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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1588524

Title:
  FIPS_mode_set reports incorrect error message

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Hi! Some integration tests we run attempt to enable FIPS mode in
  OpenSSL, and assert that either our software continues to work, or
  that the error message emitted by OpenSSL is related to missing the
  FIPS module.

  On Ubuntu 14.10, running FIPS_mode_set fails and produces an error like:
  140225357260448:error:0F06D065:common libcrypto routines:FIPS_mode_set:fips 
mode not supported:o_fips.c:92:

  On Ubuntu 16.04 running OpenSSL/libssl1.0.0 version 1.0.2g-1ubuntu4.1,
  FIPS_mode_set fails, but does not produce an error message.

  I have attached a C file which, when executed on both these platforms,
  will demonstrate this behavior.

  I believe this may have been introduced by this ticket: 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553309
  It provides a patch called openssl-1.0.2g-ubuntu-fips-cleanup.patch which 
includes this statement:
  +@@ -443,6 +430,7 @@ int FIPS_module_mode_set(int onoff, const char *auth)
  + fips_selftest_fail = 0;
  + ret = 1;
  +  end:
  ++ERR_clear_error(); /* clear above err msg; fips mode disabled for now */
  + fips_clear_owning_thread();
  + fips_w_unlock();
  + return ret;

  This appears to be clearing the error messages we're asserting on
  before returning from FIPS_module_mode_set.

  For reference, here is our ticket where we are tracking this issue:
  https://jira.mongodb.org/browse/SERVER-24350

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1588524/+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 1594748] Re: CRYPTO_set_mem_functions() is broken

2016-09-13 Thread Marc Deslauriers
** 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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1594748

Title:
  CRYPTO_set_mem_functions() is broken

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Fix Committed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
   *** 1.0.2g-1ubuntu4.1 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  CRYPTO_set_mem_functions() always returns 0 because library
  initialization already calls CRYPTO_malloc() and disables it:

  #0  CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c 
"fips_drbg_lib.c",
  line=line@entry=106) at mem.c:329
  #1  0x770596df in FIPS_drbg_new (type=type@entry=0, 
flags=flags@entry=0)
  at fips_drbg_lib.c:106
  #2  0x7705aeb9 in FIPS_drbg_health_check (
  dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
  #3  0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960 
,
  type=, flags=) at fips_drbg_lib.c:94
  #4  0x76fe38f3 in RAND_init_fips () at rand_lib.c:287
  #5  0x76f26f7a in OPENSSL_init_library () at o_init.c:119
  #6  0x77de74ea in call_init (l=, argc=argc@entry=1,
  argv=argv@entry=0x7fffe5e8, env=env@entry=0x7fffe5f8) at 
dl-init.c:72
  #7  0x77de75fb in call_init (env=0x7fffe5f8, argv=0x7fffe5e8, 
argc=1,
  l=) at dl-init.c:30
  #8  _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffe5e8,
  env=0x7fffe5f8) at dl-init.c:120

  This doesn't happen in upstream OpenSSL or in Debian's OpenSSL.
  Looking at the patches, this is caused by FIPS_drbg_init() in
  openssl-1.0.2g-fips.patch:

  +if (!(dctx->xflags & DRBG_FLAG_TEST)) {
  +if (!FIPS_drbg_health_check(dctx)) {
  +FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE);
  +return 0;
  +}
  +}

  I don't want any FIPS mode enabled though, so does it really even need
  to call RAND_init_fips() then?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1594748/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-13 Thread Joakim Koed
Scott: Good idea. I will look into that this weekend and see if I can
figure it out :)

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1606078] Re: No sound with Ubuntu 16.04

2016-09-13 Thread Johnny
After installing a new hard drive, I installed Ubuntu 16.04 on my Sony
VPCL116FX and after experiencing difficulty with audio, attempted the
above fix, but to no avail.

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

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+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 1168742] Re: [udev] Disks are not unmounted when physical eject button is used

2016-09-13 Thread Peter Bennett
The above workaround prevent loading of Video CD's. With that workaround
in place, the system immediately ejects any Video CD inserted, and
prevents it being mounted.

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

Title:
  [udev] Disks are not unmounted when physical eject button is used

Status in systemd:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the
  hardware button on the drive. After ejecting disks via the hardware
  button, an entry for the disk still shows up in the file manager, and
  shows when I run df. If I do a soft eject (ie from the right click
  menu from the icon on the launcher), however, everything works
  properly.

  Just as a note, as per
  https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I
  attempted to report this using ubuntu-bug storage, however there is
  not an option dealing with unmounting devices, and clicking other
  tells you that you should run ubuntu-bug again with a specific package
  name. In an attempt to get this to a semi-relevant audience, I ended
  up just saying that a disk wasn't auto-mounted, clicking through the
  next few popups, and ended up here. If this isn't the right place to
  report this bug, I apologize.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-17-generic 3.8.0-17.27
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1590 F pulseaudio
   /dev/snd/controlC0:  chris  1590 F pulseaudio
  Date: Sat Apr 13 12:54:33 2013
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2013-03-26 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.105
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   12:54:42.343: The udisks-daemon is running (name-owner :1.39).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1168742/+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 1612270] Re: [MIR] qdjango

2016-09-13 Thread Michael Terry
** Changed in: qdjango (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

  [Security]
   * No known security issues at this time.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

  [Standards compliance]
   * This package uses qmake and does not require translations.

  [Maintenance]
   * This package is maintained by Jeremy Laine, upstream in Debian and 
actively in use on the phone images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qdjango/+bug/1612270/+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 1623142] [NEW] notify-send does not work when used in a Libertine container

2016-09-13 Thread Christopher Townsend
Public bug reported:

When using notify-send from within a Libertine container, the
notification immediately gets canceled.  This is due to
NotificationServer::isCmdLine() not being able to detect notify-send
running in an LXC container due to the LXC having a separate process
namespace.

** Affects: unity-notifications
 Importance: Low
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: unity-notifications (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unity-notifications (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-notifications
   Importance: Undecided => Low

** Changed in: unity-notifications
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: unity-notifications
   Status: New => In Progress

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

Title:
  notify-send does not work when used in a Libertine container

Status in unity-notifications:
  In Progress
Status in unity-notifications package in Ubuntu:
  New

Bug description:
  When using notify-send from within a Libertine container, the
  notification immediately gets canceled.  This is due to
  NotificationServer::isCmdLine() not being able to detect notify-send
  running in an LXC container due to the LXC having a separate process
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1623142/+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 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

2016-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  Hi, vim-gtk3 crashes so often on my system that it's borderline unusable.
  My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my 
customized ~/.vimrc and ~/.vim. My system is up-to-date as of today 
(2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1.

  The crash happens only (but very frequently, not always) when I launch
  gvim, either by calling it from a shell or by double-clicking a file
  in Nautilus. Note that the crash is independent of whether I'm opening
  a file or not. (At least I tried both variations from the terminal.)

  There's also a report on vim's bugtracker, but since unity appears in
  the backtrace, the consensus is that it's probably Ubuntu-specific.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: vim-gtk3 2:7.4.1689-3ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  9 14:34:31 2016
  ExecutablePath: /usr/bin/vim.gtk3
  InstallationDate: Installed on 2016-07-10 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: gvim -f 
/home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex
  Signal: 11
  SourcePackage: vim
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64()
  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/vim/+bug/1611363/+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 1597453] Re: [MIR] content-hub

2016-09-13 Thread Ken VanDine
@cyphermox: I don't get that from lintian on xenial, is that new for
yakkety?

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

Title:
  [MIR] content-hub

Status in content-hub package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.  It has been reviewed by security 
in the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * ubuntu-download-manager (bug #1488425)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1597453/+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 1620338] Re: Ubuntu One account page is blank

2016-09-13 Thread Rodney Dawes
** Changed in: ubuntuone-credentials (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntuone-credentials (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntuone-credentials (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

Title:
  Ubuntu One account page is blank

Status in Canonical System Image:
  In Progress
Status in ubuntuone-credentials package in Ubuntu:
  In Progress

Bug description:
  current build number: 31
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu

  The U1 account page is blank with just a title.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620338/+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 1615021] Comment bridged from LTC Bugzilla

2016-09-13 Thread bugproxy
--- Comment From dougm...@us.ibm.com 2016-09-13 14:16 EDT---
This bug was opened because of a hang being experienced while booting the 
Ubuntu 16.04 network installer on Briggs & Stratton machines with their X710 
ethernet adapters, using the i40e driver.

During investigation, and problem/mistake was found with systemd but is
almost-certainly not the cause of the hang. This fixed systemd was
supposedly being made available in xenial-proposed repositories, but so
far does not seem to have appeared there.

This bug was placed in "verify" state and it started causing email to be
sent several times a day reminding me to verify the fix.Since we don't
believe that the "fix to systemd" will fix the hang during the installer
boot, and since this new systemd has not been pushed out to the xenial-
proposed installer after 6 days, I have taken this bug out of "verify"
state by re-opening it.

When there actually is something to be tested, and it has made it's way
into the xenial-proposed installer, then this bug can be set back to
"verify" and I will test the fix.

--- Comment From dougm...@us.ibm.com 2016-09-13 14:18 EDT---
I should also ammend my previous comment by saying, if Canonical has some 
suggestions of how to gather more information in order to help debug this, they 
should let us know and we can make test runs for them.

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable systemd debug; only the files "init" and "start-udev" were
  changed in initrd, both attached here.

  We've attached here a saved screen session that shows the entire boot
  process until it gets flooded with lots of messages like:

  "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'

  seq 3244 queued, 'add' 'pci_bus'
  starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'
  passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 
running'/bin/readlink /etc/udev/rules.d/80-net-setup-l
  ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink 
/etc/udev/rules.d/80-net-setup-link.rules': No such
  file or directory'
  '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to 
execute '/bin/readlink' '/bin/readlink /etc/
  udev/rules.d/80-net-setup-link.rules': No such file or directory'
  Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with 
exit code 2.
  PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' 
/lib/udev/rules.d/73-usb-net-by-mac.rules:6
  passed device to netlink monitor 0x1003d01f730
  "

  Then it keeps hanged in this stage. We re-tested it by changing the
  file 73-usb-net-by-mac.rules in initrd, replacing "
  /etc/udev/rules.d/80-net-setup-link.rules" to  "/lib/udev/rules.d/80
  -net-setup-link.rules", since the former does not exist whereas the
  latter does. Same issue were observed!

  Notice that if we boot the installer with command-line "net.ifnames=0"
  or "net.ifnames=1", the problem does not reproduces anymore.

  We want to ask C

[Touch-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB

2016-09-13 Thread Samuel Henrique
See discussion at:
https://github.com/joewing/jwm/issues/194

** Bug watch added: github.com/joewing/jwm/issues #194
   https://github.com/joewing/jwm/issues/194

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

** Changed in: jwm (Ubuntu)
 Assignee: (unassigned) => Samuel Henrique (samueloph)

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

Title:
  Port from legacy Xlib to modern XCB

Status in Compiz:
  Triaged
Status in 9wm package in Ubuntu:
  New
Status in aewm package in Ubuntu:
  New
Status in aewm++ package in Ubuntu:
  New
Status in afterstep package in Ubuntu:
  New
Status in amiwm package in Ubuntu:
  New
Status in blackbox package in Ubuntu:
  New
Status in cairo package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Triaged
Status in ctwm package in Ubuntu:
  New
Status in dwm package in Ubuntu:
  Opinion
Status in enlightenment package in Ubuntu:
  New
Status in fvwm package in Ubuntu:
  New
Status in fvwm1 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in icewm package in Ubuntu:
  New
Status in jwm package in Ubuntu:
  Invalid
Status in larswm package in Ubuntu:
  New
Status in lwm package in Ubuntu:
  New
Status in matchbox-window-manager package in Ubuntu:
  New
Status in metacity package in Ubuntu:
  Invalid
Status in miwm package in Ubuntu:
  New
Status in muffin package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in pekwm package in Ubuntu:
  New
Status in ratpoison package in Ubuntu:
  New
Status in sapphire package in Ubuntu:
  New
Status in sawfish package in Ubuntu:
  New
Status in spectrwm package in Ubuntu:
  Fix Released
Status in tinywm package in Ubuntu:
  New
Status in tritium package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New
Status in vtwm package in Ubuntu:
  New
Status in w9wm package in Ubuntu:
  New
Status in windowlab package in Ubuntu:
  New
Status in wm2 package in Ubuntu:
  New
Status in wmaker package in Ubuntu:
  New
Status in xmonad package in Ubuntu:
  New

Bug description:
  Port/rewrite the window manager to use the modern XCB (X C Binding)
  library instead of the old legacy Xlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1030022/+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 1623151] [NEW] Screen flickers when using external monitor

2016-09-13 Thread Bryan Abhser
Public bug reported:

Continued from Bug 1572667

Occasionally my external monitor will go black for a second and then
return. Currently I am running the mainline kernel version 4.6.7-040607
and the problem does not appear.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
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: Tue Sep 13 11:25:58 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
InstallationDate: Installed on 2016-08-04 (39 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20BSCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET32W (1.10 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET32W(1.10):bd08/13/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BSCTO1WW
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
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.3-1ubuntu2.3
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: Tue Sep 13 11:24:55 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1049 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  Screen flickers when using external monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Continued from Bug 1572667

  Occasionally my external monitor will go black for a second and then
  return. Currently I am running the mainline kernel version
  4.6.7-040607 and the problem does not appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  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: Tue Sep 13 11:25:58 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2016-08-04 (39 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET32W (1.10 )
  dmi.board.asset.tag: Not Available
  d

[Touch-packages] [Bug 1622888] [NEW] cups server error after dist. upgrade to 16.04

2016-09-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Yes - similar bug, but NO, not the same bug: There was an error during
the CUPS operation: 'failed to connect to server'. Cannot print with my
machine since I ran dist. upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.16
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Tue Sep 13 03:50:48 2016
InstallationDate: Installed on 2013-10-31 (1047 days ago)
InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to xenial on 2016-07-30 (45 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
cups server error after dist. upgrade to 16.04
https://bugs.launchpad.net/bugs/1622888
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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


[Touch-packages] [Bug 1622888] Re: cups server error after dist. upgrade to 16.04

2016-09-13 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) => cups (Ubuntu)

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

Title:
  cups server error after dist. upgrade to 16.04

Status in cups package in Ubuntu:
  New

Bug description:
  Yes - similar bug, but NO, not the same bug: There was an error during
  the CUPS operation: 'failed to connect to server'. Cannot print with
  my machine since I ran dist. upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Sep 13 03:50:48 2016
  InstallationDate: Installed on 2013-10-31 (1047 days ago)
  InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (45 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1622888/+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 1591426] Re: LCD remains off once it is turned off for power saving

2016-09-13 Thread Carlos Eduardo Moreira dos Santos
Same here with Dell Latitude 131L. Restarting lightdm works, but the
session is gone. It didn't happen on 14.*. I tried to purge lightdm and
then installing it again, but now gpu-manager fails and lightdm doesn't
start:

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.4.0-36-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.4.0-36-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? no
Is radeon loaded? yes
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 1002:5975
BusID "PCI:1@0:5:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "radeon"
Found "/dev/dri/card0", driven by "radeon"
output 0:
LVDS connector
Number of connected outputs for /dev/dri/card0: 1
Skipping "/dev/dri/card0", driven by "radeon"
Skipping "/dev/dri/card0", driven by "radeon"
Does it require offloading? no
last cards number = 1
Has amd? yes
Has intel? no
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path i386-linux-gnu, other_arch_path x86_64-linux-gnu
Current alternative: /usr/lib/i386-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/i386-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Kernel Module is not loaded
Nothing to do
No change - nothing to do

lspci output:
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RS482M [Mobility Radeon Xpress 200] (prog-if 00 [VGA 
controller])
Subsystem: Dell RS482M [Mobility Radeon Xpress 200]
Flags: bus master, 66MHz, medium devsel, latency 66, IRQ 17
Memory at c000 (32-bit, prefetchable) [size=256M]
I/O ports at 9000 [size=256]
Memory at b010 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at b012 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
Kernel driver in use: radeon
Kernel modules: radeonfb, radeon

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

Title:
  LCD remains off once it is turned off for power saving

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ¡Hola!

  LCD stays off on Dell Inspiron 1501.

  See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596269

  ¡Gracias!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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 Jun 10 20:58:06 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
 Subsystem: Dell RS482M [Mobility Radeon Xpress 200] [1028:01f5]
  InstallationDate: Installed on 2013-01-01 (1256 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. Inspiron 1501
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b42f093d-7eba-4e2b-9df4-7e0a29917796 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 1501
  dmi.product.version: No

[Touch-packages] [Bug 1623142] Re: notify-send does not work when used in a Libertine container

2016-09-13 Thread Lukáš Tinkl
** Changed in: unity-notifications (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

** Changed in: unity-notifications (Ubuntu)
   Status: New => In Progress

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

Title:
  notify-send does not work when used in a Libertine container

Status in unity-notifications:
  In Progress
Status in unity-notifications package in Ubuntu:
  In Progress

Bug description:
  When using notify-send from within a Libertine container, the
  notification immediately gets canceled.  This is due to
  NotificationServer::isCmdLine() not being able to detect notify-send
  running in an LXC container due to the LXC having a separate process
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1623142/+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 1623142] Re: notify-send does not work when used in a Libertine container

2016-09-13 Thread Christopher Townsend
** Changed in: unity-notifications
 Assignee: Christopher Townsend (townsend) => (unassigned)

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

Title:
  notify-send does not work when used in a Libertine container

Status in unity-notifications:
  In Progress
Status in unity-notifications package in Ubuntu:
  In Progress

Bug description:
  When using notify-send from within a Libertine container, the
  notification immediately gets canceled.  This is due to
  NotificationServer::isCmdLine() not being able to detect notify-send
  running in an LXC container due to the LXC having a separate process
  namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1623142/+subscriptions

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


Re: [Touch-packages] [Bug 1615021] Comment bridged from LTC Bugzilla

2016-09-13 Thread Steve Langasek
On Tue, Sep 13, 2016 at 06:20:49PM -, bugproxy wrote:
> During investigation, and problem/mistake was found with systemd but is
> almost-certainly not the cause of the hang.

Agreed.

> This fixed systemd was supposedly being made available in xenial-proposed
> repositories, but so far does not seem to have appeared there.

The systemd package is present in the xenial-proposed repository, but no
updated installer image has yet been produced that includes it.

We have had sufficient verification of the systemd change that it will be
released to xenial users for the general problem; we will also update the
debian-installer images as a matter of course.

Based on the feedback from gpicc...@br.ibm.com, it does not appear that the
buggy udev rule is blocking progress on this bug.

> This bug was placed in "verify" state and it started causing email to be
> sent several times a day reminding me to verify the fix.

I don't know why this would be.  Our process generates a single message to
the bug when a package is accepted into the -proposed repository, it does
not send daily reminder messages.

> --- Comment From dougm...@us.ibm.com 2016-09-13 14:18 EDT---
> I should also ammend my previous comment by saying, if Canonical has some
> suggestions of how to gather more information in order to help debug this,
> they should let us know and we can make test runs for them.

My previous suggestion to gpiccoli on IRC was to modify the initrd to dump
the state of the udev database at a point after the hang.  I haven't seen
such output attached here; does that mean it's not possible to produce such
results because the kernel hard locks?  Currently the only debugging
information I've seen is that the /lib/debian-installer/start-udev script
never returns, but that does not mean the kernel has locked up - it only
shows that udev believes it has not finished processing.  I would still like
to see a dump of the udev database at the point of the hang, not just a udev
debug log showing processing up to that point.

Is this problem only reproducible with the X710 ethernet adapter?  Is this a
removable ethernet adapter, and have you tested what happens if it's
removed?  If it's not removable, have you tested what happens if you
blacklist the i40e driver?  The ethernet driver may be a complete red
herring, and the problem may be with something that normally happens after
ethernet driver initialization rather than with the ethernet driver itself.

I would also have asked whether this could be an issue with the console
output being redirected to some different device, but since Guilherme
indicated that the problem appeared to be racy, with boot to the installer
sometimes succeeding, that seems unlikely to be the problem.

If you can reproduce this problem with the cloud image from
,
that would present additional debugging opportunities since that uses a
standard Ubuntu initramfs instead of the installer initramfs and will
support various 'break=' options to interrupt the boot and introspect the
system state.

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

Title:
  Unable to network boot Ubuntu 16.04 installer normally on Briggs

Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in busybox source package in Xenial:
  Won't Fix
Status in debian-installer source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in busybox source package in Yakkety:
  Fix Released
Status in debian-installer source package in Yakkety:
  Triaged
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #7 - Guilherme Guaglianoni Piccoli  - 
2016-08-19 10:08:07 ==
  The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to 
download the latest vmlinux and initrd.gz files available, and kexec them with 
no parameters (at least in ppc64el).

  We're experiencing a strange issue in which the installer freezes
  before menus are showed. The system hangs in the point specified
  below, right after the i40e driver initialization:

  [   11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0
  [   11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1
  [   11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2
  [   11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3
  ***HANG***

  The most difficult part in this issue is that it seems to be a timing
  issue/race condition, and many debug trials end up by avoiding the
  issue reproduction (heisenbug).

  We were successful though in getting logs by booting the kernel with
  the command-line "BOOT_DEBUG=2" and by changing the initrd in order to
  enable 

[Touch-packages] [Bug 1623172] [NEW] [Asus ZenBook UX501VW] Function keys to change keyboard brightness don't work

2016-09-13 Thread David DIDIER
Public bug reported:

On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7,
4.7.3 nor 4.8-rc6.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.8.0-040800rc6-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Sep 13 21:44:06 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2016-06-01 (104 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
 Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N501VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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: Tue Sep 13 21:14:29 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 [drm] Failed to open DRM device for (null): -22
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12876 
 vendor SDC
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  [Asus ZenBook UX501VW] Function keys to change keyboard brightness
  don't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvi

[Touch-packages] [Bug 1623175] [NEW] package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured bec

2016-09-13 Thread Janne Granström
Public bug reported:

i just get error message to my desktop and i really dont know why or
what application sends it :/

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 13 08:16:32 2016
DuplicateSignature:
 package:libgssapi3-heimdal:amd64:1.7~git20160703+dfsg-1
 Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
 dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
  package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
ErrorMessage: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be 
configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-08-23 (21 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3~rc4ubuntu1
SourcePackage: heimdal
Title: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

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


** Tags: amd64 apport-package package-from-proposed yakkety

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

Title:
  package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libgssapi3-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libgssapi3-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  i just get error message to my desktop and i really dont know why or
  what application sends it :/

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 13 08:16:32 2016
  DuplicateSignature:
   package:libgssapi3-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-08-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: heimdal
  Title: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1623175/+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 1623173] [NEW] [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

2016-09-13 Thread David DIDIER
Public bug reported:

On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7,
4.7.3 nor 4.8-rc6.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.8.0-040800rc6-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Sep 13 21:49:46 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2016-06-01 (104 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
 Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N501VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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: Tue Sep 13 21:14:29 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 [drm] Failed to open DRM device for (null): -22
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12876 
 vendor SDC
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.regist

[Touch-packages] [Bug 1623174] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured b

2016-09-13 Thread Janne Granström
Public bug reported:

i just get error message to my desktop and i really dont know why or
what application sends it :/

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 13 08:16:32 2016
DuplicateSignature:
 package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
 Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
 dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
  package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-08-23 (21 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3~rc4ubuntu1
SourcePackage: heimdal
Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

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


** Tags: amd64 apport-package package-from-proposed yakkety

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libhcrypto4-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  i just get error message to my desktop and i really dont know why or
  what application sends it :/

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 13 08:16:32 2016
  DuplicateSignature:
   package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-08-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1623174/+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 1623175] Re: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured becau

2016-09-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libgssapi3-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libgssapi3-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  i just get error message to my desktop and i really dont know why or
  what application sends it :/

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 13 08:16:32 2016
  DuplicateSignature:
   package:libgssapi3-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-08-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: heimdal
  Title: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libgssapi3-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libgssapi3-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1623175/+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 1623174] Re: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured bec

2016-09-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: package libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 cannot be configured because
  libhcrypto4-heimdal:i386 is at a different version (1.7~git20150920
  +dfsg-4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  i just get error message to my desktop and i really dont know why or
  what application sends it :/

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 13 08:16:32 2016
  DuplicateSignature:
   package:libhcrypto4-heimdal:amd64:1.7~git20160703+dfsg-1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
   dpkg: error processing package libasn1-8-heimdal:amd64 (--configure):
package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured 
because libasn1-8-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  ErrorMessage: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 cannot 
be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-08-23 (21 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 
cannot be configured because libhcrypto4-heimdal:i386 is at a different version 
(1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: Upgraded to yakkety on 2016-09-13 (0 days ago)

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


  1   2   >