[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

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

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
    File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
    File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  ---
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769cb426a

  Regression potential: This changes a central place of systemd
  (although the fix is quite obvious), so if that code is broken it
  could potentially lead to boot failure. However, the fix has been
  tested in yakkety, and all the time in upstrean and downstream CI, so
  if this would actually break anything it should have surfaced by now.
  So low overall.

  Test case: Should be verified by the reporter as the bug description
  did not include a reproducer.

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

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

[Touch-packages] [Bug 1621327] [NEW] alt-left/right moves VTs even when in X

[Michael Hudson-Doyle]

Public bug reported:

I'm experiencing something very like https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=834367 but on 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep  8 17:44:06 2016
InstallationDate: Installed on 2016-04-17 (143 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160416)
MachineType: LENOVO 20BSCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET25W (1.03 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BSCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BSCTO1WW
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  alt-left/right moves VTs even when in X

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm experiencing something very like https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=834367 but on 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  8 17:44:06 2016
  InstallationDate: Installed on 2016-04-17 (143 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160416)
  MachineType: LENOVO 20BSCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET25W (1.03 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 202459] Re: Apt performs some actions multiple times when once would suffice

[Mathew Hodson]

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

** Package changed: debian => ubuntu

** Changed in: ubuntu
   Importance: Unknown => Undecided

** Changed in: ubuntu
   Status: Won't Fix => New

** Changed in: ubuntu
 Remote watch: Debian Bug tracker #481542 => None

** No longer affects: ubuntu

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

** This bug has been marked a duplicate of bug 1250109
   Please use dpkg-triggers

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

Title:
  Apt performs some actions multiple times when once would suffice

Status in apt package in Ubuntu:
  Invalid
Status in dpkg package in Ubuntu:
  Invalid

Bug description:
  I've noticed that if I just ask aptitude to purge kernel packages
  (packages linux-image-, linux-restricted-modules- and linux-ubuntu-
  modules-2.6.24-11-generic), apt/dpkg is invoking twice:

  1) update-initramfs which doesn't need to be invoked at all (or once at the 
end when it's got nothing to do)
  2) update-grub which needs to be invoked just once at the end

  (you can see output of aptitude in attachment). I think that this is
  reason, why has bug #44535 so bad impact.

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

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

[Touch-packages] [Bug 1156929] Re: triggers called multiple times in one upgrade

[Mathew Hodson]

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

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

** This bug is no longer a duplicate of bug 396381
   Update-grub should probably be set up to be a dpkg trigger.
** This bug has been marked a duplicate of bug 1250109
   Please use dpkg-triggers

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

Title:
  triggers called multiple times in one upgrade

Status in apt package in Ubuntu:
  New

Bug description:
  Filing against apt, since I think I've seen seen this with plain apt-
  get update commands. However, this might be the fault of dpkg or do-
  release-upgrade.

  When I upgraded from 12.10 to Raring, I found multiple instances of
  running kernel triggers. It seemed inefficient to me to see the grub
  configuration regenerated over and over again:

  Removing linux-headers-3.5.0-22-generic ...
  Removing linux-headers-3.5.0-22 ...
  Removing linux-headers-3.5.0-23-generic ...
  Removing linux-headers-3.5.0-23 ...
  Removing linux-headers-3.5.0-24-generic ...
  Removing linux-headers-3.5.0-24 ...
  Removing linux-headers-3.5.0-25-generic ...
  Removing linux-headers-3.5.0-25 ...
  Removing linux-image-extra-3.5.0-22-generic ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.5.0-22-generic 
/boot/vmlinuz-3.5.0-22-generic
  update-initramfs: Deleting /boot/initrd.img-3.5.0-22-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.5.0-22-generic 
/boot/vmlinuz-3.5.0-22-generic
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.8.0-13-generic
  Found initrd image: /boot/initrd.img-3.8.0-13-generic
  Found linux image: /boot/vmlinuz-3.5.0-25-generic
  Found initrd image: /boot/initrd.img-3.5.0-25-generic
  Found linux image: /boot/vmlinuz-3.5.0-24-generic
  Found initrd image: /boot/initrd.img-3.5.0-24-generic
  Found linux image: /boot/vmlinuz-3.5.0-23-generic
  Found initrd image: /boot/initrd.img-3.5.0-23-generic
  Found linux image: /boot/vmlinuz-3.5.0-22-generic
  Found linux image: /boot/vmlinuz-3.2.0-35-generic
  Found initrd image: /boot/initrd.img-3.2.0-35-generic
  Found memtest86+ image: /boot/memtest86+.bin
  File descriptor 59 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 4440: /bin/sh
  File descriptor 60 (/dev/pts/12) leaked on lvs invocation. Parent PID 4440: 
/bin/sh
  File descriptor 63 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 4440: /bin/sh
  File descriptor 117 (/dev/pts/12) leaked on lvs invocation. Parent PID 4440: 
/bin/sh
  File descriptor 119 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 4440: /bin/sh
  File descriptor 170 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 4440: /bin/sh
  File descriptor 171 (/dev/pts/12) leaked on lvs invocation. Parent PID 4440: 
/bin/sh
  File descriptor 172 (/dev/pts/12) leaked on lvs invocation. Parent PID 4440: 
/bin/sh
No volume groups found
  done
  Removing linux-image-3.5.0-22-generic ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.5.0-22-generic 
/boot/vmlinuz-3.5.0-22-generic
  update-initramfs: Deleting /boot/initrd.img-3.5.0-22-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.5.0-22-generic 
/boot/vmlinuz-3.5.0-22-generic
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-3.8.0-13-generic
  Found initrd image: /boot/initrd.img-3.8.0-13-generic
  Found linux image: /boot/vmlinuz-3.5.0-25-generic
  Found initrd image: /boot/initrd.img-3.5.0-25-generic
  Found linux image: /boot/vmlinuz-3.5.0-24-generic
  Found initrd image: /boot/initrd.img-3.5.0-24-generic
  Found linux image: /boot/vmlinuz-3.5.0-23-generic
  Found initrd image: /boot/initrd.img-3.5.0-23-generic
  Found linux image: /boot/vmlinuz-3.2.0-35-generic
  Found initrd image: /boot/initrd.img-3.2.0-35-generic
  Found memtest86+ image: /boot/memtest86+.bin
  File descriptor 59 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 5475: /bin/sh
  File descriptor 60 (/dev/pts/12) leaked on lvs invocation. Parent PID 5475: 
/bin/sh
  File descriptor 63 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 5475: /bin/sh
  File descriptor 117 (/dev/pts/12) leaked on lvs invocation. Parent PID 5475: 
/bin/sh
  File descriptor 119 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 5475: /bin/sh
  File descriptor 170 (/var/log/dist-upgrade/apt.log) leaked on lvs invocation. 
Parent PID 5475: /bin/sh
  File descriptor 171 (/dev/pts/12) leaked on lvs invocation. Parent PID 5475: 
/bin/sh
  File descriptor 172 (/dev/pts/12) leaked on lvs invocation. Parent PID 5475: 
/bin/sh
No volume groups found
  done
  

[Touch-packages] [Bug 1612461] Re: [MIR] unity-scopes-api

[Michi Henning]

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => High

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

Title:
  [MIR] unity-scopes-api

Status in unity-scopes-api package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues

  [Quality assurance]
   * This package has unit tests

  [Dependencies]
   * 

  [Standards compliance]
   * This package uses cmake and is properly translated

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1612461/+subscriptions

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

[Touch-packages] [Bug 1250109] Re: Please use dpkg-triggers

[Mathew Hodson]

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

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

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

Title:
  Please use dpkg-triggers

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in grub2 package in Debian:
  Unknown

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

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

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

[Touch-packages] [Bug 45225] Re: update-initramfs should update all initrds

[Mathew Hodson]

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Released => Won't Fix

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

Title:
  update-initramfs should update all initrds

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Packages like dmraid, evms, udev and usplash call update-initramfs in
  their .postinst scripts with the -u option only. Therefore only the
  current or latest initrd is updated, and none of the others that the
  user might has installed.

  This should maybe be fixed in all the individual packages to use "-k
  all". (BTW the usage hint in update-initramfs says "ALL" with
  capitals, whilst the scripts checks for "all".)

  A useful side-effect of the current behaviour is that the other
  initrds are kept as "backups" in case the newly created initrd does
  not work. However, other programs might depend on the new
  functionality in the new initrd.

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

-- 
Mailing list: https://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 1580882] Re: [Intel Broadwell HDMI, Digital Out] Sound like half speed after suspend

[Luke Yelavich]

I don't see anything obvious in those logs and I can't reproduce...

You could try updating your ALSA drivers, as descirbed here:
https://wiki.ubuntu.com/Audio/UpgradingALSA/DKMS

This could very well make a difference since xenial is 4 major kernel
versions behind, and the problem may very well fixed in newer ALSA
driver code.

Thanks.

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

Title:
  [Intel Broadwell HDMI, Digital Out] Sound like half speed after
  suspend

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 all updates applied.

  Playback to headphones is just fine. If I switch output to one of my monitor, 
connected by HDMI, the soudn comes out there, but with half speed. That sounds 
kinda funny, but weird and not as it should.
  Maybe it is somehow related to suspend mode as it was fine a few days ago 
(after a reboot? Can't reboot now to test, sorry).

  I already tried sudo /sbin/alsa force-reload but that didn't do
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jott   3698 F pulseaudio
   /dev/snd/pcmC0D3p:   jott   3698 F...m pulseaudio
   /dev/snd/controlC0:  jott   3698 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 08:42:46 2016
  InstallationDate: Installed on 2016-04-25 (16 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Internes Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [, Intel Broadwell HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580882/+subscriptions

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

[Touch-packages] [Bug 1575878] Re: Xorg freeze when see videos or animation 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze when see videos or animation 16.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When videos are played the system randomly freezes to start playing
  the video, or when it takes a few minutes. It also happens with
  animations webs. This happened with the previous kernel of 15.10 and
  with the current kernel of 16.04. The bios is the latest version and
  use public graphics drivers.

  If I do not watch videos or animations I can work full days without
  freezing.

  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
  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: Wed Apr 27 21:01:26 2016
  DistUpgraded: 2016-04-21 20:00:24,411 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:2224]
  InstallationDate: Installed on 2016-01-14 (104 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20D9S00D00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3e293fa3-ec43-4f0a-a925-562901db8088 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (6 days ago)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N15ET66W (1.26)
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0G00622 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn20D9S00D00:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0G00622WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20D9S00D00
  dmi.product.version: ThinkPad 11e
  dmi.sys.vendor: LENOVO
  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: Wed Apr 27 21:00:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1161 
   vendor IVO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1382163] Re: Printer dialog paper type is not used, instead MODELrc is used

[Launchpad Bug Tracker]

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

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

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

Title:
  Printer dialog paper type is not used, instead  MODELrc is used

Status in cups package in Ubuntu:
  Expired

Bug description:
  I have the problem that after every Cups update (I think) my printer
  is cutting the top of the printout because it is using Letter instead
  of A4.

  The problem lies within that the printer settings (GUI) paper type is not 
used, instead the driver settings file in  
  /usr/local/Brother/inf/brDCP7030rc is used.

  If I set the paper type in the file to A4 all is good, however every
  now and then it is set back to letter, I think after a cups update,
  but might be a different package.

  I'm on Kubuntu Trusty.

  Proposed solution: Printer dialog should take precedence over hidden
  config file.

  Here's a blog post on it that has about 20 page impressions a month:
  http://vedanova.com/ubuntu/2013/11/05/printer-cutting-top-page-
  brother.html

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

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

[Touch-packages] [Bug 1598818] Re: I am just trying to install my VGA

[Launchpad Bug Tracker]

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

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

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

Title:
  I am just trying to install my VGA

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I have intel/AMD and I am trying install the driver, I am still in the
  process when I fond this

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  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
  CurrentDmesg:
   [   23.127588] init: plymouth-upstart-bridge main process ended, respawning
   [   45.260506] audit_printk_skb: 123 callbacks suppressed
   [   45.260509] type=1400 audit(1467632693.312:68): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2133 comm="apparmor_parser"
   [   45.260514] type=1400 audit(1467632693.312:69): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2133 comm="apparmor_parser"
   [   45.260814] type=1400 audit(1467632693.312:70): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2133 comm="apparmor_parser"
  Date: Mon Jul  4 14:47:49 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-92-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:380b]
  InstallationDate: Installed on 2016-07-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN44WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN44WW(V3.03):bd12/07/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.name: 20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jul  4 14:44:30 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18258 
   vendor SDC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1599243] Re: Left mouse click does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  Left mouse click does not work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Unable to use mouse to open applications. Keyboard works.

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  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 Kernel Module  304.131  Sun Nov  8 21:44:08 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jul  5 13:04:29 2016
  DistUpgraded: 2016-06-23 14:32:51,855 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-38-generic, i686: installed
   bbswitch, 0.8, 4.4.0-24-generic, i686: installed
   nvidia-304, 304.131, 4.2.0-38-generic, i686: installed
   nvidia-304, 304.131, 4.4.0-24-generic, i686: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GF100GL [Quadro 4000] [10de:06dd] (rev a3) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GF100GL [Quadro 4000] [10de:0780]
  MachineType: Dell Inc. Precision WorkStation T7500
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=UUID=fe7866ba-f513-4068-8738-8ff7fdd3a1b1 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-23 (11 days ago)
  Xrandr: Screen 0: minimum 0 x 0, current 3840 x 1200, maximum 4096 x 4096
  dmi.bios.date: 10/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06FW8P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/30/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA02:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jul  5 11:36:57 2016
  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

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

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

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Dan Kortschak]

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

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 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 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  

[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed

[Mathew Hodson]

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

** No longer affects: update-manager (Ubuntu)

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

Title:
  Autoupdater fills /boot and crashes because old kernel images are
  never removed

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1) Install Ubuntu with the default LVM encryption recipe
  2) Set Ubuntu to automatically install security updates on the background
  3) Use ubuntu for 5 months

  Actual results:
  The system automatically installs security updates for the kernel under 
/boot. It's never removes previous kernel images. After about five months, the 
/boot partition created by the install recipe (i.e. sized according to the 
judgment of Ubuntu developers—not me) fills up and the unattended updater 
crashes during the next kernel update.

  Expected results:
  Expected the unattended updater to leave the nearest kernel and the previous 
one on /boot and to automatically remove older kernel images. Expected the 
system installer to set up /boot such that it never runs out of space when the 
system updater operates automatically.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: update-manager 1:0.156.14.9
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Sun Sep 23 12:53:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436203] Re: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"

[Launchpad Bug Tracker]

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

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

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

Title:
  [Dash] unity8-dash crashed with ASSERT:
  "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"

Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed 
successfully. Unity8 loads, the indicators are visible and working.
  However, nothing else works: the scope shell doesn't load, only the splash 
screen is shown with the progress indicator spinning, and you can see that 
periodically it's restarted. Upstart logs for unity8-shell show an infinite 
loop of these:

  ==
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269742.137055] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269742.137918] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  [1427269742.139587] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2
  [1427269742.140657] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/mesa.so
  QSocketNotifier: Can only be used with threads started with QThread
  QSocketNotifier: Can only be used with threads started with QThread
  QObject::startTimer: Timers can only be used with threads started with QThread
  QIBusPlatformInputContext: invalid bus.
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  UbuntuWindow - regular geometry
  file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not 
defined
  ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file 
../../../src/ubuntumirclient/glcontext.cpp, line 70
  Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0'
  [1427269746.575630] Loader: Loading modules from: 
/usr/lib/i386-linux-gnu/mir/client-platform/
  [1427269746.576432] Loader: Loading module: 
/usr/lib/i386-linux-gnu/mir/client-platform/dummy.so
  ...
  ==

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: i386
  Date: Tue Mar 24 17:31:02 2015
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2012-10-07 (898 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   qt_assert(char const*, char const*, int) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago)
  UserGroups: adm lpadmin nopasswdlogin sambashare sudo

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

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

[Touch-packages] [Bug 1052360] Re: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason

[Mathew Hodson]

Closing this. If you experience a crash in unattended-upgrades please
follow the instructions in comment #17 and report a new bug.

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

** Tags removed: raring trusty

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

Title:
  unattended-upgrade crashed with SystemError: E:Sub-process
  /usr/bin/dpkg returned an error code (2) for an unknown reason

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Happens by itself

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: unattended-upgrades 0.73ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-26.42-generic 3.0.42
  Uname: Linux 3.0.0-26-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Tue Sep 18 09:24:15 2012
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/sh
  PythonArgs: ['/usr/bin/unattended-upgrade']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with SystemError: E:Sub-process 
/usr/bin/dpkg returned an error code (2)
  Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2012-08-24T13:58:31.952771

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

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

[Touch-packages] [Bug 1613799] Re: No pbuffer configurations available on Mir on X even if available in X

[Chris Halse Rogers]

There's no reason to provide pbuffers (and a number of platforms,
notably Wayland, do not). FBOs do the same thing, but better.

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

** Changed in: mir
   Status: New => Won't Fix

** Changed in: mir (Ubuntu)
   Status: New => Won't Fix

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

Title:
  No pbuffer configurations available on Mir on X even if available in X

Status in Mir:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix

Bug description:
  Available configurations via eglinfo

  X11 platform:
  EGL API version: 1.4
  EGL vendor string: Mesa Project
  EGL version string: 1.4 (DRI2)
  EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
  EGL extensions string:
  EGL_CHROMIUM_sync_control EGL_EXT_create_context_robustness
  EGL_EXT_image_dma_buf_import EGL_KHR_create_context
  EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses
  EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
  EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base
  EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_KHR_wait_sync
  EGL_MESA_configless_context EGL_MESA_drm_image
  EGL_MESA_image_dma_buf_export EGL_NOK_swap_region
  EGL_NOK_texture_from_pixmap EGL_NV_post_sub_buffer
  EGL_WL_bind_wayland_display
  Configurations:
   bf lv colorbuffer dp st  msvis   cav bi  renderable  supported
id sz  l  r  g  b  a th cl ns bid   eat nd gl es es2 vg surfaces 
  -
  0x0e 32  0  8  8  8  8  0  0  0 0 0x20TC  a  y  y  y win,pb,pix
  0x12 32  0  8  8  8  8 24  8  0 0 0x20TC  a  y  y  y win,pb,pix
  0x15 24  0  8  8  8  0  0  0  0 0 0x20TC  y  y  y  y win,pb,pix
  0x19 24  0  8  8  8  0 24  8  0 0 0x20TC  y  y  y  y win,pb,pix
  0x2e 32  0  8  8  8  8  0  0  4 1 0x20TC  a  y  y  y win,pb
  0x30 32  0  8  8  8  8 24  8  4 1 0x20TC  a  y  y  y win,pb
  0x31 24  0  8  8  8  0  0  0  4 1 0x20TC  y  y  y  y win,pb
  0x33 24  0  8  8  8  0 24  8  4 1 0x20TC  y  y  y  y win,pb
  0x42 32  0  8  8  8  8  0  0  0 0 0x21DC  a  y  y  y win,pb,pix
  0x46 32  0  8  8  8  8 24  8  0 0 0x21DC  a  y  y  y win,pb,pix
  0x49 24  0  8  8  8  0  0  0  0 0 0x21DC  y  y  y  y win,pb,pix
  0x4d 24  0  8  8  8  0 24  8  0 0 0x21DC  y  y  y  y win,pb,pix
  0x62 32  0  8  8  8  8  0  0  4 1 0x21DC  a  y  y  y win,pb
  0x64 32  0  8  8  8  8 24  8  4 1 0x21DC  a  y  y  y win,pb
  0x65 24  0  8  8  8  0  0  0  4 1 0x21DC  y  y  y  y win,pb
  0x67 24  0  8  8  8  0 24  8  4 1 0x21DC  y  y  y  y win,pb

  Mir platform:
  EGL API version: 1.4
  EGL vendor string: Mesa Project
  EGL version string: 1.4 (DRI2)
  EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
  EGL extensions string:
  EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
  EGL_KHR_create_context EGL_KHR_get_all_proc_addresses
  EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
  EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base
  EGL_KHR_image_pixmap EGL_KHR_surfaceless_context
  EGL_MESA_configless_context EGL_MESA_drm_image
  EGL_MESA_image_dma_buf_export
  Configurations:
   bf lv colorbuffer dp st  msvis   cav bi  renderable  supported
id sz  l  r  g  b  a th cl ns bid   eat nd gl es es2 vg surfaces 
  -
  0x07 32  0  8  8  8  8  0  0  0 0 0x00-- y  y  y win
  0x09 32  0  8  8  8  8 24  8  0 0 0x00-- y  y  y win
  0x17 32  0  8  8  8  8  0  0  4 1 0x00-- y  y  y win
  0x18 32  0  8  8  8  8 24  8  4 1 0x00-- y  y  y win

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

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

[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Jérôme Poulin]

The package that was submitted to xenial-proposed fixes the problem on
my computer, machinectl start  and virsh start  can now
be run without removing systemd-nspawn.

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
    File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
    File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  ---
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769cb426a

  Regression potential: This changes a central place of systemd
  (although the fix is quite obvious), so if that code is broken it
  could potentially lead to boot failure. However, the fix has been
  tested in yakkety, and all the time in upstrean and downstream CI, so
  if this would actually break anything it should have surfaced by now.
  So low overall.

  Test case: Should be verified by the reporter as the bug description
  did not include a reproducer.

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

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

[Touch-packages] [Bug 1621265] Re: lose monitor during boot up if I don't add 'nomodeset' to kernel options

[Christopher M. Penalver]

seeker5528, in order to allow additional upstream developers to examine the 
issue, at your earliest convenience, could you please test the latest upstream 
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? 
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags added: latest-bios-1.4

** Description changed:

- If I connect my monitor to my computer with a VGA cable, I have to stop
- at the grub menu and add 'nomodeset' to the kernel options with all the
- 4.4.0-* kernels.
- 
- If I do not add 'nomodeset' to the kernel options, my monitor goes
+ If I connect my monitor to my computer with a VGA cable my monitor goes
  blank, complains of no video signal, then goes to sleep as soon as the
  kernel attempts to enable mode setting.
  
  Turning the monitor off and back on does not help, unplugging the VGA
  cable and connecting the DVI cable does not help. I have to hit
  'Ctrl'+'Alt'+'Del' and wait for the computer to restart or hit the power
  button and wait for the computer to shutdown.
  
- If I connect the monitor to the computer with a DVI cable, I do not have
- to add 'nomodeset' to the kernel options, everything works as expected.
+ If I connect the monitor to the computer with a DVI cable, everything
+ works as expected.
  
  I do not have the option for HDMI on the monitor currently attached.
- Will see if I can get that tested either with another monitor or DVI to
- HDMI adapter.
+ 
+ WORKAROUND:  Add to the grub menu kernel parameter:
+ nomodeset
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: /dev/sda6: clean, 615456/10196352 files, 5471760/20831539 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: Wed Sep  7 15:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] 
(prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] Sumo [Radeon HD 6410D] 
[1462:7786]
+  Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] 
(prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] Sumo [Radeon HD 6410D] 
[1462:7786]
  MachineType: MSI MS-7786
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=dafa5f62-dc35-4803-b094-5062e73974b0 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 

[Touch-packages] [Bug 1572667] Re: [Thinkpad T450s] Screen flickering on external monitors with docking station

[Christopher M. Penalver]

Bryan Abhser, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  [Thinkpad T450s] Screen flickering on external monitors with docking
  station

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Gnome 16.04 RC.
  Screen does flickering some times.
  Intel HD graphics.

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

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

[Dan Streetman]

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

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

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

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

Bug description:
  * Description

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

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

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

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

  * Test Case

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

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

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

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

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

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

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

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

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

  reboot
  exit 0

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

  * Workaround

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

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

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

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

[Touch-packages] [Bug 1224007] Re: mtu not always set properly on bond/vlan interface

[Dan Streetman]

I should note that this is marked as Fix Released in debian, but from
the debian bug comments it just looks like Chris asked for that bug to
be closed as a configuration issue (which this is not).

This is actually only a VLAN issue with higher-than-default mtu.  The
bond does not have anything to do with the problem.  The problem is the
vlan package (required for ifupdown vlan support) installs a udev rule
that triggers for each new interface; it checks the ifupdown
configuration, and creates any corresponding vlan interfaces.  The real
interface and all its vlan interfaces then race to finish udev
processing and notify upstart, which then calls ifup directly on each
interface.  If upstart calls ifup for the vlan before the actual
interface (and the vlan has a high mtu), it will fail while being
brought up.

I think this can be fixed in a similar way to bug 1609367, where the
problem is higher-than-default mtu on ipv6 (i.e. inet6 section);
although in an easier way, since ifupdown already requires the 'vlan'
package for vlan support, and that package provides an if-pre-up script
already.

If we edit the /etc/network/if-pre-up.d/vlan script (from the vlan
package) like below (for trusty, similar patch for x and y), it will
increase the raw device's mtu if needed.

--- vlan.orig   2016-09-08 02:12:55.901172000 +
+++ vlan2016-09-08 02:10:49.213172000 +
@@ -51,7 +51,14 @@
 echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE"
 exit 1
 fi
-ip link set up dev $IF_VLAN_RAW_DEVICE
+if [ -n "$IF_MTU" ]; then
+CUR_DEV_MTU=`cat /sys/class/net/$IF_VLAN_RAW_DEVICE/mtu`
+# increase the vlan raw device mtu if needed
+if [ -n "$CUR_DEV_MTU" ] && [ $CUR_DEV_MTU -lt $IF_MTU ]; then
+MTU_PARAM="mtu $IF_MTU"
+fi
+fi
+ip link set up dev $IF_VLAN_RAW_DEVICE $MTU_PARAM
 vconfig add $IF_VLAN_RAW_DEVICE $VLANID
 fi

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

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

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

Bug description:
  * Description

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

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

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

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

  * Test Case

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

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

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

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

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

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

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

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

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

  reboot
  exit 0

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

  * Workaround

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

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

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Daniel van Vugt]

Invalid for the Mir project. Sounds like it's just another protobuf bug.

Hopefully we won't need to workaround it in Mir, but that's not
completely out of the question. Especially if protobuf3 hits distro
without first getting fixed we won't have much choice.

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

[Dongdong88]

** Description changed:

  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group
  .
  
  Ubuntu version is:
  
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .
  
  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,
  
  -1 mean it will kill all the process .
  
  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0'
  - optopt) " is not right .
  
  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);
  
  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }
  
  (4) the cause
-  sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal this 
jvm process ,it is a normal behavior for hadoop for hadoop could reexcute this 
task. but with kill bug ,it kill all the process belong to a hadoop user .
+  sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .
  
  (5) The way to workaround
-  I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way   .
+  I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

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

Title:
  /bin/kill in ubuntu16.04 has bug in killing process group

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

To 

[Touch-packages] [Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

[Zak Peirce]

While I fully appreciate the work you have taken  in this bug report I
do not feel comfortable running with this workaround in production.

If and when this is resolved I will upgrade these nodes back to 16.04.

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

Title:
  /bin/kill in ubuntu16.04 has bug in killing process group

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal this 
jvm process ,it is a normal behavior for hadoop for hadoop could reexcute this 
task. but with kill bug ,it kill all the process belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way   .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1610499/+subscriptions

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

[Lampros Liontos]

Nope.  Apparently, the issue is with either with PulseAudio or SDL... or
possibly both.  SDL 1.2 does the locking thing when using timer-driven
scheduling, while SDL 2.0 does it when using interrupt-driven
scheduling.  I've already submitted a ticket for SDL, so this should
probably focus on the PulseAudio side of the issue, in case it's
specifically a bug in PA.

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

Title:
  OpenAL Software Silent/Freezes

Status in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1620173] Re: Qt5 5.6 regression: conversion from QVariant to QString is broken

[Mathieu Pellerin]

Timo, yes sorry, you've got the proper link :)

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

Title:
  Qt5 5.6 regression: conversion from QVariant to QString is broken

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

Bug description:
  A regression was introduced in Qt5 5.5 - fixed in 5.7 - whereas
  conversion from QVariant to QString is broken for double and float
  values (you can see more details on this here:
  https://bugreports.qt.io/browse/QTBUG-47192).

  The patch fixing this issue is the following:
  
http://code.qt.io/cgit/qt/qtbase.git/patch/src/corelib/tools/qlocale.h?id=726fed0d67013cbfac7921d3d4613ca83406fb0f

  Would it be possible to apply this patch against the package (based on
  Qt5 5.6.1) Ubuntu 16.10 will ship in October? It's a pretty ugly bug,
  which needs addressing. Hopefully the Qt devs can eventually merge
  this patch onto their 5.6 LTS branch.

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

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

[Touch-packages] [Bug 1620934] Re: QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all apps, dash are just black windows

[Daniel van Vugt]

unity8.log is a little bit flooded and even unity8.log.1 isn't old
enough to show us start-up. Can you please provide unity8.log.[2-9] from
when the bug is occurring?

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

Title:
  QEGLPlatformContext: eglMakeCurrent failed: 3001, nothing works, all
  apps, dash are just black windows

Status in Mir:
  Incomplete
Status in QtMir:
  Incomplete
Status in qtubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

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

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

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Daniel van Vugt]

** Changed in: mir
   Status: Confirmed => Invalid

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

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1031098] Re: Auto-updates should be enabled by default

[Bug Watch Updater]

** Changed in: unattended-upgrades (Debian)
   Status: Unknown => Fix Released

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

Title:
  Auto-updates should be enabled by default

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  situation: 
  minimal ubuntu server image, installation of this package done manually with 
"aptitude install unattended-upgrades".

  problem: 
  unattended-upgrades actually do not happen, because I have to edit config 
files before - but the system does not give me any hint about this - so I just 
install this package and think "great feature, can sleep now very good" - evil 
guys are just waiting for the first remote exploit and they know that I am 
sleeping well while my system gets more vulnarable with every missed security 
update... 

  [Additionally, the documentation about "Automatic updates" - btw, why
  the irritating change of terminology here? - is flawed, see bug filed
  there by me today.]

  I do not understand why unattended-upgrades do not just happen after I
  install this package. This looks like a design error to me and should
  be corrected - this security related feature should be as easy as
  possible to get working. This package should just start working with
  reasonable defaults without any need for the user to edit config
  files.

  And if there is a need to edit config files after installation, the
  user should be informed about this fact right after installation -
  from what I see from doing tests with 12.04 this feature does not just
  start working ootb, but needs manual config file editing after
  installation.

  It would be even better if the installation process will not end
  successfully, if it just installs this package without proper config -
  there is no sense in having an installed package named "unattended-
  upgrades" if these upgrades are actually not going to happen.

  My observations may be wrong. I hope so.

  Thank you very much for your attention!

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Mathew Hodson]

I don't think backporting the new defaults to Precise and Trusty would
be right for an SRU.

On Precise and Trusty, you can set Unattended-Upgrade::Remove-Unused-
Dependencies "true";

This is false by default. Setting it to true will remove *all* unused
dependencies after every unattended upgrade.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Mathew Hodson]

This was fixed in Xenial. The default is now to remove newly unused
dependencies after every unattended upgrade.

---
unattended-upgrades (0.89) unstable; urgency=medium

  [ Michael Vogt ]
  * Add `Unattended-Upgrade::Remove-New-Unused-Dependencies` that
defaults to "yes". This ensures that older kernel
get automatically cleaned up and /boot will not overflow.
LP: #1267059
  * Remove downloaded deb packages after successful installs.
This can be controlled via the option:
`Unattended-Upgrade::Keep-Debs-After-Install`
(Closes: #809428)
  * Only remove debs in the cache dir

  [ Steffen Köhler ]
  * Allow to configure sender email via `Unattended-Upgrade::Sender`

  [ Antti Riikonen ]
  * Minor typo fix in comment

  [ Cleto Martin ]
  * bugfix: non-ascii chars in dpkg log file crashes unattended upgrades
Closes: #812857

  [ James Valleroy ]
  * Set debconf value for auto updates based on current configuration.

  [ Alexandre Detiste ]
  * update French transalation

 -- Michael Vogt   Sat, 30 Jan 2016 16:04:52 +0100

** Tags removed: xenial

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

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

[Dongdong88]

** Description changed:

- The /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group  
 . 
+ when i run hadoop in ubuntu 16.04, ssh will exit, all process which
+ belong to hadoop user will be killed ,through debug ,i found the
+ /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group
+ .
+ 
  Ubuntu version is:
  
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
-  
- (1)The way to repeat this bug 
+ (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .
  
- (2)Cause analysis 
- The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 , 
+ (2)Cause analysis
+ The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,
  
- -1 mean it will kill all the process . 
-  
- (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0' - 
optopt) " is not right .
-  
+ -1 mean it will kill all the process .
+ 
+ (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0'
+ - optopt) " is not right .
+ 
  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
-   case '?':
- if (!isdigit(optopt)) {
- xwarnx(_("invalid argument %c"), optopt);
- kill_usage(stderr);
- } else {
- /* Special case for signal digit negative
-  * PIDs */
- pid = (long)('0' - optopt);
- 
- if (kill((pid_t)pid, signo) != 0)
-  exitvalue = EXIT_FAILURE;
- exit(exitvalue);
- }
- loop=0;
+   case '?':
+ if (!isdigit(optopt)) {
+ xwarnx(_("invalid argument %c"), optopt);
+ kill_usage(stderr);
+ } else {
+ /* Special case for signal digit negative
+  * PIDs */
+ pid = (long)('0' - optopt);
+ 
+ if (kill((pid_t)pid, signo) != 0)
+  exitvalue = EXIT_FAILURE;
+ exit(exitvalue);
+ }
+ loop=0;
  }
+ 
+ (4) the cause
+  sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal this 
jvm process ,it is a normal behavior for hadoop for hadoop could reexcute this 
task. but with kill bug ,it kill all the process belong to a hadoop user . 
   
  
-  
- (4) The way to workaround 
-  I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way   .
+ (5) The way to workaround
+  I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way   .

** Description changed:

  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group
  .
  
  Ubuntu version is:
  
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .
  
  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,
  
  -1 mean it will kill all the process .
  
  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0'
  - optopt) " is not right .
  
  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);
  
  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }
  
  (4) the cause
-  sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal this 
jvm process ,it is a 

[Touch-packages] [Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group

[Dongdong88]

To Zak Peirce (plastikman) : 
  i found this issue when i run hadoop also, after i replace /bin/kill with 
binary from 14.04 , hadoop is ok, i don't meet other issue again, so you also 
can use ubuntu16.04.

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

Title:
  /bin/kill in ubuntu16.04 has bug in killing process group

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group  
 . 
  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

   
  (1)The way to repeat this bug 
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis 
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 , 

  -1 mean it will kill all the process . 
   
  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0' - 
optopt) " is not right .
   
  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);
  
  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }
   

   
  (4) The way to workaround 
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way   .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1610499/+subscriptions

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

[Bug Watch Updater]

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

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in One Hundred Papercuts:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1615039] Re: [FFe] /usr/bin/gnupg --version should be 2.1

[Launchpad Bug Tracker]

This bug was fixed in the package gnupg2 - 2.1.15-1ubuntu2

---
gnupg2 (2.1.15-1ubuntu2) yakkety; urgency=medium

  * Add breaks for software-properties-common at 0.96.24.3 or lower.

 -- Dimitri John Ledkov   Thu, 01 Sep 2016 11:34:12
+0100

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

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

Title:
  [FFe] /usr/bin/gnupg --version should be 2.1

Status in gnupg package in Ubuntu:
  New
Status in gnupg1 package in Ubuntu:
  Fix Committed
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in libconfig-identity-perl package in Ubuntu:
  Fix Released
Status in libgnupg-interface-perl package in Ubuntu:
  Fix Released
Status in python-gnupg package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubuntu-keyring package in Ubuntu:
  Fix Released

Bug description:
  FFe to merge recent changes in debian packaging to make /usr/bin/gnupg
  the modern implementation of gnupg.

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

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

[Touch-packages] [Bug 1615039] Re: [FFe] /usr/bin/gnupg --version should be 2.1

[Launchpad Bug Tracker]

This bug was fixed in the package python-gnupg - 0.3.8-3ubuntu2

---
python-gnupg (0.3.8-3ubuntu2) yakkety; urgency=medium

  * Re-sync with Debian (LP: #1615039)

 -- Jeremy Bicha   Thu, 01 Sep 2016 03:42:27 -0400

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

Title:
  [FFe] /usr/bin/gnupg --version should be 2.1

Status in gnupg package in Ubuntu:
  New
Status in gnupg1 package in Ubuntu:
  Fix Committed
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in libconfig-identity-perl package in Ubuntu:
  Fix Released
Status in libgnupg-interface-perl package in Ubuntu:
  Fix Released
Status in python-gnupg package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubuntu-keyring package in Ubuntu:
  Fix Released

Bug description:
  FFe to merge recent changes in debian packaging to make /usr/bin/gnupg
  the modern implementation of gnupg.

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

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

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

[Mathew Hodson]

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

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1031098] Re: Design flaw: does nothing after install? split package into {, -core} ?

[Mathew Hodson]

I believe this is fixed in Xenial and auto-updates should be enabled by
default.

---
unattended-upgrades (0.90) unstable; urgency=medium

  [ Alexandre Detiste ]
  * tweak a bit the French translations

  [ Michael Vogt ]
  * debian/templates: set unattended-upgrades/enable_auto_updates to
"true" (Closes: #707055)
  * debian/config: set debconf questions about origin/enable to low

 -- Michael Vogt   Thu, 18 Feb 2016 14:05:58 -0800

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: In Progress => Fix Released

** Summary changed:

- Design flaw: does nothing after install? split package into {,-core} ?
+ Auto-updates should be enabled by default

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

Title:
  Auto-updates should be enabled by default

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  situation: 
  minimal ubuntu server image, installation of this package done manually with 
"aptitude install unattended-upgrades".

  problem: 
  unattended-upgrades actually do not happen, because I have to edit config 
files before - but the system does not give me any hint about this - so I just 
install this package and think "great feature, can sleep now very good" - evil 
guys are just waiting for the first remote exploit and they know that I am 
sleeping well while my system gets more vulnarable with every missed security 
update... 

  [Additionally, the documentation about "Automatic updates" - btw, why
  the irritating change of terminology here? - is flawed, see bug filed
  there by me today.]

  I do not understand why unattended-upgrades do not just happen after I
  install this package. This looks like a design error to me and should
  be corrected - this security related feature should be as easy as
  possible to get working. This package should just start working with
  reasonable defaults without any need for the user to edit config
  files.

  And if there is a need to edit config files after installation, the
  user should be informed about this fact right after installation -
  from what I see from doing tests with 12.04 this feature does not just
  start working ootb, but needs manual config file editing after
  installation.

  It would be even better if the installation process will not end
  successfully, if it just installs this package without proper config -
  there is no sense in having an installed package named "unattended-
  upgrades" if these upgrades are actually not going to happen.

  My observations may be wrong. I hope so.

  Thank you very much for your attention!

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

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

[Touch-packages] [Bug 1031098] Re: Design flaw: does nothing after install? split package into {, -core} ?

[Mathew Hodson]

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

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

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

Title:
  Auto-updates should be enabled by default

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  situation: 
  minimal ubuntu server image, installation of this package done manually with 
"aptitude install unattended-upgrades".

  problem: 
  unattended-upgrades actually do not happen, because I have to edit config 
files before - but the system does not give me any hint about this - so I just 
install this package and think "great feature, can sleep now very good" - evil 
guys are just waiting for the first remote exploit and they know that I am 
sleeping well while my system gets more vulnarable with every missed security 
update... 

  [Additionally, the documentation about "Automatic updates" - btw, why
  the irritating change of terminology here? - is flawed, see bug filed
  there by me today.]

  I do not understand why unattended-upgrades do not just happen after I
  install this package. This looks like a design error to me and should
  be corrected - this security related feature should be as easy as
  possible to get working. This package should just start working with
  reasonable defaults without any need for the user to edit config
  files.

  And if there is a need to edit config files after installation, the
  user should be informed about this fact right after installation -
  from what I see from doing tests with 12.04 this feature does not just
  start working ootb, but needs manual config file editing after
  installation.

  It would be even better if the installation process will not end
  successfully, if it just installs this package without proper config -
  there is no sense in having an installed package named "unattended-
  upgrades" if these upgrades are actually not going to happen.

  My observations may be wrong. I hope so.

  Thank you very much for your attention!

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

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

[Touch-packages] [Bug 1085218] Re: upgrade to kernel 2.6.32-45 fails with "disk full error"

[Mathew Hodson]

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

** This bug is no longer a duplicate of bug 1089195
   linux-headers will eat your inodes on LTS.
** This bug has been marked a duplicate of bug 1357093
   Kernels not autoremoving, causing out of space error on LVM or Encrypted 
installation or on any installation, when /boot partition gets full

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

Title:
  upgrade to kernel 2.6.32-45 fails with "disk full error"

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Unable to upgrade the package 'linux-headers-2.6.32-45' either using
  Update Manager or apt-get.

  Error: There are almost 3GB of free space, but apt-get says no disk
  space. See below for details.

  I attempted the usual tricks like apt-get clean, autoclean,
  autoremove, but it made no change.

  Kind Regards.

  $ sudo apt-get upgrade

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be upgraded:
linux-headers-2.6.32-45
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 10.2MB of archives.
  After this operation, 0B of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Get:1 http://mirror.anl.gov/pub/ubuntu/ lucid-updates/main 
linux-headers-2.6.32-45 2.6.32-45.100 [10.2MB]
  Fetched 10.2MB in 0s (11.7MB/s)   
  (Reading database ... 598967 files and directories currently installed.)
  Preparing to replace linux-headers-2.6.32-45 2.6.32-45.99 (using 
.../linux-headers-2.6.32-45_2.6.32-45.100_all.deb) ...
  Unpacking replacement linux-headers-2.6.32-45 ...
  dpkg: error processing 
/var/cache/apt/archives/linux-headers-2.6.32-45_2.6.32-45.100_all.deb 
(--unpack):
   unable to create 
`/usr/src/linux-headers-2.6.32-45/arch/s390/include/asm/nmi.h.dpkg-new' (while 
processing `./usr/src/linux-headers-2.6.32-45/arch/s390/include/asm/nmi.h'): No 
space left on device
  No apport report written because the error message indicates a disk full error

dpkg-deb: subprocess paste killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-2.6.32-45_2.6.32-45.100_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ df -h

  FilesystemSize  Used Avail Use% Mounted on
  /dev/sda5 9.4G  6.2G  2.8G  70% /
  none  2.0G  388K  2.0G   1% /dev
  none  2.0G  212K  2.0G   1% /dev/shm
  none  2.0G  360K  2.0G   1% /var/run
  none  2.0G 0  2.0G   0% /var/lock
  none  2.0G 0  2.0G   0% /lib/init/rw
  /dev/sda6  94G   45G   45G  51% /home

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: apt 0.7.25.3ubuntu9.14
  ProcVersionSignature: Ubuntu 2.6.32-45.99-generic-pae 2.6.32.60+drm33.26
  Uname: Linux 2.6.32-45-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Nov 30 15:33:28 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: apt

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

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

[Touch-packages] [Bug 1446552] Re: Unattended upgrades handles new dependencies inconsistently

[Mathew Hodson]

** No longer affects: unattended-upgrades (Ubuntu Wily)

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

Title:
  Unattended upgrades handles new dependencies inconsistently

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When an installed package adds a dependency that is not yet installed
  on the system, this sometimes causes the package to not be installed,
  depending on the origin containing the original candidate version.

  I believe that the problem is in /usr/bin/unattended-upgrade, line
  102. Here a check is performed to prevent downgrades. However, as a
  side effect it also prevents adjusting the candidate version for
  packages that have not yet been installed (because pkg.is_upgradable
  is False for packages that have not been installed).

  This makes updating private packages using unattended-upgrades
  troublesome, especially when new dependencies have been added.
  Currently it requires repackaging the dependencies with a slightly
  higher version number than what is in the main repository, and then
  hosting them on the private repository, which is time consuming and
  error-prone. With the included patch, it is sufficient to just host
  the same version on the private repository.

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

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

[Touch-packages] [Bug 1585771] Re: Automatic security upgrades are always enabled

[Mathew Hodson]

** No longer affects: unattended-upgrades (Ubuntu)

** No longer affects: unattended-upgrades (Ubuntu Xenial)

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

Title:
  Automatic security upgrades are always enabled

Status in pkgsel package in Ubuntu:
  Fix Released
Status in pkgsel source package in Xenial:
  Fix Released

Bug description:
  After installing 16.04 server and selecting the option "no automatic
  upgrades" the system will still be configured to automatically perform
  security upgrades.

  $ cat /etc/apt/apt.conf.d/20auto-upgrades 
  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Unattended-Upgrade "1";

  $ head -n 8 /etc/apt/apt.conf.d/50unattended-upgrades 
  // Automatically upgrade packages from these (origin:archive) pairs
  Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
  //"${distro_id}:${distro_codename}-updates";
  //"${distro_id}:${distro_codename}-proposed";
  //"${distro_id}:${distro_codename}-backports";
  };

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

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

[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot

[igor]

im not sure, but looks the problem i have here is the same problem 14.04

gave up waiting for root device
common problems:
--boot arts (cat /proc/cmdline)
-check root delay (did the system wait long enough?)
-check root (did the system wait for the right device?)
-missing modules ls/dev
ALERT! /dev/mapper/ubuntu-vg-root noes not exist!
droping to a shell.
budt box 1.21.1 (ubuntu 1.1.21.0-1ubuntu1) built-in-shell (ash)
enter 'help' for a list of built-in- commants
(initramfs)


on a live cd>

ubuntu@ubuntu:~$ sudo lvm lvscan 
  ACTIVE'/dev/ubuntu-vg2/root' [929.36 GiB] inherit


ubuntu@ubuntu:~$ sudo mkdir /newroot
ubuntu@ubuntu:~$ sudo mount /dev/ubuntu-vg2/root /newroot
mount: special device /dev/ubuntu-vg2/root does not exist

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

Title:
  LVM VG is not activated during system boot

Status in One Hundred Papercuts:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  Hi all,

  I open this report based on the linked conversation I had on the linux-lvm 
mailing list, and the Ask Ubuntu question I posted regarding this case.
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
  https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
  
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot

  I have 2 VGs on my system, and for some reason, only one of them gets
  activated during the initrd boot sequence, which doesn't have my root
  LV, so my boot sequence halts with an initrd prompt.

  When I get to the initrd BusyBox prompt, I can see my LVs are inactive
  with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
  boot sequence continues as I exit the BusyBox prompt. The expected
  behaviour would be that both VGs should activate automatically.

  On LVM mailing list, I've been advised it may be a problem with Ubuntu
  initrd scripts, hence I report this problem here. (I'm not sure if I'm
  reporting it to the correct place by assigning it to "linux", but I
  didn't find a package directly related to the initrd only, so I
  assumed initrd scripts are maintained by the kernel team. If you think
  it's an error, and know the correct package, please reassign!) Our
  suspicion is, initrd prematurely issues "vgchange -ay" before all the
  PVs come online. This makes sense.

  I already tried to set the "rootdelay" kernel parameter to make initrd
  wait longer for the boot LV to come up, but it didn't work. Note
  however, it worked with previous kernel versions.

  The problem came up when I upgraded to Utopic, and got kernel 
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty 
(vmlinuz-3.13.0-37-generic), it works fine.
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.16.0-23-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit 
code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
  InstallationDate: Installed on 2013-12-06 (354 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: WinFast 6150M2MA
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@ 
rootdelay=300
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UnreportableReason: The report belongs to a package 

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

[seeker5528]

Christopher, I filed the report and subscribled you.

For others following here.

Did also find out in my case it happens when the monitor is attached
with a VGA cable.

It does not happen if I use a DVI cable to connect the monitor.

Still have to test have to test with monitor connected on HDMI port.

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

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 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))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  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: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1621265] [NEW] lose monitor during boot up if I don't add 'nomodeset' to kernel options

[seeker5528]

Public bug reported:

If I connect my monitor to my computer with a VGA cable, I have to stop
at the grub menu and add 'nomodeset' to the kernel options with all the
4.4.0-* kernels.

If I do not add 'nomodeset' to the kernel options, my monitor goes
blank, complains of no video signal, then goes to sleep as soon as the
kernel attempts to enable mode setting.

Turning the monitor off and back on does not help, unplugging the VGA
cable and connecting the DVI cable does not help. I have to hit
'Ctrl'+'Alt'+'Del' and wait for the computer to restart or hit the power
button and wait for the computer to shutdown.

If I connect the monitor to the computer with a DVI cable, I do not have
to add 'nomodeset' to the kernel options, everything works as expected.

I do not have the option for HDMI on the monitor currently attached.
Will see if I can get that tested either with another monitor or DVI to
HDMI adapter.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
BootLog: /dev/sda6: clean, 615456/10196352 files, 5471760/20831539 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: Wed Sep  7 15:46:17 2016
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Sumo [Radeon HD 6410D] 
[1462:7786]
MachineType: MSI MS-7786
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=dafa5f62-dc35-4803-b094-5062e73974b0 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128
 M vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A55M-P25 (MS-7786)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd05/14/2012:svnMSI:pnMS-7786:pvr1.0:rvnMSI:rnA55M-P25(MS-7786):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7786
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-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: Wed Sep  7 15:33:21 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHID 413c:3010MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 reproducible single-occurrence ubuntu 
yakkety

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

Title:
  lose monitor during boot up if I don't add 

[Touch-packages] [Bug 1603620] Re: Unattended upgrades does not upgrade kernel even if new one is available.

[Mathew Hodson]

Since it did upgrade, it seems like the package list just had not been
synchronized yet.

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

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

Title:
  Unattended upgrades does not upgrade kernel even if new one is
  available.

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Newest kernel available currently is 4.4.0-31-generic, but

  $ linux-version list
  4.2.0-38-generic
  4.4.0-24-generic
  4.4.0-28-generic

  `apt-get dist-upgrade` does not upgrade kernel either, unless I run
  `apt-get update` first.

  I wonder why kernel was not upgraded 2016-07-16 morning.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jul 16 11:40:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (237 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (21 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-02-15T22:39:19.560937
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2016-06-24T18:13:45.181749

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Mathew Hodson]

** Tags added: precise trusty xenial

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[Seth Arnold]

eproust, could you run dmesg | grep DENIED to see if there are AppArmor
denials blocking your server?

Thanks

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[eproust]

Bad news...

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1598759] Re: incomplete apparmor definition for ntpd

[Joshua Powers]

@knz, can you verify this still exists on your system and if so:

* Provide the version of ntp and apparmor you are using
* Command or what you do to get the error to show up

I was unable to reproduce on both xenial and yakkety. The versions I had
available to me are below and the only DENIED messages from
/var/log/kern.log are below in each instance when I ran 'sudo ntpd'

yakkety
---
powersj@ubuntu:/var/log$ dpkg -l | grep ntp
ii  ntp  1:4.2.8p8+dfsg-1ubuntu1   
amd64Network Time Protocol daemon and utility programs
powersj@ubuntu:/var/log$ dpkg -l | grep apparmor
ii  apparmor 2.10.95-4ubuntu4  
amd64user-space parser utility for AppArmor

Sep  7 17:44:17 ubuntu kernel: [  138.147239] audit: type=1400 
audit(1473284657.365:17): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=2179 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Sep  7 17:44:17 ubuntu kernel: [  138.147316] audit: type=1400 
audit(1473284657.365:18): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=2179 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


xenial
---
ubuntu@xenial:~$ dpkg -l | grep ntp
ii  ntp  1:4.2.8p4+dfsg-3ubuntu5.1   amd64  
  Network Time Protocol daemon and utility programs
ubuntu@xenial:~$ dpkg -l | grep apparmor
ii  apparmor 2.10.95-0ubuntu2.2  amd64  
  user-space parser utility for AppA

Sep  7 22:04:18 ubuntu kernel: [   60.182587] audit: type=1400 
audit(1473285858.665:15): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=3265 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Sep  7 22:04:18 ubuntu kernel: [   60.182675] audit: type=1400 
audit(1473285858.665:16): apparmor="DENIED" operation="open" 
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=3265 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

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

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

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

Title:
  incomplete apparmor definition for ntpd

Status in apparmor package in Ubuntu:
  Incomplete
Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  On this plain install of Xenial apparmor complains about ntpd:

  [   19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0
  [   23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" 
operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" 
pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0

  Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the
  problem:

  #include 

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Mathew Hodson]

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

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

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[Steve Langasek]

Ok, your 'systemctl show' output matches the default by all relevant
measures, and the only modified conffile is the expected one (your dhcpd
config).  So I'm afraid this brings us no closer to understanding why
this fails for some people and not for others.

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1275376] Re: apt-get autoremove should leave (n-1)th kernel

[Mathew Hodson]

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

** This bug is no longer a duplicate of bug 1440608
   /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except 
the latest one
** This bug has been marked a duplicate of bug 1429041
   Autoremoval not working reliably

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

Title:
  apt-get autoremove should leave (n-1)th kernel

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Running autoremove tonight on a 13.10 machine being upgraded to 14.04,
  I was informed by apt-get that I could delete no longer needed kernel
  packages with autoremove.  When I did so I was left with just the
  current kernel.  I suggest that autoremove should always leave the
  (n-1)th kernel behind.  Otherwise users cannot revert to the previous
  kernel if something goes wrong.  I believe this has been the default
  behavior for "apt-get autoremove" for some time now.

  You could argue that if a user is able to run autoremove, then there
  is no point to keeping the previous kernel image.  I disagree.  Users
  may not test out all their connected devices before running autoremove
  and then discover they cannot use a camera or audio device.

  Release: 14.04 (Trusty)
  Package: apt, Version: 0.9.14.1ubuntu2  (and earlier)
  Expected: "apt-get autoremove" would leave current and prior kernel images 
installed
  Actual: only current kernel image remains

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

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

[Mathew Hodson]

Autoremoval issues for Trusty were solved in Bug #1429041

** Tags removed: trusty utopic

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

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in One Hundred Papercuts:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Unknown

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621210] Re: [MIR] fonts-android

[Gunnar Hjalmarsson]

I suppose this is due to . In Ubuntu
(and flavors) previous fonts-droid depends/recommends were replaced with
fonts-noto-cjk in Xenial; please see
.

Wondering if it would be better in Ubuntu to change that libgs9-common
recommend to fonts-noto-cjk instead. (Maybe also in Debian.)

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

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Incomplete

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1621210/+subscriptions

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

[Touch-packages] [Bug 1613678] Re: [MIR] unity-notifications

[Mathieu Trudel-Lapierre]

Looks good to me; thanks. MIR approved.

** Changed in: unity-notifications (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [MIR] unity-notifications

Status in unity-notifications package in Ubuntu:
  Fix Committed

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is a dependency of unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests

  [Dependencies]
   The whole list of dependencies being MIR'ed is being tracked by 
https://trello.com/b/mab4G8UQ/unity-8-in-16-10
   * None

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

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

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

[Touch-packages] [Bug 1621246] Re: Bluetooth A2DP audio stops after reconnecting headset

[Dan Dascalescu]

The same problem was reported by another user at
https://answers.launchpad.net/ubuntu/+source/alsa-
driver/+question/266299

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

Title:
  Bluetooth A2DP audio stops after reconnecting headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.1 64-bit. DELL E7450 laptop, connected to an LG HBS900
  headset.

  1. Pair the headset
  2. All Settings -> Sound, set the mode to High Fidelity Playback (A2DP Sink) 
(otherwise the sound is horrible)
  3. Test, ensure "Front Left" and "Front Right" sound as they should.
  4. Disconnect the headset via the Bluetooth indicator in the system tray.
  5. Connect the headset to another device and play audio through it (I took a 
call).
  6. Connect back the headset to the laptop.
  7. Attempt to play audio, say in SMPlayer.

  No audio comes through. SMPlayer doesn't advance the seek button.

  8. Run `pulseaudio --kill`.
  9. Reconnect the headset a bunch of times.
  10. In Settings -> Sound, try to set the mode to High Fidelity. Only the 
Headset mode worked, with mono sound. When I'd change the value to High 
Fidelity, the active sound device moved to the internal sound card.

  After a couple more reconnections, I could finally get A2DP sound
  again.

  However, the sound SKIPS randomly a couple times a minute (bug
  405294). Playing the exact same MP3 with the exact same player
  (SMPlayer) on Kubuntu 16.04.1 doesn't reproduce this problem, despite
  presumably using the same Bluetooth stack.

  Super frustrating.

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

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

[Touch-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[Paul White]

** Description changed:

  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.
  
- The text of loaded files shows against the desktop wallpaper.
+ The text of loaded files shows against the desktop wallpaper but when no
+ files are loaded gedit displays its edit window or pane as it should do.
+ 
+ To clarify this bug is only apparent when a file is loaded.
  
  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[eproust]

# debsums -e isc-dhcp-server
/etc/init.d/isc-dhcp-server   OK
/etc/dhcp/dhcpd.conf  FAILED
/etc/logcheck/ignore.d.server/isc-dhcp-server OK
/etc/init/isc-dhcp-server6.conf   OK
/etc/apparmor.d/usr.sbin.dhcpdOK
/etc/init/isc-dhcp-server.confOK


** Attachment added: "isc-dhcp-server-systemctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+attachment/4736440/+files/isc-dhcp-server-systemctl.txt

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1621246] [NEW] Bluetooth A2DP audio stops after reconnecting headset

[Dan Dascalescu]

Public bug reported:

Ubuntu 16.04.1 64-bit. DELL E7450 laptop, connected to an LG HBS900
headset.

1. Pair the headset
2. All Settings -> Sound, set the mode to High Fidelity Playback (A2DP Sink) 
(otherwise the sound is horrible)
3. Test, ensure "Front Left" and "Front Right" sound as they should.
4. Disconnect the headset via the Bluetooth indicator in the system tray.
5. Connect the headset to another device and play audio through it (I took a 
call).
6. Connect back the headset to the laptop.
7. Attempt to play audio, say in SMPlayer.

No audio comes through. SMPlayer doesn't advance the seek button.

8. Run `pulseaudio --kill`.
9. Reconnect the headset a bunch of times.
10. In Settings -> Sound, try to set the mode to High Fidelity. Only the 
Headset mode worked, with mono sound. When I'd change the value to High 
Fidelity, the active sound device moved to the internal sound card.

After a couple more reconnections, I could finally get A2DP sound again.

However, the sound SKIPS randomly a couple times a minute (bug 405294).
Playing the exact same MP3 with the exact same player (SMPlayer) on
Kubuntu 16.04.1 doesn't reproduce this problem, despite presumably using
the same Bluetooth stack.

Super frustrating.

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

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

Title:
  Bluetooth A2DP audio stops after reconnecting headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.1 64-bit. DELL E7450 laptop, connected to an LG HBS900
  headset.

  1. Pair the headset
  2. All Settings -> Sound, set the mode to High Fidelity Playback (A2DP Sink) 
(otherwise the sound is horrible)
  3. Test, ensure "Front Left" and "Front Right" sound as they should.
  4. Disconnect the headset via the Bluetooth indicator in the system tray.
  5. Connect the headset to another device and play audio through it (I took a 
call).
  6. Connect back the headset to the laptop.
  7. Attempt to play audio, say in SMPlayer.

  No audio comes through. SMPlayer doesn't advance the seek button.

  8. Run `pulseaudio --kill`.
  9. Reconnect the headset a bunch of times.
  10. In Settings -> Sound, try to set the mode to High Fidelity. Only the 
Headset mode worked, with mono sound. When I'd change the value to High 
Fidelity, the active sound device moved to the internal sound card.

  After a couple more reconnections, I could finally get A2DP sound
  again.

  However, the sound SKIPS randomly a couple times a minute (bug
  405294). Playing the exact same MP3 with the exact same player
  (SMPlayer) on Kubuntu 16.04.1 doesn't reproduce this problem, despite
  presumably using the same Bluetooth stack.

  Super frustrating.

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

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

[Touch-packages] [Bug 405294] Re: a2dp skips terribly

[Dan Dascalescu]

I'm on Ubuntu 16.04.1, and A2DP Bluetooth audio still skips about twice
a minute, though randomly. I'm playing the same MP3 track on repeat,
using SMPlayer. If I do that in Kubuntu 16.04.1, there are no skips.
This is strange - don't Ubuntu and Kubuntu use the same Bluetooth stack?

I've installed blueman; no improvement.

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

Title:
  a2dp skips terribly

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

[Mathew Hodson]

** No longer affects: linux (Ubuntu)

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

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

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in One Hundred Papercuts:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Unknown

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621243] [NEW] [MIR] mesa-demos

[Launchpad Bug Tracker]

Brian Murray (brian-murray) has assigned this bug to you for mesa-demos in 
Ubuntu:

libqt5gui5 now (as of version 5.6.1+dfsg-3) recommends mesa-utils which
is provided by mesa-demos.


apt-cache show libqt5gui5
Package: libqt5gui5
Priority: optional
Section: libs
Installed-Size: 9369
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian Qt/KDE Maintainers 
Architecture: amd64
Source: qtbase-opensource-src
Version: 5.6.1+dfsg-3ubuntu3~3
Replaces: libqt5egldeviceintegration5 (<< 5.6.0~beta+dfsg-5~), libqt5xcbqpa5 
(<< 5.6.0~beta+dfsg-5~)
Depends: fontconfig, libc6 (>= 2.14), libdrm2 (>= 2.4.25), libegl1-mesa (>= 
7.8.1) | libegl1-x11, libfontconfig1 (>= 2.11.94), libfreetype6 (>= 2.3.5), 
libgbm1 (>= 8.1~0), libgcc1 (>= 1:3.4), libgl1-mesa-glx | libgl1, libglib2.0-0 
(>= 2.12.0), libharfbuzz0b (>= 0.9.11), libice6 (>= 1:1.0.0), libinput10 (>= 
0.15.0), libjpeg8 (>= 8c), libmtdev1 (>= 1.0.8), libpng16-16 (>= 1.6.2-1), 
libqt5core5a (>= 5.6.1), libqt5dbus5 (>= 5.0.2), libqt5network5 (>= 5.0.2), 
libsm6, libstdc++6 (>= 5), libudev1 (>= 183), libx11-6, libx11-xcb1, 
libxcb-glx0, libxcb-icccm4 (>= 0.4.1), libxcb-image0 (>= 0.2.1), 
libxcb-keysyms1 (>= 0.4.0), libxcb-randr0 (>= 1.3), libxcb-render-util0, 
libxcb-render0, libxcb-shape0, libxcb-shm0, libxcb-sync1, libxcb-xfixes0, 
libxcb-xinerama0, libxcb-xkb1, libxcb1 (>= 1.8), libxi6 (>= 2:1.5.99.2), 
libxkbcommon-x11-0 (>= 0.5.0), libxkbcommon0 (>= 0.5.0), libxrender1, 
qtbase-abi-5-6-1, zlib1g (>= 1:1.1.4)
Recommends: libqt5svg5, mesa-utils

** Affects: mesa-demos (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Touch seeded packages (touch-packages)
 Status: Incomplete


** Tags: yakkety
-- 
[MIR] mesa-demos
https://bugs.launchpad.net/bugs/1621243
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is a bug assignee.

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

[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial

[Pat McGowan]

** 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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1586013

Title:
  UITK Date picker broken on xenial

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6
  (right).

  More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting

  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml
  [...]
  FAIL!  : components::DatePicker13API::test_1_changeMinimumBeforeDate() 
Uncaught exception: Cannot call method hasOwnProperty of null
   Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)]

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

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

[Touch-packages] [Bug 1619254] Re: Make sure debian/{control, rules} files are appropriate for arm64

[Pat McGowan]

** Also affects: address-book-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: telephony-service (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: telephony-service (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Make sure debian/{control,rules} files are appropriate for arm64

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-app-launch package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  We found several packages compiled with inappropriate parameters,
  build deps on arm64. So here is the list of the packages with armhf
  and/or arm64 strings in their debian/rules, debian/control:

  ./address-book-app-0.2+16.04.20160823/debian
  ./android-tools-5.1.1r36+git20160322/debian
  ./boost1.58-1.58.0+dfsg/debian
  ./dbus-1.10.6/debian
  ./elfutils-0.165/debian
  ./fftw3-3.3.4/debian
  ./gcc-5-5.4.0/debian
  ./gccgo-6-6.0.1/debian
  ./gdb-7.11.1/debian
  ./glibc-2.23/debian
  ./gnutls28-3.4.10/debian
  ./gst-plugins-bad1.0-1.8.2/debian
  ./hud-14.10+16.04.20160415/debian
  ./indicator-network-0.8.0+16.04.20160817.2/debian
  ./indicator-transfer-0.2+16.04.20160808.1/debian
  ./initramfs-tools-ubuntu-touch-0.94xenial1~overlay1/debian
  ./klibc-2.0.4/debian
  ./libdbusmenu-12.10.3+16.04.20160223.1/debian
  ./libdrm-2.4.67/debian
  ./libertine-1.3.1+16.04.20160812.3/debian
  ./libhybris-0.1.0+git20151016+6d424c9/debian
  ./libusermetrics-1.1.1+16.04.20160808.3/debian
  ./libvpx-1.5.0/debian
  ./libwebp-0.4.4/debian
  ./llvm-toolchain-3.8-3.8/debian
  ./location-service-3.0.0+16.04.20160811/debian
  ./mesa-11.2.0/debian
  ./mir-0.24.0+16.04.20160815.3/debian
  ./mpdecimal-2.4.2/debian
  ./nspr-4.12/debian
  ./pay-service-15.10+16.04.20160816.1/debian
  ./pulseaudio-8.0/debian
  ./python3.5-3.5.2/debian
  ./qt4-x11-4.8.7+dfsg/debian
  ./qtbase-opensource-src-5.6.1+dfsg/debian
  ./qtfeedback-opensource-src-5.0~git20130529/debian
  ./qtmir-0.4.8+16.04.20160826.1/debian
  ./qtubuntu-0.63+16.04.20160826/debian
  ./qtubuntu-camera-0.3.3+16.04.20160517/debian
  ./qtvideo-node-0.2.1+16.04.20151104/debian
  ./speex-1.2~rc1.2/debian
  ./systemd-229/debian
  ./telepathy-ofono-0.2+16.04.20160719/debian
  ./telephony-service-0.1+16.04.20160601.1/debian
  ./trust-store-2.0.0+16.04.20160119/debian
  ./ubuntu-app-launch-0.9+16.04.20160825/debian
  ./ubuntu-meta-1.361/debian
  ./ubuntu-push-0.68+16.04.20160825.4/debian
  ./ubuntu-system-settings-0.4+16.04.20160826/debian
  ./ubuntu-system-settings-online-accounts-0.7+16.04.20160718/debian
  ./ubuntu-touch-meta-1.264xenial12/debian
  ./ubuntu-ui-toolkit-1.3.2073+16.04.20160824build1~~xenialoverlay1~1/debian
  ./unity-7.4.0+16.04.20160801.2/debian
  ./unity8-8.14+16.04.20160826/debian
  ./unity-api-7.117+16.04.20160819/debian
  ./unity-scope-click-0.1.1+16.04.20160808/debian
  ./wavpack-4.75.2/debian
  ./xorg-7.7+13ubuntu3/debian

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

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

[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

[Pat McGowan]

** Description changed:

  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.
  
  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s
+ 
+ ---
+ 
+ This has been traced to two causes:
+ pam was not installed, it is now a dependency of ubuntu-app-launch or can be 
installed directly
+ $ sudo apt-get install libpam-cgfs
+ 
+ and cgmanager is not enabled by default on systems that were upgraded
+ and not clean installs. To enable it
+ 
+ $ sudo systemctl enable cgmanager

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

Title:
  applications close instantly when launched from the launcher or dash

Status in Canonical System Image:
  Confirmed
Status in cgmanager package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.

  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s

  ---

  This has been traced to two causes:
  pam was not installed, it is now a dependency of ubuntu-app-launch or can be 
installed directly
  $ sudo apt-get install libpam-cgfs

  and cgmanager is not enabled by default on systems that were upgraded
  and not clean installs. To enable it

  $ sudo systemctl enable cgmanager

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

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

[Touch-packages] [Bug 1620945] Re: Additional dbus patch required for Qt 5.6

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

Title:
  Additional dbus patch required for Qt 5.6

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  The patch from https://codereview.qt-project.org/#/c/170356/ is
  required to fix telephony-service tests and also potential real
  problems.

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

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

[Touch-packages] [Bug 1613977] Re: Timezone gets reset on boot on xenial

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Timezone gets reset on boot on xenial

Status in Canonical System Image:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps:
  * set a timezone in settings app
  * reboot

  Expected:
  * time is correct and datetime indicator shows the timezone

  Current:
  * time is in UTC and datetime indicator shows UTC

  $ system-image-cli -i
  current build number: 1
  device name: frieza
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-08-16 17:09:33
  version version: 1
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160816

  $ cat /etc/timezone 
  Europe/Warsaw
  $ date
  Wed Aug 17 08:11:37 UTC 2016

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

In any case, if protobuf choses to remain resident it is only polite to
work when the startup/shutdown cycle is repeated. (And that's what the
patch achieves.)

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in protobuf package in Ubuntu:
  In Progress

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

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

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

[Touch-packages] [Bug 1580172] Re: UITK unit test failures on arm64

[Pat McGowan]

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

** 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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1580172

Title:
  UITK unit test failures on arm64

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Trying to enable unit tests on xenial arm64, I get the following
  problems:

  ---
  9 failures which MUST be fixed:
    tst_pagehead_visible.qml
    tst_picker.qml
    tst_tabs_with_repeater.DEPRECATED_TOOLBAR.qml
    tst_tabs_with_repeater.qml
    tst_textinput_touch.qml
  ---

  Full build log at https://launchpadlibrarian.net/258791309
  /buildlog_ubuntu-xenial-arm64.ubuntu-ui-
  toolkit_1.3.1960+16.04.20160502+arm64~1_BUILDING.txt.gz

  arm64 builds are fine from UITK perspective, but as arm64 is started
  to be used we should be executing and passing the tests too.

  https://code.launchpad.net/~timo-jyrinki/ubuntu-ui-
  toolkit/enable_arm64_unittests/+merge/292144 can't go in before these
  are fixed.

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

-- 
Mailing list: https://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 1572667] Re: [Thinkpad T450s] Screen flickering on external monitors with docking station

[Bryan Abhser]

I can take over. Not sure what there is to do though.

On Wed, Sep 7, 2016, 1:56 AM bhat3  wrote:

> This bug is still present! I am sorry but i don't have access to the HW
> atm, so someone else needs to take over :)
>
> @Bryan Can you do that?
>
> ** Changed in: xorg (Ubuntu)
>Status: Expired => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1572667
>
> Title:
>   [Thinkpad T450s] Screen flickering on external monitors with docking
>   station
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ubuntu Gnome 16.04 RC.
>   Screen does flickering some times.
>   Intel HD graphics.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572667/+subscriptions
>

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

Title:
  [Thinkpad T450s] Screen flickering on external monitors with docking
  station

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Gnome 16.04 RC.
  Screen does flickering some times.
  Intel HD graphics.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

[Lampros Liontos]

Scratch that; an unrelated issue was resolved, but not this one.
Programs making use of OpenAL are still not making any sound, and still
freezing upon close.

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

Title:
  OpenAL Software Silent/Freezes

Status in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Alan Griffiths]

This shows the problem, but not the underlying cause:

$ gdb bin/mir_test_reload_protobufGNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 
7.11.90.20160906-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"...
Reading symbols from bin/mir_test_reload_protobuf...done.
(gdb) b /home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
No source file named 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 
(/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36) pending.
(gdb) r
Starting program: 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf
 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
MIR_CLIENT_PLATFORM_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/client-modules/
MIR_SERVER_PLATFORM_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/server-modules/
LD_LIBRARY_PATH=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib
exec=/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf.bin
process 2335 is executing new program: 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/mir_test_reload_protobuf.bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, main (argc=1, argv=0x7fffde58) at 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
36  dl = dlopen(libname, RTLD_NOW);
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
(gdb) n
37  if (dl)
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
0x77360c60  0x773c3e86  Yes 
/home/alan/.CLion2016.2/system/cmake/generated/mir-9ec817d/9ec817d/Debug/bin/../lib/libmirprotobuf.so.3
0x7710ddd0  0x7712a3c6  Yes 
/usr/local/lib/libprotobuf-lite.so.10
0x76df8900  0x76ea7c79  Yes (*) 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
0x76b58a90  0x76b688e5  Yes (*) 
/lib/x86_64-linux-gnu/libgcc_s.so.1
0x76852710  0x768c3bfa  Yes 
/lib/x86_64-linux-gnu/libm.so.6
(*): Shared library is missing debugging information.
(gdb) c
Continuing.
[0] dlopen `libmirprotobuf.so.3' = 0x557564c0

Breakpoint 1, main (argc=1, argv=0x7fffde58) at 
/home/alan/display_server/mir/tests/loader-tests/test_reload.c:36
36  dl = dlopen(libname, RTLD_NOW);
(gdb) info share
>FromTo  Syms Read   Shared Object Library
0x77dd8aa0  0x77df6130  Yes /lib64/ld-linux-x86-64.so.2
0x77bd4d80  0x77bd598e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x779bba60  0x779c8e01  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x7760e9c0  0x7775f0c3  Yes 
/lib/x86_64-linux-gnu/libc.so.6
0x7710ddd0  0x7712a3c6  Yes 
/usr/local/lib/libprotobuf-lite.so.10
0x76df8900  0x76ea7c79  Yes (*) 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
0x76b58a90  0x76b688e5  Yes (*) 
/lib/x86_64-linux-gnu/libgcc_s.so.1
0x76852710  0x768c3bfa  Yes 
/lib/x86_64-linux-gnu/libm.so.6
(*): Shared library is missing debugging information.

With protobuf-2.6.1 the libprotobuf-lite library is unloaded at this

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

[Lampros Liontos]

Looks like it is a PulseAudio issue; the problem was resolved when I
reverted PulseAudio to interrupt-driven scheduling (tsched=0).  Since
this isn't the default state of Pulseaudio on new systems, however, this
is more likely a workaround than a solution.

Whether the problem is that a new scheduling system requires new
interfaces, or if the problem is entirely in PulseAudio's
implementation, I honestly don't know.

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

Title:
  OpenAL Software Silent/Freezes

Status in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1499858] Re: bluetoothd[650]: Failed to obtain handles for "Service Changed" characteristic

[Felipe Monteiro Jácome]

It only stop the service if I disable it by bluetooth-manager.
the commands bellow not worked
sudo systemctl stop bluetooth
sudo service bluetooth stop

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

Title:
  bluetoothd[650]: Failed to obtain handles for "Service Changed"
  characteristic

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Failed to obtain 
handles for "Service Changed" characteristic
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Error adding Link 
Loss service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Current Time Service 
could not be registered
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: gatt-time-server: 
Input/output error (5)
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Not enough free 
handles to register service
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: Sap driver 
initialization failed.
  sep 25 11:03:01 username-530U3C-530U4C bluetoothd[650]: sap-server: Operation 
not permitted (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bluez 5.34-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 25 16:37:42 2015
  InstallationDate: Installed on 2015-07-26 (61 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: C4:85:08:6C:01:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:12620731 acl:54193 sco:0 events:799035 errors:0
TX bytes:447934374 acl:1637190 sco:0 commands:1459 errors:0

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

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

[Touch-packages] [Bug 1621226] [NEW] grep does not output null when -o is used

[Jarno Suni]

Public bug reported:

testcase

$ printf 'a\0b\0b1' | grep --null-data --null b | hexdump -C
  62 00 62 31 00|b.b1.|
0005

but

$ printf 'a\0b\0b1' | grep -o --null-data --null b | hexdump -C
  62 0a 62 0a   |b.b.|
0004

This is fixed in Xenial, but IMO should be fixed in Trusty, too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: grep 2.16-1
ProcVersionSignature: Ubuntu 4.4.0-37.56~14.04.1-generic 4.4.19
Uname: Linux 4.4.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep  7 22:48:42 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (717 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
SourcePackage: grep
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  grep does not output null when -o is used

Status in grep package in Ubuntu:
  New

Bug description:
  testcase

  $ printf 'a\0b\0b1' | grep --null-data --null b | hexdump -C
    62 00 62 31 00|b.b1.|
  0005

  but

  $ printf 'a\0b\0b1' | grep -o --null-data --null b | hexdump -C
    62 0a 62 0a   |b.b.|
  0004

  This is fixed in Xenial, but IMO should be fixed in Trusty, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grep 2.16-1
  ProcVersionSignature: Ubuntu 4.4.0-37.56~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep  7 22:48:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (717 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: grep
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1167014] Re: MIssing cmake files

[linas]

Recommend closing this bug...  Here's why.

TL;DR: libopencv-dev provides /usr/share/OpenCV/OpenCVConfig.cmake etc

I experienced a bizarre bug, though:

On xenial (16.04), having a CMakeLists.txt with a find_package(OpenCV
REQUIRED) gave me an error:

CMake Error at CMakeLists.txt:9 (find_package):
  By not providing "FindOpenCV.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "OpenCV", but
  CMake did not find one.

This error leads to a fruitless hunt for FindOpenCV.cmake which leads to
this bug report.  However, the above error should never have happened,
because xenial libopencv-dev does provide the needed files in
/usr/share/OpenCV/  The error went away, for me, after running  cmake
--trace and after that, the error goes away, and becomes
unreproducible(!) (despite being highly reproducible for hours...)  I'm
befuddled. However

TL;DR: libopencv-dev provides /usr/share/OpenCV/OpenCVConfig.cmake etc.

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

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

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

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

[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

[Pat McGowan]

fwiw I bombarded usensord with direct dbus requests simultaneously and
could not reproduce the issue

#!/bin/bash
i=$1
while [ $i -gt 0 ]; do
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
com.canonical.usensord.haptic.Vibrate uint32:500
((i--))
sleep $2
done

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  UPDATE: see comment #5, it turns out it's the haptics plugin doing
  SYNC dbus calls and blocking the UI thread when the dbus service does
  not reply or the replies come with a big delay

  
  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[Brad Larson]

** Description changed:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads me
  to believe it's an intermittent problem with some hardware. This did not
  happen on Ubuntu 15.10 (which was an upgrade of 15.04).
  
  Ubuntu Release:
  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  Pulseaudio Version:
  
  pulseaudio:
-   Installed: 1:8.0-0ubuntu3
-   Candidate: 1:8.0-0ubuntu3
-   Version table:
-  *** 1:8.0-0ubuntu3 500
- 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1:8.0-0ubuntu3
+   Candidate: 1:8.0-0ubuntu3
+   Version table:
+  *** 1:8.0-0ubuntu3 500
+ 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  Device info:
  
- [bluetooth]# info 44:5E:F3:B4:07:29 
+ [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
-   Name: BlueBuds X
-   Alias: BlueBuds X
-   Class: 0x240404
-   Icon: audio-card
-   Paired: yes
-   Trusted: yes
-   Blocked: no
-   Connected: no
-   LegacyPairing: no
-   UUID: Headset   (1108--1000-8000-00805f9b34fb)
-   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
-   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
-   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
-   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
-   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)
+  Name: BlueBuds X
+  Alias: BlueBuds X
+  Class: 0x240404
+  Icon: audio-card
+  Paired: yes
+  Trusted: yes
+  Blocked: no
+  Connected: no
+  LegacyPairing: no
+  UUID: Headset   (1108--1000-8000-00805f9b34fb)
+  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
+  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
+  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
+  UUID: Handsfree (111e--1000-8000-00805f9b34fb)
+  UUID: Unknown   (80ff--1000-8000-00805f9b34fb)
  
  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

Status in pulseaudio package in Ubuntu:
  In Progress

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

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

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

  Device info:

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

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

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

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

[Touch-packages] [Bug 1167014] Re: MIssing cmake files

[linas]

... except that /usr/share/OpenCV/ already contains the required files!
So, in principle, find_package(OpenCV REQUIRED) should just plain work.
So why doesn't it? ??

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

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

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

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

[Touch-packages] [Bug 1621216] [NEW] [MIR] geoclue-2.0

[Launchpad Bug Tracker]

Brian Murray (brian-murray) has assigned this bug to you for geoclue-2.0 in 
Ubuntu:

libqt5positioning5 now recommends geoclue-2.0

+qtlocation-opensource-src (5.6.0-1) experimental; urgency=medium
+
+  [ Lisandro Damián Nicanor Pérez Meyer ]
+  * New upstream release.
+- Bump Qt build dependencies.
+  * Make qtlocation5-examples depend on qml-module-qtpositioning.
+  * Make libqt5positioning5 recommend geoclue-2.0. It will connect to it by
+using dbus.

geoclue-2.0 was previously in main see the MIR for it in bug #1388294.

** Affects: geoclue-2.0 (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Touch seeded packages (touch-packages)
 Status: Incomplete


** Tags: yakkety
-- 
[MIR] geoclue-2.0
https://bugs.launchpad.net/bugs/1621216
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is a bug assignee.

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

[Touch-packages] [Bug 1621210] [NEW] [MIR] fonts-android

[Brian Murray]

Public bug reported:

libgs9-common now recommends fonts-droid-fallback which is provided by
the fonts-android package.  fonts-android used to be in main, see LP:
#1249132 for the previous MIR.

apt-cache show libgs9-common
Package: libgs9-common
Priority: optional
Section: libs
Installed-Size: 5353
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian Printing Team 
Architecture: all
Source: ghostscript
Version: 9.19~dfsg+1-0ubuntu2
Recommends: fonts-droid-fallback

** Affects: fonts-android (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Printing Team (ubuntu-printing)
 Status: Incomplete


** Tags: yakkety

** Changed in: fonts-android (Ubuntu)
 Assignee: (unassigned) => Ubuntu Printing Team (ubuntu-printing)

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

Title:
  [MIR] fonts-android

Status in fonts-android package in Ubuntu:
  Incomplete

Bug description:
  libgs9-common now recommends fonts-droid-fallback which is provided by
  the fonts-android package.  fonts-android used to be in main, see LP:
  #1249132 for the previous MIR.

  apt-cache show libgs9-common
  Package: libgs9-common
  Priority: optional
  Section: libs
  Installed-Size: 5353
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian Printing Team 
  Architecture: all
  Source: ghostscript
  Version: 9.19~dfsg+1-0ubuntu2
  Recommends: fonts-droid-fallback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1621210/+subscriptions

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

[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue

[Frank Heimes]

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

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

** Changed in: openssl-ibmca (Ubuntu)
   Status: New => Confirmed

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

Title:
  openssl engine error if trying to exploit hw crypto on z due to
  library issue

Status in libica package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Confirmed
Status in openssl-ibmca package in Ubuntu:
  Confirmed

Bug description:
  openssl-ibmca usually requires libica2 and libica-utils for proper
  functioning and all required tooling (like icainfo, icastats, etc.)

  But after the installation of these packages and the configuration, with is 
like this:
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo vi /etc/ssl/openssl.cnf
  adding the following line as the first active one:
  openssl_conf = openssl_def
  and removing or commenting all other occurrences of that line in the config 
file
  and saving and closing the openssl.cnf file
  this output of the openssl engine command is expected:

  $ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support

  or even more precise these chiphers should be listed in case of "-c":

  $ openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, 
DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, 
AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, 
AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512]

  But instead openssl is giving this error, due to a missing "libica.so":
  $ openssl engine
  Error configuring OpenSSL
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load 
the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open 
shared object file: No such file or directory
  4395950360208:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:dso_lib.c:233:
  4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286:
  4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine 
configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1
  4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module 
initialization error:conf_mod.c:223:module=engines, value=engine_section, 
retcode=-1  
  $

  There is no libica.so that is shipped with any of the above packages 
(verified with dpkg -l) or otherwise available in the filesystem:
  $ sudo find / -name "libica.so" 2>/dev/null
  ubuntu@HWE0001:~$ 

  But there is a different verison of that libica:
  $ sudo find / -name "*libica.so*" 2>/dev/null
  /usr/lib/s390x-linux-gnu/libica.so.2
  /usr/lib/s390x-linux-gnu/libica.so.2.6.1
  $ 

  So there are right now two workarounds:
  1)
  creating a (symbolic) link from libica.so.2 to libica.so, like
  $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 
/usr/lib/s390x-linux-gnu/libica.so 
  that allows openssl to find a library named 'libica.so':
  18:15:00: frank.hei...@canonical.com: ubuntu@HWE0001:~$ openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  But this could lead to issues in case of any potential functions or interface 
changes there we introduced with libica.so.2
  2)
  installation of the "libica-dev" package that provides a (development) 
version of libica.so:
  $ dpkg -L libica-dev | grep libica.so
  /usr/lib/s390x-linux-gnu/libica.so
  $

  But the hardware crypto exploitation should work out of the box w/o
  the link or the libica-dev package.

  Either libica.so should be shipped (in addition to libica.so.2) with
  the proper dependency to openssl-ibmca - openssh-ibmca should make use
  of libica2 instead of libica.so.2...

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

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

[Touch-packages] [Bug 1621162] Re: zeitgeist totem plugin not enabled by default

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 16.10.2

---
ubuntu-settings (16.10.2) yakkety; urgency=medium

  * debian/ubuntu-settings.override:
- Skip "Let's Go Shopping" pop-up on first run of Software app.
  This change was accidentally dropped in 16.10.1
- Drop totem override that doesn't work (LP: #1621162)
- Drop gedit override since the zeitgeist plugin isn't installed
  by default so this override doesn't work either (LP: #1621176)
- Drop font-hinting override; 'slight' is now upstream default
- Tweak Epiphany search URL and update GNOME Shell favorites
  (copied from ubuntu-gnome-default-settings)

 -- Jeremy Bicha   Wed, 07 Sep 2016 12:57:06 -0400

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  zeitgeist totem plugin not enabled by default

Status in totem package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The zeitgeist totem plugin is not enabled by default. The intent is
  for it to be enabled, see near the bottom of:

  https://bazaar.launchpad.net/~ubuntu-desktop/+junk/ubuntu-
  settings/view/head:/debian/ubuntu-settings.gsettings-override

  - I think that's because the override should be org.gnome.totem instead of 
org.gnome.Totem
  - My understanding is that when totem starts, it loads all the plugin listed 
in gsettings' "enabled-plugins" and loads all plugins that have Builtin=true. 
It then writes the combined list to "enabled-plugins".
  - Every other plugin in the gsettings override is Builtin, so the only 
purpose for that line is to try to activate zeitgeist by default. But this 
method doesn't work for upgraders since the list of plugins is already 
"user-configured" by totem when it runs.
  - Builtin plugins are not show in Preferences>Plugins. They cannot be 
disabled by the user (without editing system files).

  I propose that we set the Zeitgeist plugin to Builtin=true. If someone
  wants to configure Zeitgeist, they should use System Settings>Security
  & Privacy in Unity or install and run activity-log-manager in other
  desktops.

  If people complain (or if this is a problem), we could split the
  Zeitgeist plugin to another package.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: totem-plugins 3.21.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-5.6-generic 4.8.0-rc4
  Uname: Linux 4.8.0-5-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  7 11:55:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1621176] Re: zeitgeist gedit plugin not enabled by default

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 16.10.2

---
ubuntu-settings (16.10.2) yakkety; urgency=medium

  * debian/ubuntu-settings.override:
- Skip "Let's Go Shopping" pop-up on first run of Software app.
  This change was accidentally dropped in 16.10.1
- Drop totem override that doesn't work (LP: #1621162)
- Drop gedit override since the zeitgeist plugin isn't installed
  by default so this override doesn't work either (LP: #1621176)
- Drop font-hinting override; 'slight' is now upstream default
- Tweak Epiphany search URL and update GNOME Shell favorites
  (copied from ubuntu-gnome-default-settings)

 -- Jeremy Bicha   Wed, 07 Sep 2016 12:57:06 -0400

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  zeitgeist gedit plugin not enabled by default

Status in gedit-plugins package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  This is similar to totem bug 1621162 except that gedit doesn't have
  "builtin" plugins.

  ubuntu-settings has this override:
  [org.gnome.gedit.plugins]
  active-plugins = ['docinfo', 'modelines', 'filebrowser', 'spell', 'time', 
'zeitgeistplugin']

  This would work except that the zeitgeist plugin is not installed by
  default (it's bundled with gedit-plugins which is in universe). The
  first time gedit is run, it removes 'zeitgeistplugin' from 'active-
  plugins' because it can't find the plugin. This means that if a user
  later installs gedit-plugins, the zeitgiest plugin still won't be
  enabled.

  Proposed fixes:
  1. Have gedit recommend gedit-plugins. Or…
  2. Split the zeitgeist plugin to its own binary package, promote that to 
main, and have gedit recommend it. Or…
  3. Drop the override since it's not working anyway (the other plugins in that 
list are already set in the upstream schema). Or…
  4. Work with upstream for a better way for certain plugins to be enabled by 
default.

  For now, I'm going to go with #3 because it's easiest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1621176/+subscriptions

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

[Dmitry Shachnev]

Thanks for testing!

I'll try to get that patch included in the next Qt upload. Also
submitted upstream: https://codereview.qt-project.org/170467.

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions

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

[Touch-packages] [Bug 1167014] Re: MIssing cmake files

[linas]

... except that I am unable to find any version of FindOpenCV.cmake that
actually works with the OpenCV that is provided in trusty or xenial
(14.04 or 16.04) -- one of many problems is that the way that the opencv
version numbers are specified is not compatible with how version numbers
used to be specified(!)  After fixing this, additional bugs appear.

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

Title:
  MIssing cmake files

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  This two files are part of libopencv-core-dev package in 12.04:
  /usr/share/OpenCV/OpenCVConfig.cmake
  /usr/share/OpenCV/OpenCVConfig-version.cmake

  But they disappeared in 12.10 and 13.04.
  This is causing problems when compiling projects using cmake and opencv.

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

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

[Touch-packages] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  [enhancement] Support copy-paste between X and Mir

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Fix Released
Status in Libertine devel series:
  Fix Released
Status in Libertine trunk series:
  Fix Released
Status in Mir:
  Fix Released
Status in content-hub package in Ubuntu:
  In Progress
Status in libertine package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  X applications should be able to paste from Mir applications and vice
  versa.

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

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

[Touch-packages] [Bug 1604009] Re: Empty menus in global app-menu in VirtualBox second window

[Michael Thayer]

Sorry for the noise.  After fixing my change the local menus are gone.

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

Title:
  Empty menus in global app-menu in VirtualBox second window

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Reporting this following this IRC discussion:

  https://irclogs.ubuntu.com/2016/07/15/%23ubuntu-devel.html#t14:00

  The basic summary: when I run a two-screen/two-window virtual machine
  with VirtualBox under Ubuntu 16.04 with Unity and the global app-menu,
  the menus are empty when the second screen window has the input focus.
  During start-up I get a number (55) of these messages on the console:

  Qt WARNING: void
  DBusMenuExporterPrivate::fillLayoutItem(DBusMenuLayoutItem*, QMenu*,
  int, int, const QStringList&): No id for action

  and a number (7) of these:

  Qt WARNING: uint DBusMenuExporterDBus::GetLayout(int, int, const
  QStringList&, DBusMenuLayoutItem&): Condition failed: menu

  Then another 55 of the first and two of the second.

  Looking at the interesting parts of the VirtualBox source code, I see
  that the menu items for the first window (menu displayed correctly)
  and the second (not displayed) share the same QAction objects.  A very
  quick guess is that this might be triggering the condition in
  DBusMenuExporterPrivate::addMenu().

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libdbusmenu-qt5 0.9.3+16.04.20160218-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 18 15:44:00 2016
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.1
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.1
  InstallationDate: Installed on 2016-05-31 (48 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1604009/+subscriptions

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

[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

[Jeremy Bicha]

Test Case works.

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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

[Touch-packages] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04

[Jeremy Bicha]

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

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

Title:
  Switch user feature has disappeared from GNOME Shell since upgrade
  from 15.10 to 16.04

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Fix Committed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed
Status in accountsservice package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu 16.04's accountsservice was built without systemd support because 
systemd dropped libsystemd-login because that functionality was merged into 
libsystemd.

  At a minimum, this broke GNOME Shell's "Switch User" feature.

  Test Case
  =
  1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages.
  2. Add a user if necessary to ensure you have at least 2 user accounts 
configured.
  3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower 
case letter r. Or you can log out of all user accounts and log back in.
  4. Click the system status area in the top right of GNOME Shell.
  5. Click your user name. "Switch User" should appear in the list.

  Regression Potential
  
  None.
  The one-line change to accountsservice's configure check was made in Debian's 
accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was 
included in accountsservice 0.6.42 released in June.

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

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

[Touch-packages] [Bug 1613698] Update Released

[Chris J Arges]

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

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-Encoded 
data") introduced in curl 7.35.0 
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  [ test case]
  * curl -v 'http://curl.haxx.se/download/' 
  (this might work on some configurations)

  
  [ fix ]

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!

  [Regression Potential] 
  * none, fix comes from upstream, and is a fix of a bad commit

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

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

[Touch-packages] [Bug 1613698] Re: curl: Problem with chunked encoded data

[Launchpad Bug Tracker]

This bug was fixed in the package curl - 7.35.0-1ubuntu2.9

---
curl (7.35.0-1ubuntu2.9) trusty; urgency=medium

  [ Joe Afflerbach ]
  * debian/patches/curl-chunk-fix.patch:
- fix problem with chunked encoded data (LP: #1613698)

 -- Gianfranco Costamagna   Sun, 28 Aug 2016
21:27:34 +0200

** Changed in: curl (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  curl: Problem with chunked encoded data

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-Encoded 
data") introduced in curl 7.35.0 
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).

  See the corresponding thread on the curl mailing list:
  * https://curl.haxx.se/mail/lib-2014-02/0100.html
  * https://curl.haxx.se/mail/lib-2014-02/0108.html

  Googling for "Problem (2) in the Chunked-Encoded data" shows that this seems 
to be a problem for other Ubuntu users, too. For example:
  * 
https://github.com/jackalope/jackalope-jackrabbit/issues/89#issuecomment-55084492
  * 
https://www.mastizada.com/blog/chunked-encoded-data-error-in-php-curl-requests/
  * https://bugs.php.net/bug.php?id=72131

  [ test case]
  * curl -v 'http://curl.haxx.se/download/' 
  (this might work on some configurations)

  
  [ fix ]

  The issue was fixed in curl 7.36.0 with
  https://github.com/curl/curl/commit/0ab97ba0090f2609760c33000181f08757336a48

  If you apply that patch to curl in Ubuntu 14.04, I'm sure you'll make
  a lot of people happy - including me. Thanks!

  [Regression Potential] 
  * none, fix comes from upstream, and is a fix of a bad commit

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

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

[Touch-packages] [Bug 1621162] Re: zeitgeist totem plugin not enabled by default

[Launchpad Bug Tracker]

This bug was fixed in the package totem - 3.21.91-0ubuntu2

---
totem (3.21.91-0ubuntu2) yakkety; urgency=medium

  * Add ubuntu-make-zeitgeist-plugin-builtin.patch:
- Make sure that zeitgeist plugin is enabled by default (LP: #1621162)

 -- Jeremy Bicha   Wed, 07 Sep 2016 12:21:05 -0400

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

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

Title:
  zeitgeist totem plugin not enabled by default

Status in totem package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The zeitgeist totem plugin is not enabled by default. The intent is
  for it to be enabled, see near the bottom of:

  https://bazaar.launchpad.net/~ubuntu-desktop/+junk/ubuntu-
  settings/view/head:/debian/ubuntu-settings.gsettings-override

  - I think that's because the override should be org.gnome.totem instead of 
org.gnome.Totem
  - My understanding is that when totem starts, it loads all the plugin listed 
in gsettings' "enabled-plugins" and loads all plugins that have Builtin=true. 
It then writes the combined list to "enabled-plugins".
  - Every other plugin in the gsettings override is Builtin, so the only 
purpose for that line is to try to activate zeitgeist by default. But this 
method doesn't work for upgraders since the list of plugins is already 
"user-configured" by totem when it runs.
  - Builtin plugins are not show in Preferences>Plugins. They cannot be 
disabled by the user (without editing system files).

  I propose that we set the Zeitgeist plugin to Builtin=true. If someone
  wants to configure Zeitgeist, they should use System Settings>Security
  & Privacy in Unity or install and run activity-log-manager in other
  desktops.

  If people complain (or if this is a problem), we could split the
  Zeitgeist plugin to another package.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: totem-plugins 3.21.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-5.6-generic 4.8.0-rc4
  Uname: Linux 4.8.0-5-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  7 11:55:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

[David Kalnischkies]

1. Removing the _apt user is really not needed nor a good idea. Its enough to 
have this in a config file:
APT::Sandbox::User "root"; // remove file again after testing!
2. Symlinking /usr/bin/gpgv to /bin/true will never work as verifying 
signatures is more involved then just checking the exit code… there are ways to 
have a similar effect, but as that would be an enormous security hole I am not 
going to describe it here for fear of someone blindly copying it. Obviously NOT 
a good idea at all.

Now that we have that out of the way two "common" problems:
1. Check that /tmp has reasonable permissions. It should have 1777 and be owned 
by root:root.
2. ls -ld /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d /etc/apt/trusted.gpg.d/*
Everything shown should be owned by root:root and everything world-readable (= 
the last of the three r's).

(the first is hard to detect, the second has a proper warning in newer
apt versions)

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

Title:
  apt-key works fine, yet apt fails with "Could not execute 'apt-key'"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Apt can fail to verify a Release file which verifies just fine when
  calling apt-key directly.

  Please advise how i can supply further debug information to help fix
  the underlying bug.

  Expected:
  apt-get should only report that a repository is not signed when no such 
signature was found.
  If a signature was in fact successfully acquired but not verified, apt-get 
should report failure to verify instead.
  apt-get should have a meaningful error message when calling apt-key fails.

  Bonus:
  Calling apt-key should not fail when the same thing works fine on command 
line.
  A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) 
documentation.

  Observed:

  # uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
i686 i686 i686 GNU/Linux
  # chroot reproducable
  $ uname -a
  Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 
armv7l armv7l armv7l GNU/Linux

  $ lsb_release -a 2>/dev/null
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  $ apt-get -o "Debug::Acquire::gpgv=true" update
  Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB]
  0% [1 InRelease gpgv 92.2 kB]igners 
  Preparing to exec:  /usr/bin/apt-key --quiet --readonly verify --status-fd 3 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv exited with status 111
  Summary:
Good: 
Bad: 
Worthless: 
SoonWorthless: 
NoPubKey: 
  Ign:1 http://ports.ubuntu.com xenial-security InRelease
  Fetched 92.2 kB in 1s (79.5 kB/s)
  Reading package lists... Done
  W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not 
execute 'apt-key' to verify signature (is gnupg installed?)
  W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not 
signed.
  N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

  $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr 
/tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using DSA key ID 437D05B5
  [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137
  [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key 
"
  [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 
1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5
  gpgv: Signature made Tue May  3 19:02:17 2016 UTC using RSA key ID C0B21F32
  [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137
  [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) 

  gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) 
"
  [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 
1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32

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

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[Steve Langasek]

eproust, since yours was a fresh install the cause of your problem is
unlikely to be the same.  But you may want to install the debsums
package and check whether any of the files on your system differ from
the ones in the package:

$ sudo apt install debsums
$ debsums -e isc-dhcp-server

You may also want to check that your systemd unit is the expected one,
by running the following command and attaching the resulting file:

systemctl show isc-dhcp-server > isc-dhcp-server-systemctl.txt

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file

[eproust]

Just checked, I have the five capability lines (below) in the
/etc/apparmor.d/usr.sbin.dhcpd of my fresh installed 16.04 and I still
have the issue.

  capability chown,
  capability net_bind_service,
  capability net_raw,
  capability setgid,
  capability setuid,

Ready to try any proposed fix...

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

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

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

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

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

  It looks like a permission problem, because

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions

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

[Touch-packages] [Bug 1621176] [NEW] zeitgeist gedit plugin not enabled by default

[Jeremy Bicha]

Public bug reported:

This is similar to totem bug 1621162 except that gedit doesn't have
"builtin" plugins.

ubuntu-settings has this override:
[org.gnome.gedit.plugins]
active-plugins = ['docinfo', 'modelines', 'filebrowser', 'spell', 'time', 
'zeitgeistplugin']

This would work except that the zeitgeist plugin is not installed by
default (it's bundled with gedit-plugins which is in universe). The
first time gedit is run, it removes 'zeitgeistplugin' from 'active-
plugins' because it can't find the plugin. This means that if a user
later installs gedit-plugins, the zeitgiest plugin still won't be
enabled.

Proposed fixes:
1. Have gedit recommend gedit-plugins. Or…
2. Split the zeitgeist plugin to its own binary package, promote that to main, 
and have gedit recommend it. Or…
3. Drop the override since it's not working anyway (the other plugins in that 
list are already set in the upstream schema). Or…
4. Work with upstream for a better way for certain plugins to be enabled by 
default.

For now, I'm going to go with #3 because it's easiest.

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

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

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

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

Title:
  zeitgeist gedit plugin not enabled by default

Status in gedit-plugins package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This is similar to totem bug 1621162 except that gedit doesn't have
  "builtin" plugins.

  ubuntu-settings has this override:
  [org.gnome.gedit.plugins]
  active-plugins = ['docinfo', 'modelines', 'filebrowser', 'spell', 'time', 
'zeitgeistplugin']

  This would work except that the zeitgeist plugin is not installed by
  default (it's bundled with gedit-plugins which is in universe). The
  first time gedit is run, it removes 'zeitgeistplugin' from 'active-
  plugins' because it can't find the plugin. This means that if a user
  later installs gedit-plugins, the zeitgiest plugin still won't be
  enabled.

  Proposed fixes:
  1. Have gedit recommend gedit-plugins. Or…
  2. Split the zeitgeist plugin to its own binary package, promote that to 
main, and have gedit recommend it. Or…
  3. Drop the override since it's not working anyway (the other plugins in that 
list are already set in the upstream schema). Or…
  4. Work with upstream for a better way for certain plugins to be enabled by 
default.

  For now, I'm going to go with #3 because it's easiest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1621176/+subscriptions

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

[Touch-packages] [Bug 1621176] Re: zeitgeist gedit plugin not enabled by default

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/+junk/ubuntu-settings

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

Title:
  zeitgeist gedit plugin not enabled by default

Status in gedit-plugins package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This is similar to totem bug 1621162 except that gedit doesn't have
  "builtin" plugins.

  ubuntu-settings has this override:
  [org.gnome.gedit.plugins]
  active-plugins = ['docinfo', 'modelines', 'filebrowser', 'spell', 'time', 
'zeitgeistplugin']

  This would work except that the zeitgeist plugin is not installed by
  default (it's bundled with gedit-plugins which is in universe). The
  first time gedit is run, it removes 'zeitgeistplugin' from 'active-
  plugins' because it can't find the plugin. This means that if a user
  later installs gedit-plugins, the zeitgiest plugin still won't be
  enabled.

  Proposed fixes:
  1. Have gedit recommend gedit-plugins. Or…
  2. Split the zeitgeist plugin to its own binary package, promote that to 
main, and have gedit recommend it. Or…
  3. Drop the override since it's not working anyway (the other plugins in that 
list are already set in the upstream schema). Or…
  4. Work with upstream for a better way for certain plugins to be enabled by 
default.

  For now, I'm going to go with #3 because it's easiest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1621176/+subscriptions

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