date:20170113

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  just updating ubuntu mate, then this erroe occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  Uname: Linux 3.4.108 armv7l
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: armhf
  Date: Fri Apr 29 17:14:59 2016
  DuplicateSignature: package:initramfs-tools:0.122ubuntu8:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago)
  mtime.conffile..etc.initramfs.tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1576762/+subscriptions

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

[Touch-packages] [Bug 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

2017-01-13 Thread Mauricio Maluff Masi

The label is pretty faded, so I'm not positive on this. But I think
it's:

Make: DisplayLink
Model: E364109

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

Title:
  Mouse flickers and disappears on primary monitor when additional
  monitor is connected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Any time I connect my Acer G236HL LCD monitor with VGA via my
  Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
  flickers and disappears in the primary monitor. It displays perfectly
  on the additional monitor. It also displays perfectly after the
  additional monitor is disconnected.

  I see that there are a number of similar bug reports:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu8.2
  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: Tue Jan 10 22:34:58 2017
  DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
   File:  does not exist.

   bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2016-01-26 (350 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash 
usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
  XorgLogOld:

  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Jan 10 20:18:19 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.4-1ubuntu6.1

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

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

[Touch-packages] [Bug 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic

2017-01-13 Thread yeib

I just did the same as John Russel, edited /etc/lsb-release to 16.10,
and now it works again.

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

Title:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/utopic

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  lsb_release -rd
  Description:Ubuntu Utopic Unicorn (development branch)
  Release:14.10

  
  apt-cache policy software-properties-gtk 
  software-properties-gtk:
Installed: 0.92.37
Candidate: 0.92.37
Version table:
   *** 0.92.37 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.92.36 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: software-properties-gtk 0.92.37
  Uname: Linux 3.14.0-999-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Fri Apr 25 19:27:37 2014
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2012-09-30 (572 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.1)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 
--toplevel 62914567
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', 
'--toplevel', '62914567']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with 
aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not 
find a distribution template for Ubuntu/utopic
  UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312673/+subscriptions

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

[Touch-packages] [Bug 1565080] Re: ubuntuBSD support

This bug was fixed in the package mesa - 13.0.3-1ubuntu2

---
mesa (13.0.3-1ubuntu2) zesty; urgency=medium

  * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already.
(LP: #1605796)
  * control: Fix dependencies for ubuntuBSD. (LP: #1565080)
  * compat,rules: Don't bump compat to 10, breaks applying patches
before autoreconf which we need for the Mir EGL platform.

 -- Timo Aaltonen   Thu, 12 Jan 2017 09:49:20 +0200

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

Title:
  ubuntuBSD support

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Hi

  Please could you apply attached patch to make mesa buildable on
  ubuntuBSD? It just needs to adjust a few dependencies.

  Thanks!

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

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

[Touch-packages] [Bug 1605796] Re: mesa FTBFS on ppc64el with -O3 due to ICE

This bug was fixed in the package mesa - 13.0.3-1ubuntu2

---
mesa (13.0.3-1ubuntu2) zesty; urgency=medium

  * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already.
(LP: #1605796)
  * control: Fix dependencies for ubuntuBSD. (LP: #1565080)
  * compat,rules: Don't bump compat to 10, breaks applying patches
before autoreconf which we need for the Mir EGL platform.

 -- Timo Aaltonen   Thu, 12 Jan 2017 09:49:20 +0200

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

Title:
  mesa FTBFS on ppc64el with -O3 due to ICE

Status in gcc-6 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Dropping optimization to -O2 allows this build to succeed:

  https://launchpad.net/ubuntu/+source/mesa/12.0.1-3ubuntu1/+build/10484583

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1605796/+subscriptions

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

[Touch-packages] [Bug 1655556] Re: intel: add support for 16k wide textures

This bug was fixed in the package mesa - 13.0.3-1ubuntu2

---
mesa (13.0.3-1ubuntu2) zesty; urgency=medium

  * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already.
(LP: #1605796)
  * control: Fix dependencies for ubuntuBSD. (LP: #1565080)
  * compat,rules: Don't bump compat to 10, breaks applying patches
before autoreconf which we need for the Mir EGL platform.

 -- Timo Aaltonen   Thu, 12 Jan 2017 09:49:20 +0200

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

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

Title:
  intel: add support for 16k wide textures

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 13 doesn't support 16k wide textures, needs backports from git.
  This is needed to support a horizontal monitor array of 3x4k in unity.

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-01-13 Thread Matt Wear

I have a similar problem with a super micro X10DRH system board.  If I have the 
intel sata controller set to ACHI and install a fresh instance of 16.04 the 
server works without issue.  If I have the intel sata controller in RSTe RAID 
mode with a 2 drive RAID1 configuration the server will hang on reboot at the 
'Reached target shutdown" message.  Are there any logs that I can provide to 
assist in troubleshooting?
Thanks,
-Matt

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

2017-01-13 Thread Timo Aaltonen

preliminary build for xenial:

http://koti.kapsi.fi/~tjaalton/lp1607666

included this patch too:
https://www.sudo.ws/repos/sudo/rev/50d8d88bcc28

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Xenial:
  Confirmed
Status in sudo source package in Yakkety:
  New

Bug description:
  Sudo currently fails to validate netgroups against host netgroups
  returned from the sss plugin, see
  https://fedorahosted.org/freeipa/ticket/6139 for the glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

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

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

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

2017-01-13 Thread Timo Aaltonen

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

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Xenial:
  Confirmed
Status in sudo source package in Yakkety:
  New

Bug description:
  Sudo currently fails to validate netgroups against host netgroups
  returned from the sss plugin, see
  https://fedorahosted.org/freeipa/ticket/6139 for the glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

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

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

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-01-13 Thread Jorge Niedbalski

Hello,

I have been working to track down the origin of the performance penalty
exposed by this bug.

All the tests that I am performing are made on top of a locally compiled 
version of python 2.7.12 (from upstream sources, not applying any ubuntu patch 
on it)
built with different versions of GCC, 5.3.1 (current) and 4.8.0 both coming 
from the Ubuntu archives.

I can see important performance differences as I mentioned on my previous 
comments (check the full comparisons stats) just by
switching the GCC version. I decided to focus my investigation on the pickle 
module, since it seems to be the most affected one being
approximately 1.17x slower between the different gcc versions.

Due to the amount of changes introduced between 4.8.0 and 5.3.1 I decided to 
not persue the approach
of doing a bisection of the changes for identifying an offending commit yet, 
until we can identify which optimization or change
at compile time is causing the regression and focus our investigation on that 
specific area.

My understanding is that the performance penalty caused by the compiler might 
be related
to 2 factors, a important change on the linked libc or a optimization made by 
the compiler in the resulting object. 

Since the resulting objects are linked against the same glibc version 2.23, I 
will not consider that factor as part of the analysis,
instead I will focus on analyzing the performance of the resulting objects 
generated by the compiler.

For following this approach I ran the pyperformance suite and used a valgrind 
session excluding all the modules with the exception of the pickle module, 
using the default supressions to avoid missing any reference in the python 
runtime with the following arguments:

valgrind --tool=callgrind --instr-atstart=no --trace-children=yes
venv/cpython2.7-6ed9b6df9cd4/bin/python -m performance run --python
/usr/local/bin/python2.7 -b pickle --inside-venv

I did run this process multiple times with both GCC 4.8.0 and 5.3.1  to produce 
a large set of callgrind files to analyze , those callgrind files contains the 
full tree of execution 
including all the relocations, jumps, calls to the libc and the python runtime 
itself and of course time spent per function and the amount of calls made to it.

I cleaned out all the resulting callgrind files removing the files smaller than 
100k and the ones that were not loading the cPickle
extension (https://pastebin.canonical.com/175951/). 

Over that set of files I executed callgrind_annotate to generate the stats per 
function ordered by the exclusive cost of function, 
Then with this script (http://paste.ubuntu.com/23795048/
) I added all the costs per function per GCC version (4.8 and 5.3.1) and then I 
calculated the variance in cost between them.

The resulting file contains a tuple with the following format:

function name - gcc 4.8 cost - gcc 5.3.1 cost - variance in percent

As an example:

/home/ubuntu/python/cpython/Objects/tupleobject.c:tupleiter_dealloc 
258068.00 445009.00 (variance: 0.724387)
/home/ubuntu/python/cpython/Objects/object.c:try_3way_compare 984860.00 
1676351.00 (variance: 0.702121)
/home/ubuntu/python/cpython/Python/marshal.c:r_object 183524.00 
27742.00 (variance: -0.848837)

The full results can be located here sorted by variance in descending
order http://paste.ubuntu.com/23795023/

Now that we have these results we can move forward comparing the generated code 
for the functions with bigger variance 
and track which optimization done by GCC might be altering the resulting 
objects.

I will update this case after further investigation.

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

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also

[Touch-packages] [Bug 1656450] [NEW] Desktop notifications stop working

2017-01-13 Thread lediableboiteux

Public bug reported:

I don’t know how and why, but sometimes desktop notifications
(libnotify) just stop working and are not shown – either applications’
notifications (like telling you not to unplug your external HDD while
unmounting), or these called directly by notify-send. Killing notify-osd
doesn’t help.

I have Ubuntu 16.10 x64, but I remember this issue back from 15.10 or
even before, but I’m not sure.

libnotify4: 0.7.6-2svn1
libnotify-bin: 0.7.6-2svn1

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

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

Title:
  Desktop notifications stop working

Status in libnotify package in Ubuntu:
  New

Bug description:
  I don’t know how and why, but sometimes desktop notifications
  (libnotify) just stop working and are not shown – either applications’
  notifications (like telling you not to unplug your external HDD while
  unmounting), or these called directly by notify-send. Killing notify-
  osd doesn’t help.

  I have Ubuntu 16.10 x64, but I remember this issue back from 15.10 or
  even before, but I’m not sure.

  libnotify4: 0.7.6-2svn1
  libnotify-bin: 0.7.6-2svn1

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

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

[Touch-packages] [Bug 1656442] [NEW] (firefox:3354): GLib-GIO-CRITICAL

2017-01-13 Thread John-Albert Eadie

Public bug reported:

New installation of 14.04 .. I get dbus errors for virtually all apps

Description:Ubuntu 14.04.5 LTS
Release:14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dbus 1.6.18-0ubuntu4.4
ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 13 15:09:02 2017
InstallationDate: Installed on 2017-01-05 (8 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  (firefox:3354): GLib-GIO-CRITICAL

Status in dbus package in Ubuntu:
  New

Bug description:
  New installation of 14.04 .. I get dbus errors for virtually all apps

  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 15:09:02 2017
  InstallationDate: Installed on 2017-01-05 (8 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

2017-01-13 Thread taiebot65

i am testing silo 2366 and it does not fix the problem. i can also see
that twitter is back to its old version

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-13 Thread Barry Warsaw

I think we know almost the entire story now.  See LP: #1656391

The one piece still missing is what changed.  Very clearly the armhf
container tests passed for several months, and then stopped working.  My
best guess is that they switched from using privileged containers to
unprivileged containers.  In any event, I'm going to close this bug.
See the above referenced bug for further discussion.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: linux (Ubuntu)
   Status: Invalid => Incomplete

** Changed in: lvm2 (Ubuntu)
   Status: Invalid => Incomplete

** Changed in: multipath-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete
Status in multipath-tools package in Ubuntu:
  Incomplete

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-13 Thread Dan Streetman

Yakkety:

with udev 231-9ubuntu2, the /dev/disk/by-id/ NVMe symlinks were not
created correctly:

$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jan 13 22:34 nvme-Amazon -> ../../nvme2n1

and with udev 231-9ubuntu3, the /dev/disk/by-id/ NVMe symlinks are
created correctly:

$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jan 13 22:38 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1AB7AEFBFB76BA92D -> ../../nvme2n1
lrwxrwxrwx 1 root root 13 Jan 13 22:38 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1D210FA708BA29450 -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Jan 13 22:38 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS6AB7AEFBFB76BA92D -> ../../nvme3n1
lrwxrwxrwx 1 root root 13 Jan 13 22:38 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS6D210FA708BA29450 -> ../../nvme1n1


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

** Tags added: verification-done

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1648237] Re: update-manager and unattended-upgrades failure

2017-01-13 Thread bedfojo

Additional info:
on one occasion I have the following in .xsession-errors
debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied

Further additional info:
manually refreshing the cache then manually running unattended-upgrades works.

I deduce from this that the cache is not updating automatically.

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

Title:
  update-manager and unattended-upgrades failure

Status in ubuntu-mate:
  New
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  A series of issues about update-manager and unattended-upgrade. I have set 
the system to:
  - automatically check for update daily
  - when there are security updates, download and install them automatically
  - when there are other updates, display them immediately.

  What occurs:

  (1) unattended-upgrade runs on boot but systematically its log states
  every day that: "No packages found that can be upgraded unattended and
  no pending auto-removals" even where there are security updates to
  install.

  (2) update-manager appears not to refresh the cache automatically
  after boot.

  (3) when the cache is manually refreshed so there are updates, update-
  manager runs after a subsequent boot and appears in the panel. However
  clicking on it leads it to simply disappear.

  (4) update-manager will not launch from the menu. When launched from a
  terminal it runs correctly, refreshes the cache and will install
  updates.

  No crash reports, nothing obvious in log files.

  Ubuntu-MATE 16.10 clean install, fully updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1648237/+subscriptions

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-13 Thread Barry Warsaw

On Jan 13, 2017, at 09:26 PM, dkg wrote:

>a hang during key generation is often due to lack of entropy on the
>system.  Can you ensure that the system isn't entropy-starved somehow?

Oh, oh.  I wonder if you're getting bitten by PEP 524

https://www.python.org/dev/peps/pep-0524/

I don't believe this was back ported to Python 3.5 or 2.7 though.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-13 Thread Dan Streetman

Xenial:

with udev 229-4ubuntu13, the /dev/disk/by-id/ NVMe symlinks were not
correctly created:

$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jan 13 22:01 nvme-Amazon -> ../../nvme0n1


and with udev 229-4ubuntu15 from -proposed, the /dev/disk/by-id/ NVMe symlinks 
were correctly created for all NVMe drives:

$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jan 13 22:08 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1318514BBE1749B07 -> ../../nvme2n1
lrwxrwxrwx 1 root root 13 Jan 13 22:08 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS14A8A28D6E51FDF6D -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Jan 13 22:08 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS6318514BBE1749B07 -> ../../nvme3n1
lrwxrwxrwx 1 root root 13 Jan 13 22:08 
nvme-Amazon_EC2_NVMe_Instance_Storage_AWS64A8A28D6E51FDF6D -> ../../nvme1n1

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-13 Thread dkg

On Thu 2017-01-12 17:10:07 -0500, Rik Mills wrote:
> Adding some debug statements on other the builds showed that that hang
> is occurring in
>
> lang / python / tests / t-callbacks.py
>
> specifically, when the c.op_genkey call is made in the section shown
> below.

a hang during key generation is often due to lack of entropy on the
system.  Can you ensure that the system isn't entropy-starved somehow?

 --dkg

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2017-01-13 Thread Daniel

Just to add to my previous comment, both things (pointer jumping randomly to 
the lower left and left-handed touchpad unavailable) happen on the new Acer 
Aspire whose touchpad doesn't have buttons (or, more precisely, are integrated 
with the touchpad in a single surface). I have Ubuntu 16.04 on an old Toshiba 
and that doesn't happen (touchpad with separate buttons).
Again, it does not happen in Windows 10

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 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:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1656431] [NEW] Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

2017-01-13 Thread Rik Mills

Public bug reported:

libkf5kipi https://userbase.kde.org/KIPI
parley
kidentitymanagement
libkeduvocdocument

FTBFS with errors similar to the one shown at the bottom of this

As is the case with LP Bug #1654820, it seems likely that

kmail
kdepim-addons

would also fail in the same fashion, but the build depends are not yet
in place to confirm that absolutely.

Again, this seems to be a case of qtbase using the gold linker, and I
would surmise that as with amd64 etc, setting no gold linker for  arm64
and ppc64el would resolve this.

no gold linker is already set in qtbase for amd64, i386, powerpc &
armhf.


--- log extract --

[ 56%] Linking CXX executable plaintexteditortest
cd 
/<>/obj-aarch64-linux-gnu/src/texteditor/plaintexteditor/autotests 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/plaintexteditortest.dir/link.txt --verbose=1
/usr/bin/c++   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic  -Wl,--enable-new-dtags -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest.cpp.o 
CMakeFiles/plaintexteditortest.dir/plaintexteditortest_automoc.cpp.o  -o 
plaintexteditortest -Wl,-rpath,/<>/obj-aarch64-linux-gnu/src 
-rdynamic ../../../libKF5PimTextEdit.so.5.4.0.abi1 
/usr/lib/aarch64-linux-gnu/libQt5Test.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1 
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `_edata'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `__bss_start'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `_end'
collect2: error: ld returned 1 exit status
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Gui.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `__bss_start'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_edata'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
/usr/lib/aarch64-linux-gnu/libQt5Core.so.5.7.1:(*IND*+0x0): multiple definition 
of `_end'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `_edata'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `__bss_start'
//usr/lib/aarch64-linux-gnu/libQt5Network.so.5:(*IND*+0x0): multiple definition 
of `_end'
collect2: error: ld returned 1 exit status

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

Title:
  Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el

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

Bug description:
  libkf5kipi https://userbase.kde.org/KIPI
  parley
  kidentitymanagement
  libkeduvocdocument

  FTBFS with errors similar to the one shown at the bottom of this

  As is the case with LP Bug #1654820, it seems likely that

  kmail
  kdepim-addons

  would also fail in the same fashion, but the build depends are not yet
  in place to confirm that absolutely.

  Again, this seems to be a case of qtbase using the gold linker,

[Touch-packages] [Bug 1474563] Re: 1:15/1:16 fails to report support for nvidia 304 have terminated

2017-01-13 Thread Christopher M. Penalver

Galen Thurber (godfree2), as requested in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/comments/40
please do not apport-collect with different hardware. Instead, file a
new report.

Despite this, could you please advise to my question from #40?

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

** Attachment removed: ".proc.driver.nvidia.params.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803627/+files/.proc.driver.nvidia.params.txt

** Attachment removed: "BootDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803628/+files/BootDmesg.txt

** Attachment removed: "BootLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803629/+files/BootLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803630/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803631/+files/Dependencies.txt

** Attachment removed: "DpkgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803632/+files/DpkgLog.txt

** Attachment removed: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803633/+files/LightdmDisplayLog.txt

** Attachment removed: "LightdmLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803634/+files/LightdmLog.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803635/+files/Lspci.txt

** Attachment removed: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803637/+files/NvidiaBugReportLog.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803636/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803638/+files/ProcCpuinfo.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803639/+files/ProcEnviron.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803640/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803641/+files/ProcModules.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803642/+files/UdevDb.txt

** Attachment removed: "UdevLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803643/+files/UdevLog.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803644/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803645/+files/XorgLogOld.txt

** Attachment removed: "Xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803646/+files/Xrandr.txt

** Attachment removed: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803647/+files/nvidia-bug-report.log.gz

** Attachment removed: "xdpyinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803648/+files/xdpyinfo.txt

** Attachment removed: "xserver.devices.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1474563/+attachment/4803649/+files/xserver.devices.txt

** Description changed:

  The conclusion is that xorg versions above 1:12 fail to support legacy
  driver 304. Therefore it should be reported in release notes for users
  of such hardware that they will be unable to use hardware 3D
  acceleration.
  
  ---
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.131  Sun Nov  8 21:43:33 
PST 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2015-04-21 17:09:45,057 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation Device [10de:0370]
  InstallationDate: Installed on 2013-06-24 (1164 days ago)
  InstallationMedia: Xubuntu 12.04.2

[Touch-packages] [Bug 1254804] Re: [wishlist] Apport doesn't log when a core dump is ignored because of the limit

2017-01-13 Thread Brian Murray

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

** Summary changed:

- [wishlist] Apport doesn't log when a core dump is ignored because of the limit
+ Apport doesn't log when a core dump is ignored because of the limit

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

Title:
  Apport doesn't log when a core dump is ignored because of the limit

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When ulimit -c is 0, apport doesn't report any reason not to skip the 
dumping. For applications that are not packaged, the last message in 
/var/log/apport.log is:
  ERROR: apport (pid 4415) Mon Nov 25 17:52:11 2013: executable does not belong 
to a package, ignoring

  This makes very confusing diagnosing why the core was not generated,
  and is very hard to track down how the particular ulimit of the
  application was configured, so it would be better to add a message
  telling the core dump won't be generated because the limit is 0.

  Basically the suggested change is:

   if limit == '0':
  +error_log('skipping core dump writing, current limit is 0')
   return

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport 2.0.1-0ubuntu17.6 [modified: usr/share/apport/apport]
  ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
  Uname: Linux 3.5.0-41-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CrashReports:
   664:1000:133:0:2013-11-25 11:26:18.943268131 +0100:2013-11-25 
11:26:18.943268131 +0100:/var/crash/_usr_bin_pidgin.1000.upload
   640:1000:133:9780109:2013-11-25 11:26:16.687254000 +0100:2013-11-25 
11:26:19.963279496 +0100:/var/crash/_usr_bin_pidgin.1000.crash
   600:122:133:0:2013-11-25 18:11:42.092417577 +0100:2013-10-16 
17:18:00.112172935 +0200:/var/crash/_usr_bin_pidgin.1000.uploaded
  Date: Mon Nov 25 18:16:02 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to precise on 2012-05-24 (550 days ago)

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

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-01-13 Thread Brian Murray

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => High

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

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

[Touch-packages] [Bug 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected

2017-01-13 Thread Christopher M. Penalver

Mauricio Maluff Masi, in addition to 4), could you please provide the
full manufacturer and model as noted on the sticker of the DisplayLink
adapter itself (not from the Bug Description, or the result of a
terminal command)?

** Tags added: xenial

** Description changed:

- Any time I connect an additional monitor via my Displaylink adapter, the
- mouse flickers and disappears in the primary monitor. It displays
- perfectly on the additional monitor. It also displays perfectly after
- the additional monitor is disconnected.
+ Any time I connect my Acer G236HL LCD monitor with VGA via my
+ Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
+ flickers and disappears in the primary monitor. It displays perfectly on
+ the additional monitor. It also displays perfectly after the additional
+ monitor is disconnected.
  
  I see that there are a number of similar bug reports:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001
- 
- I'd be willing to help track it down.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu8.2
  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: Tue Jan 10 22:34:58 2017
  DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-trusty-amd64-20140620-0
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
-  File:  does not exist.
-  
-  bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
+  bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could 
not locate dkms.conf file.
+  File:  does not exist.
+ 
+  bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Dell HD Graphics 5500 [1028:0665]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2016-01-26 (350 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash 
usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
  XorgLogOld:
-  
+ 
  dmi.bios.date: 08/29/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Jan 10 20:18:19 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id

[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression

2017-01-13 Thread Jorge Niedbalski

** Changed in: python2.7 (Ubuntu)
Importance: Undecided => High

** Changed in: python2.7 (Ubuntu)
Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

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

Title:
Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
Confirmed

Bug description:
I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both versions
of Ubuntu.

After more digging, I tested python performance (using the
'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There
is a significant performance difference between each version of
python. That is detailed in a spreadsheet[0].

I began using perf to dig into the differences when running the python
performance module and when using Ansible playbooks. CPU migrations
(as measured by perf) are doubled in Ubuntu 16.04 when running the
same python workloads.

I tried changing some of the kerne.sched sysctl configurables but they
had very little effect on the results.

I compiled python 2.7.12 from source on 14.04 and found the
performance to be unchanged there. I'm not entirely sure where the
problem might be now.

We also have a bug open in OpenStack-Ansible[1] that provides
additional detail. Thanks in advance for any help you can provide!

[0]
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
[1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2017-01-13 Thread Daniel

Also happening to me. Just bought an Acer Aspire F with intel i3 core. 
Installed Ubuntu 16.04 (Dual Boot)
Touch pad works perfectly well with Windows 10 (ouch)
Also I have found impossible to chancge touch pad to left-handed (I know it's 
another topic, but I have searched TONS of pages and found nothing).
Whatever... the pointer jumping randomly and opening Trash can is certainly a 
BIG issue. Just because of that I avoid using Ubuntu on that laptop as much as 
possible.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 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:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1656252] Re: some applications fail to start twice

** Branch linked: lp:~ken-vandine/gallery-app/lp1656252

** Branch linked: lp:~ken-vandine/address-book-app/lp1656252

** Branch linked: lp:~ken-vandine/camera-app/lp1656252

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

Title:
  some applications fail to start twice

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it 
  3. Launch the webbrowser from the app scope

  
  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1640320] Re: FTBFS in zesty

2017-01-13 Thread Brian Morton

I don't see evidence of this error in the amd64 build log at
https://launchpadlibrarian.net/298782129/buildlog_ubuntu-zesty-amd64
.location-service_3.0.0+16.10.20160912-0ubuntu2_BUILDING.txt.gz.
However, the package does FTBFS due to this bug
https://bugs.launchpad.net/ubuntu/+source/googletest/+bug/1644062

Looks like it may need some CMakeLists changes to be compatible with
GoogleTest 1.8

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  New

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions

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

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-01-13 Thread Ubuntu Foundations Team Bug Bot

The attachment "qdbustrayicon-try-to-save-temp-icons-in-readable-
location.debdiff" seems to be a debdiff.  The ubuntu-sponsors team has
been subscribed to the bug report so that they can review and hopefully
sponsor the debdiff.  If the attachment isn't a patch, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

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

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-13 Thread Rik Mills

Seems that even completely disabling the hanging tests is not enough
now. Doing that results in failing tests on arm64 and armhf.

amd64, i386 and ppc64el pass

As in this build https://launchpad.net/~rikmills/+archive/ubuntu
/staging-kde-apps-16.12/+sourcepub/7397892/+listing-archive-extra

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour

2017-01-13 Thread Tessa

I have never done any manual Avahi configuration, and this is a fresh
install of Ubuntu 16.10 on my new Macbook Pro. Where do the valgrind
logs live?

Also, it's doing the 100% cpu thing right now, so bt is below. Note
there's a lot of missing debugging symbols, but I don't see any -dbg
packages for libavahi or similar. If you can suggest how to get these
debugging symbols installed, I imagine it'll make the backtrace more
illuminating:


$ sudo gdb -p 12169
GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 12169
Reading symbols from /usr/sbin/avahi-daemon...(no debugging symbols 
found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3...(no 
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7...(no 
debugging symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libdaemon.so.0...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libexpat.so.1...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libcap.so.2...(no debugging symbols 
found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...Reading symbols from 
/usr/lib/debug//lib/x86_64-linux-gnu/libdl-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...Reading symbols 
from 
/usr/lib/debug/.build-id/71/b2c79a4defc42524ea7e564173f0b65fe89010.debug...done.
done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from 
/usr/lib/debug//lib/x86_64-linux-gnu/libc-2.24.so...done.
done.
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from 
/usr/lib/debug//lib/x86_64-linux-gnu/ld-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libsystemd.so.0...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libselinux.so.1...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...Reading symbols from 
/usr/lib/debug//lib/x86_64-linux-gnu/librt-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/liblzma.so.5...(no debugging symbols 
found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libgcrypt.so.20...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libpcre.so.3...(no debugging symbols 
found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libgpg-error.so.0...(no debugging 
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...Reading symbols 
from /usr/lib/debug//lib/x86_64-linux-gnu/libnss_compat-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...Reading symbols from 
/usr/lib/debug//lib/x86_64-linux-gnu/libnsl-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...Reading symbols 
from /usr/lib/debug//lib/x86_64-linux-gnu/libnss_nis-2.24.so...done.
done.
Reading symbols from /lib/x86_64-linux-gnu/libnss_files.so.2...Reading symbols 
from /usr/lib/debug//lib/x86_64-linux-gnu/libnss_files-2.24.so...done.
done.
0x7f36c9a08f0a in __mmap (addr=0x0, len=4096, prot=, 
flags=34, fd=, offset=0) at 
../sysdeps/unix/sysv/linux/wordsize-64/mmap.c:34
34  ../sysdeps/unix/sysv/linux/wordsize-64/mmap.c: No such file or 
directory.
(gdb) bt
#0  0x7f36c9a08f0a in __mmap (addr=0x0, len=4096, prot=, 
flags=34, fd=, offset=0) at 
../sysdeps/unix/sysv/linux/wordsize-64/mmap.c:34
#1  0x7f36c998a5d1 in sysmalloc (nb=nb@entry=32, av=) at 
malloc.c:2332
#2  0x7f36c998b50a in _int_malloc (av=av@entry=0x0, bytes=bytes@entry=8) at 
malloc.c:3862
#3  0x7f36c998dc0a in __libc_calloc (n=, 
elem_size=) at malloc.c:3281
#4  0x7f36c9f0e067 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x7f36c9f0a9e7 in dbus_message_get_path_decomposed () from 
/lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x7f36c9f0da93 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7f36c9eff264 in dbus_connection_dispatch () from 
/lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x5628bc167506 in ?? ()
#9

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-13 Thread Barry Warsaw

LP: #1656391

And it's reproducible in an amd64 container run locally.  So probably
some change in the images or lxc.  Maybe a new missing dependency?

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1656352] Re: apt does not honor Proxy-Auto-Detect for HTTPS URLs

2017-01-13 Thread Julian Andres Klode

Proxy Auto detect for https works perfectly fine, but there's a catch:
The proxy needs to be the same type as the URL. So https only supports
an https proxy, not an http proxy url.

I'm not sure how far we should open that up, but https via http and http
via https are things you probably want to work. The former is possible,
the latter we cannot support at all yet.

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

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

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

Title:
  apt does not honor Proxy-Auto-Detect for HTTPS URLs

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt(-get) does not honor Proxy-Auto-Detect configuration in any way
  for HTTPS URLs.

  ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect

  Acquire::http:Proxy-Auto-Detect "/path/to/app";

  "app" performs some actions and output the name of the proxy server
  according to some internal rules, in the form
  "http://proxy.domain.tld:1234/;

  This works perfectly for all HTTP-like "deb http://example.com/ xxx"
  URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-
  Auto-Detect" or even the legacy variable name "ProxyAutoDetect"
  (without dashes) does not help either.

  This is very annoying as the very purpose of this auto-detection is to
  be network environment aware instead of using a hardcoded value for
  the proxy setting.

  This should be fixed. Thank you.

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

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
vivid-2366

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

This has had systemd 231-9ubuntu3 stacked on top into xenial-proposed.
See bug 1647485 for details. When verifying, please test and verify
systemd 231-9ubuntu3, not the previous version, and confirm the package
version you tested in your comment to avoid any misunderstanding.
Thanks!

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed
Status in resolvconf source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  Fix Committed

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  
  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  
  Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash

# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd

# enable networkd and netplan
apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
version: 2
ethernets:
  eth0:
dhcp4: true
  EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

netplan generate

# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a 
After=systemd-network-wait-online.service' 
/lib/systemd/system/cloud-init.service

reboot

# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

# the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  
  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

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

Hello Dan, or anyone else affected,

Accepted systemd into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/231-9ubuntu3 in a few
hours, and then in the -proposed repository.

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

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

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

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer

The warning appears although I use UUIDs all over the place in my
/etc/fstab.

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions

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

[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer

A also need to add that my hard disks are unencrypted from the
perspective of the OS (I use hardware encrypted SSDs).

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions

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

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

Hello Dan, or anyone else affected,

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

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

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

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

** Changed in: systemd (Ubuntu Yakkety)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

There was further discussion in #ubuntu-devel and #ubuntu-release on
this review. See irclogs.ubuntu.com for details.

I have reviewed the patch carefully. As far as I can tell, it does what
it is supposed to do, and I don't see any bugs.

However, this code, particularly the udev_event_apply_format function,
seems to have grown organically and could be significantly improved
IMHO. This patch makes the state of the code worse, and increasingly
fragile. It took hours for me to review the patches for correctness as a
consequence, and I think that this and future changes and reviews are
far more prone to error than they need to be.

Some specifics:

1) The mechanism employed of redirecting s and l (destination buffer and
length remaining count) means that the code inside the redirection is
incredibly fragile. The code inside the switch should be pulled out into
a separate function. Then the redirection would become unnecessary. On
IRC, Dan acknowledged that this may require a large number of parameters
to be provided to the factored out function, but this is in part my
point. Unintended interactions could happen through any of those
parameters. Isolating them would be helpful, since that would identify
and reduce the interactions that need to be checked.

2) IMHO, the patch should use the sizeof(x)/sizeof(x[0]) idiom to get
the buffer lengths, rather than assuming that they are defined by the
same macro. I think likely that someone will attempt to change the array
length by assuming it is only necessary to change it in one place. Dan
suggested on IRC that the opposite point is that changing it from a
buffer to a pointer would cause the sizeof idiom to break, but I think
it's far more likely that a developer will check how a variable is used
before changing its type.

3) The upstream PR refers to tests, but does not add a test for this bug
being fixed. Given the fragility of this fix, I think we should do that.

We have to maintain this code for another four years in Xenial. If we
have to touch this function again in that time, I think we'll need to
spend even more time fixing and reviewing it.

I realise that the fix has already been accepted upstream. But as we (in
Ubuntu) originated the patch, I think we have a responsibility to make
it cleaner. Please refactor it and send that upstream.

I understand that this SRU is necessary to fix an important regression
in Ubuntu, so I don't think it's appropriate to block this given that I
can't find a bug in it. However, I've written this up to register my
unhappiness with this patch.

I appreciate the previous state of the code made it difficult to fix in
a better way; IMHO, this is a reason to refactor it first when sending
the development fix upstream. Perhaps the SRU would then need to have
been a different, more minimal and hacky patch, but that could be
focused on minimising regression risk and fixing just the problem at
hand rather than the general case.

If you add a test for this bug, please bundle it with the next SRU of
this package in Xenial.

I note that Zesty is not Fix Released. However, since this is a
regression fix, I don't think it would be appropriate to wait. Please
get the fix landed in Zesty as soon as possible; I certainly expect the
Zesty fix to be able to land well before we are ready to release this in
to Xenial/Yakkety -updates.

Given that this is a regression fix, we might expect to cut short the
usual 7-day aging period. However, given the fragility of the code
involved and because this is not a straight revert, I don't think that is
warranted in this case.


** Changed in: systemd (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

** Tags removed: verification-needed
** Tags added: regression-update

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace

[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab

2017-01-13 Thread Thomas Mayer

Doing updates with apt-get, I get messages like

cryptsetup: WARNING: failed to detect canonical device of /dev/sdXY

Besides the warning message, everything seems to run fine.

I'm using ubuntu 16.04 with recent updates.

related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056

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

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

Title:
  update-initramfs cryptsetup must correctly take into account PARTLABEL
  inside /etc/fstab

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Systematically,

  -  With a /etc/fstab using UUID or LABEL, update-initramfs works
  correctly

  -  With a /etc/fstab using PARTLABEL, update-initramfs displays following 
error messages :
  cryptsetup: WARNING: failed to detect canonical device of 
PARTLABEL=Ubuntu-Gnome
  cryptsetup: WARNING: could not determine root device from /etc/fstab
  cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu

  The cryptsetup part of update-initramfs must correctly take into
  account PARTLABEL inside /etc/fstab

  Thank you in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue May 10 21:14:24 2016
  InstallationDate: Installed on 2014-11-03 (553 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)
  mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

** Branch linked: lp:~osomon/webbrowser-app/ota14-fix1656310

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

2017-01-13 Thread Treviño

Upstream fix for pure Qt apps (when not including appmenu-qt5) is
proposed at https://codereview.qt-project.org/#/c/182307/.

Here's the patch for the ubuntu package too.

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

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

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

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Changed in: qt
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: qt
   Status: New => In Progress

** Patch added: 
"qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff"
   
https://bugs.launchpad.net/qt/+bug/1600136/+attachment/4803964/+files/qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

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

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

2017-01-13 Thread Olivier Tilloy

Indeed that looks similar. Sorry it fell off my radar.

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

2017-01-13 Thread Alberto Mardegan

Might be the same as bug 1644585.

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1574776] Re: Only one subtitle displayed at any given time

Please:

1. Report to (https://bugzilla.gnome.org/enter_bug.cgi).
2. Paste the new report link here.
3. Set status back to "confirmed".

Thank you.

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Only one subtitle displayed at any given time

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Many of the videos I watch are subtitled foreign works; they generally
  have multiple subtitles onscreen at once, with one translating the
  speech and others translating onscreen text. Gstreamer invariably only
  displays one and more often than not it's the less helpful one,
  leaving me unable to tell what's  been said because "episode 2" is
  deemed more important information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 25 18:25:16 2016
  InstallationDate: Installed on 2015-06-28 (302 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to xenial on 2016-04-19 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1574776/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

2017-01-13 Thread Olivier Tilloy

I am not seeing issues with calendar or keep, but I can reliably observe
the problem with g+. A simple UA override seems to do the trick.

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1656358] Re: dash crashes if an app is launched with system's u-a-l instead of unity8-session.u-a-l

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

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

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

Title:
  dash crashes if an app is launched with system's u-a-l instead of
  unity8-session.u-a-l

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty + unity8-session 349

  Test Case:
  1. Launch an app from the command line with system's ual. For example
  $ ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26

  Expected result
  The app fails to launch but the dash doesn't crash

  Actual result
  The app fails to launch and the dash crashes. Launching with 
unity8-session.u-a-l works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656358/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

** Branch linked: lp:~osomon/webbrowser-app/1656310-ua-override-gplus

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1652516] Re: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 139

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I DON'T KNOW

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jayachitra   1514 F pulseaudio
  Date: Sun Dec 25 19:52:55 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 139
  HibernationDevice: RESUME=UUID=73e2f5bd-93f6-4c8f-aec4-6090372de0b4
  InstallationDate: Installed on 2016-07-28 (149 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=1aba02be-eab0-416e-8f86-52396085f8a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1652516/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

2017-01-13 Thread Olivier Tilloy

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

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1652466] Re: Totem can't play videos on Gallium graphics

** Summary changed:

- [Xenial] va-driver-all should depend on mesa-va-drivers, otherwise, Totem 
can't play videos if gstreamer1.0-vaapi is installed on Gallium graphics
+ Totem can't play videos on Gallium graphics

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

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

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

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

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

** Changed in: totem (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  Totem can't play videos on Gallium graphics

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  What is the problem:
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-13 Thread Bug Watch Updater

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

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1656358] Re: dash crashes if an app is launched with system's u-a-l instead of unity8-session.u-a-l

2017-01-13 Thread Ken VanDine

I can confirm this bug on xenial+overlay+silo 2129, however slightly
different.

This doesn't crash the dash:
ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26

This does crash the dash:
ubuntu-app-launch ubuntu-calculator-app

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

Title:
  dash crashes if an app is launched with system's u-a-l instead of
  unity8-session.u-a-l

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  zesty + unity8-session 349

  Test Case:
  1. Launch an app from the command line with system's ual. For example
  $ ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26

  Expected result
  The app fails to launch but the dash doesn't crash

  Actual result
  The app fails to launch and the dash crashes. Launching with 
unity8-session.u-a-l works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656358/+subscriptions

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

[Touch-packages] [Bug 1656358] [NEW] dash crashes if an app is launched with system's u-a-l instead of unity8-session.u-a-l

2017-01-13 Thread Jean-Baptiste Lallement

Public bug reported:

zesty + unity8-session 349

Test Case:
1. Launch an app from the command line with system's ual. For example
$ ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26

Expected result
The app fails to launch but the dash doesn't crash

Actual result
The app fails to launch and the dash crashes. Launching with 
unity8-session.u-a-l works as expected.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

Title:
  dash crashes if an app is launched with system's u-a-l instead of
  unity8-session.u-a-l

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  zesty + unity8-session 349

  Test Case:
  1. Launch an app from the command line with system's ual. For example
  $ ubuntu-app-launch ubuntu-calculator-app_ubuntu-calculator-app_26

  Expected result
  The app fails to launch but the dash doesn't crash

  Actual result
  The app fails to launch and the dash crashes. Launching with 
unity8-session.u-a-l works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656358/+subscriptions

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

[Touch-packages] [Bug 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp

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

** Information type changed from Public to Public Security

** Changed in: apparmor (Ubuntu)
   Importance: Critical => High

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

Title:
  From v49.0, Firefox needs read access to @{PROC}/net/arp

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Since the latest upgrade of Firefox to 49.0, it will need read access
  to @{PROC}/net/arp

  I don't know what the security implications are, so I don't know if we
  want to give read access to explicitely deny it. Both seem to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 29 16:55:21 2016
  InstallationDate: Installed on 2015-10-04 (361 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus 
mediation is enabled
   Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus 
mediation is enabled
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
  modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
  modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
  modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
  mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
  mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
  mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser: 
2015-10-05T12:02:05.273141
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: 
2016-04-13T19:13:25.829679
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
  mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
  mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
  mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
  mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
  mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
  mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981

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

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

[Touch-packages] [Bug 1646956] Re: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure)

2017-01-13 Thread bugproxy

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1704

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

Title:
  ping -I support broken in yakkety version 3:20150815-2ubuntu3
  (multicast test failure)

Status in iputils package in Ubuntu:
  New

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 ==
  ---Problem Description---
  Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x)
   
  Machine Type = S822l1 
   
  ---Steps to Reproduce---
   On Host:  Enable multicast for the test interface
  1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
  2. ip link set enP5p1s0f1 allmulticast on
  root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1
  enP5p1s0f1: flags=4675  mtu 1500
  inet 170.1.1.20  netmask 255.255.255.0  broadcast 170.1.1.255
  inet6 fe80::9abe:94ff:fe5c:f1c1  prefixlen 64  scopeid 0x20
  ether 98:be:94:5c:f1:c1  txqueuelen 1000  (Ethernet)
  RX packets 488  bytes 50254 (50.2 KB)
  RX errors 0  dropped 442  overruns 0  frame 0
  TX packets 25  bytes 2226 (2.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 226  memory 0x3d400100-3d40017f 


  On Peer: --> catch the Test interface from the multicast group
  ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20

   
  ---uname output---
  Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 ==

  I'm able to replicate this behavior in a KVM environment with Yakkety,
  so it does not appear to be related to the specific type of interface.

  From my testing, it looks like the SO_BINDTODEVICE option is not being
  honored, so both broadcasts and multicasts are going out the default
  route device instead of the device specified by -I option to ping.

  I am unable to replicate this on a xenial host with the same 4.8.0-27
  kernel version. so I suspect some other setting is interfering with
  the ability to bind the output to a specific device.

  From my own testing:

  Xenial:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s6:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe15:b7ba/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fee1:35be/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s6 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data.
  64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms
  64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!)
  ^C
  ...

  Yakkety:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s5:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:febe:97ab/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe30:d014/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s5 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data.
  64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms
  64 bytes from

[Touch-packages] [Bug 1649185] Re: package apport 2.20.1-0ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

Title:
  package apport 2.20.1-0ubuntu2.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  This problem occurs only when you upgrade. Other manifestations are
  not found.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-53.74-lowlatency 4.4.30
  Uname: Linux 4.4.0-53-lowlatency x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Mon Dec 12 08:36:57 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-14 (27 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649105] Re: ubuntu 16.04 conflict with nvidia GeForce 6150SE

Please:

1. Edit the description, so it explains the perceptible consequences of the bug.
2. Set status back to confirmed.

Thanks for your help.

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

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

Title:
  ubuntu 16.04 conflict with nvidia GeForce 6150SE

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  seems conflictual behaviour between compiz version and available
  drivers (private and free). No solution found yet to stabilize.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Dec 11 18:05:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2016-12-01 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=b5bf3784-f5af-4627-8503-a82a628a8998 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.name: EL1358
  dmi.sys.vendor: eMachines
  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.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Dec 11 17:55:46 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1656252] Re: some applications fail to start twice

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

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

Title:
  some applications fail to start twice

Status in Canonical System Image:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it 
  3. Launch the webbrowser from the app scope

  
  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1654568] Re: On screen keyboard transparent - buffer not updated

** Summary changed:

- OSK transparent - buffer not updated
+ On screen keyboard transparent - buffer not updated

** Description changed:

- The OSK is unusable on frieza_arm64/staging. It's just not displayed.
+ The on screen keyboard is unusable on frieza_arm64/staging. It's just
+ not displayed.
  
  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 12:22:32
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106
  
  Note you'll need to downgrade dbus and reboot (bug #1654365):
  
  $ sudo apt install {dbus{,-x11},libdbus-1-3}=1.10.6-1ubuntu3.1
  $ sudo reboot
  
  [2017-01-06:14:06:06.521] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::MirSurface(type=input Method,state=restored)
  [2017-01-06:14:06:06.522] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::registerSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [...]
  [2017-01-06:14:06:06.630] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setInputBounds(QRect(0,1159 1200x761))
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4e2f00,"unity8-dash"]::setFocused(false)
  [2017-01-06:14:06:06.862] qtmir.applications: 
Application["unity8-dash"]::focusedChanged(false)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setFocused(true)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setReady()
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::prependSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::setState(state=running)
  [2017-01-06:14:06:06.863] toplevelwindowmodel: 
setFocusedWindow(Window[0x1c3958a0, id=3, 
MirSurface[0x1c4a0820,"MaliitOnScreenKeyboard"]])
  [2017-01-06:14:06:06.864] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setKeymap("us")
  [2017-01-06:14:06:07.120] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::dropPendingBuffer() dropped=0 left=1 - failed to 
upate texture
  
  That last one suggests unity8 didn't properly pick the input method up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.15+16.04.20161215-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 14:05:11 2017
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  On screen keyboard transparent - buffer not updated

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The on screen keyboard is unusable on frieza_arm64/staging. It's just
  not displayed.

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 12:22:32
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  Note you'll need to downgrade dbus and reboot (bug #1654365):

  $ sudo apt install {dbus{,-x11},libdbus-1-3}=1.10.6-1ubuntu3.1
  $ sudo reboot

  [2017-01-06:14:06:06.521] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::MirSurface(type=input Method,state=restored)
  [2017-01-06:14:06:06.522] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::registerSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [...]
  [2017-01-06:14:06:06.630] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setInputBounds(QRect(0,1159 1200x761))
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4e2f00,"unity8-dash"]::setFocused(false)
  [2017-01-06:14:06:06.862] qtmir.applications: 
Application["unity8-dash"]::focusedChanged(false)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setFocused(true)
  [2017-01-06:14:06:06.862] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setReady()
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::prependSurface(surface=qtmir::MirSurface(0x1c4a0820))
  [2017-01-06:14:06:06.863] qtmir.surfaces: 
Session[0x1c571960,name="maliit-server"]::setState(state=running)
  [2017-01-06:14:06:06.863] toplevelwindowmodel: 
setFocusedWindow(Window[0x1c3958a0, id=3, 
MirSurface[0x1c4a0820,"MaliitOnScreenKeyboard"]])
  [2017-01-06:14:06:06.864] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::setKeymap("us")
  [2017-01-06:14:06:07.120] qtmir.surfaces: 
MirSurface[0x1c4a0820,"-"]::dropPendingBuffer() dropped=0 left=1 - failed to 
upate texture

  That last one suggests unity8 didn't properly pick the input method
  up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8

[Touch-packages] [Bug 1656352] [NEW] apt does not honor Proxy-Auto-Detect for HTTPS URLs

2017-01-13 Thread MelkorLord

Public bug reported:

apt(-get) does not honor Proxy-Auto-Detect configuration in any way for
HTTPS URLs.

ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect

Acquire::http:Proxy-Auto-Detect "/path/to/app";

"app" performs some actions and output the name of the proxy server
according to some internal rules, in the form
"http://proxy.domain.tld:1234/;

This works perfectly for all HTTP-like "deb http://example.com/ xxx"
URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-Auto-
Detect" or even the legacy variable name "ProxyAutoDetect" (without
dashes) does not help either.

This is very annoying as the very purpose of this auto-detection is to
be network environment aware instead of using a hardcoded value for the
proxy setting.

This should be fixed. Thank you.

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

** Description changed:

  apt(-get) does not honor Proxy-Auto-Detect configuration in any way for
  HTTPS URLs.
  
  ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect
  
  Acquire::http:Proxy-Auto-Detect "/path/to/app";
  
  "app" performs some actions and output the name of the proxy server
  according to some internal rules, in the form
  "http://proxy.domain.tld:1234/;
  
  This works perfectly for all HTTP-like "deb http://example.com/ xxx"
  URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-Auto-
  Detect" or even the legacy variable name "ProxyAutoDetect" (without
- dashes) does help either.
+ dashes) does not help either.
  
  This is very annoying as the very purpose of this auto-detection is to
  be network environment aware instead of using a hardcoded value for the
  proxy setting.
  
  This should be fixed. Thank you.

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

Title:
  apt does not honor Proxy-Auto-Detect for HTTPS URLs

Status in apt package in Ubuntu:
  New

Bug description:
  apt(-get) does not honor Proxy-Auto-Detect configuration in any way
  for HTTPS URLs.

  ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect

  Acquire::http:Proxy-Auto-Detect "/path/to/app";

  "app" performs some actions and output the name of the proxy server
  according to some internal rules, in the form
  "http://proxy.domain.tld:1234/;

  This works perfectly for all HTTP-like "deb http://example.com/ xxx"
  URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-
  Auto-Detect" or even the legacy variable name "ProxyAutoDetect"
  (without dashes) does not help either.

  This is very annoying as the very purpose of this auto-detection is to
  be network environment aware instead of using a hardcoded value for
  the proxy setting.

  This should be fixed. Thank you.

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

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

[Touch-packages] [Bug 1656252] Re: some applications fail to start twice

2017-01-13 Thread Jean-Baptiste Lallement

** Summary changed:

- frequently applications fails to start
+ some applications fail to start twice

** Description changed:

  zesty desktop
  unity8 session snap 349
  
- 
  Test Case:
  1. Launch the webbrowser from the app scope
+ 2. close it 
+ 3. Launch the webbrowser from the app scope
+ 
  
  Expected result:
- It launches
+ It starts twice
  
  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

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

Title:
  some applications fail to start twice

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it 
  3. Launch the webbrowser from the app scope

  
  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Please test proposed package

2017-01-13 Thread Brian Murray

Hello Albert, or anyone else affected,

Accepted xorg-server-lts-xenial into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/xorg-
server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty2 in a few hours, and then
in the -proposed repository.

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

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

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

-- 
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:
  Fix Released
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 1656252] Re: frequently applications fails to start

2017-01-13 Thread Ken VanDine

I can confirm that removing single instance from the desktop file works
around it.

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

Title:
  some applications fail to start twice

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  Test Case:
  1. Launch the webbrowser from the app scope
  2. close it 
  3. Launch the webbrowser from the app scope

  
  Expected result:
  It starts twice

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1656310] Re: google + is not accessible anymore via the browser app

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

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  google + is not accessible anymore via the browser app

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Something must have changed in google it used to work flawlessly.
  Now i have a message saying that this browser is not supported and i cannot 
see any public google plus sites

  mako
  rc proposed
  vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656310/+subscriptions

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

[Touch-packages] [Bug 1656252] Re: frequently applications fails to start

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

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

** Changed in: canonical-devices-system-image
Milestone: None => p2

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  frequently applications fails to start

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  
  Test Case:
  1. Launch the webbrowser from the app scope

  Expected result:
  It launches

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1656341] [NEW] Packaging error (trusty) suspend/resume scripts missing

2017-01-13 Thread D J Gardner

Public bug reported:

systemd-204-5ubuntu20.20, on trusty.

sudo /lib/systemd/systemd-sleep  suspend   / hibernate / hybrid-sleep
all function perfectly, however:

sudo systemctl suspend  / hibernate / hybrid-sleep
 totally fails. further investigation shows that while man-pages for 
systemd-suspend.service, etc. are installed, the actual .service and .target 
files are missing.

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

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

Title:
  Packaging error (trusty) suspend/resume scripts missing

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-204-5ubuntu20.20, on trusty.

  sudo /lib/systemd/systemd-sleep  suspend   / hibernate / hybrid-sleep
  all function perfectly, however:

  sudo systemctl suspend  / hibernate / hybrid-sleep
   totally fails. further investigation shows that while man-pages for 
systemd-suspend.service, etc. are installed, the actual .service and .target 
files are missing.

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

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

2017-01-13 Thread Łukasz Zemczak

Hello Iain, or anyone else affected,

Accepted gst-plugins-good1.0 into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-good1.0/1.8.3-1ubuntu0.3 in a few hours, and then in the
-proposed repository.

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

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

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

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1656250] Re: session crashes without any user action

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

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

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

Title:
  session crashes without any user action

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  On Zesty desktop with unity8-session 16.04 349

  Test Case
  1. Start a unity8 session
  2. Launch an app (eg Calculator)
  3. Wait 

  Expected result
  After an hour the session and the calculator are still running

  Actual result
  At some point (less than an hour) the session restarts (the calculator is 
gone if you were not staring at the screen when it restarted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656250/+subscriptions

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

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

2017-01-13 Thread Jan Hübner

Thanks for your quick reply. I don't want to sound harsh or be the guy
who is always complaining, but this is just so annoying. I can't test
packages on production servers or run "testing" packages on them, even
if known good, when it's company policy to only run stable/official
packages (especially when it's a LTS release).

And be honest: how much more basic from a user/admin perspective than
"SSH is working" can it get?

So: sorry for my "outburst" - I felt better afterwards ;) - and
obviously something is moving again :)

Kind regards,
Jan

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

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

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

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

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

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

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

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

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

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

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

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

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

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

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

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

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

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

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

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

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook

[Touch-packages] [Bug 1646256] Re: Update sudo for proper support of netgroups

2017-01-13 Thread Timo Aaltonen

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

** This bug has been marked a duplicate of bug 1607666
   sudo fails with host netgroup returned from freeipa

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

Title:
  Update sudo for proper support of netgroups

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  sudo v1.8.16 has a bug that prevents it from working properly with
  netgroups.

  The main affected usage case that I'm aware of is when using FreeIPA
  to define host groups, and then using those host groups within sudo
  rules.

  It would appear that a release >=1.8.17 resolves the issue.

  https://bugzilla.redhat.com/show_bug.cgi?id=1348672
  
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/sudo.html#abt-sudo2

  Package: sudo 1.8.16-0ubuntu1.2
  Distribution: Ubuntu 16.04 and later

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

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

[Touch-packages] [Bug 1653373] Re: [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView color format.

This bug was fixed in the package gst-plugins-bad1.0 - 1.10.2-1ubuntu2

---
gst-plugins-bad1.0 (1.10.2-1ubuntu2) zesty; urgency=medium

  [ Ratchanan Srirattanamet ]
  * hybris: add color format for fp2 (LP: #1653373)

  [ Alfonso Sanchez-Beato ]
  * Refactor patches to have only one for mir/androidmediahybris support

 -- Iain Lane   Fri, 13 Jan 2017 12:39:20 +

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [gst-hybris] Support COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView
  color format.

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released

Bug description:
  From gstamc-constants.h:
/* NV12 but with stride and plane heights aligned to 32, Stores two images,
 * one after the other in top-bottom layout */
COLOR_QCOM_FormatYVU420SemiPlanar32mMultiView = 0x7fa30c05,

  Support is added by adding android-gst color format mapping, using the
  same code as COLOR_QCOM_FormatYUV420SemiPlanar to handle software
  conversion (as in gstamc.c) and adding special handling for multi-view
  nature of the format (as in gstamcvideodec.c).

  Adding support for this format fixes video playback on Fairphone 2.

  gst-plugins-bad1.0 version 1.8.2-1ubuntu0.1~overlay1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1653373/+subscriptions

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

[Touch-packages] [Bug 1655302] Re: [Trusty] systemd startup fails in the presence of cgmanager

2017-01-13 Thread Dimitri John Ledkov

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

Will be handled part of the systemd SRU.

** This bug has been marked a duplicate of bug 1656280
   Support installing subordinate systemd on Ubuntu Desktop 14.04.5

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

Title:
  [Trusty] systemd startup fails in the presence of cgmanager

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In trusty, systemd 204 clashes with cgmanager, with systemd failing to
  start up properly. As a consequence, snapd fails to operate properly.

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

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

[Touch-packages] [Bug 1656250] Re: session crashes without any user action

2017-01-13 Thread kevin gunn

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  session crashes without any user action

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  On Zesty desktop with unity8-session 16.04 349

  Test Case
  1. Start a unity8 session
  2. Launch an app (eg Calculator)
  3. Wait 

  Expected result
  After an hour the session and the calculator are still running

  Actual result
  At some point (less than an hour) the session restarts (the calculator is 
gone if you were not staring at the screen when it restarted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656250/+subscriptions

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

[Touch-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

2017-01-13 Thread kevin gunn

can we please roll back the "importance" to high?

i think it meeets the criteria
High: A bug which fulfills any of the following criteria:
Has a severe impact on a small portion of Ubuntu users (estimated)

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

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

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

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

[Touch-packages] [Bug 1560498] Re: Unity8 using vmwgfx_dri.so crashed in mir::graphics::nested::detail::DisplayBuffer::make_current() -> eglMakeCurrent() -> ... -> dri2_image_get_buffers() [platform_m

2017-01-13 Thread kevin gunn

nevertheless thanks for the progress on this one. lots of folks
requesting.

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

Title:
  Unity8 using vmwgfx_dri.so crashed in
  mir::graphics::nested::detail::DisplayBuffer::make_current() ->
  eglMakeCurrent() -> ... -> dri2_image_get_buffers()
  [platform_mir.c:138]

Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+16.04.20160310.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/7e3f860c1afbbc114bf73f9d7a2966209a25093d
  contains more details.

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

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

[Touch-packages] [Bug 1656252] Re: frequently applications fails to start

2017-01-13 Thread Jean-Baptiste Lallement

Assigning to unity8 because it happened with other apps too like system
settings or the gallery.

** Summary changed:

- frequently webbrowser fails to start
+ frequently applications fails to start

** Description changed:

  zesty desktop
  unity8 session snap 349
- webbrowser-app  20170111-staging  8
+ 
  
  Test Case:
  1. Launch the webbrowser from the app scope
  
  Expected result:
  It launches
  
  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

** Package changed: webbrowser-app (Ubuntu) => unity8 (Ubuntu)

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

Title:
  frequently applications fails to start

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  
  Test Case:
  1. Launch the webbrowser from the app scope

  Expected result:
  It launches

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1656315] [NEW] nividia driver 304 not loading under Trusty

2017-01-13 Thread Galen Thurber

Public bug reported:

Ongoing problem (for nearly one year) with nvidia drivers not installing 
properly with Trusty.
Xorg updates have broken nvidia support for this card.
I've asked questions and filed reports to no avail and no solutions.
NV7900 card, nv304 driver.
Not getting direct rendering nor openGL
On this same system Sparky Linux loads nv304 properly but Trusty does not.

I've tried using AskUbuntu but they are purging all my requests.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.132  Fri Sep 16 11:02:09 
PDT 2016
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
CurrentDmesg:
 [   15.764684] init: plymouth-upstart-bridge main process ended, respawning
 [   15.769251] init: plymouth-upstart-bridge main process (1681) terminated 
with status 1
 [   15.769259] init: plymouth-upstart-bridge main process ended, respawning
Date: Fri Jan 13 09:57:36 2017
DistUpgraded: 2016-09-06 12:12:12,865 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.132, 4.2.0-42-generic, x86_64: installed
 nvidia-304, 304.132, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G71 [GeForce 7900 GT/GTO] [10de:0291] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:c560]
InstallationDate: Installed on 2016-02-25 (322 days ago)
InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1699): WARNING **: Failed to load user image: Failed 
to open file '/home/west/.face': Permission denied
 init: indicator-application main process (1735) killed by TERM signal
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:1509): WARNING **: Failed to load user image: Failed 
to open file '/home/west/.face': Permission denied
 init: indicator-power main process (1551) killed by TERM signal
 init: indicator-application main process (1559) killed by TERM signal
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=235d26fb-efcc-4956-87be-776b1494d2d3 ro nosplash=1 vt.handoff=7 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2016-09-06 (128 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jan 13 09:52:58 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2~trusty3

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  nividia driver 304 not loading under Trusty

Status in xorg package in Ubuntu:
  New

Bug description:
  Ongoing problem (for nearly one year) with nvidia drivers not installing 
properly with Trusty.
  Xorg updates have broken nvidia support for this card.
  I've asked questions and filed

[Touch-packages] [Bug 1656252] Re: frequently webbrowser fails to start

We were seeing this on the second launch of any app that has single
instance specified in the desktop file. The theory is systemd is
confused about it successfully exiting.

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

Title:
  frequently applications fails to start

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  zesty desktop
  unity8 session snap 349

  
  Test Case:
  1. Launch the webbrowser from the app scope

  Expected result:
  It launches

  Actual result
  It does not always starts and it hangs on the launch window (blank window, 
with the webbrowser icon and a spinning loading icon)
  When it occurs it is very reproducible and a reboot of the machine is 
required to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656252/+subscriptions

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

[Touch-packages] [Bug 1655290] Re: RM: Qt 5.7.1 transition related package removals

2017-01-13 Thread Timo Jyrinki

Those seem fixed now?

Now new: unity8-fake-env

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

Title:
  RM: Qt 5.7.1 transition related package removals

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

Bug description:
  Qt 5.7.1 and associated modules and rebuilds are now in zesty-
  proposed.

  Please delete the following dropped binary packages:
  qtbase5-dbg qtbase5-dev-tools-dbg qtbase5-examples-dbg libqt5libqgtk2 
qtdeclarative5-dbg qttools5-dbg qttools5-examples-dbg 
libqt5qml-graphicaleffects qt3d-assimpsceneparser-plugin 
qt3d-gltfsceneparser-plugin qtmultimedia5-dbg qtlocation5-dbg qtpositioning5-dbg

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

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

[Touch-packages] [Bug 1655302] Re: [Trusty] systemd startup fails in the presence of cgmanager

2017-01-13 Thread Thomas Voß

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

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

Title:
  [Trusty] systemd startup fails in the presence of cgmanager

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In trusty, systemd 204 clashes with cgmanager, with systemd failing to
  start up properly. As a consequence, snapd fails to operate properly.

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

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

[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3

2017-01-13 Thread Iain Lane

I uploaded -good again.

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+subscriptions

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

[Touch-packages] [Bug 1656302] [NEW] USB sound card intermittant/unable to play audio

2017-01-13 Thread jon bird

Public bug reported:

I have a EDIROL UA-1A USB soundcard which for the most part under 12.04
worked however after a period of uptime, ALSA calls started failing with
messages of this nature:

ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave

and the kernel ring buffer would have streams of:

[673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD
[673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD

and:

[673429.575699] retire_capture_urb: 596 callbacks suppressed

sometimes unplugging/plugging the card would fix this, other times a
system reboot was required.

Since the upgrade to 14.04 this seems to have got worse in that most of
the time it behaves in this manner and the unplugging/plugging approach
never works. From a kernel perspective, I was already running a 3.13.x
release with 12.04 so there's not been a major update on this front
since the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jon   25970 F pulseaudio
 /dev/snd/pcmC0D0c:   jon   25970 F...m pulseaudio
 /dev/snd/pcmC0D0p:   jon   25970 F...m pulseaudio
CurrentDesktop: LXDE
Date: Fri Jan 13 12:56:13 2017
InstallationDate: Installed on 2013-07-25 (1268 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to trusty on 2016-12-28 (15 days ago)
dmi.bios.date: 02/22/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9SBAA
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/22/2013:svnSupermicro:pnX9SBAA:pvr0123456789:rvnSupermicro:rnX9SBAA:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9SBAA
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

** Package changed: pulseaudio (Ubuntu) => ubuntu

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

Title:
  USB sound card intermittant/unable to play audio

Status in Ubuntu:
  New

Bug description:
  I have a EDIROL UA-1A USB soundcard which for the most part under
  12.04 worked however after a period of uptime, ALSA calls started
  failing with messages of this nature:

  ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
  ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
  ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
  ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave

  and the kernel ring buffer would have streams of:

  [673754.825092] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD
  [673754.830412] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD

  and:

  [673429.575699] retire_capture_urb: 596 callbacks suppressed

  sometimes unplugging/plugging the card would fix this, other times a
  system reboot was required.

  Since the upgrade to 14.04 this seems to have got worse in that most
  of the time it behaves in this manner and the unplugging/plugging
  approach never works. From a kernel perspective, I was already running
  a 3.13.x release with 12.04 so there's not been a major update on this
  front since the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-106-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jon   25970 F pulseaudio
   /dev/snd/pcmC0D0c:   jon   25970 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jon   25970 F...m pulseaudio
  CurrentDesktop: LXDE
  Date: Fri Jan 13 12:56:13 2017
  InstallationDate: Installed on 2013-07-25 (1268 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  ProcEnviron:

[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

2017-01-13 Thread svan001

Same for me, my new bluetooth speaker is paired but I can't stream the audio to 
it. 
Someone posted a fix for this (worked for me and other people) at askubuntu 
here (first answer) : 
http://askubuntu.com/questions/689281/pulseaudio-can-not-load-bluetooth-module-15-10-16-04-16-10

seems pulseausio / X11 related

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

12:26  can I get expedited SRU review of the above systemd
SRU?  It's thought to address an emergent regression introduced by
changes in NVME support in the kernel, and blocks being able to run
MAAS-based CI against machines with NVME

12:26  there's an existing SRU in xenial-proposed which
hasn't been verified; we should just stack them

12:28  I could, but I am but a newb so someone would anyone
have to double-check before I can approve it

12:28  Since bdmurray said I still need to do some coordinated
reviews for now

12:31  slangasek: are all those patches present in systemd
323-10 from zesty? Or is that one not affected?

12:35  Is rharper happy to have the aging clock and verification
reset?

12:41  slangasek: I'm not convinced about the reason for the
urgency here. It looks like NVMe support was added in an SRU in
November, and was done wrong. So surely we need to take more time and
care this time, not less?

12:42  How long has this had time to bake in Zesty? It's not
marked Fix Released yet.

12:47  rbasak: the NVME support was added in the kernel
publication cycle that released to -updates at the beginning of this
year

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-01-13 Thread Erik Mouw

FWIW, the init script /etc/init.d/unattended-upgrades should be
removed from systemd systems (Xenial, Yaketty).

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

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

[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-01-13 Thread Erik Mouw

I have narrowed down. This bug was introduced by the fix in #1618900.
That tries to fix the problem of the the unattended-upgrades.service
by letting it depend on network.target and local-fs.target.
However, that doesn't change any of the dependencies, it only makes
the race window larger.

After some experiments, the correct dependencies in the unit file appear
to be:

Before=remote-fs.target local-fs.target

Which make it behave just like the SysV init script.

This change together with the patch I attached to this bug report
together should fix the issue and also fix #1618900 .


Regards,
Erik

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.

  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).

  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.

  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:

  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True

  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.

  Additional information:

  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2)
  unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions

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

[Touch-packages] [Bug 1656104] Re: Please demote unity8-tests to universe

2017-01-13 Thread Steve Langasek

Override component to universe
unity8-tests 8.15+17.04.20170110.4-0ubuntu1 in zesty amd64: 
main/x11/optional/100% -> universe
unity8-tests 8.15+17.04.20170110.4-0ubuntu1 in zesty arm64: 
main/x11/optional/100% -> universe
unity8-tests 8.15+17.04.20170110.4-0ubuntu1 in zesty armhf: 
main/x11/optional/100% -> universe
unity8-tests 8.15+17.04.20170110.4-0ubuntu1 in zesty i386: 
main/x11/optional/100% -> universe
Override [y|N]? y
4 publications overridden.


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

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

Title:
  Please demote unity8-tests to universe

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  unity8-tests is a new package: simply a renamed unity8-fake-env, which
  was in universe.  We'd also like unity8-tests to be in universe.
  Thanks!

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

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

[Touch-packages] [Bug 1576341] Re: fails in lxd container

2017-01-13 Thread Hamy

i can also confirm this. i noticed it when an update for open-iscsi came
along and i tried to update the container:

...
...
...
Setting up open-iscsi (2.0.873+git0.3b4b4500-14ubuntu8.2) ...
Job for open-iscsi.service failed because the control process exited with error 
code.
See "systemctl status open-iscsi.service" and "journalctl -xe" for details.
invoke-rc.d: initscript open-iscsi, action "start" failed.
● open-iscsi.service - Login to default iSCSI targets
   Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2017-01-13 11:35:10 UTC; 16ms 
ago
 Docs: man:iscsiadm(8)
   man:iscsid(8)
  Process: 4334 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service 
(code=exited, status=3)

Jan 13 11:35:10 testi systemd[1]: open-iscsi.service: Failed to reset 
devices.list: Operation not permitted
Jan 13 11:35:10 testi systemd[1]: Starting Login to default iSCSI targets...
Jan 13 11:35:10 testi systemd[1]: open-iscsi.service: Control process exited, 
code=exited status=3
Jan 13 11:35:10 testi systemd[1]: Failed to start Login to default iSCSI 
targets.
Jan 13 11:35:10 testi systemd[1]: open-iscsi.service: Unit entered failed state.
Jan 13 11:35:10 testi systemd[1]: open-iscsi.service: Failed with result 
'exit-code'.

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

Title:
  fails in lxd container

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exc x1 systemctl is-system-running
  degraded

  $ lxc exec x1 systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  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
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target