[Touch-packages] [Bug 1623768] Re: Adapt to new Totem icon name

2016-09-26 Thread Jeremy Bicha
** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Adapt to new Totem icon name

Status in humanity-icon-theme package in Ubuntu:
  Fix Committed
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in moka-icon-theme package in Ubuntu:
  Fix Released
Status in ubuntukylin-theme package in Ubuntu:
  New
Status in xubuntu-artwork package in Ubuntu:
  Fix Committed

Bug description:
  Totem has changed its icon name for easier integration with flatpak

  -Icon=totem
  +Icon=org.gnome.Totem

  If your icon theme will be used in Ubuntu 16.04 LTS also, then I
  recommend making a symlink from the totem icon to the new
  org.gnome.Totem icon. Alternatively, you could drop the icon and let
  users use the high resolution icons shipped by Totem itself.

  See also bug 1618138 which lists some other app icon name changes but
  those icons aren't shipped in all themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+subscriptions

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


[Touch-packages] [Bug 1623768] Re: Adapt to new Totem icon name

2016-09-26 Thread Launchpad Bug Tracker
** Branch linked: lp:~jbicha/+junk/humanity-adapt-to-new-totem-icon-name

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

Title:
  Adapt to new Totem icon name

Status in humanity-icon-theme package in Ubuntu:
  Fix Committed
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in moka-icon-theme package in Ubuntu:
  Fix Released
Status in ubuntukylin-theme package in Ubuntu:
  New
Status in xubuntu-artwork package in Ubuntu:
  Fix Committed

Bug description:
  Totem has changed its icon name for easier integration with flatpak

  -Icon=totem
  +Icon=org.gnome.Totem

  If your icon theme will be used in Ubuntu 16.04 LTS also, then I
  recommend making a symlink from the totem icon to the new
  org.gnome.Totem icon. Alternatively, you could drop the icon and let
  users use the high resolution icons shipped by Totem itself.

  See also bug 1618138 which lists some other app icon name changes but
  those icons aren't shipped in all themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+subscriptions

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


[Touch-packages] [Bug 1543228] Re: Latest update caused removal of ubuntu-make

2016-09-26 Thread Launchpad Bug Tracker
[Expired for ubuntu-make (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Latest update caused removal of ubuntu-make

Status in python3.4 package in Ubuntu:
  Expired
Status in ubuntu-make package in Ubuntu:
  Expired

Bug description:
  The latest updates I did on my Xenial machine caused ubuntu-make to be
  removed.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libqt5xcbqpa5 python3-gnupg python3-progressbar python3-yaml
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED
libpython3.4-minimal libpython3.4-stdlib python3-argcomplete python3.4
python3.4-minimal ubuntu-make
  The following packages will be upgraded:
acl aspell binutils bsdutils findutils gdisk init init-system-helpers
iso-codes language-pack-de language-pack-en language-pack-es
language-pack-fr language-pack-gnome-de language-pack-gnome-en
language-pack-gnome-es language-pack-gnome-fr language-pack-gnome-it
language-pack-gnome-pt language-pack-gnome-ru language-pack-gnome-zh-hans
language-pack-it language-pack-pt language-pack-ru language-pack-zh-hans
libaa1 libacl1 libaspell15 libblkid1 libcaca0 libchromaprint0 libdc1394-22
libfdisk1 libhunspell-1.3-0 libhunspell-1.3-0v5 libio-socket-ssl-perl
libltdl7 libltdl7:i386 libmount1 libmp3lame0 libqt5core5a libqt5dbus5
libqt5gui5 libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5sql5
libqt5sql5-sqlite libqt5test5 libqt5widgets5 libqt5xcbqpa5 libqt5xml5
libsmartcols1 libtheora0 libuuid1 libuuid1:i386 mount psmisc
unattended-upgrades util-linux uuid-runtime wine wine1.6 wine1.6-amd64
wine1.6-i386:i386 xterm
  66 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
  Need to get 72,2 MB of archives.
  After this operation, 31,5 MB disk space will be freed.
  Do you want to continue? [Y/n]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1543228/+subscriptions

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


[Touch-packages] [Bug 1543228] Re: Latest update caused removal of ubuntu-make

2016-09-26 Thread Launchpad Bug Tracker
[Expired for python3.4 (Ubuntu) because there has been no activity for
60 days.]

** Changed in: python3.4 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Latest update caused removal of ubuntu-make

Status in python3.4 package in Ubuntu:
  Expired
Status in ubuntu-make package in Ubuntu:
  Expired

Bug description:
  The latest updates I did on my Xenial machine caused ubuntu-make to be
  removed.

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libqt5xcbqpa5 python3-gnupg python3-progressbar python3-yaml
  Use 'sudo apt autoremove' to remove them.
  The following packages will be REMOVED
libpython3.4-minimal libpython3.4-stdlib python3-argcomplete python3.4
python3.4-minimal ubuntu-make
  The following packages will be upgraded:
acl aspell binutils bsdutils findutils gdisk init init-system-helpers
iso-codes language-pack-de language-pack-en language-pack-es
language-pack-fr language-pack-gnome-de language-pack-gnome-en
language-pack-gnome-es language-pack-gnome-fr language-pack-gnome-it
language-pack-gnome-pt language-pack-gnome-ru language-pack-gnome-zh-hans
language-pack-it language-pack-pt language-pack-ru language-pack-zh-hans
libaa1 libacl1 libaspell15 libblkid1 libcaca0 libchromaprint0 libdc1394-22
libfdisk1 libhunspell-1.3-0 libhunspell-1.3-0v5 libio-socket-ssl-perl
libltdl7 libltdl7:i386 libmount1 libmp3lame0 libqt5core5a libqt5dbus5
libqt5gui5 libqt5network5 libqt5opengl5 libqt5printsupport5 libqt5sql5
libqt5sql5-sqlite libqt5test5 libqt5widgets5 libqt5xcbqpa5 libqt5xml5
libsmartcols1 libtheora0 libuuid1 libuuid1:i386 mount psmisc
unattended-upgrades util-linux uuid-runtime wine wine1.6 wine1.6-amd64
wine1.6-i386:i386 xterm
  66 to upgrade, 0 to newly install, 6 to remove and 0 not to upgrade.
  Need to get 72,2 MB of archives.
  After this operation, 31,5 MB disk space will be freed.
  Do you want to continue? [Y/n]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1543228/+subscriptions

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


[Touch-packages] [Bug 1589550] Re: Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT

2016-09-26 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT

Status in Light Display Manager:
  Incomplete
Status in Mir:
  Expired
Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT.

  The result is a black screen, as Unity8 is running but the system
  defaults to the wrong VT so it's not visible.

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

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


[Touch-packages] [Bug 1589550] Re: Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but doesn't switch to that VT

2016-09-26 Thread Launchpad Bug Tracker
[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT

Status in Light Display Manager:
  Incomplete
Status in Mir:
  Expired
Status in lightdm package in Ubuntu:
  Expired

Bug description:
  Lightdm starts USC (and hence Unity8) on a different VT (8 or 9) but
  doesn't switch to that VT.

  The result is a black screen, as Unity8 is running but the system
  defaults to the wrong VT so it's not visible.

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

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


[Touch-packages] [Bug 1627919] [NEW] package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1

2016-09-26 Thread FernandoCáceres
Public bug reported:

me encontraba instalando un paquete .deb descargado de la página oficial
de mysongbook, similar a lo que sería guitar pro... y el instalador de
paquetes dpkg estalló

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Sep 26 22:49:04 2016
ErrorMessage: el subproceso instalado el script pre-removal devolvió el código 
de salida de error 1
InstallationDate: Installed on 2016-02-11 (228 days ago)
InstallationMedia: It
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: sudo
Title: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el subproceso 
instalado el script pre-removal devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers análisis OK
 /etc/sudoers.d/README análisis OK

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


** Tags: amd64 apport-package xenial

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

Title:
  package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el
  subproceso instalado el script pre-removal devolvió el código de
  salida de error 1

Status in sudo package in Ubuntu:
  New

Bug description:
  me encontraba instalando un paquete .deb descargado de la página
  oficial de mysongbook, similar a lo que sería guitar pro... y el
  instalador de paquetes dpkg estalló

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 26 22:49:04 2016
  ErrorMessage: el subproceso instalado el script pre-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-02-11 (228 days ago)
  InstallationMedia: It
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.2 failed to install/upgrade: el 
subproceso instalado el script pre-removal devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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


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

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

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

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

  $ 

[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

2016-09-26 Thread Daniel van Vugt
** Summary changed:

- 
/usr/bin/unity8-dash:11:QQmlData::isSignalConnected:QObjectPrivate::isSignalConnected:QMetaObject::activate:QMetaObject::activate:QAbstractItemModel::modelAboutToBeReset
+ unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from 
QObjectPrivate::isSignalConnected from QMetaObject::activate from 
QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

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

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
  contains more details.

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

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


[Touch-packages] [Bug 1627799] Re: unity8-dash crashed with SIGEMT on arm in QBasicAtomicOps<4>::ref from QBasicAtomicInteger::ref from QtPrivate::RefCount::ref from QHash:QForeachContainer

2016-09-26 Thread Daniel van Vugt
** Summary changed:

- 
/usr/bin/unity8-dash:7:QBasicAtomicOps:QBasicAtomicInteger:QtPrivate::RefCount::ref:QHash:QForeachContainer
+ unity8-dash crashed with SIGEMT on arm in QBasicAtomicOps<4>::ref from 
QBasicAtomicInteger::ref from QtPrivate::RefCount::ref from 
QHash:QForeachContainer

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

Title:
  unity8-dash crashed with SIGEMT on arm in QBasicAtomicOps<4>::ref
  from QBasicAtomicInteger::ref from QtPrivate::RefCount::ref from
  QHash:QForeachContainer

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cfb4d968ebc83f6253d0122bc0b169214e42cc0d
  contains more details.

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

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


[Touch-packages] [Bug 1627743] Re: arale dash horizontal swipe dip

2016-09-26 Thread Daniel van Vugt
Horizontal Scrolling > Animation Updates shows a significant regression in 
Percent under 50 FPS:
416: 8.5%
420: 26.1%

And Vertical scrolling regressed too, but not as significantly.

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

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

** Summary changed:

- arale dash horizontal swipe dip
+ Arale dash scrolling performance regression between 416 and 420

** Changed in: canonical-devices-system-image
Milestone: None => 14

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

Title:
  Arale dash scrolling performance regression between 416 and 420

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

Bug description:
  dip between 416 ~60fps and 420 ~50fps

  https://platform-qa-dashboard.canonical.com/dashboard/db/arale-dash

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

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


[Touch-packages] [Bug 1606927] Re: Qt 5.6.1 causes some powerpc tests to fail

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+16.10.20160830.2-0ubuntu1

---
ubuntu-system-settings-online-accounts (0.7+16.10.20160830.2-0ubuntu1) yakkety; 
urgency=medium

  [ Alberto Mardegan ]
  * debian/rules:
- Don't run tests on powerpc (LP: #1606927)

  [ Gary.Wzl ]
  * add a new property "userAgent" for OAuth item. (LP: #1587282)

  [ Timo Jyrinki ]
  * Add qttools5-dev-tools build dependency (LP: #1608814)

 -- Alberto Mardegan   Tue, 30 Aug 2016
08:37:06 +

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Qt 5.6.1 causes some powerpc tests to fail

Status in biometryd package in Ubuntu:
  Fix Released
Status in maliit-framework package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-api package in Ubuntu:
  Fix Released

Bug description:
  An example: ubuntu-system-settings:

  https://launchpadlibrarian.net/275303704/buildlog_ubuntu-yakkety-
  powerpc.ubuntu-system-
  settings_0.4+16.10.20160727.2-0ubuntu1_BUILDING.txt.gz

  Stacktraces:
  http://pastebin.ubuntu.com/21137254/
  http://pastebin.ubuntu.com/21137968/
  http://pastebin.ubuntu.com/21138111/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libqt5qml5 5.6.1-4ubuntu1~4
  ProcVersionSignature: Ubuntu 3.13.0-79.123-powerpc64-smp 3.13.11-ckt33
  Uname: Linux 3.13.0-79-powerpc64-smp ppc
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: powerpc
  Date: Wed Jul 27 13:27:50 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: qtdeclarative-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627743] Re: arale dash horizontal swipe dip

2016-09-26 Thread Daniel van Vugt
** Tags added: performance regression

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

Title:
  Arale dash scrolling performance regression between 416 and 420

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

Bug description:
  dip between 416 ~60fps and 420 ~50fps

  https://platform-qa-dashboard.canonical.com/dashboard/db/arale-dash

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

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


[Touch-packages] [Bug 1608814] Re: qdoc moved to qttools5-dev-tools

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+16.10.20160830.2-0ubuntu1

---
ubuntu-system-settings-online-accounts (0.7+16.10.20160830.2-0ubuntu1) yakkety; 
urgency=medium

  [ Alberto Mardegan ]
  * debian/rules:
- Don't run tests on powerpc (LP: #1606927)

  [ Gary.Wzl ]
  * add a new property "userAgent" for OAuth item. (LP: #1587282)

  [ Timo Jyrinki ]
  * Add qttools5-dev-tools build dependency (LP: #1608814)

 -- Alberto Mardegan   Tue, 30 Aug 2016
08:37:06 +

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  qdoc moved to qttools5-dev-tools

Status in online-accounts-api package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  qdoc was moved from qtbase to qttools in Qt 5.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/online-accounts-api/+bug/1608814/+subscriptions

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


[Touch-packages] [Bug 1606489] Re: Right clicking on the webbrowser-app location bar, the popup is blurry (e.g. Select All, Paste)

2016-09-26 Thread Daniel van Vugt
My text also looks quite blurry. But we're talking about an offset of
less than one pixel so it might not be immediately obvious to everyone.
If it's not the same bug then the text rendering needs improving because
no other text on the screen looks this bad. But it feels like the same
amount of blur I'm seeing in the icons and text below them.

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

Title:
  Right clicking on the webbrowser-app location bar, the popup is blurry
  (e.g. Select All, Paste)

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

Bug description:
  Right clicking on the location bar, the popup is blurry (e.g. Select
  All, Paste). It looks like the pop-up is not pixel-aligned.

  The rest of the app, including right clicking on a web page is clear
  and has no such problem.

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

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


[Touch-packages] [Bug 1335494] Re: No value for 'fnlibgomp' in /usr/share/info/dir

2016-09-26 Thread Bug Watch Updater
** Changed in: gcc-4.9-doc (Debian)
   Status: New => Fix Released

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

Title:
  No value for 'fnlibgomp' in /usr/share/info/dir

Status in gcc-4.8 package in Ubuntu:
  New
Status in gcc-4.9 package in Ubuntu:
  New
Status in gcc-4.9-doc package in Debian:
  Fix Released

Bug description:
  Incorrect entries are added to /usr/share/info/dir for libgomp,
  libitm, and libquadmath. This makes it impossible to read the
  documentation in the info viewer and Emacs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gcc-4.8-doc 4.8.2-19ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 28 23:02:54 2014
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: gcc-4.8
  UpgradeStatus: Upgraded to trusty on 2014-04-05 (84 days ago)

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

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


[Touch-packages] [Bug 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication

2016-09-26 Thread Aron Xu
@all, I'm amending this SRU to only .p12 files for which is confirmed
working to allow the fix land in -updates, and opened Bug #1627903 for
follow-ups of other types key files.

** Summary changed:

- [SRU]Can't select secret key for TLS auth for 802.1X authentication
+ [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication

** Tags removed: verification-failed
** Tags added: verification-done verification-done-xenial

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

Title:
  [SRU]Can't select p12 secret key for TLS auth for 802.1X
  authentication

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Users cannot select TLS certificate when connecting to a network that
  requires TLS type 802.1X authentication

  [Test case]
  STR:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wired connection
  4. Go to 802.1x tab
  5. Check the Use 802.1X checkbox
  6. Choose TLS
  7. Click on Secret key button
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  For wifi connection:
  1. Click on Connections icon in status panel
  2. Click on Edit connections
  3. Select Wi-Fi connection
  4. Go to Wi-Fi Security tab
  5. Select WPA & WPA2 Enterprise in the drop-down list
  6. Choose TLS
  7. Click on (None) next to Private key
  8. In file chooser navigate to the folder where key is located and try to 
select key file - the list is empty

  [Regression Potential]
  The fix is quite straight forward and the possibility of causing regression 
is limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1575614/+subscriptions

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


[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-09-26 Thread Aron Xu
@Brian, I believe the patch should fix mentioned bug, feedbacks
shouldn't be the same issue, perhaps another one not addressed yet or
kernel issue.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

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


[Touch-packages] [Bug 1627901] [NEW] /lib/systemd/systemd-journald:6:server_read_dev_kmsg:source_dispatch:sd_event_dispatch:sd_event_run:main

2016-09-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding systemd.  This problem was most recently seen with version
229-4ubuntu8, the problem page at
https://errors.ubuntu.com/problem/b36dbf417b25f2ad6c8f3e648c98a253db6f4f65
contains more details.

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


** Tags: vivid wily 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/1627901

Title:
  /lib/systemd/systemd-
  
journald:6:server_read_dev_kmsg:source_dispatch:sd_event_dispatch:sd_event_run:main

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding systemd.  This problem was most recently seen with version
  229-4ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/b36dbf417b25f2ad6c8f3e648c98a253db6f4f65
  contains more details.

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

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


[Touch-packages] [Bug 1614542] Re: [MIR] ubuntu-keyboard

2016-09-26 Thread Steve Langasek
Override component to main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety: universe/libs -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety amd64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety arm64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety armhf: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety i386: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety powerpc: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety ppc64el: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-keyboard-extensions0.1 0.100+16.10.20160818-0ubuntu1 in 
yakkety s390x: universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntu-keyboard 0.100+16.10.20160818-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntu-keyboard-arabic 0.100+16.10.20160818-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntu-keyboard-autopilot 0.100+16.10.20160818-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntu-keyboard-azerbaijani 0.100+16.10.20160818-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
ubuntu-keyboard-bosnian 0.100+16.10.20160818-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
ubuntu-keyboard-catalan 0.100+16.10.20160818-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
ubuntu-keyboard-catalan 0.100+16.10.20160818-0ubuntu1 in 

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

2016-09-26 Thread Dongdong88
** Summary changed:

- /bin/kill in ubuntu16.04 has bug in killing process group
+ hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

-- 
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:
  hadoop crash: /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 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 1612240] Re: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package zmqpp - 4.1.2-0ubuntu1

---
zmqpp (4.1.2-0ubuntu1) yakkety; urgency=medium

  * New upstream release
  * debian/copyright:
- Follow up on the license change to MPLv2
  * debian/watch:
- Point to the new upstream location
  * debian/patches/support_use_fd_option.diff:
- Support for ZMQ_USE_FD (LP: #1612240)
  * debian/patches/fix_ftbfs_new_boost.diff:
- Fix FTBFS on yakkety due to boost1.61
  * debian/control:
- Bump the libzmq3-dev dependency for the new required features in zeromq
- Add the libsodium-dev build-dep for the test libs
- Rename package to libzmqpp4 as the ABI changed and the soname was bumped
- Bump the standards version to 3.9.7
  * debian/rules:
- Remove the unneeded statically linked library archive
  * Drop debian/patches/mkdir_before_install.diff
  * Drop debian/patches/fix_1256886.diff

 -- Łukasz 'sil2100' Zemczak   Thu, 11 Aug
2016 17:15:27 +0200

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

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

Title:
  [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

Status in zeromq3 package in Ubuntu:
  Confirmed
Status in zmqpp package in Ubuntu:
  Fix Released

Bug description:
  Please update zmqpp to version 4.1.2 with the following patch that I proposed 
upstream (it got merged into their "develop" branch):
  https://github.com/zeromq/zmqpp/pull/167/files

  (alternatively, use master + my patch or develop branch of zmqpp).

  This will require the current git snapshot of the zmq library (which
  will be version 4.2 when it's released) -
  https://github.com/zeromq/libzmq

  All the above is needed to support the new USE_FD socket option, which
  will probably be critical for scopes as snaps.

  == Feature Freeze Exception details ==

  These packages are required by the ongoing work of the unity scopes
  for snappy. Due to unrelated to zeromq issues (unity-scopes-api unit-
  test issues on arm64, possibly due to recent toolchain changes) we did
  not make it in time before Feature Freeze. The packages have been
  prepared and tested in:

  https://launchpad.net/~ci-train-ppa-
  
service/+archive/ubuntu/landing-005/+packages?field.name_filter=_filter=published_filter=yakkety

  There is no ABI breakage in zeromq3 so no reverse-depends rebuilds are
  required. The zmqpp package does break ABI so a so bump and rebuild of
  rev-deps was needed, but the currently only consumer of the zmqpp
  packages is unity-scopes-api. The new release of zeromq3 is based on a
  git snapshot as a new stable release of this project is planned in the
  nearest future, so a bit too late for the current plans. Some reverse-
  depends of zeromq3 have been tested to work fine with the new package
  as is.

  We kindly request a FFe for this very particular case.

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

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


[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Barry Kolts
Brian,
This weekend we had updates for libssl and a libssl regression. Both required a 
reboot and no second reboot. In other words worked as expected. 

Perhaps the bug only occurs for kernel updates. I have had this happen a few 
times in the past. So the next time it happens I will not run autoremove 
manually, to see what happens.
What files and logs can I provide at that time that will help?

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

Title:
  After rebooting for updates, reboot is still required.

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Yesterday unattended-upgrades required a reboot for kernel updates as
  expected. But today unattended-upgrades required a reboot even though
  there were no updates.

  2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 
  2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 
  2016-09-20 05:20:10,411 INFO Starting unattended upgrades script
  2016-09-20 05:20:10,411 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic 
linux-headers-generic linux-image-generic linux-libc-dev
  2016-09-20 05:21:13,119 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  2016-09-20 05:24:17,405 INFO All upgrades installed
  2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting
  2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 
  2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 
  2016-09-21 05:10:54,089 INFO Starting unattended upgrades script
  2016-09-21 05:10:54,089 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-21 05:11:02,624 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting

  On this machine (16.04 server) unattended-upgrades is configured to
  reboot automatically.

  This also happened on another 16.04 server with default unattended-
  upgrades configuration. It displayed the ***System restart
  required*** message. The same on a 14.04 server and a 14.04
  desktop.

  Expected behaviour: Not to do an unnecessary reboot.

  Let me know what other information I can provide.

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

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


[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread Tyler Hicks
Thanks, I gave it a shot (after putting the profile into complain mode)
and here are the unique denials that I see when starting the guest
session:

operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1295/fd/2" pid=1295 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=998 ouid=998
operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1297/fd/2" pid=1297 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=998 ouid=998
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1446 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="file_perm" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1293 
comm="upstart" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive" denied_mask="send" addr="@/com/ubuntu/upstart-session/998/1293" 
peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1709 
comm="unity-panel-ser" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"

and when logging out of the guest session:

operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2042 
comm="dbus-send" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="file_perm" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1293 
comm="upstart" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive" denied_mask="send" addr="@/com/ubuntu/upstart-session/998/1293" 
peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2046 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1709 
comm="unity-panel-ser" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread Tyler Hicks
Marking the apparmor task as invalid since the changes will likely need
to be made to the profile shipped by lightdm.

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

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Alexandre Cavaco
Sure Brian, here it is.

I think my case was exactly the same, as I also did a 'apt-get
autoremove'.

But, the strange think is that the reboot file vanished and the system
is no longer asking me for reboots (probably since yesterday), but I
didn't do anything specific to try to solve the problem.

** Attachment added: "My /var/log/apt/history.log"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4749048/+files/history.log

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

Title:
  After rebooting for updates, reboot is still required.

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Yesterday unattended-upgrades required a reboot for kernel updates as
  expected. But today unattended-upgrades required a reboot even though
  there were no updates.

  2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 
  2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 
  2016-09-20 05:20:10,411 INFO Starting unattended upgrades script
  2016-09-20 05:20:10,411 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic 
linux-headers-generic linux-image-generic linux-libc-dev
  2016-09-20 05:21:13,119 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  2016-09-20 05:24:17,405 INFO All upgrades installed
  2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting
  2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 
  2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 
  2016-09-21 05:10:54,089 INFO Starting unattended upgrades script
  2016-09-21 05:10:54,089 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-21 05:11:02,624 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting

  On this machine (16.04 server) unattended-upgrades is configured to
  reboot automatically.

  This also happened on another 16.04 server with default unattended-
  upgrades configuration. It displayed the ***System restart
  required*** message. The same on a 14.04 server and a 14.04
  desktop.

  Expected behaviour: Not to do an unnecessary reboot.

  Let me know what other information I can provide.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-09-26 Thread fksdlöfioenvdfsdji
evendough people talk about not adding more comments to this thread.

i had the problem, then they/you/here they said solution is upgrade to
16.04

- i solved the problem manually und than upgraded to 16.04

- now some months later i wanted to update && upgrade my server and boot
is full again. - and i had to solve it manually again.

so for my experience > fix didn't work.

what i did is:
- nothing
- just have the unatended auto updater install security updates. (configured as 
in 14.04) super default basic.


i now loocket in to the "50unattended-upgrades" file and


// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
// Unattended-Upgrade::Remove-Unused-Dependencies "false";

is commented..
Would i need to change that? or is that the unrelated one?

-- 
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 1627869] [NEW] package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libkmod2/chan

2016-09-26 Thread Francisco Carlos Meneses Bezerra da Silva
Public bug reported:

 ok

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libkmod2 22-1ubuntu4 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Sep 26 18:50:29 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libkmod2/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libkmod2:i386
InstallationDate: Installed on 2016-09-26 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: kmod
Title: package libkmod2 22-1ubuntu4 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libkmod2/changelog.Debian.gz' partilhado, que é 
diferente de outras instâncias do pacote libkmod2:i386
UpgradeStatus: Upgraded to xenial on 2016-09-26 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libkmod2 22-1ubuntu4 [modified:
  usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade:
  a tentar sobreescrever '/usr/share/doc/libkmod2/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libkmod2:i386

Status in kmod package in Ubuntu:
  New

Bug description:
   ok

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libkmod2 22-1ubuntu4 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 26 18:50:29 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libkmod2/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libkmod2:i386
  InstallationDate: Installed on 2016-09-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kmod
  Title: package libkmod2 22-1ubuntu4 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libkmod2/changelog.Debian.gz' partilhado, que é 
diferente de outras instâncias do pacote libkmod2:i386
  UpgradeStatus: Upgraded to xenial on 2016-09-26 (0 days ago)

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

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


[Touch-packages] [Bug 1616448] Re: [MIR] qtsensors-opensource-src

2016-09-26 Thread Steve Langasek
Override component to main
qtsensors-opensource-src 5.6.1-2build1 in yakkety: universe/libs -> main
libqt5sensors5 5.6.1-2build1 in yakkety amd64: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety arm64: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety armhf: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety i386: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety powerpc: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety ppc64el: universe/libs/optional/100% -> 
main
libqt5sensors5 5.6.1-2build1 in yakkety s390x: universe/libs/optional/100% -> 
main
libqt5sensors5-dev 5.6.1-2build1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libqt5sensors5-dev 5.6.1-2build1 in yakkety s390x: 
universe/libdevel/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety amd64: 
universe/libs/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety arm64: 
universe/libs/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety armhf: 
universe/libs/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety i386: universe/libs/optional/100% 
-> main
qml-module-qtsensors 5.6.1-2build1 in yakkety powerpc: 
universe/libs/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
qml-module-qtsensors 5.6.1-2build1 in yakkety s390x: 
universe/libs/optional/100% -> main
qtsensors5-dbg 5.6.1-2build1 in yakkety amd64: universe/debug/extra/100% -> main
qtsensors5-dbg 5.6.1-2build1 in yakkety arm64: universe/debug/extra/100% -> main
qtsensors5-dbg 5.6.1-2build1 in yakkety armhf: universe/debug/extra/100% -> main
qtsensors5-dbg 5.6.1-2build1 in yakkety i386: universe/debug/extra/100% -> main
qtsensors5-dbg 5.6.1-2build1 in yakkety powerpc: universe/debug/extra/100% -> 
main
qtsensors5-dbg 5.6.1-2build1 in yakkety ppc64el: universe/debug/extra/100% -> 
main
qtsensors5-dbg 5.6.1-2build1 in yakkety s390x: universe/debug/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety amd64: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety arm64: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety armhf: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety i386: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety powerpc: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety ppc64el: universe/doc/extra/100% -> main
qtsensors5-doc 5.6.1-2build1 in yakkety s390x: universe/doc/extra/100% -> main
qtsensors5-doc-html 5.6.1-2build1 in yakkety amd64: universe/doc/extra/100% -> 
main
qtsensors5-doc-html 5.6.1-2build1 in yakkety arm64: universe/doc/extra/100% -> 
main
qtsensors5-doc-html 5.6.1-2build1 in yakkety armhf: universe/doc/extra/100% -> 
main
qtsensors5-doc-html 5.6.1-2build1 in yakkety i386: universe/doc/extra/100% -> 
main
qtsensors5-doc-html 5.6.1-2build1 in yakkety powerpc: universe/doc/extra/100% 
-> main
qtsensors5-doc-html 5.6.1-2build1 in yakkety ppc64el: universe/doc/extra/100% 
-> main
qtsensors5-doc-html 5.6.1-2build1 in yakkety s390x: universe/doc/extra/100% -> 
main
qtsensors5-examples 5.6.1-2build1 in yakkety amd64: universe/x11/optional/100% 
-> main
qtsensors5-examples 5.6.1-2build1 in yakkety arm64: universe/x11/optional/100% 
-> main
qtsensors5-examples 5.6.1-2build1 in yakkety armhf: universe/x11/optional/100% 
-> main
qtsensors5-examples 5.6.1-2build1 in yakkety i386: universe/x11/optional/100% 
-> main
qtsensors5-examples 5.6.1-2build1 in yakkety powerpc: 
universe/x11/optional/100% -> main
qtsensors5-examples 5.6.1-2build1 in yakkety ppc64el: 
universe/x11/optional/100% -> main
qtsensors5-examples 5.6.1-2build1 in yakkety s390x: universe/x11/optional/100% 
-> main
50 publications overridden.

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

Title:
  [MIR] qtsensors-opensource-src

Status in qtsensors-opensource-src package in Ubuntu:
  Fix Committed

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

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

  Security: No known security 

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

2016-09-26 Thread Brian Murray
Could somebody on the desktop team please follow up with this bug?

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

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


[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

2016-09-26 Thread Erik Brinkman
Attached are two logs with Luke's modified package. I attached two
because I couldn't replicate the bug with the modified logging package.
Instead of immediately crashing and disconnecting after a pair, instead,
the pair would succeed, but audio would not play when set to "High
Fidelity Playback (A2DP Sink)" mode. Figuring that this may be an issue
with the initial pair, I restarted and ran it again creating a second
log. Pulse still didn't crash. This time I tried changing the mode to
"Headset Head Unit (HSP/HFP)". In this mode, the test sound would play,
but it would only come through as static. Attempts to change back to
A2DP resulted in the device being removed and readded in HSP/HFP mode.

Despite not reproducing the bug with the logging package, I was still
able to replicate the bug with the stock package, and fix it with
Joakim's package.

** Attachment added: "pulseverbose.tar.bz2"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+attachment/4749027/+files/pulseverbose.tar.bz2

-- 
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 1492252] Re: Allow direct linking to a Preview via uri

2016-09-26 Thread Brian Douglass
Hi guys! I was just wondering if this issue was on a feature roadmap or
anything. It would be really useful for uApp Explorer.

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

Title:
  Allow direct linking to a Preview via uri

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  I can already link to a scopes search via the scope:// protocol but it
  would be great to be able to link directly to a preview page via a
  scope:// uri. This would be especially helpful for uApp Explorer to
  link directly to an app in the official store (rather than the search
  page like it does now).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1492252/+subscriptions

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


[Touch-packages] [Bug 1626345] Re: After rebooting for updates, reboot is still required.

2016-09-26 Thread Brian Murray
@Alexandre - Could you add your /var/log/apt/history.log entries from
before the reboot-required.pkgs file was created?

In Barry's case I believe the reboot-required was created because of
running 'apt autoremove' which removed older kernels and triggered a run
of update-initramfs.

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

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

Title:
  After rebooting for updates, reboot is still required.

Status in One Hundred Papercuts:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Yesterday unattended-upgrades required a reboot for kernel updates as
  expected. But today unattended-upgrades required a reboot even though
  there were no updates.

  2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 
  2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 
  2016-09-20 05:20:10,411 INFO Starting unattended upgrades script
  2016-09-20 05:20:10,411 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic 
linux-headers-generic linux-image-generic linux-libc-dev
  2016-09-20 05:21:13,119 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
  2016-09-20 05:24:17,405 INFO All upgrades installed
  2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting
  2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 
  2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 
  2016-09-21 05:10:54,089 INFO Starting unattended upgrades script
  2016-09-21 05:10:54,089 INFO Allowed origins are: 
['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
  2016-09-21 05:11:02,624 INFO No packages found that can be upgraded 
unattended and no pending auto-removals
  2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting

  On this machine (16.04 server) unattended-upgrades is configured to
  reboot automatically.

  This also happened on another 16.04 server with default unattended-
  upgrades configuration. It displayed the ***System restart
  required*** message. The same on a 14.04 server and a 14.04
  desktop.

  Expected behaviour: Not to do an unnecessary reboot.

  Let me know what other information I can provide.

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

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


[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager

2016-09-26 Thread Steve Langasek
Override component to main
ubuntu-download-manager 1.3+16.10.20160909.1-0ubuntu1 in yakkety: universe/net 
-> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/libdevel/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/doc/optional/100% -> main
libubuntu-download-manager-client-doc 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/doc/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libs/optional/100% -> main
libubuntu-download-manager-client1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/libs/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/libdevel/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libs/optional/100% -> main
libubuntu-download-manager-common1 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/libs/optional/100% -> main
libubuntu-upload-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libdevel/optional/100% -> main
libubuntu-upload-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libdevel/optional/100% -> main
libubuntu-upload-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libdevel/optional/100% -> main
libubuntu-upload-manager-common-dev 1.3+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libdevel/optional/100% -> main
libubuntu-upload-manager-common-dev 

[Touch-packages] [Bug 1597453] Re: [MIR] content-hub

2016-09-26 Thread Steve Langasek
Override component to main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety: universe/libs -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
content-hub 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
content-hub-testability 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libcontent-hub-dev 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/doc/optional/100% -> main
libcontent-hub-doc 0.2+16.10.20160914-0ubuntu1 in yakkety s390x: 
universe/doc/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libcontent-hub0 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-content1 0.2+16.10.20160914-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
38 publications overridden.


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

Title:
  [MIR] content-hub

Status in Canonical System Image:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

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

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * ubuntu-download-manager (bug #1488425)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This 

[Touch-packages] [Bug 1627608] Re: resize2fs crashed with SIGSEGV in ext2fs_extent_translate()

2016-09-26 Thread Theodore Ts'o
Known problem, fixed in e2fsprogs 1.42.2 or 1.42.3 in commit:

commit 3d6fc974831a360aee460e54c442538445f3017c
Author: Theodore Ts'o 
Date:   Wed Aug 10 15:49:35 2016 -0400

resize2fs: fix crash when there is an ea block and no blocks to migrate

This fixes a bug introduced in 1.43 by commit fb47b94fffc: "resize2fs:
rewrite extent/dir/ea block checksums when migrating".  If there is an
extended attribute block and there are no blocks that need to migrate,
we will crash.

The bug was caused by a botched De Morgan's transformation.

Signed-off-by: Theodore Ts'o 


Note that e2fsprogs 1.43.3-1 is in Debian unstable, and the only reason why 
it's blocked from entering testing for the last three weeks is because of the 
glibc 2.24 transition.

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

Title:
  resize2fs crashed with SIGSEGV in ext2fs_extent_translate()

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  I was trying to install yakkety from a bootable USB with latest the
  image, but when trying to resize partition an error window appeared.
  All the information about it is here>

  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1627603

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: e2fsprogs 1.43.1-1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  Date: Mon Sep 26 06:41:43 2016
  ExecutablePath: /sbin/resize2fs
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  ProcCmdline: resize2fs /dev/sda5 139789789K
  SegvAnalysis:
   Segfault happened at: 0x5635641f751c:cmpq   $0x0,0x20(%rdi)
   PC (0x5635641f751c) ok
   source "$0x0" ok
   destination "0x20(%rdi)" (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: e2fsprogs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5635641f6080, argc=3, argv=0x7ffef0c06668, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffef0c06658) at ../csu/libc-start.c:291
   ?? ()
  Title: resize2fs crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1594013] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-09-26 Thread Brian Murray
Happened when running a Live CD, which is something you can't update a
kernel on.

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

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

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

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  This happened when I am installing Ubuntu mate 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 18 18:12:10 2016
  DuplicateSignature:
   Setting up initramfs-tools (0.122ubuntu8) ...
   update-initramfs: deferring update (trigger activated)
   cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file 
or directory
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1578762] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-09-26 Thread Brian Murray
*** This bug is a duplicate of bug 1594013 ***
https://bugs.launchpad.net/bugs/1594013

** This bug has been marked a duplicate of bug 1594013
   package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  but i know no further about initramfs, i'm sure it pertains to ram
  drive creation, well..best guess anyhow

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   iucode-tool: Install
   intel-microcode: Install
   iucode-tool: Configure
   intel-microcode: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May  5 18:13:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1595640] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-09-26 Thread Brian Murray
*** This bug is a duplicate of bug 1594013 ***
https://bugs.launchpad.net/bugs/1594013

** This bug is no longer a duplicate of bug 1578762
   package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1594013
   package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  as

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   iucode-tool: Install
   intel-microcode: Install
   iucode-tool: Configure
   intel-microcode: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun 23 17:34:11 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1609898] Update Released

2016-09-26 Thread Martin Pitt
The verification of the Stable Release Update for isc-dhcp 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1609898

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

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

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

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


[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-26 Thread Richard Laager
The fix was merged upstream here:
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

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

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

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

Bug description:
  [Impact]

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

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

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

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

  [Test Case]

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

  [Regression Potential]

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

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.3

---
isc-dhcp (4.3.3-5ubuntu12.3) xenial; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * debian/isc-dhcp-client.install: install new files for initramfs-tools
to their proper locations; from debian/initramfs-tools. (LP: #1621507)

 -- LaMont Jones   Fri, 23 Sep 2016 15:09:46 -0600

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

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

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.7

---
isc-dhcp (4.2.4-7ubuntu12.7) trusty; urgency=medium

  * Don't assume IPv6 prefix length of 64 (LP: #1609898).
Pulled from debian commit c347ab8a43587164486ce1f104eedfd638594e59.

 -- Dan Streetman   Thu, 04 Aug 2016
13:07:23 -0400

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

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

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

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


[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.1.ESV-R4-0ubuntu5.11

---
isc-dhcp (4.1.ESV-R4-0ubuntu5.11) precise; urgency=medium

  * Don't assume IPv6 prefix length of 64 (LP: #1609898).
Pulled from debian commit c347ab8a43587164486ce1f104eedfd638594e59.

 -- Dan Streetman   Thu, 04 Aug 2016
13:07:23 -0400

** Changed in: isc-dhcp (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

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

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

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


[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

2016-09-26 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.3

---
isc-dhcp (4.3.3-5ubuntu12.3) xenial; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * debian/isc-dhcp-client.install: install new files for initramfs-tools
to their proper locations; from debian/initramfs-tools. (LP: #1621507)

 -- LaMont Jones   Fri, 23 Sep 2016 15:09:46 -0600

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in klibc package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  New
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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


[Touch-packages] [Bug 1627845] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()

2016-09-26 Thread Apport retracing service
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1545811, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748977/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748979/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748981/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748982/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748983/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748984/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1627845/+attachment/4748985/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1545811

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus suddenly crashed without any further interaction.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ibus 1.5.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7
  Uname: Linux 4.8.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Sep 26 22:31:02 2016
  ExecutablePath: /usr/bin/ibus-daemon
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim --address 
unix:tmpdir=/tmp/ibus
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo

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

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


[Touch-packages] [Bug 1512378] Re: On first boot the setup wizard reporting page is not consistent with the default diagnostics setting in ubuntu-system-settings.

2016-09-26 Thread Lukáš Tinkl
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

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

Title:
  On first boot the setup wizard reporting page is not consistent with
  the default diagnostics setting in ubuntu-system-settings.

Status in Canonical System Image:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Device: arale
  Image: version 152 from ubuntu-touch/rc-proposed/meizu.en

  Steps:

  1) Using a freshly flashed device, run through the settings wizard. Note that 
the reporting page is not shown.
  2) Complete the edges demo.
  3) Open System Settings -> Security & Privacy.
  4) Note that default diagnostics setting is 'sent'.
  5) Without changing any settings close ubuntu-system-settings.
  6) Now enable the wizard again: adb shell rm 
/home/phablet/.config/ubuntu-system-settings/wizard-has-run
  7) Reboot device.
  8) Run through the settings wizard again.
  9) This time note that the reporting page is shown.

  Expected result:

  On first boot the reporting page of the settings wizard should be
  consistent with the default value of the reporting setting in ubuntu-
  system-settings.

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

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


[Touch-packages] [Bug 1597439] Re: [MIR] zeromq3

2016-09-26 Thread Steve Langasek
Override component to main
zeromq3 4.1.5-2 in yakkety: universe/libs -> main
libzmq3-dev 4.1.5-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety armhf: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety i386: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety powerpc: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety ppc64el: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety s390x: universe/libdevel/optional/100% -> main
libzmq5 4.1.5-2 in yakkety amd64: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety arm64: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety armhf: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety i386: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety powerpc: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety ppc64el: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety s390x: universe/libs/optional/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety amd64: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety arm64: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety armhf: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety i386: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety powerpc: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety ppc64el: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety s390x: universe/debug/extra/100% -> main
22 publications overridden.


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

Title:
  [MIR] zeromq3

Status in zeromq3 package in Ubuntu:
  Fix Released

Bug description:
  Trying to get unity8 in main this cycle, that's one of the depends of
  unity-scopes-api (MIR to come)

  * availability
  it's available/built on all the ubuntu architectures, 
https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

  * security
  the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
  http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

  * quality
  - the package is well maintained in Debian
  - it works out of the box with no configuration required
  - it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
   
  * dependencies
  requires libsodium which is universe

  * standards compliance
  FHS and Debian Policy compliant.

  * ubuntu maintainance
  the desktop team is going to look after it, desktop-bugs has been subscribed

  * background
  no specific info

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

-- 
Mailing list: https://launchpad.net/~touch-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

2016-09-26 Thread Johnny Klonaris
I've been seeing the same problem - numerous services being shutdown,
including cron, ssh and even a script I have running on the console to
recover.   The syslog shows that various systemd "targets" being
shutdown, including:  Default, Basic System, Timers, Paths, Sockets...

This has correlated to running a script on our system (that has been
running for many years on many systems) that finds and sends a kill
signal to a ser2net connection before opening a remote console.

This has been a nightmare on our Ubuntu 16 systems since upgrading from
14, and nearly a daily occurrence on one of 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 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 1611680] Re: Scrolling on www.ceskenoviny.cz is very slow

2016-09-26 Thread Olivier Tilloy
Another interesting observation with http://www.ceskenoviny.cz/zpravy
/francouzska-justice-obvinila-16letou-divku-z-planovani-teroru/1379685:
as soon as I scroll on this page (by dragging a finger on a phone or
using the mouse scroll wheel on desktop), the contents of the title
element change, so we get a huge number of titleChanged events (which in
turn may trigger a history db update). I have verified that the same
happens in chromium, so it’s not an oxide/webbrowser-app bug, more
likely a website bug. Still, we should try and handle this gracefully.

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

Title:
  Scrolling on  www.ceskenoviny.cz is very slow

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  the Czech news site I am reading quite often was recently updated to a new 
design and as of this update scrolling on the site gets quite tricky. On some 
articles scrolling is almost impossible.

  Now this is not the first site I find difficult to scroll on with an
  Ubuntu's web browser unfortunately, though it is usually the case of
  some heavy javascript ballast on the site I am sure.

  The worst experience I am getting so far is on this article:
  http://www.ceskenoviny.cz/zpravy/francouzska-justice-obvinila-16letou-
  divku-z-planovani-teroru/1379685 where scrolling is very laggy and
  more or less only gets me either to the absolute top or the absolute
  bottom of the article, not anywhere in the middle. Slow scrolling
  won't help the issue.

  Other articles like this one http://www.ceskenoviny.cz/zpravy/ceske-
  drahy-dostaly-pokutu-150-000-kc-za-chybejici-ceniky/1380181 feels only
  very laggy but not that bad from my experience.

  I've been testing this on my Meizu MX4 with rc-proposed. Maybe this is
  only the device issue though I doubt it.

  Is there something you can do about it?
  Thank you very much.

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

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


[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-26 Thread Ihar Hrachyshka
Right, we need the dhcp_release6 tool in xenial dnsmasq package.

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

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

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

  Checking it's present first would fix this problem.

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

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

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

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


[Touch-packages] [Bug 1627641] Re: Backport netplan to xenial

2016-09-26 Thread Martin Pitt
** Changed in: systemd (Ubuntu Xenial)
   Importance: High => Wishlist

** Changed in: systemd (Ubuntu Xenial)
   Importance: Wishlist => Low

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

Title:
  Backport netplan to xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  In Progress

Bug description:
  For snappy (at first at least) we need to provide netplan in xenial,
  as for the first snappy GA release we must not use any PPAs any more.

  netplan's NetworkManager backend depends on two patches to read
  configuration and connections from /run/NetworkManager/. These will
  need to be backported for full netplan support; but they are not
  required for snappy as this will use a snapped NM. However, this will
  need a temporary hack
  (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607)
  until snaps can actually properly support OS components like
  NetworkManager.

  PATCHES:
  
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85
  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb

  REGRESSION POTENTIAL:
  netplan: The risk for existing installations is practically zero as nplan 
does not exist in xenial yet and thus will not be pulled in during upgrades.
  NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as 
it's an ephemeral tmpfs there is no risk of existing files there. If the 
patches are broken it could in theory happen that NetworkManager also does not 
properly read files from /etc/NetworkManager/ any more, so the -proposed 
package must verify that existing connections still work.
  systemd: This does change behavior of networkd on restart, but the previous 
behaviour was arguably buggy. networkd is not being used by default or 
advertised in Ubuntu 16.04, so this will not affect the vast majority of 
installations.

  TEST PLAN:
  1. Run "NetworkManager --print-config" and save the output.
  2. Install the proposed NetworkManager and confirm that existing connections 
(from /etc/NetworkManager/system-connections) still work.
  3. Run "NetworkManager --print-config" again and verify that the output is 
the same as in step 1.
  4. netplan has a very comprehensive integration test suite run as 
autopkgtest, which covers NetworkManager (including the /run patches) and 
network. Confirm that it succeeds.

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

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


[Touch-packages] [Bug 1367551] Re: [MIR] capnproto

2016-09-26 Thread Steve Langasek
Override component to main
capnproto 0.5.3-2ubuntu1 in yakkety: universe/misc -> main
capnproto 0.5.3-2ubuntu1 in yakkety amd64: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety arm64: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety armhf: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety i386: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety powerpc: universe/devel/optional/100% -> 
main
capnproto 0.5.3-2ubuntu1 in yakkety ppc64el: universe/devel/optional/100% -> 
main
capnproto 0.5.3-2ubuntu1 in yakkety s390x: universe/devel/optional/100% -> main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety amd64: universe/libs/optional/100% -> 
main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety arm64: universe/libs/optional/100% -> 
main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety armhf: universe/libs/optional/100% -> 
main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety i386: universe/libs/optional/100% -> 
main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety powerpc: universe/libs/optional/100% 
-> main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety ppc64el: universe/libs/optional/100% 
-> main
libcapnp-0.5.3 0.5.3-2ubuntu1 in yakkety s390x: universe/libs/optional/100% -> 
main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety amd64: universe/libdevel/optional/100% 
-> main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety arm64: universe/libdevel/optional/100% 
-> main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety armhf: universe/libdevel/optional/100% 
-> main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety i386: universe/libdevel/optional/100% -> 
main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety powerpc: universe/libdevel/optional/100% 
-> main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety ppc64el: universe/libdevel/optional/100% 
-> main
libcapnp-dev 0.5.3-2ubuntu1 in yakkety s390x: universe/libdevel/optional/100% 
-> main
22 publications overridden.


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

Title:
  [MIR] capnproto

Status in capnproto package in Ubuntu:
  Fix Released

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

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

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

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

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


[Touch-packages] [Bug 1620496] Re: Calendar widget gets confused with DST changes

2016-09-26 Thread Lukáš Tinkl
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  Calendar widget gets confused with DST changes

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Fix Released

Bug description:
  I can see two October 30ths on my phone, see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qml-module-ubuntu-settings-components 0.9+15.04.20160818.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Sep  6 09:24:34 2016
  InstallationDate: Installed on 2016-09-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160903-020304)
  SourcePackage: ubuntu-settings-components
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1623768] Re: Adapt to new Totem icon name

2016-09-26 Thread Jeremy Bicha
This bug was fixed in the package moka-icon-theme - 5.3.2-2
Sponsored for fossfreedom (fossfreedom)

---
moka-icon-theme (5.3.2-2) unstable; urgency=medium

  * cherry-pick upstream patches
- fix GTK+3.22 and GTK+3.20 based apps not displaying correctly due
  to upstream changing their .desktop exec=icon names
- fix ubuntu-software, ImageMagik and Guake icon display
  * Packaging Changes:
- update maintainer email address

 -- David Mohammed   Sun, 25 Sep 2016 10:48:43
+0100

** Also affects: moka-icon-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: moka-icon-theme (Ubuntu)
   Status: New => Fix Released

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

Title:
  Adapt to new Totem icon name

Status in humanity-icon-theme package in Ubuntu:
  New
Status in lubuntu-artwork package in Ubuntu:
  Fix Committed
Status in moka-icon-theme package in Ubuntu:
  Fix Released
Status in ubuntukylin-theme package in Ubuntu:
  New
Status in xubuntu-artwork package in Ubuntu:
  Fix Committed

Bug description:
  Totem has changed its icon name for easier integration with flatpak

  -Icon=totem
  +Icon=org.gnome.Totem

  If your icon theme will be used in Ubuntu 16.04 LTS also, then I
  recommend making a symlink from the totem icon to the new
  org.gnome.Totem icon. Alternatively, you could drop the icon and let
  users use the high resolution icons shipped by Totem itself.

  See also bug 1618138 which lists some other app icon name changes but
  those icons aren't shipped in all themes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+subscriptions

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


[Touch-packages] [Bug 1627608] Re: resize2fs crashed with SIGSEGV in ext2fs_extent_translate()

2016-09-26 Thread Brian Murray
** Tags added: rls-y-incoming

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

Title:
  resize2fs crashed with SIGSEGV in ext2fs_extent_translate()

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  I was trying to install yakkety from a bootable USB with latest the
  image, but when trying to resize partition an error window appeared.
  All the information about it is here>

  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1627603

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: e2fsprogs 1.43.1-1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  Date: Mon Sep 26 06:41:43 2016
  ExecutablePath: /sbin/resize2fs
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  ProcCmdline: resize2fs /dev/sda5 139789789K
  SegvAnalysis:
   Segfault happened at: 0x5635641f751c:cmpq   $0x0,0x20(%rdi)
   PC (0x5635641f751c) ok
   source "$0x0" ok
   destination "0x20(%rdi)" (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: e2fsprogs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5635641f6080, argc=3, argv=0x7ffef0c06668, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffef0c06658) at ../csu/libc-start.c:291
   ?? ()
  Title: resize2fs crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1612460] Re: [MIR] unity-scopes-shell

2016-09-26 Thread Steve Langasek
Override component to main
unity-scopes-shell 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety: universe/libs -> 
main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety i386: 
universe/libdevel/optional/100% -> main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libscope-harness-dev 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety i386: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libscope-harness3 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety amd64: 
universe/libs/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety arm64: 
universe/libs/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety armhf: 
universe/libs/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety i386: 
universe/libs/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety powerpc: 
universe/libs/optional/100% -> main
python3-scope-harness 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety ppc64el: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety amd64: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety arm64: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety armhf: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety i386: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety powerpc: 
universe/libs/optional/100% -> main
unity-plugin-scopes 0.5.7+16.10.20160624.2-0ubuntu2 in yakkety ppc64el: 
universe/libs/optional/100% -> main
25 publications overridden.


** Changed in: unity-scopes-shell (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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1612460

Title:
  [MIR] unity-scopes-shell

Status in unity-scopes-shell package in Ubuntu:
  Fix Released

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-shell/+bug/1612460/+subscriptions

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


[Touch-packages] [Bug 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop

2016-09-26 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/brightnessControl

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

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

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

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

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

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


[Touch-packages] [Bug 1516696] Re: SMS notifications are received only when the phone is unlocked

2016-09-26 Thread Launchpad Bug Tracker
** Branch linked: lp:~tiagosh/telephony-service/request-wake-lock

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

Title:
  SMS notifications are received only when the phone is unlocked

Status in Canonical System Image:
  Confirmed
Status in powerd:
  New
Status in Unity System Compositor:
  New
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  WHAT HAPPENED:
  The phone stays quiet while locked but once the power button is pressed 
(unlocked), SMS notification are received with vibration, notification bubble 
and sound alert. The message received shows that it was actually received 10 
minutes ago.
  This happened multiple times already but I think I ignored them and this 
seems to have started after OTA-7 was released.

  
  EXPECTED:
  The phone should have the vibration, notification bubble/indicator and sound 
alert even if the phone is locked.

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

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


[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-26 Thread Brian Haley
Christian - I believe we added dnsmasq in order to see about getting
v2.76 into LTS (xenial) since having a better dhcpv6 stateful offering
would be a good thing.  It's currently only in Y.

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

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

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

  Checking it's present first would fix this problem.

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

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

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

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


[Touch-packages] [Bug 1627831] [NEW] [Precision WorkStation T5400, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] No sound at all

2016-09-26 Thread Aisha
Public bug reported:

After I replaced my previous Nvidia graphics card with Nvidia GeForce
Titan X gpu, I do not hear any sound for audio files i.e. I hear no
sound at all. I dont see any output devices in Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aisha  2408 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Mon Sep 26 15:28:57 2016
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aisha  2408 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Precision WorkStation T5400, Nvidia GPU 70 HDMI/DP, Digital Out, HDMI] 
No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0RW203
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/21/2008:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T5400
dmi.sys.vendor: Dell Inc.

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

Title:
  [Precision WorkStation T5400, Nvidia GPU 70 HDMI/DP, Digital Out,
  HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After I replaced my previous Nvidia graphics card with Nvidia GeForce
  Titan X gpu, I do not hear any sound for audio files i.e. I hear no
  sound at all. I dont see any output devices in Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aisha  2408 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Mon Sep 26 15:28:57 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aisha  2408 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Precision WorkStation T5400, Nvidia GPU 70 HDMI/DP, Digital Out, 
HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0RW203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/21/2008:svnDellInc.:pnPrecisionWorkStationT5400:pvr:rvnDellInc.:rn0RW203:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T5400
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1613640] Re: [MIR] ubuntu-settings-components

2016-09-26 Thread Steve Langasek
Override component to main
ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety: 
universe/misc -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
amd64: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
arm64: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
armhf: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
i386: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
powerpc: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
ppc64el: universe/misc/optional/100% -> main
qml-module-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in yakkety 
s390x: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety amd64: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety arm64: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety armhf: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety i386: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety powerpc: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety ppc64el: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components 0.9+16.10.20160909-0ubuntu1 in 
yakkety s390x: universe/misc/optional/100% -> main
15 publications overridden.


** Changed in: ubuntu-settings-components (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 ubuntu-settings-components
in Ubuntu.
https://bugs.launchpad.net/bugs/1613640

Title:
  [MIR] ubuntu-settings-components

Status in ubuntu-settings-components package in Ubuntu:
  Fix Released

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
   Potential to skip:
   * biometryd [https://trello.com/c/oP4UmB9t]

  [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/ubuntu-settings-components/+bug/1613640/+subscriptions

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


[Touch-packages] [Bug 1612259] Re: [MIR] libusermetrics

2016-09-26 Thread Steve Langasek
Override component to main
libusermetrics 1.1.1+16.10.20160909-0ubuntu1 in yakkety: universe/libs -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/doc/optional/100% -> main
libusermetrics-doc 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/doc/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libusermetrics-tools 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libusermetricsinput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libusermetricsinput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libusermetricsoutput1 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libusermetricsoutput1-dev 1.1.1+16.10.20160909-0ubuntu1 in yakkety s390x: 
universe/libdevel/optional/100% -> main
qtdeclarative5-usermetrics0.1 1.1.1+16.10.20160909-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
qtdeclarative5-usermetrics0.1 1.1.1+16.10.20160909-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
qtdeclarative5-usermetrics0.1 1.1.1+16.10.20160909-0ubuntu1 in yakkety armhf: 

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

2016-09-26 Thread Steve Langasek
Override component to main
unity-notifications 0.1.3+16.10.20160819-0ubuntu1 in yakkety: universe/libs -> 
main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety amd64: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety arm64: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety armhf: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety i386: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety powerpc: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety ppc64el: universe/libs/optional/100% -> main
qtdeclarative5-unity-notifications-plugin 0.1.3+16.10.20160819-0ubuntu1 in 
yakkety s390x: universe/libs/optional/100% -> main
8 publications overridden.


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

Title:
  [MIR] unity-notifications

Status in unity-notifications package in Ubuntu:
  Fix Released

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 1588994] Re: Location not working since OTA-11 on BQ 4.5

2016-09-26 Thread Saif Ahmed
On my bq e4.5 it had not been working since OTA-12. but after OTA-13 it
worked briefly (for 3 days).  Sensor status app indicates "back-end
found" and "Active", but not able to deliver any location data.  Nearby
scope says please enable location services.  Location  detection is on.
some diagnostic tests would be nice.

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

Title:
  Location not working since OTA-11 on BQ 4.5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Since installing OTA-11 Google maps reports 'Google maps could not
  determine your precise location' and Here maps says 'Can't find your
  location'.

  Location detection is ON.

  'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
  Location settings.

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

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


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

2016-09-26 Thread Steve Langasek
Override component to main
qdjango 0.6.2-2 in yakkety: universe/libs -> main
libqdjango-db0 0.6.2-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libqdjango-db0 0.6.2-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libqdjango-db0 0.6.2-2 in yakkety armhf: universe/libdevel/optional/100% -> main
libqdjango-db0 0.6.2-2 in yakkety i386: universe/libdevel/optional/100% -> main
libqdjango-db0 0.6.2-2 in yakkety powerpc: universe/libdevel/optional/100% -> 
main
libqdjango-db0 0.6.2-2 in yakkety ppc64el: universe/libdevel/optional/100% -> 
main
libqdjango-db0 0.6.2-2 in yakkety s390x: universe/libdevel/optional/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety amd64: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety arm64: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety armhf: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety i386: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety powerpc: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety ppc64el: universe/debug/extra/100% -> main
libqdjango-dbg 0.6.2-2 in yakkety s390x: universe/debug/extra/100% -> main
libqdjango-dev 0.6.2-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety armhf: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety i386: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety powerpc: universe/libdevel/optional/100% -> 
main
libqdjango-dev 0.6.2-2 in yakkety ppc64el: universe/libdevel/optional/100% -> 
main
libqdjango-dev 0.6.2-2 in yakkety s390x: universe/libdevel/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety amd64: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety arm64: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety armhf: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety i386: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety powerpc: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety ppc64el: universe/doc/optional/100% -> main
libqdjango-doc 0.6.2-2 in yakkety s390x: universe/doc/optional/100% -> main
libqdjango-http0 0.6.2-2 in yakkety amd64: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety arm64: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety armhf: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety i386: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety powerpc: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety ppc64el: universe/libdevel/optional/100% -> 
main
libqdjango-http0 0.6.2-2 in yakkety s390x: universe/libdevel/optional/100% -> 
main
36 publications overridden.


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

Title:
  [MIR] qdjango

Status in qdjango package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 infographics

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

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   All dependencies are already in main

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

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

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-26 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-26 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

2016-09-26 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

** Tags added: verification-needed-vivid

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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


[Touch-packages] [Bug 1612363] Re: [MIR] qmenumodel

2016-09-26 Thread Steve Langasek
Override component to main
qmenumodel 0.2.9+16.04.20160329-0ubuntu1 in yakkety: universe/libs -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libqmenumodel-dev 0.2.9+16.04.20160329-0ubuntu1 in yakkety s390x: 
universe/libdevel/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libqmenumodel0 0.2.9+16.04.20160329-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
qmenumodel-qml 0.2.9+16.04.20160329-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
22 publications overridden.


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

Title:
  [MIR] qmenumodel

Status in qmenumodel package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * Unknown

  [Quality assurance]
   * This package has no tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This package uses cmake.

  [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/qmenumodel/+bug/1612363/+subscriptions

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


[Touch-packages] [Bug 1552860] Re: [MIR] qtsystems-opensource-src

2016-09-26 Thread Steve Langasek
Override component to main
qtsystems-opensource-src 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety: 
universe/libs -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety amd64: 
universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety arm64: 
universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety armhf: 
universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety i386: 
universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
powerpc: universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
ppc64el: universe/libs/optional/100% -> main
libqt5publishsubscribe5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety s390x: 
universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety amd64: 
universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety arm64: 
universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety armhf: 
universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety i386: 
universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
powerpc: universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
ppc64el: universe/libs/optional/100% -> main
libqt5serviceframework5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety s390x: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety amd64: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety arm64: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety armhf: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety i386: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety powerpc: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libqt5systeminfo5 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety s390x: 
universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
amd64: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
arm64: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
armhf: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
i386: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
powerpc: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
ppc64el: universe/libs/optional/100% -> main
qml-module-qtpublishsubscribe 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
s390x: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
amd64: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
arm64: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
armhf: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
i386: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
powerpc: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
ppc64el: universe/libs/optional/100% -> main
qml-module-qtserviceframework 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
s390x: universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety amd64: 
universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety arm64: 
universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety armhf: 
universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety i386: 
universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
powerpc: universe/libs/optional/100% -> main
qml-module-qtsysteminfo 5.0~git20141206~44f70d99-0ubuntu10~13 in yakkety 
ppc64el: universe/libs/optional/100% -> main

[Touch-packages] [Bug 945430] Re: Lists lack zebra-striping

2016-09-26 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => Confirmed

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

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

Title:
  Lists lack zebra-striping

Status in GTK+:
  Confirmed
Status in light-themes:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in light-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  We had it before and was taken out in Precise. We need this back. It
  makes apps like Rhythmbox much easier to handle.

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

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


[Touch-packages] [Bug 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-26 Thread Brian Murray
** Tags added: rls-y-incoming

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

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1627528] Re: dont know

2016-09-26 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Please also change the bug title to something more meaningful.

Thanks!

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

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  dont know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 25 23:39:06 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller 
[104d:90b8]
 Subsystem: Sony Corporation GK208M [GeForce GT 740M] [104d:90b8]
  InstallationDate: Installed on 2016-09-21 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation SVF15218SNB
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=781dd7ba-a7da-40a0-a141-af33640e13de ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0220DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF15218SNB:pvrC10HEB4D:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15218SNB
  dmi.product.version: C10HEB4D
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Sep 25 22:40:48 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5547 
   vendor CMO
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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


[Touch-packages] [Bug 1572199] Re: cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

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

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

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

Title:
  cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  cups 2.1.3-3 does not have this problem.  Confirmed on 32 bit virtual
  and real machines.  Problem was reported on VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CasperVersion: 1.368
  CupsErrorLog:
   
  CurrentDesktop: LXDE
  Date: Tue Apr 19 15:12:05 2016
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1572199] Re: cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

2016-09-26 Thread Bryan Quigley
This seems like it's common - https://askubuntu.com/questions/760952
/slow-shutdown-on-ubuntu-16-04-lts-stopping-thermal-daemon-running-fit-
make-remo#763803

Did you have to do anything to make it reproduce in a VM?

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

Title:
  cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  cups 2.1.3-3 does not have this problem.  Confirmed on 32 bit virtual
  and real machines.  Problem was reported on VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CasperVersion: 1.368
  CupsErrorLog:
   
  CurrentDesktop: LXDE
  Date: Tue Apr 19 15:12:05 2016
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1627801] [NEW] /usr/sbin/NetworkManager:11:set_ap_scan_cb:g_simple_async_result_complete:reply_cb:g_simple_async_result_complete:g_dbus_connection_call_done

2016-09-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager.  This problem was most recently seen with
version 1.2.2-0ubuntu1~vivid3, the problem page at
https://errors.ubuntu.com/problem/6304c615f4962c2e584f1c4af9f76ea613721fc9
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/sbin/NetworkManager:11:set_ap_scan_cb:g_simple_async_result_complete:reply_cb:g_simple_async_result_complete:g_dbus_connection_call_done

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.2-0ubuntu1~vivid3, the problem page at
  https://errors.ubuntu.com/problem/6304c615f4962c2e584f1c4af9f76ea613721fc9
  contains more details.

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

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


[Touch-packages] [Bug 1627800] [NEW] Xorg crash

2016-09-26 Thread Emanuel Negromonte
Public bug reported:

The error occurred when playing streams, such as youtube, soundcloud and
others by web browser.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep 26 14:55:07 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 i915-4.6.3-4.4.0, 1, 4.4.0-31-generic, x86_64: installed
 i915-4.6.3-4.4.0, 1, 4.4.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2010]
InstallationDate: Installed on 2016-09-22 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 2571:4101  
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation HuronRiver Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=2465629d-ee53-4759-bbc2-a56450823561 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 1.05_
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: Intel Corp.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr1.05_:bd03/05/2011:svnIntelCorporation:pnHuronRiverPlatform:pvr0.1:rvnIntelCorp.:rnEmeraldLake:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.68-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Sep 25 22:43:46 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id  19 
 vendor INL
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 crash third-party-packages ubuntu xenial

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The error occurred when playing streams, such as youtube, soundcloud
  and others by web browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 26 14:55:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-31-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2010]
  

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

2016-09-26 Thread Pat McGowan
@peter thanks for the follow up, hope you can get a new one or get it
fixed

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

** No longer affects: vegetahd

** No longer affects: powerd (Ubuntu)

** No longer affects: unity-system-compositor (Ubuntu)

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Invalid

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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


[Touch-packages] [Bug 1627797] [NEW] /usr/bin/content-hub-service:11:QDBusContext::message:com::ubuntu::content::detail::Transfer::Charge:action_dismiss:proxy_g_signal_cb:ffi_call_VFP

2016-09-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding content-hub.  This problem was most recently seen with version
0.2+15.04.20160830-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4d4e84105b32318c816b8665d4c352d7de069ea4
contains more details.

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid xenial

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

Title:
  /usr/bin/content-hub-
  
service:11:QDBusContext::message:com::ubuntu::content::detail::Transfer::Charge:action_dismiss:proxy_g_signal_cb:ffi_call_VFP

Status in content-hub package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding content-hub.  This problem was most recently seen with
  version 0.2+15.04.20160830-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/4d4e84105b32318c816b8665d4c352d7de069ea4
  contains more details.

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

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


[Touch-packages] [Bug 1627795] [NEW] /usr/bin/unity8-dash:11:QQmlData::isSignalConnected:QObjectPrivate::isSignalConnected:QMetaObject::activate:QMetaObject::activate:QAbstractItemModel::modelAboutToB

2016-09-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8.  This problem was most recently seen with version
8.14+15.04.20160831.3-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/bin/unity8-dash:11:QQmlData::isSignalConnected:QObjectPrivate::isSignalConnected:QMetaObject::activate:QMetaObject::activate:QAbstractItemModel::modelAboutToBeReset

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
  contains more details.

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

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


[Touch-packages] [Bug 1627799] [NEW] /usr/bin/unity8-dash:7:QBasicAtomicOps:QBasicAtomicInteger:QtPrivate::RefCount::ref:QHash:QForeachContainer

2016-09-26 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8.  This problem was most recently seen with version
8.14+15.04.20160831.3-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/cfb4d968ebc83f6253d0122bc0b169214e42cc0d
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/bin/unity8-dash:7:QBasicAtomicOps:QBasicAtomicInteger:QtPrivate::RefCount::ref:QHash:QForeachContainer

Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/cfb4d968ebc83f6253d0122bc0b169214e42cc0d
  contains more details.

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

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


[Touch-packages] [Bug 1627428] Re: apport generates report of third party packages

2016-09-26 Thread Emily Ratliff
*** This bug is a duplicate of bug 985681 ***
https://bugs.launchpad.net/bugs/985681

** This bug has been marked a duplicate of bug 985681
   Apport suggests I report a bug on a third-party package, then refuses to 
report it and suggests I remove it.

** Information type changed from Private Security to Public

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

Title:
  apport generates report of third party packages

Status in apport package in Ubuntu:
  New

Bug description:
  Atom crashed and I find it weird apport tried to make a report of a
  third party package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 25 00:23:14 2016
  InstallationDate: Installed on 2016-09-19 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1151844] Re: [MIR] google-glog

2016-09-26 Thread Steve Langasek
Thanks, repromoted.

Override component to main
google-glog 0.3.4-2 in yakkety: universe/libs -> main
libgoogle-glog-dev 0.3.4-2 in yakkety amd64: universe/libdevel/optional/100% -> 
main
libgoogle-glog-dev 0.3.4-2 in yakkety arm64: universe/libdevel/optional/100% -> 
main
libgoogle-glog-dev 0.3.4-2 in yakkety armhf: universe/libdevel/optional/100% -> 
main
libgoogle-glog-dev 0.3.4-2 in yakkety i386: universe/libdevel/optional/100% -> 
main
libgoogle-glog-dev 0.3.4-2 in yakkety powerpc: universe/libdevel/optional/100% 
-> main
libgoogle-glog-dev 0.3.4-2 in yakkety ppc64el: universe/libdevel/optional/100% 
-> main
libgoogle-glog-dev 0.3.4-2 in yakkety s390x: universe/libdevel/optional/100% -> 
main
libgoogle-glog-doc 0.3.4-2 in yakkety amd64: universe/doc/optional/100% -> main
libgoogle-glog-doc 0.3.4-2 in yakkety arm64: universe/doc/optional/100% -> main
libgoogle-glog-doc 0.3.4-2 in yakkety armhf: universe/doc/optional/100% -> main
libgoogle-glog-doc 0.3.4-2 in yakkety i386: universe/doc/optional/100% -> main
libgoogle-glog-doc 0.3.4-2 in yakkety powerpc: universe/doc/optional/100% -> 
main
libgoogle-glog-doc 0.3.4-2 in yakkety ppc64el: universe/doc/optional/100% -> 
main
libgoogle-glog-doc 0.3.4-2 in yakkety s390x: universe/doc/optional/100% -> main
libgoogle-glog0v5 0.3.4-2 in yakkety amd64: universe/libs/optional/100% -> main
libgoogle-glog0v5 0.3.4-2 in yakkety arm64: universe/libs/optional/100% -> main
libgoogle-glog0v5 0.3.4-2 in yakkety armhf: universe/libs/optional/100% -> main
libgoogle-glog0v5 0.3.4-2 in yakkety i386: universe/libs/optional/100% -> main
libgoogle-glog0v5 0.3.4-2 in yakkety powerpc: universe/libs/optional/100% -> 
main
libgoogle-glog0v5 0.3.4-2 in yakkety ppc64el: universe/libs/optional/100% -> 
main
libgoogle-glog0v5 0.3.4-2 in yakkety s390x: universe/libs/optional/100% -> main
gflags 2.1.2-3 in yakkety: universe/libs -> main
libgflags-dev 2.1.2-3 in yakkety amd64: universe/libdevel/optional/100% -> main
libgflags-dev 2.1.2-3 in yakkety arm64: universe/libdevel/optional/100% -> main
libgflags-dev 2.1.2-3 in yakkety armhf: universe/libdevel/optional/100% -> main
libgflags-dev 2.1.2-3 in yakkety i386: universe/libdevel/optional/100% -> main
libgflags-dev 2.1.2-3 in yakkety powerpc: universe/libdevel/optional/100% -> 
main
libgflags-dev 2.1.2-3 in yakkety ppc64el: universe/libdevel/optional/100% -> 
main
libgflags-dev 2.1.2-3 in yakkety s390x: universe/libdevel/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety amd64: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety arm64: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety armhf: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety i386: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety powerpc: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety ppc64el: universe/doc/optional/100% -> main
libgflags-doc 2.1.2-3 in yakkety s390x: universe/doc/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety amd64: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety arm64: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety armhf: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety i386: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety powerpc: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety ppc64el: universe/libs/optional/100% -> main
libgflags2v5 2.1.2-3 in yakkety s390x: universe/libs/optional/100% -> main
44 publications overridden.


** Changed in: google-glog (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] google-glog

Status in gflags package in Ubuntu:
  Fix Released
Status in google-glog package in Ubuntu:
  Fix Released

Bug description:
  Rationale
  

  There is currently no C++ compatible logging package in main.

  Canonical projects that require logging should not be resolving the
  requirement.

  The mir project is an an example - and glog seems the most lightweight
  solution to its logging requirements. As a system component, mir
  requires all dependencies to be in main. Other components will have
  the same requirements.

  
  Violations of UbuntuMainInclusionRequirements
  

  There's a dependency on libgflags, but no violations

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

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


[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd

2016-09-26 Thread Scott Moser
** Description changed:

  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]
  
  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.
  
  We'd like to have a way to fully support this in cloud-init.
  
  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out
   * bug 1623570: Azure: cannot start walinux agent (Transaction order is 
cyclic.)
-  * bug 1623868: cloud-final.service does not run due to dependency cycle
+  * bug 1623868: cloud-final.service does not run due to dependency cycle
+  * bug 1627436: [gce] Startup scripts do not run on 1604 images 
  
  SRU INFORMATION
  ===
  FIX for init-system-helpers: 
https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02
  
  REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d
  and service, two very central pieces of packaging infrastructure. Errors
  in it will break installation/upgrades of packages or /etc/network/if-
  up.d/ hooks and the like. This changes the condition when systemd units
  get started without their dependencies, and the condition gets weakened.
  This means that behaviour in a booted system is unchanged, but during
  boot this could change the behaviour of if-up.d/ hooks (although they
  have never been defined well during boot anyway). However, I tested this
  change extensively in cloud images and desktop installations
  (particularly I recreated https://bugs.debian.org/777113 and confirmed
  that this approach also fixes it) and could not find any regression.
  
  TEST CASE (for both packages):
  Run
     lxc launch ubuntu-daily:x --config=user.user-data="$(printf 
"#cloud-config\npackages: [postgresql, samba, postfix]")" x1
  
  This will install all three packages, but "systemctl status
  postgresql@9.5-main" will not be running.
  
  Now prepare a new image with the proposed cloud-init and init-system-
  helpers:
  
     lxc launch ubuntu-daily:x xprep
     lxc exec xprep bash
     # enable -proposed and dist-upgrade, then poweroff
     lxc publish xprep x-proposed
  
  Now run the initial lxc launch again, but against that new x-proposed
  image instead of the standard daily:
  
    lxc launch x-proposed --config=user.user-data="$(printf "#cloud-
  config\npackages: [postgresql, samba, postfix]")" x1
  
  You should now have "systemctl status postgresql@9.5-main" running.
  Directly after rebooting the instance, check that there are no hanging
  jobs (systemctl list-jobs), particularly networking.service, to ensure
  that https://bugs.debian.org/777113 did not come back.
  
  Also test interactively installing a package that ships a service, like
  "apache2", and verify that it starts properly after installation.
  
  Verify that journalctl shows no dependency cycles and that all cloud
  init services and the target are active:
  
  $ systemctl list-units --no-legend --all 'cloud*'
  cloud-config.service loaded active exited Apply the settings specified in 
cloud-config
  cloud-final.service  loaded active exited Execute cloud user/final scripts
  cloud-init-local.service loaded active exited Initial cloud-init job 
(pre-networking)
  cloud-init.service   loaded active exited Initial cloud-init job 
(metadata service crawler)
  cloud-config.target  loaded active active Cloud-config availability
  cloud-init.targetloaded active active Cloud-init target

** Description changed:

  in cloud-init users can install packages via cloud-config:
  #cloud-config
  packages: [apache2]
  
  Due to some intricacies of systemd and service installation that doesn't work 
all that well.
  We fixed the issue for simple services that do not have any dependencies on 
other services, or at least don't check those dependencies well under bug 
1575572.
  
  We'd like to have a way to fully support this in cloud-init.
  
  Related bugs:
   * bug 1575572:  apache2 fails to start if installed via cloud config (on 
Xenial)
   * bug 1611973: postgresql@9.5-main service not started if postgres installed 
via cloud-init
   * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades 
(snapd packaging bug, but this cloud-init fix will workaround it)
   * bug 1620780: dev-sda2.device job running and times out
   * bug 1623570: Azure: cannot start walinux agent (Transaction order is 
cyclic.)
   * bug 1623868: cloud-final.service does not run due to dependency cycle
-  

[Touch-packages] [Bug 1619481] Re: package libnl-3-200 (not installed) failed to install/upgrade: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií balíka l

2016-09-26 Thread Varun Garg
I had same issue, when I removed ubuntu gnome desktop using tasksel. I
solved this by moving these files to a backup location

sudo mv /etc/libnl-3/classid /etc/libnl-3/classid.bak
sudo mv /etc/libnl-3/pktloc /etc/libnl-3/pktloc.bak

then
sudo apt-get -f install

and then restored these files
sudo mv /etc/libnl-3/classid.bak /etc/libnl-3/classid
sudo mv /etc/libnl-3/pktloc.bak /etc/libnl-3/pktloc

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

Title:
  package libnl-3-200 (not installed) failed to install/upgrade: pokus o
  prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od
  iných inštancií balíka libnl-3-200:i386

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  I do not know more.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libnl-3-200 (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Thu Sep  1 22:31:44 2016
  DuplicateSignature: package:libnl-3-200:(not installed):pokus o prepísanie 
zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných inštancií 
balíka libnl-3-200:i386
  ErrorMessage: pokus o prepísanie zdieľaného súboru „/etc/libnl-3/classid“, 
ktorý sa líši od iných inštancií balíka libnl-3-200:i386
  InstallationDate: Installed on 2016-04-16 (137 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libnl3
  Title: package libnl-3-200 (not installed) failed to install/upgrade: pokus o 
prepísanie zdieľaného súboru „/etc/libnl-3/classid“, ktorý sa líši od iných 
inštancií balíka libnl-3-200:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2016-09-26 Thread clel
Thanks for the update. Nice this is probably finally implemented.

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

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

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


[Touch-packages] [Bug 1602628] Re: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right

2016-09-26 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  ubuntu 16.10
  can't drag/move window if it's semi-maximized

  open random app, semi-miaximize left or rigt (CTRL SUPER + Left or
  Right), try to move the window by draggin' it from the title bar.

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

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


[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

2016-09-26 Thread Tyler Hicks
Swapping verification-failed for verification-needed now that bug
1579135 has been fixed for ~1 week.

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

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Committed
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  IMPORTANT: SRU Team, see comment #25 for why this bug is temporarily
  marked verification-failed

  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = SRU apparmor =
  [Impact]
  The upload that adjusts ibus-daemon to start with "--address 
'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be 
sufficient due to the lack of a rule for the new socket path. This upload adds 
such a rule.

  [Test Case]
  1. Start a unity session after updating to the im-config package in -proposed 
but before the apparmor package in -proposed

  2. Use the ibus client program to list the available engines
  $ ibus list-engine
  language: Spanish; Castilian
    xkb:latam::spa - Spanish (Latin American)
    xkb:es::spa - Spanish
  language: Slovak
    xkb:sk:qwerty:slo - Slovak (qwerty)
    xkb:sk::slo - Slovak
  ...

  3. Create an AppArmor profile file, called ibus, with the following
  contents:

  #include 

  profile ibus {
    #include 
    #include 
    #include 

    /usr/bin/ibus mr,

  }

  4. Load the profile
  $ sudo apparmor_parser -qr ibus

  5. Rerun the ibus client program under confinement to see that it fails
  $ aa-exec -p ibus -- ibus list-engine
  Can't connect to IBus.

  6. Note the AppArmor denial in the syslog

  audit: type=1400 audit(1472252079.589:57): apparmor="DENIED"
  operation="connect" profile="ibus" pid=5364 comm="ibus" 

[Touch-packages] [Bug 1611796] Re: Recent searches text overflows boundary in tablet mode

2016-09-26 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Recent searches text overflows boundary in tablet mode

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce

   1) Search for a long text string in the dash on a tablet

   2) Press cancel

   3) Press search button

  Expected result

   Recent search text should either be elided or the box should expand
  to contain it.

  Actual result

   Recent search text overflows the edge of its container (see attached
  screenshot)

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

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


[Touch-packages] [Bug 1615675] Re: performance test creep in wrong direction for dash vertical scroll compile

2016-09-26 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: New => Fix Committed

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

Title:
  performance test creep in wrong direction for dash vertical scroll
  compile

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  After reviewing this morning, there is a slight increase in the trend of 
compile times for dash vertical scrolling metrics.
  https://platform-qa-dashboard.canonical.com/dashboard/db/krillin-dashboard

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

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


[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()

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

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

** Tags added: iso-testing

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

Title:
  scoperunner crashed with SIGSEGV in QObject::disconnect()

Status in Canonical System Image:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Invalid

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1
  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
  Date: Tue Aug 30 17:54:20 2016
  ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner
  InstallationDate: Installed on 2016-08-27 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner  
/usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini
  Scope: Apps
  Signal: 11
  SourcePackage: unity-scope-click
  StacktraceTop:
   QObject::disconnect(QObject const*, char const*, QObject const*, char 
const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   start_thread (arg=0x7fae9eade700) at pthread_create.c:333
  Title: scoperunner crashed with SIGSEGV in QObject::disconnect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread flocculant
Sep 23 21:42:38 wolf-wolf kernel: [   69.411731] audit: type=1400
audit(1474663358.636:31): apparmor="DENIED" operation="connect"
profile="/usr/lib/lightdm/lightdm-guest-session" pid=3713 comm="initctl"
family="unix" sock_type="stream" protocol=0 requested_mask="send receive
accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-
session/999/3321" peer_addr=none peer="unconfined"

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627769] [NEW] limits.conf not applied

2016-09-26 Thread Aurélien Leblond
Public bug reported:

Since upgraded to 16.10 Yakkety, modifications in
/etc/security/limits.conf are not taken into consideration when logging
in the graphical interface.


/etc/security/limits.conf:
@audio   -  rtprio 99
@audio   -  memlockunlimited

I tried the same settings in /etc/security/limits.d/audio.conf, to the
same results.


After logging in Unity, opening a console, the limits are not set:
blablack@ideaon:~$ ulimit -l -r
max locked memory   (kbytes, -l) 64
real-time priority  (-r) 0


Reloging to my user via bash DOES apply the limits:
blablack@ideaon:~$ ulimit -l -r
max locked memory   (kbytes, -l) 64
real-time priority  (-r) 0
blablack@ideaon:~$ su blablack
Password: 
blablack@ideaon:~$ ulimit -l -r
max locked memory   (kbytes, -l) unlimited
real-time priority  (-r) 95


Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.


The exact same setup used to work fine on Xenial 16.04 before upgrade.


If you need any more information, please let me know.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: lightdm 1.19.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.8.0-16-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 26 17:27:10 2016
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages yakkety

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

Title:
  limits.conf not applied

Status in lightdm package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1589149] Re: the two Hotspots buttons seem to disagree

2016-09-26 Thread boehm
i also can confirm that the sequence -> toggle in system settings and
then the toggle in the status menu - works for me too on mx4 arale
ota-13 (date 20160913).

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

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

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

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


[Touch-packages] [Bug 1626435] Re: Keyboard layout not applied on the shell

2016-09-26 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/defaultKeymap

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

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Split out from bug #1611859:

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread Tyler Hicks
Hi - are there any AppArmor denials in the syslog? To check, you can
trigger this bug and then look in /var/log/syslog for lines that contain
'apparmor="DENIED"'.  Thanks!

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

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

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627641] Re: Backport netplan to xenial

2016-09-26 Thread Martin Pitt
** Description changed:

  For snappy (at first at least) we need to provide netplan in xenial, as
  for the first snappy GA release we must not use any PPAs any more.
  
  netplan's NetworkManager backend depends on two patches to read
  configuration and connections from /run/NetworkManager/. These will need
  to be backported for full netplan support; but they are not required for
  snappy as this will use a snapped NM. However, this will need a
  temporary hack
  (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607)
  until snaps can actually properly support OS components like
  NetworkManager.
  
  PATCHES:
  
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85
- 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4d4d305538
+ 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb
  
  REGRESSION POTENTIAL:
  netplan: The risk for existing installations is practically zero as nplan 
does not exist in xenial yet and thus will not be pulled in during upgrades.
  NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as 
it's an ephemeral tmpfs there is no risk of existing files there. If the 
patches are broken it could in theory happen that NetworkManager also does not 
properly read files from /etc/NetworkManager/ any more, so the -proposed 
package must verify that existing connections still work.
  systemd: This does change behavior of networkd on restart, but the previous 
behaviour was arguably buggy. networkd is not being used by default or 
advertised in Ubuntu 16.04, so this will not affect the vast majority of 
installations.
  
  TEST PLAN:
  1. Run "NetworkManager --print-config" and save the output.
  2. Install the proposed NetworkManager and confirm that existing connections 
(from /etc/NetworkManager/system-connections) still work.
  3. Run "NetworkManager --print-config" again and verify that the output is 
the same as in step 1.
  4. netplan has a very comprehensive integration test suite run as 
autopkgtest, which covers NetworkManager (including the /run patches) and 
network. Confirm that it succeeds.

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

Title:
  Backport netplan to xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  In Progress

Bug description:
  For snappy (at first at least) we need to provide netplan in xenial,
  as for the first snappy GA release we must not use any PPAs any more.

  netplan's NetworkManager backend depends on two patches to read
  configuration and connections from /run/NetworkManager/. These will
  need to be backported for full netplan support; but they are not
  required for snappy as this will use a snapped NM. However, this will
  need a temporary hack
  (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607)
  until snaps can actually properly support OS components like
  NetworkManager.

  PATCHES:
  
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85
  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb

  REGRESSION POTENTIAL:
  netplan: The risk for existing installations is practically zero as nplan 
does not exist in xenial yet and thus will not be pulled in during upgrades.
  NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as 
it's an ephemeral tmpfs there is no risk of existing files there. If the 
patches are broken it could in theory happen that NetworkManager also does not 
properly read files from /etc/NetworkManager/ any more, so the -proposed 
package must verify that existing connections still work.
  systemd: This does change behavior of networkd on restart, but the previous 
behaviour was arguably buggy. networkd is not being used by default or 
advertised in Ubuntu 16.04, so this will not affect the vast majority of 
installations.

  TEST PLAN:
  1. Run "NetworkManager --print-config" and save the output.
  2. Install the proposed NetworkManager and confirm that existing connections 
(from /etc/NetworkManager/system-connections) still work.
  3. Run "NetworkManager --print-config" again and verify that the output is 
the same as in step 1.
  4. netplan has a very comprehensive integration test suite run as 
autopkgtest, which covers NetworkManager (including the /run patches) and 
network. Confirm that it succeeds.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread Iain Lane
(The security team will look soon)

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1627304] Re: User locking problems - guest login crashing

2016-09-26 Thread Iain Lane
I think this is an issue with the lightdm(-guest-session) apparmor
profiles.

In dmesg:

laney@yakkety-vm:~$ dmesg | grep DENIED
[  142.273990] audit: type=1400 audit(1474905574.718:125): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/osrelease" pid=2167 comm="pkill" requested_mask="r" 
denied_mask="r" fsuid=998 ouid=0
[  142.274396] audit: type=1400 audit(1474905574.718:126): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274428] audit: type=1400 audit(1474905574.718:127): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/2/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274457] audit: type=1400 audit(1474905574.718:128): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/3/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274484] audit: type=1400 audit(1474905574.718:129): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/4/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274513] audit: type=1400 audit(1474905574.718:130): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/5/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274542] audit: type=1400 audit(1474905574.718:131): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/6/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274569] audit: type=1400 audit(1474905574.718:132): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/7/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274598] audit: type=1400 audit(1474905574.718:133): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/8/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274626] audit: type=1400 audit(1474905574.718:134): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.434462] audit: type=1400 audit(1474905579.878:282): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2843 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.450970] audit: type=1400 audit(1474905579.894:283): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2855 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.494563] audit: type=1400 audit(1474905579.938:284): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2871 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.511922] audit: type=1400 audit(1474905579.954:285): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/osrelease" pid=2879 comm="pkill" requested_mask="r" 
denied_mask="r" fsuid=998 ouid=0
[  147.512279] audit: type=1400 audit(1474905579.958:286): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512303] audit: type=1400 audit(1474905579.958:287): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/2/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512322] audit: type=1400 audit(1474905579.958:288): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/3/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512340] audit: type=1400 audit(1474905579.958:289): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/4/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512356] audit: type=1400 audit(1474905579.958:290): apparmor="DENIED" 
operation="open" 

  1   2   >